↧
Unable to Create Folder (name: ) Error
↧
Veeam Backup for Microsoft Office 365 Support for Microsoft Office 365 Multi-Geo Tenant
Challenge
This article explains how Veeam Backup for Microsoft Office 365 supports backups of Veeam Backup for Microsoft Office 365 tenants with the Multi-Geo feature enabled.Solution
- Exchange Online
Veeam Backup for Microsoft Office 365 fully supports Exchange Online mailbox backups for Multi-Geo configured tenants.
- SharePoint Online / OneDrive for Business
Veeam Backup for Microsoft Office 365 supports SharePoint Online Personal sites only and OneDrive for Business backups for Multi-Geo tenants with the following limitation:
After data migration, a full backup will be performed for the site on the next backup job run. This limitation is caused by an inability to get the required information on site changes after its migration to a different region. At the same time, backup consistency is preserved without any data duplication.
More Information
https://docs.microsoft.com/en-us/office365/enterprise/office-365-multi-geo↧
↧
Support statement for Tiger Bridge
Challenge
Using cloud storage gateway software like Tiger Bridge to copy backup data to cloud storage providers like and/or to reclaim disk space belonging to copied backups from the primary backup repository based on certain thresholds.Cause
Veeam Backup & Replication architecture and interaction with its backup files requires that all backup file's data remains in the backup repository, and does not support external data movers that offload some or all of backup file's data to another storage, including object storage.Veeam recommends using native Veeam Backup & Replication functionality for offloading backup files to object storage, which operates in a significantly different manner:
1. It preserves certain essential parts of offloaded backup files' data in the primary backup repository permanently.
2. It passes the awareness of offloaded data blocks to various product functions, which then treat such data blocks in a special manner to ensure reliable operations, acceptable levels of performance, and reduced storage/ingress/egress costs.
Solution
Veeam Customer Support will not support environments where some or all of backup files' data is being offloaded to another storage with 3rd party solutions. For additional information, please refer to the User Guide.Veeam Customer Support is unable to assist with failed restores from copies of backups made by 3rd party solutions, because Veeam cannot guarantee that the backup files' data was correctly managed by the 3rd party application, and is consistent. This is especially true with object storage, which often provides "eventual consistency" only.
↧
Backup Jobs with Public Folders fail
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.
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.
$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.
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.↧
Support statement for Tiger Bridge
Challenge
Using cloud storage gateway software like Tiger Bridge to copy backup data to cloud storage providers like and/or to reclaim disk space belonging to copied backups from the primary backup repository based on certain thresholds.Cause
Veeam Backup & Replication architecture and interaction with its backup files requires that all backup file's data remains in the backup repository, and does not support external data movers that offload some or all of backup file's data to another storage, including object storage.Veeam recommends using native Veeam Backup & Replication functionality for offloading backup files to object storage, which operates in a significantly different manner:
1. It preserves certain essential parts of offloaded backup files' data in the primary backup repository permanently.
2. It passes the awareness of offloaded data blocks to various product functions, which then treat such data blocks in a special manner to ensure reliable operations, acceptable levels of performance, and reduced storage/ingress/egress costs.
Solution
Veeam Customer Support will not support environments where some or all of backup files' data is being offloaded to another storage with 3rd party solutions. For additional information, please refer to the User Guide.Veeam Customer Support is unable to assist with failed restores from copies of backups made by 3rd party solutions, because Veeam cannot guarantee that the backup files' data was correctly managed by the 3rd party application, and is consistent. This is especially true with object storage, which often provides "eventual consistency" only.
↧
↧
VSS does not work on SMB shares
Challenge
A NAS backup/file to tape job skips VSS snapshot creation on SMB share and ends with the following message in the log:Failed to create a VSS snapshot for %hostname%, failing over to backup directly from the share.
Solution
To support the new VSS for SMB File Shares feature, make sure that the following requirements are met:- Application server and file server run Windows Server 2012.
- Application server and file server are domain joined to the same Active Directory domain.
- The “File Server VSS Agent Service” role service is enabled on the file server.
- The backup agent runs in a security context that has backup operators or administrator privileges on both the application server and file server.
- The backup agent/application runs in a security context that has at least the READ permission on the file share data that is being backed up.
https://docs.microsoft.com/en-us/archive/blogs/clausjor/vss-for-smb-file-shares
"File Server VSS Agent Service" role service installation and configuration
Do the following, with administrative privileges, to install the File Server role and the File Server Shadow Copy Agent role service on each file server:
GUI:
1. In the Server Manager Dashboard, click Add roles and features.
2. In the Add Roles and Features Wizard, do the following:
a. In the Before you begin wizard page, click Next.
b. In the Select installation type wizard page, select Role-based or feature-based installation.
c. In the Select destination server wizard page, select the server where you want to install the File Share Shadow Copy Agent.
d. In the Select server roles wizard page:
b. In the Select installation type wizard page, select Role-based or feature-based installation.
c. In the Select destination server wizard page, select the server where you want to install the File Share Shadow Copy Agent.
d. In the Select server roles wizard page:
i. Expand File and Storage Services.
ii. Expand File Services.
iii. Select File Server.
iv. Select File Server VSS Agent Service.
ii. Expand File Services.
iii. Select File Server.
iv. Select File Server VSS Agent Service.
e. In the Select features wizard page, click Next.
f. In the Confirm installation selections, verify that File Server and File Server VSS Agent Service are listed, and click Install.
f. In the Confirm installation selections, verify that File Server and File Server VSS Agent Service are listed, and click Install.
PowerShell
- Start elevated Windows PowerShell (Run as Administrator).
- Run the following command:
Add-WindowsFeature -Name File-Services,FS-VSS-Agent
Add backup user to Backup Operators local group on file server
The user context in which the shadow copy is performed must have the backup privilege on the remote file server(s) that is part of the shadow copy set.
Usually, this is done by adding the user that is performing the shadow copy to the Backup Operators group on the file server(s).
To add a user to the local Backup Operators group, do the following with administrative privileges on each file server:
GUI
1. In the Server Manager Dashboard, click Tools and select Computer Management.
2. In Computer Management:
a. Expand Local Users and Groups.
b. Click Groups.
c.In the results pane, double-click Backup Operators.
d. In the Backup Operators Properties window, click Add.
e. Type the username to add to the Backup Operators group, click OK.
f. In the Backup Operators Properties page, click OK.
g. Close Computer Management.
PowerShell
b. Click Groups.
c.In the results pane, double-click Backup Operators.
d. In the Backup Operators Properties window, click Add.
e. Type the username to add to the Backup Operators group, click OK.
f. In the Backup Operators Properties page, click OK.
g. Close Computer Management.
- Start elevated Windows PowerShell (Run as Administrator)
- Run the following commands, adjusting the user account and file server name to your environment:
$objUser = [ADSI]("WinNT://domain/user")
$objGroup = [ADSI]("WinNT://fileserv/Backup Operators")
$objGroup.PSBase.Invoke("Add",$objUser.PSBase.Path)
↧
Manually moving backup files between Scale-Out Backup Repository extents
Challenge
One of the extents is filling up faster than the others and you want to balance them, but only certain backups/tenants need to be moved to another extent.This article applies to Backup, Backup copy, Agent backups, Agent backups with subtenant accounts.
NOTE: This article must not be applied for backup migration from a simple repository or for backup migration between extents of different Scale-out backup repositories. For such cases, refer to this article: https://www.veeam.com/kb2236
Before you proceed, check REFS Fast Clone limitations. For more information, see this article:
https://helpcenter.veeam.com/docs/backup/vsphere/backup_repository_block_cloning.html?ver=95u4
Cause
- An extent is filled up because of the “Data locality” SOBR placement policy.
- An extent is filled up because of the other extent “Evacuation”.
- A new extent was added to SOBR and a part of the backup needs to be migrated there.
Solution
Local SOBR:1. Disable the job that needs to be migrated.
2. Migrate the whole backup chain including .vbm file to another extent.
Backups need to be placed in the same folder starting from repository root.
Example:
Repository name is SOBR, there are 2 extents, backups need to be migrated from “SOBR Extent 1” to “SOBR Extent 2”.
![User-added image]()
Original folder: E:\VeeamBackup\Backup_Job_1\Backup_Job_1.vbm
New folder: C:\Backups\Backup_Job_1\Backup_Job_1.vbm
Repository name is SOBR, there are 2 extents, backups need to be migrated from “SOBR Extent 1” to “SOBR Extent 2”.
Original folder: E:\VeeamBackup\Backup_Job_1\Backup_Job_1.vbm
New folder: C:\Backups\Backup_Job_1\Backup_Job_1.vbm
3. Navigate to Veeam Console -> Backup infrastructure-> Scale-out Repositories -> Right-click on the affected SOBR -> Rescan.
Cloud Connect SOBR:
1. Disable the tenant or the job that needs to be migrated.
2. Migrate the whole backup chain including .vbm file to another extent.
Backups need to be placed in the same folder starting from repository root.
Example:
Original folder: E:\VeeamBackup\Tenant1\Backup_Job_1\Backup_Job_1.vbm
New folder: C:\Backups\Tenant1\Backup_Job_1\Backup_Job_1.vbm
3. Navigate to Veeam Cloud Connect Server -> Veeam Backup and Replication Console -> Backup infrastructure-> Scale-out Repositories -> Right-click on the affected SOBR -> Rescan.Original folder: E:\VeeamBackup\Tenant1\Backup_Job_1\Backup_Job_1.vbm
New folder: C:\Backups\Tenant1\Backup_Job_1\Backup_Job_1.vbm
4. Enable the tenant/job.
↧
Collecting Diagnostic Information for Veeam Plugin for SAP HANA
Challenge
This KB article shows how to collect the diagnostic information that may be needed if you create a Veeam Plugin for SAP HANA support case.Solution
Gather logs according to sections below.
Once logs have been gathered, upload them to the FTP provided by the Veeam Support engineer. After the upload is completed, please notify the Veeam Support engineer.
If you need to use a secure FTP, KB1661 contains secure FTP instructions.
1. Veeam Plugin source logs
This step should be done on source SAP HANA server.
Navigate to and archive the contents of this folder:
/tmp/veeam_plugin_logsExample:
tar -czvf veeam_plugin_logs.tar.gz /tmp/veeam_plugin_logs
File veeam_plugin_logs.tar.gz will contain the necessary logs.
2. Veeam Plugin target logs
This step should be done on both Veeam Backup and Veeam Repository servers.:
Navigate to and archive the contents of this folder:
%ProgramData%\Veeam\Backup\Endpoint
3. External backups list
Save information about available backup files and their EBID values. This can be done using the following query:
SELECT BACKUP_ID,SOURCE_TYPE_NAME,HOST,BACKUP_SIZE,DESTINATION_PATH,EXTERNAL_BACKUP_ID FROM M_BACKUP_CATALOG_FILES WHERE DESTINATION_TYPE_NAME='backint'Run the same query against each database in question. Save the output of this query in a text file for Veeam Support.
4. System information
Save information about available systems running on your server. This can be done using the following approach:
Login to user shell and issue the following one-liner:
ps -eo pid,command | grep -v grep | grep -v sapstartsrv | grep sapstart | awk '{print $3}'
Save the output of this query in a text file for Veeam Support.
↧
Veeam Backup for AWS Recovery/Migration Procedure
Challenge
This document explains how to recover or migrate Veeam Backup for AWS data to a new instance.A Veeam Backup for AWS instance may fail or get corrupt and requires the data volume to be moved to a new instance since it contains information about restore points, repositories, policies. Additionally, this procedure can be used when migrating between editions (for example from FREE to BYOL or MMS).
Solution
To perform a migration to a new instance, deploy a new Veeam Backup for AWS instance via the AWS marketplace using Cloud Formation as explained in the user guide on installing Veeam Backup for AWS.Before beginning, make sure that both Veeam Backup for AWS instances are in the same AWS region and availability zone.
To perform the migration, do the following:
1. Detach volume 2 from the new Veeam Backup for AWS instance. By default, this is ‘/dev/sdb’. This can be done via the EBS ID link. On the volume page, select "Detach Volume" from the Actions menu.
NOTE: It is recommended to stop instance before detaching a disk, as a disk may stuck in the Busy state for a long period of time.![User-added image]()
3. Within the Instance overview, copy the instance ID from the new Veeam Backup for AWS instance.
7. Once the new Veeam Backup for AWS instance is started, you must go through the initial setup to configure the instance and create the initial user. Afterward, you will see all your backup policies, repositories, restore points... User accounts are not migrated so they will have to be recreated.
8. Go to "Cloud Formation service" in the region where our server is deployed.
9. Select appropriate Stack from the list by clicking its name in the Stack Name column.
10. Got to "Resources" tab.
11. Find out Logical ID ‘VeeamImpersonationRole’.
12. Go to the role description by clicking it's name in the Physical ID column.
13. Copy Role ARN by clicking Copy to clipboard on order to add it to the trusted list for recently added role.
14. Go to the Roles tab in IAM service.
15. Find our recently added role.
16. Select it by clicking its name in the Role Name column.
17. Go to the Trust relationship tab.
18. Click Edit trust relationship.
19. Add the following JSON text:
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Principal":
{
"AWS": "ARN of the role from step 13"
},
"Action": "sts:AssumeRole"
}
]
}
↧
↧
The requested operation could not be completed due to a file system limitation
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/967351This 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
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
↧
Veeam Backup for AWS Recovery/Migration Procedure
Challenge
This document explains how to recover or migrate Veeam Backup for AWS data to a new instance.A Veeam Backup for AWS instance may fail or get corrupt and requires the data volume to be moved to a new instance since it contains information about restore points, repositories, policies. Additionally, this procedure can be used when migrating between editions (for example from FREE to BYOL or MMS).
Solution
To perform a migration to a new instance, deploy a new Veeam Backup for AWS instance via the AWS marketplace using Cloud Formation as explained in the user guide on installing Veeam Backup for AWS.Before beginning, make sure that both Veeam Backup for AWS instances are in the same AWS region and availability zone.
To perform the migration, do the following:
1. Detach volume 2 from the new Veeam Backup for AWS instance. By default, this is ‘/dev/sdb’. This can be done via the EBS ID link. On the volume page, select "Detach Volume" from the Actions menu.
NOTE: It is recommended to stop instance before detaching a disk, as a disk may stuck in the Busy state for a long period of time.![User-added image]()
3. Within the Instance overview, copy the instance ID from the new Veeam Backup for AWS instance.
7. Once the new Veeam Backup for AWS instance is started, you must go through the initial setup to configure the instance and create the initial user. Afterward, you will see all your backup policies, repositories, restore points... User accounts are not migrated so they will have to be recreated.
8. Go to "Cloud Formation service" in the region where our server is deployed.
9. Select appropriate Stack from the list by clicking its name in the Stack Name column.
10. Got to "Resources" tab.
11. Find out Logical ID ‘VeeamImpersonationRole’.
12. Go to the role description by clicking it's name in the Physical ID column.
13. Copy Role ARN by clicking Copy to clipboard on order to add it to the trusted list for recently added role.
14. Go to the Roles tab in IAM service.
15. Find our recently added role.
16. Select it by clicking its name in the Role Name column.
17. Go to the Trust relationship tab.
18. Click Edit trust relationship.
19. Add the following JSON text:
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Principal":
{
"AWS": "ARN of the role from step 13"
},
"Action": "sts:AssumeRole"
}
]
}
↧
Release Notes for NetApp Element Plug-In for Veeam Backup & Replication 1.0.10
Challenge
Release Notes for NetApp Element Storage Plug-In for Veeam Backup & Replication 1.0.10.This update supersedes NetApp Element Plug-In for Veeam Backup & Replication 1.0.09.
Cause
Before installing this update, make sure you are running Veeam Backup & Replication version 9.5.4.2753 or later.To check the version, do the following:
- Open the Veeam Backup & Replication console.
- In the main menu, click Help and select About.
Solution
This update resolves the most common support issues including the following:- Snapshot name format in snapshot-only backup jobs now includes a timestamp to ensure its uniqueness.
- Snapshot clone operation logic has improved to avoid unnecessary timeouts.
More Information
[[DOWNLOAD|DOWNLOAD UPDATE|https://www.veeam.com/download_add_packs/vmware-esx-backup/netapp/]]MD5 checksum for NetAppElementPlugin_1.0.10.zip: 328C2F244D3682FE62006FD400F28FA5
SHA-1 checksum for NetAppElementPlugin_1.0.10.zip: B44A9C49B325827FA6E0389198117ABA6ED10297
↧
Release Notes for Huawei Plug-In for Veeam Backup & Replication 1.0.21
Challenge
Release Notes for Huawei Storage Plug-In for Veeam Backup & Replication 1.0.21.This update supersedes Huawei Plug-In for Veeam Backup & Replication 1.0.19
Cause
Before installing this update, make sure you are running Veeam Backup & Replication version 9.5.4.2866 or later.To check the version, do the following:
- Open the Veeam Backup & Replication console.
- In the main menu, click Help and select About.
Solution
This update features the following enhancement:- Added support for OceanStor Dorado V6.
More Information
[[DOWNLOAD|DOWNLOAD UPDATE|https://www.veeam.com/download_add_packs/vmware-esx-backup/huawei/]]MD5 checksum for HuaweiPlugin_1.0.21.zip: 601C028F0B5CC38E5D93934C9C008F42
SHA-1 checksum for HuaweiPlugin_1.0.21.zip: E1FB82A63054A6EF32D3D697E8854B1B907FA37F
↧
↧
Release Notes for Huawei Plug-In for Veeam Backup & Replication 1.0.19
Challenge
Release Notes for Huawei Storage Plug-In for Veeam Backup & Replication 1.0.19This update supersedes Huawei Plug-In for Veeam Backup & Replication 1.0.16
Cause
Before installing this update, make sure you are running Veeam Backup & Replication version 9.5.4.2866 or later.To check the version, do the following:
- Open the Veeam Backup & Replication console.
- In the main menu, click Help and select About.
Solution
This update resolves the most common support issues including the following:- Snapshots created by Timing Snapshot Schedule on Huawei OceanStor Dorado couldn't be automatically deleted according to retention configured in the storage settings.
More Information
This update has been superseded by Huawei Plug-In for Veeam Backup & Replication 1.0.21↧
Release Notes for INFINIDAT Plug-In for Veeam Backup & Replication
Challenge
Release Notes for INFINIDAT Storage Plug-In for Veeam Backup & Replication 1.1.0This update supersedes INFINIDAT Plug-In for Veeam Backup & Replication 1.0.6
Cause
Please confirm that you are running version 9.5.0.1536 or later prior to installing this update. You can check this under Help | About in Veeam Backup & Replication console.Solution
This update also resolves most common support issues including the following:- Under certain circumstances backup jobs could fail upon snapshot export to the proxy server (Fibre Channel protocol)
- Connection to array could fail with HTTP timeout
- The number of login sessions to the storage was reduced
More Information
[[DOWNLOAD|DOWNLOAD UPDATE|https://www.veeam.com/download_add_packs/vmware-esx-backup/infinidat/]]MD5 checksum for InfinidatPlugin_1.1.0.zip is 5FF0C93123EC8CA8D217BD40508BA9F9
↧
Release Notes for Western Digital Plug-In for Veeam Backup & Replication 1.0.81
Challenge
Release Notes for Western Digital Plug-In for Veeam Backup & Replication 1.0.81This update supersedes Western Digital Plug-In for Veeam Backup & Replication 1.0.80
Cause
Before installing this update, make sure you are running Veeam Backup & Replication version 9.5.4.2866 or later.To check the version, do the following:
- Open the Veeam Backup & Replication console.
- In the main menu, click Help and select About.
Solution
This update features the following enhancement:- Added support for IntelliFlash OS version 3.10.x or later.
More Information
[[DOWNLOAD|DOWNLOAD UPDATE|https://www.veeam.com/download_add_packs/vmware-esx-backup/wd/]]MD5 checksum for WesternDigitalPlugin_1.0.81.zip: 3a30b5a4887eec7f038c2c3783d2123b
SHA-1 checksum for WesternDigitalPlugin_1.0.81.zip: d4b33e7b927633ced9718d257d984086bdcb4647
↧
SharePoint Online or OneDrive for Business backup jobs fail with “The remote server returned an error” warning
Challenge
Backup jobs with SharePoint Online or OneDrive for Business items fail with the following errors:Error: The remote server returned an error: (500) Internal Server Error. Error: The remote server returned an error: (409) Conflict.
NOTE:
- If you are experiencing these errors in versions higher than Veeam Backup for Microsoft Office 2.0, contact Technical Support.
- Different error codes starting from version 3.0 my appear. For more information, see this KB article.
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.↧
↧
SharePoint Online and OneDrive for Business Backup Jobs Fail with (403) Forbidden Warning Message
Challenge
SharePoint Online or OneDrive for Business backup jobs fail with the following message:2/5/2020 5:32:43 PM :: Processing site https://site.sharepoint.com/sites/111/subsite finished with warning: Failed to backup item version: /<path>/1024/Shared Documents/<file>, version: 2.0, The remote server returned an error: (403) Forbidden. :: 0:00:21
Cause
Due to limitations of history of file versions, the file cannot be downloaded.Solution
To confirm that limitations of history of file versions cause the error, do the following:1. Open the affected OneDrive or Site in the Web-browser.
2. Find the file that cannot be downloaded and open Version history.
3. Left-click on the date.
As a result, the same 403 error must appear, which confirms that the file is inaccessible. Make sure to contact Veeam Technical Support to troubleshoot the issue.
↧
Exchange Backup Jobs Warning "Failed to find group owner account"
Challenge
Backup jobs with Microsoft Exchange items may end up with the warning message shown in both the Veeam Backup for Microsoft Office 365 console and the Veeam.Archiver.Proxy.log file.1/20/2020 6:30:28 AM 62 (2600) Resolving group: 753da553-b4dd-45ad-a773-180aa920c887:00000000-0000-0000-0000-000000000000...
1/20/2020 6:30:28 AM 62 (2600) Group found: TestOwnerGroup
1/20/2020 6:30:28 AM 62 (2600) Resolving group mailbox (ID: 753da553-b4dd-45ad-a773-180aa920c887:00000000-0000-0000-0000-000000000000)...
1/20/2020 6:30:29 AM 62 (2600) Found group mailbox: testgroup@organization.onmicrosoft.com
1/20/2020 6:30:29 AM 62 (2600) Warning: Failed to find group owner account
Cause
Impersonation is not possible if Office 365 groups (mail-enabled and security groups) do not have an owner.Solution
Make sure to assign an owner to each of the Office 365 groups (mail-enabled and security groups) as described in this Microsoft article.↧
Unable to Add Workers to Bahrain or Hong Kong Regions
Challenge
When adding a worker instance to the Bahrain or Hong Kong regions, the following error occurs: "AWS was not able to validate the provided access credentials".Cause
Veeam Backup for AWS uses the Global STS endpoint.Solution
To add a worker to the Bahrain or Hong Kong regions, do the following:- Open the IAM Console.
- Go to Account Settings > Security Token Service (STS).
- Set the Global endpoint to Valid for all AWS regions.
↧