Quantcast
Channel: Veeam Support Knowledge Base
Viewing all 4470 articles
Browse latest View live

How to deploy worker instance to Bahrain Region in Veeam Backup for AWS

$
0
0

Challenge

Deploying a worker instance to the Bahrain region is not possible.

Cause

The Me-south-1 region is not present in the list.

Solution

To select the Me-south-1 region, do the following:

1.  Connect to the backup server using the following command.
ssh -i "<backup server's .pem key>" ubuntu@<Public DNS (IPv4) parameter of the backup server>
2.  Navigate to /opt/veeam.aws.service and locate AmazonS3Regions.xml.
3.  Add the following text to the .xml file (see the attached screenshot).
<Region Id="me-south-1" Name="Middle East (Bahrain)" Type="Global">
    <Endpoint Type="S3">s3.me-south-1.amazonaws.com</Endpoint>
    <Endpoint Type="S3">s3.dualstack.me-south-1.amazonaws.com</Endpoint>
    <Endpoint Type="EC2">ec2.me-south-1.amazonaws.com</Endpoint>
    <Endpoint Type="IAM">iam.amazonaws.com</Endpoint>
    <Protocol>HTTP</Protocol>
    <Protocol>HTTPS</Protocol>
    <LocationConstraint>me-south-1</LocationConstraint>
    <SignatureVersion>4</SignatureVersion>
  </Region>
4.  Restart the Veeam Backup for AWS service using the following command.
sudo systemctl restart veeamawsbackup.service

Backup Jobs with Public Folders fail

$
0
0

Challenge

The following error occurs when backing up public folders: "Processing mailbox PublicFolderMailbox@xxxxxxxx.onmicrosoft.com failed with error: Failed to synchronize item changes in folder: FOLDERNAME.. Access is denied. Check credentials and try again., ICS synchronization failed.".
 
Log files may contain the following information:
 
20.12.2012 07:55:14 16 (1448) Processing mailbox:  PublicFolderMailbox@xxxxxxxx.onmicrosoft.com...
20.12.2012 07:55:14 16 (1448) Syncing folder items: FOLDERNAME...
20.12.2012 07:55:14 16 (1448) Exchange Web Services error code: ErrorAccessDenied
20.12.2012 07:55:14 16 (1448) Error: Failed to synchronize item changes in folder: FOLDERNAME.
20.12.2012 07:55:14 16 (1448) Type: Veeam.Ews.Internal.ExServerCodeException


In addition, Veeam Explorer for Exchange may fail to show successfully backed-up public folders.

Cause

Either of the following conditions may cause the error:
  • Public folders are not located under the IPM_SUBTREE folder.
  • The Default user does not have permissions to access public folders.

Solution

The Public Folder is not Located Under IPM_SUBTREE

Veeam Backup for Microsoft Office 365 works with public folders located under the IPM_SUBTREE folder only. Other locations such as, for example, NON_IPM_SUBTREE are not supported.
To check if the public folder is located under the IPM_SUBTREE folder, run the following cmdlet and specify credentials used in Veeam Backup for Microsoft Office 365.
$creds = Get-Credential
$session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $creds -Authentication Basic -AllowRedirection
Import-PSSession $Session
Get-PublicFolder -Identity \ -Recurse | Format-List Name
Remove-PSSession $session


An output similar to the following must be displayed:
 

Name : IPM_SUBTREE
Name : PublicFolderMailbox@*********.onmicrosoft.com
Name : FOLDERNAME
Name : Second Sub Folder
Name : Third Sub Folder

If, according to the output above, a public folder is located under the IPM_SUBTREE folder, no additional actions are needed. Otherwise, if the public folder is located under any other unsupported folder, make sure to move such a public folder to IPM_SUBTREE.

The Default User Does Not Have Sufficient Permissions

Veeam Backup for Microsoft Office 365 uses impersonation to back up public folders. When a public folder is created, it automatically inherits permissions from its parent folder. One of these permissions is assigned to the Default user and grants the Author access rights. In case when an Exchange administrator revokes granted permissions from the Default user, impersonation cannot be performed.

In case you do not want the Default user to have access to public folders and want to use the service account instead, make sure to assign either the Owner or Reviewer permissions to each of the public folders of the service account.

To see the accounts that have access to public folders and the permissions given, run the following cmdlet and specify credentials used in Veeam Backup for Microsoft Office 365.
$creds = Get-Credential
$session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $creds -Authentication Basic -AllowRedirection

Import-PSSession $Session

Get-PublicFolder \ -Recurse | 
    Get-PublicFolderClientPermission | 
    Select-Object Identity,@{Expression={$_.User};Label="User";},@{Expression={$_.AccessRights};Label="AccessRights";} | 
    Export-Csv C:\PublicFolderClientPermission.csv

Remove-PSSession $session

The cmdlet saves information about users and permissions to the C:\PublicFolderClientPermission.csv file.
User-added image

To grant access, you can do either of the following:
  • Assign either the Owner or Reviewer permission to each of the public folders (and sub-folders) of the Default user.
  • Add your service account to public folders with the Owner or Reviewer permissions, and disable impersonation.
To assign permissions, run the following cmdlet and specify credentials used in Veeam Backup for Microsoft Office 365.
$creds = Get-Credential
$session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $creds -Authentication Basic -AllowRedirection

Import-PSSession $Session

$folders = get-publicfolder "\" -recurse

foreach($folder in $folders)
{
Add-PublicFolderClientPermission -Identity $folder.identity -user YourServiceAccount@*******.onmicrosoft.com -AccessRights Reviewer
}

Remove-PSSession $session

NOTE: It is recommended to use PowerShell to assign permissions to public folders.

The following table shows an example of users permissions after the cmdlet is executed.
User-added image

Once the cmdlet is executed, make sure to disable impersonation for the service account. After impersonation is disabled, the service account will have direct access to public folders.

To disable impersonation, do the following:

1.  Open the Veeam Backup for Microsoft Office 365 console and stop active backup jobs (if any).
2.  Open the Services.msc console on a proxy server that is responsible for processing public folders.
To find out which proxy server is used, in the Veeam Backup for Microsoft Office 365 console, right-click a backup job, select Edit and go to the Specify Backup Proxy and Repository step.
3.  In the Services.msc console, stop the Veeam Backup Proxy for Microsoft Office 365 Service.
4.  Create a backup copy of the C:\ProgramData\Veeam\Backup365\Proxy.xml file by copying it to another location.
5.  Open the original Proxy.xml file using any text editor and add the <Source EwsImpersonatePublics="False" /> line between <Veeam><Archiver> tags.
Example:
<Veeam>

    <Archiver>

        <Source EwsImpersonatePublics="False" />

       .....

       .....

     </Archiver>

</Veeam>

