Challenge

Product Information:

Company name: QNAP Systems, Inc.
Product Family: TS-hx83XU
Status: Veeam Ready - Repository
Classification Description: Verified backup storage that supports all Veeam backup and restore features.

Solution

Product Details:

Model number: TS-h1283XU
Storage Category: RAID Storage Array
Drive quantity, size, type: 5 – 1TB SATA HDD
Storage configuration: RAID5, no SSD caching
Firmware version: QTS Hero 4.5.0
Connection protocol and speed: SMB 10GbE
Additional support: All models and configurations of TS-hx83XU with specifications equivalent or greater than the above

The QTS hero NAS TS-h1283XU-RP is powered by an Intel® Xeon® E processor with up to 128 GB DDR4 Error Correcting Code (ECC) memory to deliver server-grade performance with dependable reliability. Running the brand new QTS hero operating system that incorporates ZFS, the TS-h1283XU-RP supports near-limitless snapshots, SnapSync, block-level inline data deduplication, and inline data compression.

Veeam testing configuration:

Veeam Build Number: 9.5.4.2866

Job Settings:

Repository Settings:

Vendor recommended configuration:

Hardware Settings:

• No array deduplication used in testing
• No array compression used in testing
• Jumbo frames used in testing (MTU=9000)

Challenge

Product Information:

Company name: Dell EMC
Product Family: PowerVault ME4
Status: Veeam Ready - Repository
Classification Description: Verified backup storage that supports all Veeam backup and restore features.

Solution

Product Details:

Model number: PowerVault ME4024
Storage Category: RAID Storage Array
Drive quantity, size, type: 4 x 1.92TB SSD, 12 x 2TB 7.2k HDD
Storage configuration: RAID10 on SSDs, ADAPT RAID on HDDs
Firmware version: G280 v1
Connection protocol and speed: 10 GbE iSCSI
Additional support: All models and configurations of PowerVault ME4 with specifications equivalent or greater than the above

Dell EMC PowerVault ME4 Series storage implements a block architecture with VMware virtualization integration and concurrent support for native iSCSI, Fibre Channel, and SAS protocols. Each system leverages dual storage processors (single storage processor systems are available) and a full 12Gb SAS back-end. Additional storage capacity is added via Disk Array Enclosures (DAEs) while Distributed RAID (ADAPT) delivers faster drive re-build times. And all ME4 Series arrays are managed by an integrated HTML5 web-based GUI.

Veeam testing configuration:

Veeam Build Number: 9.5.4.2866

Job Settings:

Repository Settings:

Vendor recommended configuration:

Hardware Settings:

• No array deduplication used in testing
• No array compression used in testing
• Multipath used during testing

Challenge

This article documents antivirus exclusions that have been found to help prevent antivirus software from interrupting Veeam Backup & Replication communications with components such as proxies and repositories or with the guest OS of VMs that are being backed up or replicated.

Cause

In some rare instances antivirus can prevent certain executables, processes, or agents from being correctly deployed or leveraged from the Veeam server, proxy, repository, or even the guest OS.

Solution

Antivirus Exclusions:

Folders on the Veeam Server:

• C:\Program Files\Veeam\
• C:\Program Files (x86)\Veeam\
• C:\Program Files\Common Files\Veeam\
• C:\Program Files (x86)\Common Files\Veeam\
• VBRCatalog ( [HKLM\SOFTWARE\Veeam\Veeam Backup Catalog] CatalogPath value)
• NFS (Configured in each repository, stored in [HKLM\SOFTWARE\Wow6432Node\Veeam\Veeam NFS] RootFolder value)
• C:\VeeamFLR\*
• C:\Windows\Veeam\
• %programdata%\Veeam\

Folder on Guest OS for VSS:

• C:\Windows\VeeamVssSupport\ (folder might be missing, depends on backup job settings)
• C:\Windows\VeeamLogShipper\ (folder might be missing, depends on backup job settings)

