Administrator Guide

4. In the Create Volume from Snapshot dialog box, accept the default, or enter a new name (such as Log Recovery). In the Create
Volume from Snapshot you can map to the server by clicking Change.
5. Click OK.
6. The system creates a View Volume and displays the Map Volume to Server dialog box.
7. Select the server to which you want to map the Replay View Volume. If necessary, create a new server and then click Continue.
8. On the server, in Disk Management, right-click and select Rescan Disks.
This action refreshes the iSCSI bus and make the new volume visible. You may have to rescan more than once.
9. Bring the disk online in Disk Management and assign the appropriate drive letter or mount point to the volume.
10. From a command-line interface (CLI) such as Command Prompt, type the following commands to clear the necessary attributes to
make the volume usable. Be sure to replace the text with your drive letter where necessary.
C:\> DISKPART.EXE
DISKPART> SELECT VOL <DRIVE LETTER>
DISKPART> DETAIL VOL
DISKPART> ATT VOL CLEAR READONLY
DISKPART> ATT VOL CLEAR HIDDEN
DISKPART> ATT VOL CLEAR SHADOWCOPY
DISKPART> DETAIL VOL
The volume is now fully readable and writable and can be used for recovery operations.
11. If the volume is recovered in a Windows Server failover cluster, the Windows IO structure must be reset using PowerShell. To reset
the Windows IO structure, use the −ResetSnapshotInfo parameter of the Set−DiskDevice cmdlet available in the Storage Center
Command Set for Windows PowerShell (version 6.1 and later). For information on using this cmdlet, refer to the online Storage Center
Command Set help.
NOTE:
Resetting the Windows IO structure is necessary only if you also want to make the new volume a cluster
resource. You can recover the volume on a node of a cluster without resetting the IO structure and still use it as a
non-clustered disk. However, some clustered applications (like SQL Server) cannot use a volume if it is not a
clustered disk.
Related concepts
Using Replay Manager as Part of a Disaster Recovery Plan on page 9
Local Volumes
Replay Manager provides the ability to create VSS backups of one or more local volumes mapped from the server to the Dell Storage
Center.
VSS for Local Volumes
Using the Local Volumes option, an administrator can use VSS to create backups of applications without using a Replay Manager
application-specific extension; however, it is up to the administrator to determine which volumes are needed for a complete backup set.
For example, the complete backup set for an Exchange Server with separate database volumes and log volumes for a storage group
requires the manual selection of all volumes and logs for the storage group. Therefore, the administrator must know the exact layout and
location of all storage group components to create a usable backup set.
The Local Volumes option is primarily intended for backing up and restoring volume file and print environments where the files are flat—
that is, the files are not in a transactional database-like environment. Servers that contain shared files or home directories can leverage the
Local Volumes backups because the restore points for local volumes can be easily exposed, allowing an administrator to recover files.
VSS for Shared Folders
VSS for Shared Folders, a similar technology built into Windows, provides the ability to back up a volume which in turn stores the shadow
copy on the volume itself in a hidden location. By default, snapshots in VSS for Shared Folders take place at 7:00 a.m. and 12:00 p.m., and
shadow copies are replaced as required by the amount of free disk space on the volume. The snapshot times can be adjusted, but the
snapshots should run no more than once every 60 minutes.
Using VSS for Shared Folders and Replay Manager on the same volumes is not recommended as this combination uses additional disk
space because VSS stores the deltas (data changes or differences) hidden on the volume while Storage Center determines which blocks
to freeze. This is essentially duplicating efforts on the volume.
54
Replay Manager Best Practices