6.  Save the Proxy.xml file.
7.  Start the Veeam Backup Proxy for Microsoft Office 365 Service.
8.  Open the Veeam Backup for Microsoft Office 365 console and run backup jobs with public folders.

NOTE: All PowerShell scripts provided above are intended to get and assign needed permissions automatically to ensure that no public folders are missed. 
Please be aware that the commands and parameters may be altered by Microsoft in the future, which may cause thees scripts to function incorrectly. 
There is no support provided for these scripts, and should they fail, we ask that you please contact Microsoft support. 

These scripts may be updated in the future to reflect changes to the Office 365 PowerShell Environment.

More Information

Do not hesitate to contact Veeam support if the error remains.

Exploring VBO365 backups: Understanding Different Restore Scopes

$
0
0

Challenge

You can explore backups in three different scopes: Backup JobOrganizationAll organizations. Consider the following organizations added to the Veeam Backup for Microsoft Office 365 backup infrastructure; each of these organizations uses its own backup repository to store data:
  • Organization A that has one active backup job (Backup Job 2), and a backup job that has been deleted at some point (Backup Job 1).
  • Organization B that has two active backup jobs — Backup Job 3 and Backup Job 4.

Each of these jobs has several restore points in total (deletion of a backup job does not delete the corresponding restore points from the database).

Solution

Exploring Backups: Job Scope

To explore backups created by the selected backup job, right-click a backup job and select any Explore option.This method finds the specified restore point and loads it into the Veeam Explorer scope.
Consider, however, that such a method cannot be used for deleted backup jobs since they are not present in the console; use PowerShell or REST API to load restore points of deleted backup jobs instead.
User-added image

Exploring Backups: Organization Scope

To explore backups created by all backup jobs of the selected organization, right-click an organization and select any Explore option.

When exploring backups of any of the organizations, Veeam Backup for Microsoft Office 365 works as follows:

  • Scans all backup repositories in the backup infrastructure and finds all restore points that have been created by both existing and deleted backup jobs.
  • Finds restore points that were created on the specified date or on the closest earlier date.
  • Merges found restore points into a single one according to the following:
    • If there are two or more copies of the same item in several restore points, then only one copy will be loaded into the Veeam Explorer scope.
    • If there are two different versions of the same item, then only the latest one will be loaded into the Veeam Explorer scope.
    • Otherwise, all unique versions of all items will be loaded into the Veeam Explorer scope.

Note: The same method is used during Veeam Cloud Connect (BAAS) restores.

Exploring Backups: All Organizations Scope

To explore backups created for each of the organizations ever added to the backup infrastructure, right-click the root Organizations node and select any Explore option.

This method works in the same way as the previous one, except for it applies to each of the organizations added to the application scope.

Backup Jobs with Public Folders fail

$
0
0

Challenge

The following error occurs when backing up public folders: "Processing mailbox PublicFolderMailbox@xxxxxxxx.onmicrosoft.com failed with error: Failed to synchronize item changes in folder: FOLDERNAME.. Access is denied. Check credentials and try again., ICS synchronization failed.".
 
Log files may contain the following information:
 
20.12.2012 07:55:14 16 (1448) Processing mailbox:  PublicFolderMailbox@xxxxxxxx.onmicrosoft.com...
20.12.2012 07:55:14 16 (1448) Syncing folder items: FOLDERNAME...
20.12.2012 07:55:14 16 (1448) Exchange Web Services error code: ErrorAccessDenied
20.12.2012 07:55:14 16 (1448) Error: Failed to synchronize item changes in folder: FOLDERNAME.
20.12.2012 07:55:14 16 (1448) Type: Veeam.Ews.Internal.ExServerCodeException


In addition, Veeam Explorer for Exchange may fail to show successfully backed-up public folders.

Cause

Either of the following conditions may cause the error:
  • Public folders are not located under the IPM_SUBTREE folder.
  • The Default user does not have permissions to access public folders.

Solution

The Public Folder is not Located Under IPM_SUBTREE

Veeam Backup for Microsoft Office 365 works with public folders located under the IPM_SUBTREE folder only. Other locations such as, for example, NON_IPM_SUBTREE are not supported.
To check if the public folder is located under the IPM_SUBTREE folder, run the following cmdlet and specify credentials used in Veeam Backup for Microsoft Office 365.
$creds = Get-Credential
$session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $creds -Authentication Basic -AllowRedirection
Import-PSSession $Session
Get-PublicFolder -Identity \ -Recurse | Format-List Name
Remove-PSSession $session


An output similar to the following must be displayed:
 

Name : IPM_SUBTREE
Name : PublicFolderMailbox@*********.onmicrosoft.com
Name : FOLDERNAME
Name : Second Sub Folder
Name : Third Sub Folder

If, according to the output above, a public folder is located under the IPM_SUBTREE folder, no additional actions are needed. Otherwise, if the public folder is located under any other unsupported folder, make sure to move such a public folder to IPM_SUBTREE.

The Default User Does Not Have Sufficient Permissions

Veeam Backup for Microsoft Office 365 uses impersonation to back up public folders. When a public folder is created, it automatically inherits permissions from its parent folder. One of these permissions is assigned to the Default user and grants the Author access rights. In case when an Exchange administrator revokes granted permissions from the Default user, impersonation cannot be performed.

In case you do not want the Default user to have access to public folders and want to use the service account instead, make sure to assign either the Owner or Reviewer permissions to each of the public folders of the service account.

To see the accounts that have access to public folders and the permissions given, run the following cmdlet and specify credentials used in Veeam Backup for Microsoft Office 365.
$creds = Get-Credential
$session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $creds -Authentication Basic -AllowRedirection

Import-PSSession $Session

Get-PublicFolder \ -Recurse | 
    Get-PublicFolderClientPermission | 
    Select-Object Identity,@{Expression={$_.User};Label="User";},@{Expression={$_.AccessRights};Label="AccessRights";} | 
    Export-Csv C:\PublicFolderClientPermission.csv

Remove-PSSession $session

The cmdlet saves information about users and permissions to the C:\PublicFolderClientPermission.csv file.
User-added image

To grant access, you can do either of the following:
  • Assign either the Owner or Reviewer permission to each of the public folders (and sub-folders) of the Default user.
  • Add your service account to public folders with the Owner or Reviewer permissions, and disable impersonation.
To assign permissions, run the following cmdlet and specify credentials used in Veeam Backup for Microsoft Office 365.
$creds = Get-Credential
$session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $creds -Authentication Basic -AllowRedirection

Import-PSSession $Session

$folders = get-publicfolder "\" -recurse

foreach($folder in $folders)
{
Add-PublicFolderClientPermission -Identity $folder.identity -user YourServiceAccount@*******.onmicrosoft.com -AccessRights Reviewer
}

Remove-PSSession $session

NOTE: It is recommended to use PowerShell to assign permissions to public folders.

The following table shows an example of users permissions after the cmdlet is executed.
User-added image

