Review the following list before completing a VSS restore.
Unless otherwise specified, a VSS restore refers to all restore
types that use VSS, including VSS restore, VSS fast restore, and VSS
instant restore.
- Install any Microsoft VSS-related urgent
fixes.
VSS instant restore considerations:
- In a DAG environment, stop the Microsoft Exchange
Replication Service on the active node before you run the VSS instant
restore operation.
- In an Exchange 2013 environment, stop the Exchange Search Host
Controller Service on the active node before you run the VSS instant
restore operation.
- Performing any type of Restore Into function
automatically disables VSS instant restore.
- When you perform VSS instant restores, you must make sure that
any previous background copies (that involve the volumes that are
being restored) are completed before you initiate the VSS instant
restore. This situation applies to DS8000®, Storwize® V7000, XIV®, and SAN Volume Controller (non-space-efficient)
volumes only.
- A VSS instant restore operation overwrites the entire contents
of the source volumes. However, you can avoid overwriting the source
volumes by setting the Instant Restore option
to False. This option bypasses volume-level
copy and uses file-level copy instead to restore the files from a
VSS backup that are on local shadow volumes.
- Any backup to LOCAL can
be restored only to the same system.
If you are performing a VSS restore of a database that was relocated
(system file path, log file path, or database file path), you must
use the Instant Restore function and specify
the same database name as the one you are restoring. The restore fails
if you do not specify the same database name.
When a VSS restore from local shadow volumes is performed, the
bytes transferred displays 0. This display occurs
because no data (0) is restored from the Tivoli® Storage Manager server.