Users Guide

Understanding Backup Types
A Replay Manager backup can be either a Windows VSS backup or a VMware backup.
Windows Backup Types
For Windows applications (Exchange, SQL Server, and Hyper-V), Replay Manager creates backups using the Microsoft Volume Shadow
Copy Services (VSS).
There are two types of VSS backups:
Copy backup—Backs up all les, including all application and log les on the selected volumes. All information on which les were
changed or deleted is preserved; therefore, copy backups do not aect the sequence of incremental and dierential backups that might
happen independent of the copy backup.
Full backup—Might truncate transactional log les after the backup nishes depending on the application. Once all transactions from a
log are applied to the database, the database sets a checkpoint (or a marker) to the last committed transaction. Once the checkpoint is
set, the logs that have been applied may be truncated or deleted.
By default, Replay Manager Service for Windows takes VSS copy backups. SQL Server transaction logs are not truncated with either a
copy or full backup.
NOTE: If backing up Exchange data and using a thirdparty backup application such as Windows Backup, NetBackup, or
BackupExec, it is important to understand which application handles the transaction logs: Replay Manager, or the third party
backup application. If you currently use any type of incremental schedule within your backup application, remember that the
backup application relies upon the transaction logs to create a successful backup. If Replay Manager is truncating logs in a full
backup, then the transaction logs would not be available to the third party application.
Related link
Summary of Backup Set Options
VMware Backup Types
During backups of VMware datastores and virtual machines, Replay Manager Service for VMware takes a temporary VMware snapshot.
Backup set options specic to VMware include the following:
If the Include virtual machine memory in vSphere snapshot option is selected in the backup set denition, the backup includes the
internal state of the virtual machine.
If the Create Storage center Replay of Physical RDMs option in selected in the backup set denition, the backup includes the physical
mode raw device mappings (pRDMs).
NOTE
: Because vSphere cannot create a VMware snapshot of physical RDMs, the physical RDM Replays are unlikely to be
consistent with the Replay containing the .vmdk le for the same virtual machine.
NOTE: Windows guest virtual machines that store data for VSS aware applications (like SQL Server or Exchange) on physical
RDMs, or iSCSI volumes mapped directly to the guest, may fail to create snapshots when using the VMware Virtual Machines
backup extension. This is a known issue with Windows VSS snapshot integration and VMware snapshot creation. If a failure
occurs, use the vSphere Client to change the value of the disk.EnableUUID parameter to FALSE. For further instructions,
see: https://kb.vmware.com/KB/1031298
NOTE: Including virtual machine memory can signicantly increase the time it required to create a snapshot and may cause the
backup creation to take longer than expected.
Related link
Summary of Backup Set Actions
30
Backing Up and Restoring Data