Once the cmdlet is executed, make sure to disable impersonation for the service account. After impersonation is disabled, the service account will have direct access to public folders.

To disable impersonation, do the following:

1.  Open the Veeam Backup for Microsoft Office 365 console and stop active backup jobs (if any).
2.  Open the Services.msc console on a proxy server that is responsible for processing public folders.
To find out which proxy server is used, in the Veeam Backup for Microsoft Office 365 console, right-click a backup job, select Edit and go to the Specify Backup Proxy and Repository step.
3.  In the Services.msc console, stop the Veeam Backup Proxy for Microsoft Office 365 Service.
4.  Create a backup copy of the C:\ProgramData\Veeam\Backup365\Proxy.xml file by copying it to another location.
5.  Open the original Proxy.xml file using any text editor and add the <Source EwsImpersonatePublics="False" /> line between <Veeam><Archiver> tags.
Example:
<Veeam>

    <Archiver>

        <Source EwsImpersonatePublics="False" />

       .....

       .....

     </Archiver>

</Veeam>

6.  Save the Proxy.xml file.
7.  Start the Veeam Backup Proxy for Microsoft Office 365 Service.
8.  Open the Veeam Backup for Microsoft Office 365 console and run backup jobs with public folders.

NOTE: All PowerShell scripts provided above are intended to get and assign needed permissions automatically to ensure that no public folders are missed. 
Please be aware that the commands and parameters may be altered by Microsoft in the future, which may cause thees scripts to function incorrectly. 
There is no support provided for these scripts, and should they fail, we ask that you please contact Microsoft support. 

These scripts may be updated in the future to reflect changes to the Office 365 PowerShell Environment.

More Information

Do not hesitate to contact Veeam support if the error remains.

Build numbers and version of Veeam Agent for Windows | Veeam Agent for Linux

$
0
0

Challenge

This KB article provides a list of all versions and respective build numbers for the following products:

  • Veeam Agent for Windows
  • Veeam Agent for Linux
  • Veeam Endpoint Backup

Solution

Veeam Agent for Windows

VersionBuild NumberRelease DateRelease Notes
Veeam Agent for Windows 3.0.23.0.2.11702019, July 16Download pdf file
Veeam Agent for Windows 3.0.13.0.1.10392019, March 26Download pdf file
Veeam Agent for Windows 3.0 3.0.0.7482019, January 22Download pdf file
Veeam Agent for Windows 2.22.2.0.5892018, July 3Download pdf file
Veeam Agent for Windows 2.12.1.0.4232017, December 19Download pdf file
Veeam Agent for Windows 2.0 2.0.0.7002017, May 11Download pdf file
 

Veeam Agent for Linux

VersionBuild NumberRelease DateRelease Notes
Veeam Agent for Linux 3.0.2 GA3.0.2.11852019, July 16Download pdf file
Veeam Agent for Linux 3.0.13.0.1.10462019, March 26Download pdf file
Veeam Agent for Linux 3.03.0.0.8652019, January 22Download pdf file
Veeam Agent for Linux 2.0.12.0.1.6652018, July 3Download pdf file
Veeam Agent for Linux 2.02.0.0.4002017, December 19 Download pdf file
Veeam Agent for Linux 1.01.0.1.3642017, May 22Download pdf file
Veeam Agent for Linux 1.01.0.0.9442016, December 13Download pdf file
 

Veeam Endpoint Backup

VersionBuild NumberRelease DateRelease Notes
Veeam Endpoint Backup 1.51.5.0.306    2016, March 17    Download pdf file
Veeam Endpoint Backup 1.11.1.1.2122015, October 5Download pdf file
Veeam Endpoint Backup 1.0     1.0.0.1954    2015, April 14Download pdf file

How to Change the settings related to Veeam Backup & Replication Log Files

$
0
0

Challenge

This article documents how to change the defaults for the following settings:

1. The absolute log file directory from which all logs will be stored.
2. Maximum size each log is allowed to reach before beginning a new log file.
3. Number of archived logs to be kept before removal.
4. The total size for a job’s logs to reach before Veeam will begin archiving (gzip) inactive logs to save space.
5. Amount of logs that are archived per job.

 
Note: After making changes to these setting the Veeam server must be restarted to apply changes and ensure that previous log files are unlocked.

Solution

The following registry keys are used to manage log file location, file size and count:

Note: All registry values are to be set within the key HKLM\SOFTWARE\Veeam\Veeam Backup and Replication on the server where the Veeam Backup & Replication console is installed.

* These values may need to be created if they are not present in the registry.  If the settings you currently have are default, then you will need to add these values as they will not inherently already exist.

 
──────────────────────────────────────────────────────────
*1. Default log directory location:

Type: String
Name: LogDirectory

Data: <Path>
 
Example:
User-added image


 
──────────────────────────────────────────────────────────
2. Maximum file size. New files are created when a file reaches the set max size.
Example: Svc.VeeamBackup.log -> Svc.VeeamBackup_1.log


Type: DWORD
Name: MaxLogSize
Data: <value in KiB>
Default: 10240 (binary)
 
──────────────────────────────────────────────────────────
3. Maximum log count. Number of log generations to retain.
Example: Svc.VeeamBackup_1.log, Svc.VeeamBackup_2.log, etc.

Type: DWORD

Name: MaxLogCount
Data: <numeric value>
Default: 10
 
──────────────────────────────────────────────────────────
*4. Total size of uncompressed logs, applies per job.
 
Type: DWORD
Name: UncompressedLogsMaxTotalSize
Data: <value in KiB>
Default: 512000
 
──────────────────────────────────────────────────────────
*5. Total amount of archived generations of logs
Example: Svc.VeeamBackup.1.gz  Svc.VeeamBackup.2.gz
 
Type: DWORD
Name: LogsArchivesMaxCount
Data: <numeric value>
Default: 10


──────────────────────────────────────────────────────────
*6. The size of an agent log file
 
Type: DWORD
Name: AgentMaxLogSize
Data: in BYTES


──────────────────────────────────────────────────────────
*7. Amount of the agent rollback files
 
Type: DWORD
Name: AgentMaxLogCount
Data: <numeric value>


──────────────────────────────────────────────────────────

The requested operation could not be completed due to a file system limitation

$
0
0

Challenge

Transform operations of a large file located on Windows Server 2012 and 2012 R2 deduplicated volume are failing with an error:
“Error: Client error The requested operation could not be completed due to a file system limitation Failed to flush file buffers. File: Filename.vbk

Cause

Veeam is not able to write any data to the affected file because of a NTFS limitation.
Manual un-deduplication (Expand-DedupFile) of the this file also fails with the same error.

Solution

Backup repository must be located on a volume formatted with the large FRS using the command “Format <Drive:> /FS:NTFS /L”