Folders on VMware Backup Proxies and CIFS Repository Gateway:

• C:\Program Files (x86)\Veeam\
• C:\Windows\Veeam\

Folders on Windows Repositories:

• C:\Program Files (x86)\Veeam\
• C:\Windows\Veeam\
• %programdata%\Veeam\
• *Also include the path the backup files*
• *Also include the path to 'ArchiveIndex' for capacity tier*

Folders on WAN Accelerator:

• C:\Program Files (x86)\Veeam\
• C:\Windows\Veeam\
• *Path of WAN cache on WAN accelerators*

Repository Files:

• VeeamAgent.exe
• VeeamAgent64.exe
• *.vmdk
• *.flat
• *.vbm
• *.vbk
• *.vib
• *.vrb
• *.vsb
• *.vlb
• *.erm

Due to the complex nature of antivirus software some additional exclusions may be needed.
If your antivirus has a logging or history system please review this to see actions it may have taken that may affect Veeam Backup & Replication operations.

Challenge

Cause

Solution

• Linux user account used by Veeam Backup and Replication server for any Veeam Agent for Linux deployment and management operations must have /bin/bash shell set by default.
• /etc/sudoers file should contain a line with ‘requiretty’ parameter negated explicitly for desired Linux user account
• The account must have either ‘root’ permissions or permissions to execute a specific list of commands as a sudoer on the target Linux machine.

Veeam Agent for Linux 4.0

Veeam Backup & Replication v10

An example of /etc/sudoers file containing proper settings:

Defaults:username !targetpw  

Defaults:username !targetpw
username ALL=(root) /bin/hostname
username ALL=(root) /bin/whoami
username ALL=(root) /bin/mkdir
username ALL=(root) /bin/arch
username ALL=(root) /bin/uname
username ALL=(root) /bin/scp
username ALL=(root) /bin/chown
username ALL=(root) /opt/veeam/veeaminstaller
username ALL=(root) /bin/veeamconfig

# FLR Restore via console
username ALL=(root) /tmp/*_vblkid
username ALL=(root) /bin/mount
username ALL=(root) /bin/[ -d /tmp/ ]
username ALL=(root) /tmp/VeeamAgent*-*-*-*
username ALL=(root) /bin/rm
username ALL=(root) /bin/ps
username ALL=(root) /bin/cat

Veeam Agent for Linux 3.x

Veeam Backup & Replication 9.5 U4

An example of /etc/sudoers file containing proper settings for SLES 11, Veeam Agent for Linux v3.0/Veeam Backup & Replication v9.5 update 4:

Defaults:username !targetpw  

username ALL=(root) /bin/hostname 
username ALL=(root) /bin/uname 
username ALL=(root) /bin/arch 
username ALL=(root) /bin/cat 
username ALL=(root) /usr/bin/test 
username ALL=(root) /bin/mkdir 
username ALL=(root) /bin/rmdir 
username ALL=(root) /bin/chown 
username ALL=(root) /usr/bin/whoami 
username ALL=(root) /usr/bin/id 
username ALL=(root) /tmp/*/veeamagentid 
 
# Agent config/backup 
username ALL=(root) /usr/bin/veeamconfig 
  
# Agent deployment 
username ALL=(root) /usr/bin/zypper 
username ALL=(root) /sbin/modinfo 
username ALL=(root) /bin/rpm 
  
# FLR Restore via console 
username ALL=(root) /bin/sh 
username ALL=(root) /bin/touch 
username ALL=(root) /bin/chmod
username ALL=(root) /tmp/VeeamAgent*-*-*-*
username ALL=(root) /bin/rm 
username ALL=(root) /bin/ps 
username ALL=(root) /bin/mv

Veeam Agent for Linux 2.0.1

Veeam Backup & Replication 9.5 U3a

