Restore Considerations

• The following are supported for hidden volume:
• File/Folder Restore
• Bare Metal Recovery
• VM Recovery
• If the volume does not have a drive letter, restoring to the original location is not supported. The restore operation is blocked on the UI.
• If a database or storage group is renamed or removed after a backup, then restore to the original location fails. Either restore from the latest recovery point or restore to the disk.
• When restoring the Microsoft Exchange database to a relational database, select the relational database on the machine where the Microsoft Exchange database is backed up. If you want to restore the Microsoft Exchange database to the relational database on another machine, copy the database file on that machine and attach to the relational database.
• Restoring a Microsoft Exchange database on to a database residing on a compressed volume or directory is not recommended or supported by Microsoft. This restore can lead the database to a dismounted state. As a workaround, move the database path to an uncompressed volume or directory before restore and perform the restore again.
• For the best practices on NTFS compression in Windows, see link.

• If you modify the password of the remote destination, update the password in Settings before submitting a restore job.
• When you restore files on an NTFS volume with the encryption attribute to a non-original backup machine, the file is not accessible. This file inaccessibility is a system limitation. Also, note the following limitations:
  • For a catalog restore, the job succeeds as normal and the file is restored. However, the restored file is not accessible.
  • For a catalog-less restore, the job fails and the encrypted file is logged as inaccessible.
• If the following conditions exist in a two node CCR cluster (cluster continuous replication), the database restore succeeds but the status of the restore job is displayed as failed:
  • The active node is paused.
  • An Arcserve UDP Agent (Windows) database restore to the original location is attempted from the active node.
• If you are restoring a Microsoft SQL Server instance, the restore is incomplete if you get the following error message:
• The process cannot access the file because it is being used by another process.
• Also, the SQL Server event log reports the following error message with Event ID 8355:
• Server-level event notifications cannot be delivered. Either Service Broker is disabled in msdb, or msdb failed to start. Event notifications in other databases could be affected as well. Bring msdb online, or enable Service Broker.
• As a workaround, free up some available memory or increase the memory to 4 GB or more.
• On the Cluster Shared Volume (CSV) environment, to restore the SQL server Master database, enable the following registry key:
• Dword 32-bit Registry key: EnableCsvMasterDBRestore
• Path: HKEY_LOCAL_MACHINE\SOFTWARE\Arcserve\Unified Data Protection\Engine\VssWrap
• Values: 0 (Disabled), 1 (Enabled)
• On the restore Browse Recovery Points dialog, when you expand a directory that contains 50 or more items, a pagination window displays. If you do not browse all the pages and expand the folder, then only the items on the pages that you have browsed are selected.
• For example, the first page displays by default. If you do not browse to the other pages, only the items on the first page are selected. Navigate to the third page directly, then only the items on the first page and the third page are selected.
• For block level restore, consider the following:
• Do not run a backup job when block level restore job is running, or the backup job will fail.
• After a block level restore is performed, the next incremental backup job may get converted to verify.
• To perform a block level restore job, the target volume size must not be less than the used space of the original volume size.
• To perform a block level restore job, the target cannot be system volume.
• Performing a block level restore job to a network mapped volume is not supported.
• To perform block level restore for ReFS volume, the target OS must not be lower than the source OS. For example, restoring the ReFS volume from Windows Server 2019 to Windows Server 2016 is not supported.
• To perform a block level restore job, the target cannot be NTFS deduplication volume, the job fails at lock volume.
• To perform a block level restore job for an NTFS deduplication volume, the target OS must support NTFS deduplication and the feature must be enabled.
• To perform the block level restore job for an NTFS deduplication volume, the target OS must support NTFS deduplication and the feature must be enabled. Do not restore Windows Server 2019 / 2016 NTFS deduplication volume to Windows Server 2012.