Workaround:
1. Disable Windows deduplication
2. Un-dedupe backup files: copy backup files to a temporary folder, delete original backup files and move copied files back to the original location.
3. Disable NTFS compression on backup repository volume.

More Information

For Windows Server 2008(R2) please refer to Microsoft KB for a detailed description of the issue:http://support.microsoft.com/kb/967351

This issue is resolved in Windows Server 2012(R2), however formatting with the large FRS using the command “Format <Drive:> /FS:NTFS /L is still needed.

Important: the command Format <Drive:> /FS:NTFS /L erases all data from the drive.


Additional information regarding suggested configuration of Server 2012 dedupe for backup storage can be found in this article: http://technet.microsoft.com/en-us/library/dn891438.aspx
 
Depending on the total size of the volume to be formatted you may have to set the cluster size during the format process. Please reference this article to determine which cluster size is needed.
 
 
For more information related to this issue please see this forum post:
 
http://forums.veeam.com/veeam-backup-replication-f2/error-related-to-file-system-limitation-t21448.html

Please note: reformating the volume with /L flag usually helps, but you can still get the same error message later, you can still hit limitation and 4096 Bytes Per FileRecord Segment will not be enough

vPower NFS Troubleshooting Mounting Issues

$
0
0

Challenge

During SureBackup, Instant Recovery, or Other-OS FLR operation, you receive the error: 

"Error during the configuration of the host: NFS Error: Unable to Mount filesystem: Unable to connect to NFS server"

The NFS datastore cannot be mounted to the host, so vPower NFS based restores fail.

Cause