An example of /etc/sudoers file containing proper settings for SLES 11, Veeam Agent for Linux v2.0.1/Veeam Backup & Replication v9.5 update 3a:

Defaults:username !requiretty  

username ALL=(root) NOPASSWD: /bin/hostname 
username ALL=(root) NOPASSWD: /bin/uname 
username ALL=(root) NOPASSWD: /bin/arch 
username ALL=(root) NOPASSWD: /bin/cat 
username ALL=(root) NOPASSWD: /usr/bin/test 
username ALL=(root) NOPASSWD: /bin/mkdir 
username ALL=(root) NOPASSWD: /bin/rmdir 
username ALL=(root) NOPASSWD: /bin/chown 
username ALL=(root) NOPASSWD: /usr/bin/scp
username ALL=(root) NOPASSWD: /tmp/*/veeamagentid 
 
# Agent config/backup 
username ALL=(root) NOPASSWD: /usr/bin/veeamconfig 
  
# Agent deployment 
username ALL=(root) NOPASSWD: /usr/bin/zypper 
username ALL=(root) NOPASSWD: /sbin/modinfo 
username ALL=(root) NOPASSWD: /bin/rpm 
  
# FLR Restore via console 
username ALL=(root) NOPASSWD: /bin/sh 
username ALL=(root) NOPASSWD: /bin/touch 
username ALL=(root) NOPASSWD: /bin/chmod
username ALL=(root) NOPASSWD: /tmp/VeeamAgent*-*-*-*
username ALL=(root) NOPASSWD: /bin/rm 
username ALL=(root) NOPASSWD: /bin/ps 
username ALL=(root) NOPASSWD: /bin/mv

For distributions other than SLES replace /usr/bin/zypper with a path to corresponding package manager binary.

Challenge

Cause

• After upgrade from Veeam Management Pack 8.0 Update 5 to Update 6, some Veeam Backup Reports start displaying incorrect data or the “No relevant data found” message in the output. For example, the ‘Protected VMs’ report considers a number of analyzed VMs to be Unprotected.
• Some Veeam Backup & Replication views in the Ops Mgr console show incorrect data for a number of Veeam Backup & Replication servers.
• The ‘Veeam Backup Repository Maintenance Mode Renewal’ monitor tends to change its state from Healthy to Warning once in a while (every 1 hour by default).
• Tape Job discovery failure in certain configurations.
• Tape Jobs show duplicated Increment and Full Media Pool values.
• Status of Agent Backup Jobs is not properly reflected in Ops. Manager.
• In some cases when Veeam Backup & Replication Proxy service consumes more than 2.2 GB RAM, Proxy service metrics "PercentProcessorTime" and "WorkingSet" are not collected.
  Event ID 2 with following description “Value was either too large or too small for an Int32” appears in the Application event log on a server where Veeam Backup & Replication Proxy service is running.

Solution

1. Check that you have Veeam Management Packs version 8.0.0.2467 installed. To do that, navigate to Administration > Management Packs in the Ops Mgr console.
2. Download the archive file using the link provided in the ‘More Information’ section.
3. Unpack the archive.
4. Import Veeam management packs included in the patch to the Ops Mgr console. To do that, navigate to Administration > Management Packs > Import MPs. For detailed instructions about importing management packs, see this Microsoft KB article.
5. Ensure that the Veeam Backup Monitoring and Veeam Backup Discovery management packs now have the following build numbers: Veeam Backup Monitoring MP — 8.0.0.2478, Veeam Backup Discovery MP — 8.0.0.2480.

More Information

Challenge

As this is an error with VSS and Veeam's Guest Processing technique for Domain Controllers it is relevant to all backup jobs for both virtual and physical Domain Controllers

Veeam Backup & Replication job using Application-Aware Processing to process a Domain Controller fails with one the following errors:

Unable to release guest. Details: Unfreeze error: [Backup job failed. Cannot create a shadow copy of the volumes containing writer's data. A VSS critical writer has failed. Writer name: [NTDS]. Class ID: [{b2014c9e-8711-4c5c-a5a9-3cf384484757}]. Instance ID: [{66fddc15-0e4c-4a2a-ad31-32eaf6dae8a3}]. Writer\'s state: [VSS_WS_FAILED_AT_POST_SNAPSHOT]. Error code: [0x800423f4].]

Error: VSSControl: 0 Backup job failed.
Cannot create a shadow copy of the volumes containing writer's data.
Cannot prepare the [NTDS] data to a subsequent restore operation.
Cannot process NTDS data.
Cannot create a backup copy of the BCD.

Error: VSSControl: -1 Backup job failed.
Cannot create a shadow copy of the volumes containing writer's data.
Cannot prepare the [NTDS] data to a subsequent restore operation.
Cannot process NTDS data.
Cannot create a backup copy of the BCD. Cannot get [BcdStore] object. COM error: Code: 0xffffffff

Solution

The actions listed in this section are to be performed within the Guest OS of the DC that is having these issues.

The cause is most likely one of the following. If a listed troubleshooting step requires attention, test the Veeam job after performing that troubleshooting task, before proceeding on to further troubleshooting steps.

Verify that the NTDS VSS writer is stable.

From an elevated command prompt run the following command:

vssadmin list writers

The results will appear as:

Writer name: 'NTDS'
Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
Writer Instance Id: {ee24b741-eaf7-4663-8f95-b92ae8c5e164}
State: [1] Stable
Last error: No error

If the NTDS writer is not listed as "State: [1]Stable", reboot the DC (Domain Controller).

Note: If the NTDS writer does not appear in the list, it is advisable to contact Microsoft support for their assistance in investigating why the writer is not present.

Verify that Automatic mounting of new volumes enabled.

From a Run prompt (Win+R) run the program 'diskpart'.

From within DiskPart run the following command.

automount

If the results do not show “Automatic mounting of new volumes enabled.” Run the following command:

automount enable

Verify that there are no .bak keys in the ProfileList within the Registry.

Open the Registry Editor (regedit.exe)

Within the registry navigate to:

HKLM\Software\Microsoft\Windows NT\CurrentVersion\ProfileList

There will be a list of Keys, you must remove any ending in .bak

More Information

The Majority of cases are resolved uses the above 3 troubleshooting steps. However in rare cases the WMI repository must be rebuilt. To do this please refer to the following article:
http://blogs.technet.com/b/askperf/archive/2009/04/13/wmi-rebuilding-the-wmi-repository.aspx

Challenge

Cause

Solution

Challenge

Solution

A Support ID number (sometimes referred to as a Contract Number) is a string of 8 numerical characters with typically one or two leading zeros (e.g., 01234567) and can be most easily located in one of three ways.
 
1. Viewing the License Information through the User Interface of a Veeam application.
If you have already installed a production license to your Veeam application, you may find the Support ID in the License Information window of that application. 
Please see the “More Information” section below for guides to accessing the License Information window in various Veeam applications.
 
2.  Veeam Customer Portal
https://my.veeam.com/#/licenses/production

In the Production Licenses section of the Veeam Customer portal, you can view the Support IDs of all licenses associated with your Company Account, as well as any additional licenses for which your login is the License Administrator.

3. A Veeam production .lic license file
 
If you have received a Veeam .lic license file, you may open that license file using a text editor (such as Notepad) to view the contents.  Please use caution as altering the contents of the license file will render the license unusable; only the filename may be changed.  The Support ID is typically located after “Support ID=” and usually near to the bottom.

More Information

• From the main menu, select License.

• Launch Veeam ONE Monitor.
• On the toolbar, click Help and select License Information.

• Double-click the Veeam Agent for Microsoft Windows icon in the system tray or right-click the Veeam Agent for Microsoft Windows icon in the system tray and select Control Panel.
• At the top of the window, click the About tab.
• In the Version section, click Manage license and edition.

• You can view information about the installed license. Use the following command:

• Log on to Veeam Backup Enterprise Manager using an account with the Portal Administrator role.
• Open the Configuration tab.
• Open the Licensing section on the left of the Configuration view.

• Log in to Veeam Availability Console as a Portal Administrator.
• For details, see Accessing Veeam Availability Console.
• At the top right corner of the Veeam Availability Console window, click Configuration.
• In the menu on the left, click Licensing.
• On the License Usage tab, click the license status link.

• First access the Veeam UI via Web Browser or Veeam MP Licensing View
  • MP for VMware: https://helpcenter.veeam.com/docs/mp/vmware_guide/accessing_veeam_ui.html?ver=80U5
  • MP for Hyper-V: https://helpcenter.veeam.com/docs/mp/hyperv_guide/accessing_web_ui.html?ver=80U5
• Open the Dashboard tab and click the License link located in the Current Status section.
  • MP for VMware: https://helpcenter.veeam.com/docs/mp/vmware_guide/checking_and_updating_veeam_license.html?ver=80U5
  • MP for Hyper-V: https://helpcenter.veeam.com/docs/mp/hyperv_guide/dashboard_tab.html?ver=80U5

• Go to the main menu > License.

Challenge

Cause

Solution

• Account Name
• Product Name and Edition
• Product Version
• Licensing Terms
• License Administrator
• They must all be Active on Support.

More Information

Challenge

Cause

• the < is assumed to be the beginning of a tag;
• the & is assumed to be the beginning a entity reference.

Solution

More Information

Challenge

Cause

Solution

Challenge

Cause

Solution

Challenge

Cause

What’s New 

• Support for Veeam Backup & Replication v10 compatibility.
• Support for Veeam Cloud Connect v10 compatibility. 

• 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)
    • version 4a (build 4.0.0.1553; see KB3035 for more details)
  • 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
  • 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

• Retention jobs do not fully purge the outdated service data, which causes product configuration database growth and impacts product upgrade duration. 

• 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.” 

• 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

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.   

More Information

Challenge

Product Information:

Company name: Zadara
Product Family: VPSA Object Storage
Status: Veeam Ready – Object
Classification Description: Verified object storage solutions that has been tested with Veeam Backup & Replication Cloud Tier features.

Solution

Product Details:

Model number: VPSA (Virtual Private Storage Array)
Storage Category: Software Defined Storage
Drive quantity, size, type: 72 – 10TB SATA
Storage configuration: 2-way protection policy
Firmware version: 20.01
Connection protocol and speed: 40 GbE
Additional support: All models and configurations of VPSA for S3 compatible storage with specifications equivalent or greater than the above.

General product family overview:
VPSA Object Storage is Zadara’s object storage service. It is provided on Zadara clouds, side by side with the virtual private storage array that provides block and file storage services. These are the key properties of Object Storage:

• Unlimited scalability (scaling out) in both capacity and total objects -simply keep adding drives
• User-defined object’s metadata
• 2- or 3-way distributed data protection
• Supports both S3 and Swift REST API
• Comprehensive usage reporting and metering
• Multi-tenancy at both the object storage and account levels

Veeam testing configuration:

Veeam Build Number: 10.0.0.4442

Challenge

Solution

• Following tenant’s update to version 10, encrypted backup job fails with the “Failed to decrypt encryption key” error;
• Logon attempt to Veeam Backup Enterprise Manager fails, if license is expired or enters grace period;
• Linux agent backup job fails during system collection operation, if computer has TUN (OpenVPN) adapter attached;
• Capacity Tier cleanup process fails with the “Specified case is not valid” error, if at the time of upgrade there were restore points that were removed from Performance Tier, but were still waiting, until cleanup process removes them from Cloud Tier;
• Linux FLR executed from EM fails with “Object reference not set to an instance of an object”, in case when VIX API is used;
• Linux FLR is aborted by HttpWebRequest.Timeout, if source datamover doesn’t load within 100 seconds;Application aware image processing fails for VMs running Windows Server 2008 with the “Guest is not supported” error;
• NAS Backup Copy job pointed to Exagrid or Quantum backup repository fails with the “Failed to process method” error;
• Following tenant’s backup copy job transform process, Service Provider gets “an unknown event has occurred” error in its backup server;
• Under certain circumstances deadlock occurs during backup job, if Direct NFS backup mode is used
• NetApp ONTAP 9.7 support;
• Recovery media creation fails with the “Failed to add recovery media files to the backup” error, if required restore points are being offloaded to Capacity Tier;

More Information

Challenge

Cause

Solution

More Information

[[DOWNLOAD|DOWNLOAD NOW|https://www.veeam.com/download_add_packs/virtualization-management-one-solution/old_one_9.5u4/]]
MD5: 9BFC92B616BA040A515B8737C19F7D65
SHA-1: 1E2F9030DE69E388932E9A6B67B8B4616D14739C
SHA-256: 1BD615507AE3F353CDD363B151081FF9B012010693CD4320D204B9545694603A

Should you have any questions, contact Veeam Support.

Challenge

Solution

• NetApp ONTAP 9.7 support.

• Application-aware image processing of Windows Server 2008 guests fails with the “Guest is not supported” error.
• Interaction with certain S3-compatible object storage devices fails with the "Mismatching region access attempt" error.
• Under certain circumstances, SOBR offload job may start failing with "specified cast not valid" errors following v10 upgrade.
• Deadlock possibility in the Direct NFS transport mode for VMware vSphere.
• Linux agent-based backup job fails to collect systen data if computer has TUN (OpenVPN) adapter attached.

• Backup jobs with encryption enabled fails with the “Failed to decrypt encryption key” error for tenants who upgraded from certain older Veeam Backup & Replication versions to the v10 RTM build.
• “An unknown event has occurred” error is logged when pre-v10 tenant backup copy job performs transform operation. This issue is purely cosmetic, and is due to no matching text resource for the corresponding operation in v10.

More Information

Challenge

Cause

Solution

• Migration from the local backup repository to the object storage repository.
• Migration between local backup repositories.

Understanding Variables and Parameters

$source = Get-VBORepository -Name "Source Repository Name"
$target = Get-VBORepository -Name "Object Storage Repository Name"
$data = Get-VBOEntityData -Type User  -Repository $source -Name "John Doe"
Move-VBOEntityData -From $source  -To $target -User $data

1. Run the Get-VBORepository cmdlet to get the source local repository. Provide the Name parameter value to get the repository by its name. Save the result to the $source variable.
2. Run the Get-VBORepository cmdlet to get the target object storage repository. Provide the Name parameter value to get the repository by its name. Save the result to the $target variable.
3. Run the Get-VBOEntityData cmdlet to get the backup data that you want to move. Provide the value for the Type parameter to specify the type of data that you want to move.(You   can specify one of the following types of data: user, group, site. For more information on the types of backup data, that you can get, see the Get-VBOEntityData article of   PowerShell Reference for Veeam Backup for Microsoft Office 365). Note: The Organization type of backup data is not supported for this scenario. In addition, the Move-   VBOEntityData cmdlet works only with a single user object. Therefore, for the purposes of data migration, the Get-VBOEntityData cmdlet should always be used with the "-Name"   parameter. Without this parameter, the Get-VBOEntityData will assign an array of users to the $data variable, which can not be used by the Move-VBOEntityData cmdlet.
4. Run the Move-VBOEntityData cmdlet to migrate data from the local backup repository to the target object storage repository.

• Mailbox
• ArchiveMailbox
• OneDrive
• Sites

• GroupMailbox
• GroupSite

Move-VBOEntityData -From $source -To $target -User $data -OneDrive -ArchiveMailbox

Scalability

Move-VBOEntityData -From $source -To $target -User $data -RunAsync

Automation

More Information

Challenge

When backing up to a deduplication storage appliance from Veeam Backup & Replication, performance or deduplication ratio is low without using best practice settings. 

Solution

The default options of Veeam Backup & Replication are intended for non-deduplication storage.

If you use deduplication storage systems, you need to additionally configure the backup architecture and Veeam settings to achieve best performance. Below are some hardware and software configuration options that can be used with deduplication storages. In some cases, you may need to combine more than one option, but in all cases, it is strongly encouraged that you consult your deduplication appliance vendor and/or a value added reseller to discuss individual needs.

For the general architecture planning, Veeam’s best practices is to follow the industry 3-2-1 backup rule:

3: Maintain at least three copies of your data and applications. That’s the one copy you’re using and two backups. This way, if one of your backups is unavailable for any reason (for example, if you store the backup in the same locations with the copy you use and both go down), you can still recover what you need.

2: Store your backups on at least two different types of media or storage controller logics. One reason for this is that each type of media has its own vulnerabilities, and you don’t want both of your backups susceptible to the same problem. 

For example: run your business on a general purpose fast storage system and store your backups on a storage system that is specialized for this purpose, or a separate server with local disks.

1: Keep one of the backups in a different location. Consider a crisis in your primary data center, such as a fire or power failure. If all your copies are collocated, they can all be affected, taking down your organization.

To achieve this, use the Veeam best practices. However, each deduplication storage vendor has specific unique feature sets that allow the usage of their storages in different ways. Please check the following links for vendor specific guidelines:

• Best Practices for HPE
• Best Practices for ExaGrid
• Best Practices for Dell EMC DataDomain
• Best Practices for Quantum

General Deduplication Storage Best Practices

Step 1:  Creating backups on the first site with long term retention.

Step 2: Add offsite target.

In addition to the above scenarios, you can use the following options to create an offsite copy of your data.

3. Place a deduplication storage on primary side and use object storage or tape on second site. Use Veeam backup to tape jobs or Veeam scale-out backup repository cloud tier (connection to object storages) to store data offsite.

The scenario above reflects general best practices. Please contact your deduplication storage vendor for further guidance and check the vendor links provided above for additional usable scenarios with the specific storage.
 

Best Practices For Deduplication Storage Systems

Backup Chains

• General Deduplication Storages + Backup Copy Job That Reads From Source Backup Chain (Exagrid, Quantum DXi, Infinidat InfiniGuard and Fujitsu Eternus CS800):

 

•  HPE StoreOnce Catalyst / Dell EMC DataDomain DDboost  + Copy Over WAN + Backup Copy Job:

The previous described option provides fast processing in situations that do not involve transport over WAN links. Also, optimized integration with Catalyst and Dell EMC DDBoost allows using synthetic processing. For these environments uncheck the “Read the entire restore point from source backup instead of synthesizing it from increments” but leave the weekly GFS backup enabled.

• Special Scenarios Based on Vendor Own Guidelines + Backup Job With Active Full or Synthetic Full Backup:

Inline Deduplication

However for deduplication devices that have a non deduplicated landing zone (Like ExaGrid) and backup only VMs, you can save some space: to do this, enable inline deduplication



 

Compression

Block Size

• Storage optimization: Local target (large blocks)

• Storage optimization: Local target 

Use this option for ExaGrid.

Block Alignment

Encryption

Health Check

  
Veeam Defragmentation And Compact Settings

More Information

Challenge

Cause

Solution

{
    "Version": "2012-10-17",
    "Statement": [
    {
        "Effect": "Allow",
        "Principal":
    {
        "AWS": "ARN of the role from step 6"
    },
        "Action": "sts:AssumeRole"
    }
  ]
}