As a new addition to Windows Server 2003, the Volume Shadow Copy Service (VSS) adds the ability to quickly restore data that was deleted from a volume locally or through a network-mapped drive or network file share. Over time, there will be several add-ons to Windows Server 2003 that will extend the functionality of VSS; however, what is built into the operating system already provides a series of data recovery functions. If an organization has available disk capacity, VSS should be enabled as a standard setting for a Client Servicesfocused networking environment. Configuring Shadow CopiesEnabling shadow copies for a volume can be a simple task. Because shadow copies are created on local disks, shadow copy performance is enhanced if a volume's shadow copy is written to a separate disk. This way, each disk mostly performs either a read or write operation, but not both. The Volume Shadow Copy Service is already installed and is automatically available on NTFS-formatted volumes. To enable and configure shadow copies, follow these steps:
Volume Shadow Copy Best PracticesIf volume shadow copies will be enabled on a volume, a few best practices and maintenance tasks should be followed. An appropriate size limit should be set for the shadow copies. Volumes that have many files changed daily should have larger limits than volumes whose data does not change very often. Also, shadow copies should be scheduled to run more often on heavily used drivesat least twice a day. Shadow copies should be stored on separate volumes if possible. This gives an administrator better performance backing up and restoring data to and from shadow copies. Lastly, the number of stored volume shadow copies should be monitored to keep management simple. LimitationsThe Volume Shadow Copy service should not be considered a tool for backing up and restoring servers to previous states. The Windows Server 2003 Backup utility should be used to back up the system volume and system state. Volume Shadow Copy works well for data volumes, and that is what Volume Shadow Copy backups should be focused toward. For system drives, Volume Shadow Copy may be used to restore some of the files on the system to a previous state, but Windows File Protection does a reasonably good job of protecting operating system files without volume shadow copies. Shadow Copy Management Using vssadmin.exeThe command-line tool vssadmin.exe can be used to enable shadow copies on a volume. This tool can be used to configure most of the configuration settings, including deleting previous shadow copies. Combining vssadmin.exe with a scheduled task and a batch file, shadow copy management can be somewhat automated. For example, vssadmin.exe commands can be added to a batch script and configured to delete the oldest shadow copy on a volume at 12:00 p.m. every day. To use vssadmin.exe to delete the oldest shadow copy on a volume, perform the following steps:
To schedule this operation, create a text document using Notepad, type the command in step 4, and then press Enter. Save the file with a .bat or .cmd extension. Finally, open the Control Panel, select Scheduled Tasks, and create a new task to execute this file during the desired schedule. |