There are several possible causes for this:

  • The Veeam vPower NFS Service is not started. (http://www.veeam.com/kb1094)
  • The Veeam server is on a subnet that does not have access to a VMkernel port on the ESXi host.
  • The Veeam server cannot reach the VMkernel port on the ESXi host due to a firewall configuration.
  • Datastores within the environment that appear as (Invalid).
  • An issue within the VMware environment is preventing the NFS datastore from being mounted.

Solution

In order to know which server to troubleshoot, one must know which server is acting as the vPower NFS server for the repository. To find this edit the repository for the backup files to be used in the restore. On the ‘vPower NFS’ tab there is a dropdown box designating which server is being used. The server listed is where the troubleshooting must be performed from.
 
*Note: An isolation step can be to try changing which server is chosen as the vPower NFS server in the Repository settings.
 
If the vPower NFS service is not running on the server designated within the repository settings, please review: http://www.veeam.com/kb1094
 
──────────────────────────────────────────────────────────
The following is a list of common troubleshooting steps
──────────────────────────────────────────────────────────

 

  • Testing for connectivity to and from VMkernel Port

Test from vPower NFS server to VMkernel port:
1.       Within a vSphere Client select the ESX(i) host that the NFS Datastore is being connected to.
2.       Go to the Configuration Tab
3.       Go to the Networking section
4.       Look for a VMkernel port, and note its IP
5.       Ping the VMkernel port from the vPower NFS server

 Test from VMkernel port to vPower NFS server
1.       Connect to the ESX(i) host that the NFS datstore is being connected to via SSH**
2.       Using the vmkping command to test connectivity to the vPower NFS servers

  • Remove “(Invalid)” datastores:

Within a vSphere Client check the Configuration>Storage section of each host for datastores starting with “VeeamBackup_”, specifically ones that show up in italics with (Inactive). Unmount each of these and try the restore or mount procedure again. 

  • Test adding the NFS Datastore manually (http://www.veeam.com/kb1284). For Veeam Backup & Replication 9.5 Update 4 and later please refer to the More Information section for additional settings required for testing.

1.       Within a vSphere Client select the ESX(i) host that the NFS Datastore is being connected to.
2.       Goto the Configuration Tab
3.       Goto the Storage section
4.       Click Add Storage…
5.       Select the radio option for ‘Network File System’
6.       For “Server”, enter either  the IP or Hostname of the vPower NFS Server
7.       For “Folder”, enter “/VeeamBackup_<servername>”  servername is the NetBIOS name of the vPower NFS Server. If your vPower NFS server is added by IP, you need to specify VeeamBackup_XXX.XXX.XXX.XXX
8.       Do not check the box for Mount NFS read only
9.       Enter in to the Datastore name the same as folder without the starting forward slash. i.e. “VeeamBackup_<servername>”
10.   Click next and complete the process.

 

  • Known Issue: “Unable to Mount VPower NFS Specified Key Name or Identifier Already Exists”

Please review: http://www.veeam.com/kb1690

 

  • Known Issue: Another service is locking a port needed by vPower NFS:
    1. Open an Administrator Command Prompt
    2. Run the following commands
         netstat -bona > portlist.txt
        notepad portlist.txt
    3. Search the text file and confirm that the following ports are not locked by another process.

     111
     6161
 

More Information

With new security enhancements in Veeam B&R 9.5 Update 4 it is no longer possible to mount vPower NFS datastore manually to an arbitrary server. To be able to perform this test, add vPowerNFSDisableIPAuth (DWORD) = 1 registry value to the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Veeam\Veeam NFS\ and restart Veeam vPower NFS Service.
Please note that this value disables built-in IP authentication for vPower datastore and is only recommended for testing purposes.

**SSH may be disabled on your ESXi host. Below are directions to enable SSH on host so that you may connect and use the vmkping command as part of the troubleshooting steps above.
Note: Veeam's vPower NFS does not require SSH to be enabled on the host, please remember to disable SSH after testing with vmkping.


1.  To enable SSH from the vSphere Client
2.  Select the host and click the Configuration tab.
3.  Click Security Profile in the Software panel.
4.  In the Services section, click Properties.
5.  Select SSH and click Options.
6.  Change the SSH options.
     a.  To temporarily start or stop the service, click the Start or Stop button.
     b.  To enable SSH permanently, click Start and stop with host. The change takes effect the next time you reboot the host.
7.  Click OK.
 
For issues related to the vPower NFS Service not starting please review: http://www.veeam.com/kb1094

Release notes for Veeam Backup for Microsoft Office 365 version 4b

$
0
0

Challenge

Release Notes for Veeam Backup for Microsoft Office 365 version 4b.

Cause

Please confirm you are running Veeam Backup for Microsoft Office 365 version 2.0 (builds 2.0.0.567, 2.0.0.594 and 2.0.0.814), version 3.0 (builds 3.0.0.422 — 3.0.0.480), version 4.0 (build 4.0.0.1345) or version 4a (build 4.0.0.1553) prior to installing version 4b (build 4.0.0.2516). You can check the product version under Help > About in the Veeam Backup for Microsoft Office 365 console. After upgrading, your build version will change to 4.0.0.2516

Version 4.0.0.2516 delivers compatibility support for Veeam Backup & Replication v10 and its applicable components and includes a set of bug fixes listed below.

What’s New
  • Veeam Backup & Replication v10 along with the corresponding Veeam Explorer for Microsoft Exchange, Veeam Explorer for Microsoft SharePoint compatibility support.
  • Veeam Cloud Connect v10 compatibility support. 
IMPORTANT NOTE:
  • Veeam Backup for Microsoft Office 365 version 4.0.0.2516 is applicable to standalone installations of Veeam Backup for Microsoft Office 365 version 2.0 (builds 2.0.0.567, 2.0.0.594 and 2.0.0.814), version 3.0 (builds 3.0.0.422 — 3.0.0.480), version 4.0 (build 4.0.0.1345) or version 4a (build 4.0.0.1553; see KB3035 for more details) and installations on top of Veeam Backup & Replication v10 and Veeam Cloud Connect v10.
  • Version 4.0.0.2516 is NOT applicable to installations on top of Veeam Backup & Replication 9.5 Update 4, 4a or 4b and Veeam Cloud Connect 9.5 Update 4, 4a or 4b.
  • Upgrading backup repositories from version 3.0 to 4b may take significant time to complete and the upgrade duration highly depends on the amount and type of backup data in a repository. According to the test results, it may take up to 8 hours in the setup with 1 TB of data in a backup repository. Plan for an appropriate maintenance window when your backup repository that is been upgraded is not available for use. Note that upgrading version 2.0 repositories to 4b requires a bigger maintenance window due to many underlying changes to backup repositories. The upgrade process requires an additional 15% of free space of the current 2.0 repository size and may take up to 17 hours per 1 TB of data in a backup repository. 
Resolved Issues

General
  • Retention jobs do not fully purge the outdated service data, which causes product configuration database growth and impacts product upgrade duration. 
SharePoint Online and OneDrive for Business backup and restore 
  • Adding users with empty Display Names to a backup job fails with the “Value cannot be null” error. 
  • Backup of user’s OneDrive fails if the user name has been changed.  
  • Backup job containing excluded SharePoint sites with changed URLs fails with the following warning: “Failed to get site collection: {url}. Access denied. You do not have permission to perform this action or access this resource.” 
Object storage repositories 
  • Backing up public folders to a repository extended with object storage may fail with the following error: “This id is of the wrong type for this conversion operation (mailbox id vs. public folder id).”
  • Adding OpenStack Swift (Stein) S3 Compatible object storage repository with the s3api middleware for S3 REST fails with the “Unable to create folder (name: {0})” error.
  • Backup and retention jobs targeted at repositories extended with Amazon S3 object storage may fail with the “Specified argument was out of the range of valid values. Parameter name: count” error.
  • If an Azure storage container that is in use with an object storage repository has been deleted, the corresponding backup repository is put into the Invalid state and the backup proxy disk usage is at 100%.
  • A repository extended with Azure Blob Storage is still available for use (i.e. it’s not put to an Invalid state) when Azure storage account credentials become invalid. 
  • After changing retention period for a repository extended with object storage, backup jobs targeted to this repository stop processing.

Solution

To install Veeam Backup for Microsoft Office 365 version 4b: 
  1. Download the ZIP archive: VeeamBackupOffice365_4.0.0.2516.zip.
  2. Run the Veeam.Backup365_4.0.0.2516.msi from the downloaded ZIP archive and follow the wizard steps to install Veeam Backup for Microsoft Office 365.
  3. Run the VeeamExplorerForExchange_10.0.0.443.msi from the downloaded ZIP archive and follow the wizard steps to install Veeam Explorer for Microsoft Exchange. 
  4. Run the VeeamExplorerForSharePoint_10.0.0.443.msi from the downloaded ZIP archive and follow the wizard steps to install Veeam Explorer for Microsoft SharePoint. Note that Veeam Explorer for Microsoft OneDrive for Business is distributed in one package with Veeam Explorer for Microsoft SharePoint and will be installed automatically.   
  5. After Veeam Backup for Microsoft Office 365 4b is installed, all backup repositories, backup proxies, and backup jobs will be marked as Out of Date. You need to upgrade these components manually from the Veeam Backup for Microsoft Office 365 UI as described here. 

More Information

[[DOWNLOAD|DOWNLOAD UPDATE|https://www.veeam.com/download_add_packs/backup-microsoft-office-365/kb3065/]]
MD5: 4aeed25923d877cf1fc556b0b54e4d5d
SHA-1: d131bd2a94aebc2721b2331e1ff9e27bc3349575

Scale-out Backup Repository offload job to Quantum DXI used as S3 storage fails with "Failed to retrieve SSL certificate. Underlying error: PRNG not seeded" error

$
0
0

Challenge

Veeam Backup & Replication fails to perform an S3 offload task if targeted to Quantum DXI storage.
The error retrieved in UI says: "Failed to retrieve SSL certificate. Underlying error: PRNG not seeded"
[06.01.2020 13:38:21] <18> Info     [PublicCloudCertificateLoader] Loading certificate for 'https://<IP ADDRESS>:9000/'
[06.01.2020 13:38:21] <18> Info             [AP] (6891) command: 'Invoke: Network.RetrieveSslCertificate { (EString) HostName = <IP ADDRESS>; (EInt32) Port = 9000; }'
[06.01.2020 13:38:21] <11> Info                   [AP] (5c63) output: <VCPCommandArgs />
[06.01.2020 13:38:21] <11> Info                   [AP] (5c63) output: >
[06.01.2020 13:38:26] <28> Info                   [AP] (6891) output: <VCPCommandResult result="false" exception="Failed to retrieve SSL certificate. Underlying error: PRNG not seeded&#x0A;Agent failed to process method {Network.RetrieveSslCertificate}." />
[06.01.2020 13:38:26] <05> Info                   [AP] (6891) output: >

Cause

Quantum DXI series storage with firmware version prior to 4.0.3 lacks several default devices that exist in typical Linux kernels. The devices below are required by Veeam Backup & Replication, and lack of them generates the error:
  • /dev/null
  • /dev/zero
  • /dev/random
  • /dev/urandom
  • /dev/tty

Solution

To resolve the issue, perform either of the following operations:
  • Upgrade Quantum DXI firmware to version 4.0.3.
or
  • Manually add required devices through Quantum DXi-Series CLI

For example:

sudo /bin/mknod -m 0666 /dev/random c 1 8
sudo /bin/mknod -m 0666 /dev/urandom c 1 9

Job reports warning "Failed to truncate transaction logs for SQL instances: Possible reasons: lack of permissions, or transaction log corruption."

$
0
0

Challenge

Job may report warning: "Failed to finalize guest processing. Details: Failed to process 'TruncateSQLLog' command. Failed to truncate transaction logs for SQL instances: <instance name>. Possible reasons: lack of permissions, or transaction log corruption."

Solution

SQL logs truncation is done under user account specified in AAIP in Job settings, if it fails then GuestHelper tries to truncate transaction logs under LocalSystem account.

In order to understand why SQL logs truncation failed you will need to open the GuestHelper log on the Guest VM, and search for "Truncation Statistics".

  • Windows 2008 or later
    \\GUESTVM\c$\ProgramData\Veeam\Backup\VeeamGuestHelper_%date%.log
  • Windows 2003
    \\GUESTVM\c$\Documents and Settings\All Users\Application Data\Veeam\Backup\VeeamGuestHelper_%date%.log

Known Errors and Solutions

  1. Error: OpenFromInitializationString failed. [Login failed for 'DOMAIN\user'.]
    Solution: give DOMAIN\user permissions on SQL instance and add db_backupoperator role for all FULL and BULK databases, or give it a sysadmin role.
     
  2. OLEDB Error: 'The server principal "DOMAIN\user" is not able to access the database "DATABASE" under the current security context.', HelpCtx: '0'
    Solution: give DOMAIN\user db_backupoperator role for all FULL and BULK databases, or give it a sysadmin role.
     
  3. OLEDB Error: 'BACKUP detected corruption in the database log. Check the error log for more information.', HelpCtx: '0'
    Solution: error points to possible corruption and issues with SQL server
     
  4. OLEDB Error: 'BACKUP LOG cannot be performed because there is no current database backup.'

    As a rule this is an issue with the secondary node of the SQL always on cluster. You can solve this by making a backup of the DB in question via SQL Management Studio. Otherwise, you can set the secondary node as primary for just one run of your backup job. As a result all its DBs will be backed up without "copy only" flag and the error will disappear.

    The issue occurs when the secondary node has always been backed up with "copy only" flag and its standalone DBs do not have any full backup. Thus during the truncation of the standalone DB logs we get the above-mentioned message.

    The same solution applies if you get this message with regard to the excluded vCenter database / Veeam database.
     
  5. "Query timeout expired" 
Veeam Backup & Replication: If you see this entry in VeeamGuestHelper log, it usually means that we couldn't truncate SQL logs in allotted time (by default timeout is only 60 seconds). Usually you might experience such issues with rather large databases, and with large amount of transaction logs
Solution: Implement the following registry value in affected VMs in [HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\] and [ HKLM\SOFTWARE\Wow6432Node\VeeaM\Veeam Backup and Replication] (if either location does not exist, create it): Try to expand that value and run a backup afterwards, safe guess here is to set it for 600 seconds.
SqlExecTimeout
Type: REG_DWORD
Default value: 60 (in seconds, decimal)
Veeam Agent for Microsoft Windows: If you see this entry in Job log, it usually means that we couldn't truncate SQL logs in allotted time (by default timeout is 300 seconds). Usually you might experience such issues with rather large databases, and with large amount of transaction logs.
 Implement the following registry value on affected machines in [HKLM\SOFTWARE\Veeam\Veeam Endpoint Backup] 
SqlExecTimeout
Type: REG_DWORD
Default value: 300 (in seconds, decimal)
Try to expand that value and run a backup afterwards, safe guess here is to set it for 1800 seconds.
 

More Information

 

If you observe the following warning "Failed to truncate transaction logs for SQL instances: MICROSOFT WID" on Veeam B&R version 8.0.0.2084, please contact Veeam Support for the hot-fix.

Veeam Backup & Replication fails to connect to Linux servers based on Debian, SLES or RHEL/CentOS distributions with default firewall configuration

$
0
0

Challenge

Veeam Backup & Replication fails to connect to Linux servers based on Debian, SLES or RHEL/CentOS distributions with default firewall configuration.

Cause

Linux OS firewall configuration and/or security rules restrict connections to the required ports.

Solution

Default security settings differ for each Linux OS distribution and may require additional configuration to allow connections to the required ports.

NOTE: keep in mind the port range for earlier versions is from 2500 to 5000


Firewall rules

Debian
In most Debian distributions, ports from 2500 to 3300 are opened by default. If connections to the Linux server fail, make sure that Linux OS does not have restrictions for this range of ports.

SLES
Use the iptables utility to allow connections to the port range 2500–3300:i

iptables -I INPUT -p tcp —dport 2500:3300 -m state —state NEW -j ACCEPT

RHEL/CentOS
Use the iptables utility to allow connections to the port range 2500–3300:

iptables -I INPUT -p tcp —dport 2500:3300 -m state —state NEW -j ACCEPT
 

SELinux policy

SELinux policy must be configured to allow connections to the required range of ports. By default, SELinux policy restricts such connections.

To disable SELinux policy, open the /etc/selinux/config file and disable the SELinux mode. Save the file and reboot your system.

More Information

Required modules and permissions for repository support for Linux
List of ports that Veeam Backup & Replication uses
Writing custom SELinux policy

Veeam Experimental Support Statement

$
0
0

Challenge

Veeam support statement for features and functionality marked as “experimental”

Cause

Features and functionality marked as “Experimental” allow customers access software features that are still in the early stages of Veeam’s quality control process, and have not been thoroughly tested across all scenarios and/or all platform versions. Veeam makes these features available to get early feedback and validation by the field testing in different environments.

Solution

Veeam will officially support features and functionality marked as “experimental” with the following limitations:
  • Support SLAs are not guaranteed, for example due to the additional time required to create a test lab to reproduce an issue.
  • Hotfixes and patches related to experimental features have lower priority, as the preference is given to non-experimental features.
Nevertheless, it is in Veeam's best interest to make experimental features and functionality work in each environment whenever possible, as it helps us to ship such features faster and at a higher quality level.

More Information

Veeam Support Policy

How to use DiskSpd to simulate Veeam Backup & Replication disk actions

$
0
0

Challenge

This document contains information on how to use Microsoft© DiskSpd to simulate Veeam Backup & Replication disk actions to measure disk performance.

The test file created by DiskSpd does not contain any diagnostic information and must be removed manually after testing has concluded. All diagnostic information regarding the performance test is displayed in the command line. Please do not send the testfile.dat to support, as its contents will not help with troubleshooting.

DiskSpd and additional info can be found here: https://aka.ms/diskspd

Solution

Below are some details on the options and some simulations you can do to measure disk speed independently of Veeam. Please keep in mind as with all synthetic benchmarks real-world results may differ.

──────────────────────────────────────────────────────────
Common parameters
──────────────────────────────────────────────────────────

Usage: diskspd [options] target1 [ target2 [ target3 ...] ]

Target
Available targets:
·         File on a volume with an assigned letter: D:\testfile.dat
·         File on a CIFS/SMB share: \\nas\share\testfile.dat
·         File on an NFS share, provided you have mounted it to a disk letter with Client for NFS: N:\testfile.dat
·         Disk: #X where X is the number of the disk in Disk Management. You can use a local disk or one attached by iSCSI, and it does not matter if they are Online are Offline. In this mode diskspd reads or writes directly from/to the disk ("RAW").

You can specify multiple targets. This way you can simulate several jobs running at the same time.

Block size
-b specifies the size of a read or write operation.

For Veeam, this size depends on the job settings. By default, "Local" storage optimization setting is selected and this corresponds to 1MB block size in backups. However, every block of data is compressed (unless using the Decompress option) before it is written to the backup file, so the size is reduced. It is safe to assume that blocks compress on average down to half the size, so in most cases picking a 512KB block size is a good estimate.

If the job is using a different setting, WAN (256KB), LAN (512KB) or Local+ (4MB; 8MB for v8 and earlier), change the -b value accordingly to 128KB, 256KB or 4MB. And if the Decompress option is on don't halve the values.

File size
-c specifies the file size you need to create for testing. Typically 1 GB should be enough. Anything lower can be easily cached by hardware and thus yield incorrect results.

Duration
-d specifies the duration of the test. By default it does 5 seconds of warm up (statistics are not collected), then 10 seconds of the test. This is OK for a short test, but for more conclusive results run the test for at least 10 minutes (-d600).

Caching
-Sh disables Windows and hardware caching.


This flag should always be set. VeeamAgents always explicitly disable caching for I/O operations for greater reliability, even though this results in lower speed. Windows Explorer for example, does use the Cache Manager and in a very simple copy-paste test will get greater speeds than Veeam does, due to cached reads and lazy writes. That is why using Explorer is never a valid test.

──────────────────────────────────────────────────────────

Active full or forward incremental
C:\diskspd\x86fre> diskspd.exe -c1G -b512K -w100 -Sh -d600 D:\testfile.dat

-w100 indicates 100% writes and 0% reads. Sequential I/O is used by default.

IMPORTANT: Contents of 
testfile.dat will be destroyed without a warning.
──────────────────────────────────────────────────────────

Reverse incremental
C:\diskspd\x86fre> diskspd.exe -c1G -b512K -w67 -r4K -Sh -d600 D:\testfile.dat

-w67 indicates 67% writes and 33% reads to simulate 2 write and 1 read operations that happen in reverse incremental backup jobs.
-r4K enables random I/O that are 4KB aligned, for a more realistic simulation.

IMPORTANT: Contents of 
testfile.dat will be destroyed without a warning.

After the test has finished, take Total IO MB/s from the results and divide it by 3. This is because for every processed block Veeam needs to do 3 I/O operations, thus the effective speed is 3 times slower.

──────────────────────────────────────────────────────────

Transforms, merges, and other synthetic operations
Includes transformation of incrementals to rollbacks, merge operations in forever forward incremental backups and backup copy jobs, and creation of synthetic full backup files and GFS points.
 

C:\diskspd\x86fre
> diskspd.exe -c1G -b512K -w50 -r4K -Sh -d600 D:\testfile.dat

-w50 indicates 50% writes and 50% reads to simulate reading data from one file and writing that data into another (or in the case of transform, reading the same number of blocks from two files as are written to two other files).
-r4K enables random I/O that are 4KB aligned, for a more realistic simulation.

IMPORTANT: Contents of
 testfile.dat will be destroyed without a warning.

After the test has finished, take Total IO MB/s from the results and divide it by 2 (4 for transform to rollbacks). This is because for every processed block Veeam needs to do 2 I/O operations, thus the effective speed is 2 times slower. For transform to rollbacks, each block must be read out of the full backup file and written into the rollback before the corresponding block can be read out of the incremental and written into the full, which results in 4x I/O.
 
To estimate an expected time to complete the synthetic operation, in seconds:
For synthetic full backup and GFS points: divide the expected size of the new full backup file (typically the same as previous full backup files) by the effective speed.
For all other synthetic operations, add the sizes of all of the incremental files which will be merged or transformed, and then divide the resulting sum by the effective speed. Typically only the oldest incremental file is merged, whereas all incremental files are transformed to rollbacks.

──────────────────────────────────────────────────────────

Slow restore or Surebackup
This is typically when you're restoring from deduplication appliances with sub-optimal settings. See [1] and [2] for the recommended settings. As a workaround in case of slow restore, manually copy the backup files elsewhere (e.g. Veeam server), import and restore from there.

Worst case scenario where the backup file is heavily fragmented inside, which implies a lot of random read I/O:

C:\diskspd\x86fre> diskspd.exe -b512K -r4K -Sh -d600 \\nas\share\VeeamBackups\Job\Job2014-01-23T012345.vbk

-r4K enables random I/O that are 4KB aligned, for a more realistic simulation.

Best case scenario where the backup file is not fragmented inside (no parallel processing), which implies linear read I/O:
 
C:\diskspd\x86fre> diskspd.exe -b512K -Sh -d600 \\nas\share\VeeamBackups\Job\Job2014-01-23T012345.vbk

In both cases you need to pick an existing .vbk file as the target. Only read operations will be performed.

──────────────────────────────────────────────────────────

Direct disk access speed
C:\diskspd\x86fre> diskspd.exe -Sh -d600 #X
 
Where X is the number of disk that you see in Disk Management.

This will not overwrite any data, it is a safe test, and it works for Offline disks too. You can simulate and measure maximum possible reading speed in SAN or hot-add modes, however this of course will not take any VDDK overhead into account.
 

More Information

FAQ
Q: Can diskspd be used to stress-test NAS boxes for reliability ("specified network name is no longer available" errors in Veeam)
A: Unfortunately, no. If the SMB share disappears, diskspd will just ignore that issue. It is better to use Wireshark.

User-added image

Q: Active full starts fast but then gradually becomes slower and slower. Target agent runs on Windows 2008 (not R2).
A: This is a known (yet undocumented) performance degradation issue on Windows 2008. Upgrade to or deploy 2008 R2 (or newer). In case of a CIFS repository you can force some other 2008 R2 server to be used as gateway/proxying. The issue itself can be demonstrated with diskspd if you set it to run for several hours, then observe how the write rate slowly goes down in Resource Monitor.

Q: I am getting extremely high I/O speed like 4 GB/s in any test I try, even though I have set the -Sh flag, what's going on?
A: Most likely you're running diskspd on a Hyper-V VM, testing performance of a virtualised (.vhdx) disk, so the data is cached by the Hyper-V host. Run the test on the datastore where that .vhdx is located instead.

Invalid Character in Amazon S3 Bucket Name

$
0
0

Challenge

When adding/editing an object storage repository and selecting (or creating) a folder in the Amazon S3 bucket, the following error occurs:
  • Could not establish trust relationship for the SSL/TLS secure channel. Applicable to build 4.0.0.1553.
  • Exception of type 'Veeam.Engine.Net.InvalidCertificateException. Applicable to build 4.0.0.1345.

Cause

The bucket name in Amazon contains a period (".") character which is not supported. For more information, see the following Amazon articles:

Solution

Select a different bucket without a period character.

 

More Information

Should you have any questions, contact Veeam Support.

 

“The default account is not initialized” error is displayed when adding an IAM role to Veeam Backup for AWS

$
0
0

Challenge

The Default Backup Restore IAM role is not created upon the Veeam Backup for AWS installation. Attempts to add IAM roles to Veeam Backup for AWS in the Add Account wizard fail with "The default account is not initialized" error.

User-added image

Cause

The backup server cannot access the required AWS services over the internet. Required AWS services are listed in the Requirements section of the Veeam Backup for AWS User Guide.

Solution

1. Make sure the backup server (EC2 instance where Veeam Backup for AWS is installed) has internet access to the required AWS services. For more information, see this AWS article. Make sure all endpoints for the required AWS services are reachable from the backup server. For more information on service endpoints and quotas for AWS services, see the AWS General Reference guide.
2. Connect to the backup server with the following command:
ssh -i "<backup server's .pem key>" ubuntu@<Public DNS (IPv4) parameter of the backup server>
3. Restart the Veeam Backup for AWS service running on the backup server with the following command:
sudo systemctl restart veeamawsbackup.service

The Default Backup Restore IAM role should be created automatically after you perform these steps.

 

SharePoint Online or OneDrive for Business Backup Jobs fail with the Warning

$
0
0

Challenge

Backup jobs with SharePoint Online or OneDrive for Business items fail with the following warning: "Processing OneDrive Username (https://orgname-my.sharepoint.com/personal/user_name) finished with warning: Failed to backup item: /personal/user_name/Documents/File.zip, The remote server returned an error: (400) Bad Request".

 

Cause

Items being backed-up might be blocked by the internal SharePoint Online antivirus. For more information, see this Microsoft article.

 

Solution

To check whether items are infected, open OneDrive or Site which cannot be backed-up and try to download files manually. If the files you are trying to download are infected, the following error appears.

User-added image

Veeam Intelligent Diagnostics signature UID field

$
0
0

Challenge

This KB provides a brief overview of the Veeam Intelligent Diagnostics feature in Veeam ONE and explains the purpose of the new Veeam Intelligent Diagnostics signature UID field in the Veeam support case submission form.

Cause

The support case submission form on the Veeam customer portal was extended with the optional Veeam Intelligent Diagnostics signature UID field. Veeam customers and partners can specify a VID Signature UID when opening a technical case for the following products:
  • Veeam Backup & Replication, version 9.5 and higher.
  • Veeam Cloud Connect, version 9.5 and higher.
  • Veeam Cloud Connect for Enterprise, version 9.5 and higher.
User-added image
 

Solution

Veeam Intelligent Diagnostics is a part of Veeam ONE functionality that detects issues in Veeam Backup & Replication environments running versions 9.5 Update 3 and later.

VID enables Veeam ONE to parse logs from Veeam Backup & Replication servers, compare the logs to a list of known issue signatures and trigger alarms with recommendations based on the results of log analysis. The Veeam Intelligent Diagnostics feature helps to detect backup infrastructure issues at an early stage and eliminate them efficiently. 

For more information on the Veeam Intelligent Diagnostics workflow, please see the user guide page below:
https://helpcenter.veeam.com/docs/one/monitor/intelligent_diagnostics.html?ver=95u4

User-added image

When opening a case based on a VID alarm received in Veeam ONE, please remember to fill the signature UID field with the relevant identifier.

More Information

Providing the VID signature UID when creating a support ticket via the support portal significantly speeds up troubleshooting since the issue number will instruct Veeam support engineer on the required actions. In addition, providing the signature UID will help our automatic tracking systems to correctly determine the most frequent issues and collect valid statistics for further enhancement of Veeam products based on real customer's experience.

Veeam Agent for Linux support of Red Hat Enterprise Linux

$
0
0

Challenge

This article describes Veeam Agent for Linux support of different kernel versions of Red Hat Enterprise Linux and its derivatives.
 

Cause

Last-minute kernel patches for Red Hat Enterprise Linux and its derivatives may cause Veeam Agent for Linux to go unstable (veeam.com/kb2786).
 

RHEL versionKernel supported up toVAL buildComments
8.14.18.0-1473.0.2.1193For packages and instructions please open a support ticket.
8.04.18.0-80.7.23.0.2.1185For standalone installations you can obtain build 3.0.2.1185 from veeam.com.
For managed installations the build is shipped with Backup & Replication v.9.5 update 4b (9.5.4.2866). For details on Backup & Replication 9.5.4.2866 please refer to kb2970.
7.7 and later3.10.0-1062 or newer3.0.2.1190For standalone installations you can obtain build 3.0.2.1190 from repository.veeam.com.
For instructions on how to deploy build 3.0.2.1190 on installations managed by Backup & Replication please refer to Veeam Agent Management Guide.
7.0 - 7.63.10.0-957.27.23.0.2.1185For standalone installations you can obtain build 3.0.2.1185 from veeam.com.
For managed installations the build is shipped with Backup & Replication v.9.5 update 4b (9.5.4.2866). For details on Backup & Replication 9.5.4.2866 please refer to kb2970.
6.x2.6.32-754.18.23.0.2.1185For standalone installations you can obtain build 3.0.2.1185 from veeam.com.
For managed installations the build is shipped with Backup & Replication v.9.5 update 4b (9.5.4.2866). For details on Backup & Replication 9.5.4.2866 please refer to kb2970.

How to Reset Password in Veeam Backup for AWS

$
0
0

Challenge

You may need to reset a password in Veeam Backup for AWS.

Solution

Make sure that the machine you are using for troubleshooting is in the list of allowed IP addresses in the Security Groups of your Veeam Backup for AWS server, then connect to the Veeam Backup for AWS server by the ssh client using the private key you have specified when deploying the server.

NOTE: You can find the name of the key in the Key pair name property located on the Description tab of your EC2 Instance. Consider checking the Lost private key file section below if you lost the private key.

To reset a password, you can use either a Linux or Windows desktop:
  • To connect to the Veeam Backup for AWS server from a Linux desktop, run the following command and enter Yes to connect to the specified server.
> ssh -i private_key.pem ubuntu@<DNS name or IP address of Veeam Backup for AWS server>
Once a connection is established, run the following command and enter a new password.
> sudo passwd <your username>
If you forgot the username, run the following command and find the correct user at the end of the list.
> sudo cat /etc/group | grep VEEAM_ADMINS
To finish the session, enter the following command.
> exit

More Information

According to security practices of AWS EC2, you are allowed to download the private security key only once — that is, only after it has been created in EC2 Services / Network & security / Key Pairs. If such a key is lost, you will not be able to connect to the Veeam Backup for AWS server by SSH.

For more information on how to reset a key for the Veeam Backup for AWS Server EC2 Instance, see the Replace a Lost SSH Key Pair article.

 
Viewing all 4470 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>