Backing Up and Restoring Data for Windows Server 2003
[LEFT][CODE]http://technet.microsoft.com/en-us/library/cc875820.aspx#EEAA[/CODE]
[B]Introduction[/B]
This document will explain how to protect your servers from losing data using Backup.
Backup helps to protect data from accidental loss if your server's hardware or storage media fails. If the original data on your hard disk is accidentally erased or overwritten, or becomes inaccessible because of a hard disk malfunction, you can easily restore the data from the archived copy.
The tasks that are covered in this document are:
[LIST][*] Creating an Automated System Recovery (ASR) set. The estimated time to complete this task is 15 minutes or longer.[*] Backing up your file and print servers. The estimated time to complete this task is 10 minutes. It will take longer if you have a large amount of data you are backing up.[*] Restoring files from Backup. The estimated time to complete this task is 5 minutes.[*] Restoring your computer using an ASR set. The estimated time to complete this task is 5 minutes.[/LIST]
When the tasks listed above are performed, your server is better protected from accidental data loss or hardware malfunction.
[B]IMPORTANT[/B]: All the step-by-step instructions included in this document were developed by using the [B]Start[/B] menu that appears by default when you install your operating system. If you have modified your [B]Start[/B] menu, the steps might differ slightly.
[URL="http://technet.microsoft.com/en-us/library/cc875820.aspx#mainSection"]Top Of Page[/URL]
[B]Before You Begin[/B]
The recommendations in this document are only for file and print servers running Microsoft Windows Server 2003. The following sections cover the options that you should consider before creating backups of your servers.
[B]Select a Type of Backup Storage[/B]
The backup storage can be a hard disk drive, a separate storage device such as a tape drive, or an entire library of tapes organized and controlled by a robotic changer.
Backing up to a tape is preferable because you can create a backup and store the tape in a different location from the computer. This protects against hard disk failure as well as loss from a fire or other catastrophic event.
If you choose to back up to a hard disk, make sure that it is a hard disk separate from your primary hard disk in case your primary hard disk fails. Backing up to a hard disk drive is convenient, but does not protect against a catastrophic event.
For more information on selecting a type of backup storage, see "Backing up and recovering data" on the Microsoft TechNet Web site at [URL="http://go.microsoft.com/fwlink/?LinkId=22347"]Backing Up and Recovering Data: File and Storage Services[/URL].
[B]Select a Schedule[/B]
It is best to perform backups late at night, on weekends, or whenever the server is not being used. You can back up files that are open or in use; however, Backup may skip over some files that are held open by other processes. It is a good practice to close your applications while Backup is running to minimize the number of files that are not backed up.
You should schedule a weekly normal backup of all of your data, including the system state data for the server. A normal backup will copy all the files you select and mark each file as having been backed up. In addition, we recommend you schedule a weekly differential backup that is run on the days of the week the normal backup is not run. A differential backup copies files that have been created or changed since the last normal backup (the "differences"). It does not mark files as having been backed up so the changed file will also be backed up as part of the next normal backup. If you are performing a combination of normal and differential backups, restoring data requires that you have the last normal as well as the last differential backup. The system state data for the server includes a collection of system-specific data maintained by the operating system that must be backed up as a unit. It is not a backup of the entire system. The system state data includes the registry, COM+ Class Registration database, system files, boot files, and files under Windows File Protection. Also, you should make sure to backup any encryption keys that you have. For information on encryption keys, see the Microsoft Web site at [URL="http://technet2.microsoft.com/windowsserver/en/library/2E0186BA-1A09-42B5-81C8-3ECCA4DDDE5E1033.mspx?mfr=true"]Windows Server 2003 Product Help[/URL]. On the left pane of the Web site, click Security and then click Encrypting File System.
[B]Backup Permissions[/B]
Certain permissions and user rights are required to back up files and folders. As part of scheduling backups, you will be asked for information about who is running the backup. If you are a member of the Administrators or Backup Operators group on the local computer, you can back up any file and folder on the local computer to which the local group applies. If you are a member of the Administrators or Backup Operators group on a domain controller, you can only back up data on the domain controller and cannot backup data on other computers in the domain unless the Built-in Administrators group is added to the Domain Admins group or the Built-in Backup Operators group is added to the local Backup Operators group of a computer joining the domain.
If you are not a member of the Backup Operators group for the domain, and you want to back up files, then you must be the owner of the files and folders that you want to back up, or you must have one or more of the following permissions for the files and folders you want to back up: Read, Read & Execute, Modify, or Full Control.
[B]Creating an Automated System Recovery (ASR) Set[/B]
In addition to regular backups of your data, you should use Backup to create an Automated System Recovery (ASR) set when you first place your server into production and again before and after any major changes to the system such as software and hardware upgrades. An ASR set contains a backup of your operating system files and a bootable floppy disk that can be used to start your computer if it will not start normally. Before creating an ASR set, make sure that you have a 3.5-inch floppy disk available to make the boot disk. If your server does not have a floppy drive, you can still perform an ASR backup by copying the asr.sif and asrpnp.sif files located in the [I]systemroot[/I]\repair directory to another computer with a floppy drive, then copy those files onto a floppy disk. However, before running the ASR restore procedure, you must attach a floppy drive to your server.
[B]Note[/B]: In Windows Server 2003, the ASR set replaces the Emergency Repair Disk (ERD) which is available in Windows 2000.
[URL="http://technet.microsoft.com/en-us/library/cc875820.aspx#mainSection"]Top Of Page[/URL]
[B]Before You Begin Using Shadow Copies of Shared Folders[/B]
Shadow Copies of Shared Folders should be used in conjunction with a regular backup plan on file servers that use shared folders to provide users access to files. Shadow Copies for Shared Folders will allow users to recover their own files without costly intervention from a backup administrator. It is not a replacement for regular backups - shadow copies cannot be used for permanent archives and may be deleted depending on the storage limits and the number of shadow copies that exist on the server.
[B]Default Schedule[/B]
When you enable Shadow Copies of Shared Folders, a default schedule is created. If you keep the default settings, shadow copies of the volume will be taken at 7:00 A.M. and noon, Monday through Friday. This schedule might work for your users, but it is important to consider the particular work habits of your users before using this default schedule. You might want to consider the following questions:
[LIST][*] Do most of your users work from 9 A.M. to 5 P.M., Monday through Friday, in the same time zone?[*] Are users spread out across time zones? Does this mean that you need more copies throughout the day to cover all of the work hours?[*] How much work time can your users afford to lose? Will the default schedule of copies twice a day (7:00 A.M. and noon, Monday through Friday) provide adequate coverage?[*] How often can copies be taken without needing to add additional storage?[*] How many days of history can be retained before reaching the limit of 64 shadow copies?[/LIST]
You might want to create an initial schedule and deploy to a small group to test whether your scheduled shadow copies stay within the storage limits you set. Also, consider polling your users to find out their work habits and when they think that a shadow copy would be beneficial. This kind of information can help you determine the best schedule for your specific users.
[B]Default Storage Settings[/B]
You can only enable Shadow Copies of Shared Folders on a per-volume basis; that is, you cannot select specific shared folders and files on a volume to be copied or not copied. By default, the shadow copies will be stored on the volume that is being copied (the source volume). If you have more than one drive available on your server, you should use a separate volume on another disk to store the shadow copies. This eliminates the possibility that high input/output (I/O) load will cause shadow copies to be deleted. This is the recommended configuration for heavily used file servers.
The default storage size is 10 percent of the source volume (the volume being copied). The minimum amount of storage space that you can specify is 100 megabytes (MB). If the shadow copies are stored on a separate volume, change the default to reflect the space available on the storage volume instead of the source volume. Remember that when the storage limit is reached, older versions of the shadow copies will be deleted and cannot be restored.
When determining the amount of space to allocate for storing shadow copies, you must consider both the number and size of files that are being copied, as well as the frequency of changes between copies. For example, 100 files that only change monthly require less storage space than 10 files that change daily.
There is a limit of 64 shadow copies that can be stored on a volume. When this limit is reached, the oldest shadow copy is deleted and cannot be retrieved.
[B]Installing Client Software[/B]
In order for client computers to use Shadow Copies of Shared Folders, the Previous Versions client software must be installed on the client computers in your organization. Previous Versions is a new feature that is available for employees who use shared folders for corporate documents. If you work with files that are located in shared folders on your network, you may be able to access previous versions of your files. It is recommended that you download and place the installation package on a shared resource and send an e-mail to users about what the client does and how to install it. See "Sample E-mail" later in this section.
If your organization only has client computers running Windows XP, the Previous Versions client software can be found on a computer running Windows Server 2003 in the following location:
%systemroot%\system32\clients\twclient directory
If your organization has client computers running Windows 2000 and Windows XP, download the installation package (ShadowCopyClient.msi) from the Microsoft Web site at [URL="http://go.microsoft.com/fwlink/?LinkId=22346"]Download details: Shadow Copy Client: Accessing Shadow Copies on Windows Server 2003[/URL]. In addition, you will need to run the same installation package on Windows Server 2003. This sets a registry setting that allows access to the server from client computers running Windows 2000.
[B]Sample E-mail[/B]
Organization members:
There is a new feature called Shadow Copies of Shared Folders that is available for employees who use shared folders for documents. If you work with files that are located in shared folders on your network, you may be able to access previous versions of your files. Accessing previous versions of your files is useful because you can:
[LIST][*] Recover files that were accidentally deleted. If you accidentally delete a file, you can open a previous version and copy it to a safe location.[*] Recover from accidentally overwriting a file. If you accidentally overwrite a file, you can recover a previous version of the file.[*] Compare versions of files while working. You can use previous versions when you want to check what has changed between two versions of a file.[/LIST]
This feature has been enabled on the following file server: \\[I]NameOfServer[/I]\[I]SharedResource[/I]. Copies are scheduled to be taken at 7:00 A.M. and noon, Monday through Friday. Remember that these are copies of the files that were taken at these times. If you have worked on the file since the copy was taken and you need to revert or recover a previous version, you will lose all the work you have done since the copy was taken. Saving your work frequently is still the best way to ensure your work is not lost.
To install the software for accessing previous versions on your desktop, go to: \\[I]NameOfServer[/I]\[I]InstallationFolder[/I] and double-click [B]ShadowCopyClient.msi[/B].
[URL="http://technet.microsoft.com/en-us/library/cc875820.aspx#mainSection"]Top Of Page[/URL]
[B]Backing Up Your Servers[/B]
The following section describes the step-by-step procedures for:
[LIST][*] Creating an Automated System Recovery (ASR) set[*] Backing up your file and print servers[/LIST]
[B]Creating an ASR Set[/B]
You should use Backup to create an ASR set when you first place your server into production and again before and after any major changes to the system such as software and hardware upgrades. An ASR set is used as a last resort in system recovery, only after you have exhausted other options such as the startup options Safe Mode and Last Known Good Configuration.
[B]Requirements[/B]
[LIST][*] Credentials: To perform this procedure, you must be a member of either the Administrators or Backup Operators group on the local computer, or you must have been delegated the appropriate authority. If the computer is joined to a domain, members of the Domain Admins group will be able to perform this procedure.[*] Tools: Backup. This procedure is only for file and print servers running Microsoft Windows Server 2003
[B]Note[/B]: Screenshots in this document reflect a test environment. The domain and server names in your environment might differ slightly from the ones shown in these screenshots.[/LIST]
[B]To create an ASR set[/B]
[LIST=1][*] Click [B]Start[/B], click [B]Run[/B], type [B]ntbackup[/B], and then click [B]OK[/B].[*] The [B]Backup or Restore Wizard[/B] will appear.
If you are an advanced user, you have the option to change backup and restore settings in [B]Advanced Mode[/B]. Otherwise, click [B]Next[/B], to perform this procedure using the wizard.[*] On the [B]Backup or Restore[/B] wizard page, ensure [B]Back up files and settings[/B] is selected, and then click [B]Next[/B].[*] On the [B]What to Back Up[/B] page, ensure [B]All information on this computer[/B] is selected, and then click [B]Next[/B].[*] On the [B]Backup Type, Destination, and Name[/B] page, in [B]Select the backup type[/B], choose [B]File[/B] if you want to back up files and folders to a file, or, if you want to back up files and folders to a tape, choose a tape device. In [B]Choose a place to save your backup[/B], click the drop-down menu or click [B]Browse[/B] to choose a location to save your backup. In [B]Type a name for this backup[/B], type a descriptive name for the backup, and then click [B]Next[/B].
[IMG]http://i.technet.microsoft.com/Cc875820.ntback01%28en-us,TechNet.10%29.gif[/IMG][*] On the [B]Completing the Backup or Restore Wizard[/B] page, verify that all of the information is correct, and then click [B]Finish[/B] to start creating the ASR set. The process of creating the ASR set may take at least 15 minutes.[*] When the [B]Backup Utility[/B] message appears, follow the directions and insert a 1.44 megabyte (MB) floppy disk into drive A, and then click [B]OK[/B]. If your server does not have a floppy drive, you can still perform an ASR backup by copying the asr.sif and asrpnp.sif files located in the [I]systemroot\[/I]repair directory to another computer with a floppy drive, then copy those files onto a floppy disk. However, before running the ASR restore procedure, you must attach a floppy drive to your server.[*] When the [B]Backup Utility[/B] message appears letting you know you can remove the floppy disk, make sure you label the disk with the information given.
[URL="http://technet.microsoft.com/en-us/library/Cc875820.ntback02_big%28en-us,TechNet.10%29.gif"][IMG]http://i.technet.microsoft.com/Cc875820.ntback02%28en-us,TechNet.10%29.gif[/IMG][/URL][*] When the backup is complete, the [B]Backup Progress[/B] dialog box will indicate that the backup is finished. To view additional information about what happened during the backup process, click [B]Report[/B] to open the backup report in Notepad. When you are finished, click [B]Close[/B].
[IMG]http://i.technet.microsoft.com/Cc875820.ntback03%28en-us,TechNet.10%29.gif[/IMG][*] After creating the ASR set, label this floppy disk and backup media carefully and keep them together. To use the backup media, you must have the floppy disk that you created with that set of media. You cannot use a floppy disk created at a different time or with a different set of media. You must also have your installation CD available at the time you perform Automated System Recovery.
Keep the ASR set in a secure location. The ASR set contains information about your system's configuration that could be used to do harm to your system.[/LIST]
[B]Backing Up Your File and Print Servers[/B]
To protect your servers, you should schedule regular backups of all of the data. We recommend that you schedule a weekly normal backup of all of your data, including the system state data for the server. A normal backup will copy all the files you select and mark each file as having been backed up. In addition, we recommend you schedule a weekly differential backup. A differential backup copies files that have been created or changed since the last normal backup (the "differences").
[B]Requirements[/B]
[LIST][*] Credentials: To perform this procedure, you must be a member of either the Administrators or Backup Operators group on the local computer, or you must have been delegated the appropriate authority. If the computer is joined to a domain, members of the Domain Admins group will be able to perform this procedure.[*] Tools: Backup.[/LIST]
[B]To schedule a weekly normal backup[/B]
[LIST=1][*] Click [B]Start[/B], click [B]Run[/B], type [B]ntbackup[/B], and then click [B]OK[/B].[*] The [B]Backup or Restore Wizard[/B] will appear. Click [B]Next[/B].[*] On the [B]Backup or Restore[/B] wizard page, ensure [B]Back up files and settings[/B] is selected, and then click [B]Next[/B].[*] On the [B]What to Back Up[/B] page, click [B]Let me choose what to back up,[/B] and then click [B]Next[/B].
To include all data on your computer in the scheduled backup, click [B]All information on this computer[/B].[*] On the [B]Items to Back Up[/B] page, click the items to expand their contents. Select the check boxes for any drives or folders that contain data that should be backed up on a regular basis, and then click [B]Next[/B].
[IMG]http://i.technet.microsoft.com/Cc875820.ntback04%28en-us,TechNet.10%29.gif[/IMG][*] On the [B]Backup Type, Destination, and Name[/B] page, in [B]Choose a place to save your backup[/B], click the drop-down menu or click [B]Browse[/B] to choose a location to save your backup. In [B]Type a name for this backup[/B], type a descriptive name for the backup, and then click [B]Next[/B].
[IMG]http://i.technet.microsoft.com/Cc875820.ntback05%28en-us,TechNet.10%29.gif[/IMG][*] On the [B]Completing the Backup or Restore Wizard[/B] page, click [B]Advanced[/B].[*] On the [B]Type of Backup[/B] page, in the drop-down menu, click [B]Normal[/B], and then click [B]Next[/B].
[IMG]http://i.technet.microsoft.com/Cc875820.ntback06%28en-us,TechNet.10%29.gif[/IMG][*] On the [B]How to Back Up[/B] page, select the [B]Verify data after backup[/B] check box, and then click [B]Next[/B].[*] On the [B]Backup Options[/B] page, ensure the [B]Append this backup to the existing backups[/B] option is selected, and then click [B]Next[/B].
[IMG]http://i.technet.microsoft.com/Cc875820.ntback07%28en-us,TechNet.10%29.gif[/IMG][*] On the [B]When to Back Up[/B] page, under [B]When do you want to run the backup[/B], click [B]Later[/B].[*] Under [B]Schedule entry[/B], type a descriptive name in [B]Job name[/B], and then click [B]Set Schedule[/B].
[IMG]http://i.technet.microsoft.com/Cc875820.ntback08%28en-us,TechNet.10%29.gif[/IMG][*] In the [B]Schedule Job[/B] dialog box, in [B]Schedule Task[/B], click [B]Weekly[/B] in the drop-down menu.[*] In [B]Start time[/B], use the up and down arrows to select the appropriate time for the backup to start. Click [B]Advanced[/B] to specify a start date and an end date for the scheduled task or to specify whether the scheduled task runs repeatedly at a particular interval.[*] Under [B]Schedule Task Weekly[/B], select one or more days when you would like to have a backup created, and then click [B]OK[/B].
[IMG]http://i.technet.microsoft.com/Cc875820.ntback09%28en-us,TechNet.10%29.gif[/IMG][*] In the [B]Set Account Information[/B] dialog box, in [B]Run as[/B], type the domain or workgroup and user name of the account that is authorized to perform backup and restore operations. Use the format [I]domain[/I]\[I]username[/I] or [I]workgroup[/I]\[I]username[/I]. In [B]Password[/B], type the password for the user account. Retype the password in [B]Confirm password[/B], and then click [B]OK[/B].
[IMG]http://i.technet.microsoft.com/Cc875820.ntback10%28en-us,TechNet.10%29.gif[/IMG] You need to update the password specified in the scheduled task anytime the account's password changes or expires to ensure the backup job runs as scheduled.[*] On the [B]Completing the Backup or Restore Wizard[/B] page, confirm the settings, and then click [B]Finish[/B].
[B]Notes[/B]: We recommend creating a summary backup log which, when regularly reviewed, will help ensure that the backup was successfully completed. To do this, click the [B]Tools[/B] menu, and then click [B]Options[/B]. On the [B]Backup Log[/B] tab, select [B]Summary[/B].
If it's determined that the backup is not occurring, review the status of the scheduled task for possible reasons. To review scheduled tasks, click [B]Start[/B], click [B]Control Panel[/B], and then double-click [B]Scheduled Tasks[/B].[/LIST]
[B]To schedule a weekly differential backup[/B]
[LIST=1][*] Click [B]Start[/B], click [B]Run[/B], type [B]ntbackup[/B], and then click [B]OK[/B].[*] The [B]Backup or Restore Wizard[/B] will appear. Click [B]Next[/B].[*] On the [B]Backup or Restore[/B] wizard page, ensure [B]Back up files and settings[/B] is selected, and then click [B]Next[/B].[*] On the [B]What to Back Up[/B] page, click [B]Let me choose what to back up[/B], and then click [B]Next[/B].[*] On the [B]Items to Back Up[/B] page, click the items to expand their contents. Select the [B]System State[/B] check box and select other check boxes for any drives or folders that contain data that should be backed up on a regular basis, and then click [B]Next[/B].
[IMG]http://i.technet.microsoft.com/Cc875820.ntback11%28en-us,TechNet.10%29.gif[/IMG][*] On the [B]Backup Type, Destination, and Name[/B] page, in [B]Choose a place to save your backup[/B], click the drop-down menu or click [B]Browse[/B] to choose a location to save your backup. In [B]Type a name for this backup[/B], type a descriptive name for the backup, and then click [B]Next[/B].
[IMG]http://i.technet.microsoft.com/Cc875820.ntback12%28en-us,TechNet.10%29.gif[/IMG][*] On the [B]Completing the Backup or Restore Wizard[/B] page, click [B]Advanced[/B].[*] On the [B]Type of Backup[/B] page, in [B]Select the type of backup[/B], click [B]Differential[/B], and then click [B]Next[/B].
[IMG]http://i.technet.microsoft.com/Cc875820.ntback13%28en-us,TechNet.10%29.gif[/IMG][*] On the [B]How to Back Up[/B] page, select the [B]Verify data after backup[/B] check box, and then click [B]Next[/B].[*] On the [B]Backup Options[/B] page, ensure the [B]Append this backup to the existing backups[/B] option is selected, and then click [B]Next[/B].
[IMG]http://i.technet.microsoft.com/Cc875820.ntback14%28en-us,TechNet.10%29.gif[/IMG][*] On the [B]When to Back Up[/B] page, under [B]When do you want to run the backup[/B], click [B]Later[/B]. Under [B]Schedule entry[/B], type a descriptive name in [B]Job name[/B], and then click [B]Set Schedule[/B].
[IMG]http://i.technet.microsoft.com/Cc875820.ntback15%28en-us,TechNet.10%29.gif[/IMG][*] In the [B]Schedule Job[/B] dialog box, in [B]Schedule Task[/B], select [B]Weekly[/B] from the drop-down menu.[*] In [B]Start time[/B], use the up and down arrows to select the appropriate time for the backup to start, and then select the days you want the differential backup to run each week. It is recommended that you schedule a differential backup on the days that a normal backup is not run. Click [B]Advanced[/B] to specify a start date and an end date for the scheduled task or to specify whether the scheduled task runs repeatedly at a particular interval. Click [B]OK[/B] when finished.
[IMG]http://i.technet.microsoft.com/Cc875820.ntback16%28en-us,TechNet.10%29.gif[/IMG][*] In the [B]Set Account Information[/B] dialog box, in [B]Run as[/B], type the domain or workgroup and user name of the account that is authorized to perform backup and restore operations. Use the format [I]domain[/I]\[I]username[/I] or [I]workgroup[/I]\[I]username[/I]. In [B]Password[/B], type the password for the user account. Retype the same password in [B]Confirm password[/B], and then click [B]OK[/B].
[IMG]http://i.technet.microsoft.com/Cc875820.ntback17%28en-us,TechNet.10%29.gif[/IMG] You need to update the password specified in the scheduled task anytime the account's password changes or expires to ensure the backup job runs as scheduled.[*] On the [B]Completing the Backup or Restore Wizard[/B] page, confirm your settings, and then click [B]Finish[/B].
[B]Notes[/B]: We recommend creating a summary backup log which, when regularly reviewed, will ensure that the backup was successfully completed. To do this, click the [B]Tools[/B] menu, and then click [B]Options[/B]. On the [B]Backup Log[/B] tab, select [B]Summary[/B].
If it's determined that the backup is not occurring, review the status of the scheduled task for possible reasons. To review scheduled tasks, click [B]Start[/B], click [B]Control Panel[/B], and then double-click [B]Scheduled Tasks[/B].[/LIST]
[B]Verifying Data after Backup is Complete[/B]
Data that is backed-up can be verified against a checksum that is also stored on the backup. When data is backed up, a checksum is calculated for every file that is backed up. Backup stores the checksum with the file itself. When data is verified, the file is read from the backup; the checksum is recalculated and then compared with the value stored in the backup. It is recommended that you verify backups of data files only; system backups are difficult to verify due to the large number of changes that happen to system files on a continual basis. Some data files that were in use during the backup might also cause verification errors, but you can generally ignore these errors. If there are a large number of verification errors, there may be a problem with the media or the file you are using to back up data. If this occurs, use different media or designate another file and run the backup operation again.
To verify data after backup, in the [B]Backup or Restore Wizard,[/B] on the [B]How to Back Up[/B] page, select the [B]Verify data after backup[/B] check box.
[B]Note[/B]: Selecting this option might substantially increase the time it takes to perform a backup.
[URL="http://technet.microsoft.com/en-us/library/cc875820.aspx#mainSection"]Top Of Page[/URL]
[B]Enabling Shadow Copies of Shared Folders on a File Server[/B]
When you enable Shadow Copies of Shared Folders on your file server, snapshots of the content of shared files and folders will be taken. These snapshots can then be accessed using the Previous Versions client. By enabling Shadow Copies of Shared Folders, you also create a default schedule that will create shadow copies at 7:00 A.M. and noon, Monday through Friday. There will also be a limit set on the amount of space that can be used to store the shadow copies. The default storage size is 10 percent of the source volume (the volume being copied). When the storage limit is reached, older versions of the shadow copies will be deleted and cannot be restored.
[B]Requirements[/B]
[LIST][*] Credentials: To perform this procedure, you must be a member of the Administrators group on the local computer, or you must have been delegated the appropriate authority. If the computer is joined to a domain, members of the Domain Admins group will be able to perform this procedure.[*] Tools: Computer Management.[/LIST]
[B]To enable Shadow Copies of Shared Folders[/B]
[LIST=1][*] Click [B]Start[/B], point to [B]All Programs[/B], point to [B]Administrative Tools[/B], and then click [B]Computer Management[/B].[*] In the console tree, right-click [B]Shared Folders[/B], point to [B]All Tasks[/B], and click [B]Configure Shadow Copies[/B].
[URL="http://technet.microsoft.com/en-us/library/Cc875820.ntback18_big%28en-us,TechNet.10%29.gif"][IMG]http://i.technet.microsoft.com/Cc875820.ntback18%28en-us,TechNet.10%29.gif[/IMG][/URL][*] In the [B]Shadow Copies[/B] dialog box, click the volume where you want to enable Shadow Copies of Shared Folders, and then click [B]Enable[/B]. The [B]Enable Shadow Copies[/B] dialog box will appear. Click [B]Yes[/B] to confirm that you want to enable shadow copies on the volume.
[IMG]http://i.technet.microsoft.com/Cc875820.ntback19%28en-us,TechNet.10%29.gif[/IMG] To create a single shadow copy of the selected volume, click [B]Create Now[/B].
[B]Note[/B]: To change default schedule settings, click [B]Settings[/B]. In the [B]Settings[/B] dialog box, click [B]Schedule[/B]. Change the settings in the task scheduler as appropriate. The default schedule is 7:00 A.M. and 12:00 noon, Monday through Friday. It is recommended that you do not schedule copies to be taken more frequently than once an hour.
[IMG]http://i.technet.microsoft.com/Cc875820.ntback20%28en-us,TechNet.10%29.gif[/IMG][*] In the [B]Shadow Copies[/B] dialog box, click [B]OK[/B] to complete the procedure.[/LIST]
[URL="http://technet.microsoft.com/en-us/library/cc875820.aspx#mainSection"]Top Of Page[/URL]
[B]Restoring Data from Backup[/B]
There are several ways to restore your server depending on what files need to be restored and whether your system will start normally. The following procedures are covered in this section:
[LIST][*] Restoring files from Backup[*] Restoring your computer using an ASR set[/LIST]
[B]Restoring Files from Backup[/B]
If the original data on your hard disk is accidentally erased or overwritten, or becomes inaccessible because of a hard disk malfunction, the data may be restored from the back up copy.
[B]Requirements[/B]
[LIST][*] Credentials: To perform this procedure, you must be a member of either the Administrators or Backup Operators group on the local computer, or you must have been delegated the appropriate authority. If the computer is joined to a domain, members of the Domain Admins group will be able to perform this procedure.[*] Tools: Backup. If you are performing a combination of normal and differential backups, restoring files and folders requires that you have the last normal as well as the last differential backup.[/LIST]
[B]To restore files from Backup[/B]
[LIST=1][*] Click [B]Start[/B], click [B]Run[/B], type [B]ntbackup[/B], and then click [B]OK[/B].[*] The [B]Backup or Restore Wizard[/B] will appear. Click [B]Next[/B].[*] On the [B]Backup or Restore[/B] page, click [B]Restore files and settings[/B], and then click [B]Next[/B].[*] On the [B]What to Restore[/B] page, click the items to expand their contents. Select any drives or folders that contain data that should be restored, and then click [B]Next[/B].
[IMG]http://i.technet.microsoft.com/Cc875820.ntback21%28en-us,TechNet.10%29.gif[/IMG][*] On the [B]Completing the Backup or Restore Wizard[/B] page, if you want to change any of the advanced restore options, such as restoring security settings and junction point data, click [B]Advanced[/B]. When you are done setting advanced restore options, click [B]OK[/B]. Verify that all of the settings are correct, and then click [B]Finish[/B].[/LIST]
[B]Restoring Your Computer Using an ASR Set[/B]
ASR should be used as a last resort in system recovery, only after you have exhausted other options such as the startup options Safe Mode and Last Known Good Configuration. For more information about these and other recovery options, see "Repair overview" in "Related Information" later in the document.
Automated System Recovery will not restore your data files. For more information, see "Restoring Files from Backup" earlier in this document.
[B]Requirements[/B]
[LIST][*] The person performing the first part of this procedure must be physically present at the computer and does not need to be a member of the Administrators or Backup Operators group on the local computer. However, to restore the data to the computer after the system has been restored, they must be a member of either the Administrators or Backup Operators group on the local computer, or have been delegated the appropriate authority. If the computer is joined to a domain, members of the Domain Admins group will be able to perform this procedure.[*] Tools: Your previously created ASR set, your previously created backup media and the floppy disk that you created with that set of media, and the original Windows Server 2003 installation CD.[/LIST]
[B]To restore your computer from an ASR set[/B]
[LIST=1][*] Insert the original Windows Server 2003 installation CD into your CD drive.[*] Restart your computer. If you are prompted to press a key to start the computer from CD, press the appropriate key.[*] Press [B]F2[/B] when prompted at the beginning of the text-only mode section of Setup. You will be prompted to insert the ASR floppy disk you have previously created.[*] Follow the directions on the screen.[/LIST]
[URL="http://technet.microsoft.com/en-us/library/cc875820.aspx#mainSection"]Top Of Page[/URL]
[B]Restoring Previous Versions of Files and Folders[/B]
With the Previous Versions client, you may be able to access previous versions of your files that are located in shared folders on your network. This feature is available when Shadow Copies of Shared Folders is enabled on the server.
Accessing previous versions of your files is useful because you can:
[LIST][*] View previous versions to compare versions of a file while working. You can use previous versions when you want to check what has changed between two versions of a file.[*] Recover files that were accidentally deleted. If you accidentally delete a file, you can open a previous version and copy it to a safe location.[*] Recover from accidentally overwriting a file. If you accidentally overwrite a file, you can recover a previous version of the file.[/LIST]
[B]Requirements[/B]
[LIST][*] Credentials: To perform this procedure, you must at least have Read permissions on the file to view or copy a previous version and Read & Execute permissions in order to restore the file.[*] Tools: Previous Versions client. The client is installed by default on computers running Windows Server 2003. For more information about installing the Previous Versions client, see "Before You Begin Using Shadow Copies of Shared Folders" earlier in this document.[/LIST]
[B]To view a previous version of a file or folder[/B]
[LIST=1][*] Locate the file that you want to view a previous version of (on the network), right-click the file, and then click [B]Properties[/B].[*] On the [B]Previous Versions[/B] tab, click the version you want to view, and then click [B]View[/B].
[B]Notes[/B]: If there are no previous versions listed, the file has not changed since the oldest copy was taken.
If you do not see the [B]Previous Versions[/B] tab, the client is not installed.
Previous versions are read-only. You cannot make changes to the previous version of the file as it exists on the server.[/LIST]
[B]To copy a previous version of a file to a new location[/B]
[LIST=1][*] Locate the file that you want to copy (on the network), right-click the file, and then click [B]Properties[/B].[*] On the [B]Previous Versions[/B] tab, click the version of the file that you want to copy, and then click [B]Copy[/B].[*] In the [B]Copy Items[/B] dialog box, click a new location to place the file, and then click [B]Copy[/B].
[B]Notes[/B]: If there are no previous versions listed, the file has not changed since the oldest copy was taken.
If you do not see the [B]Previous Versions[/B] tab, the client is not installed.
When you use [B]Copy[/B], the file permissions will be set to the default permissions for the directory where the copy of the file is placed.[/LIST]
[B]To restore a previous version of a file[/B]
[LIST=1][*] Locate the file that you want to restore (on the network), right-click the file, and then click [B]Properties[/B].[*] On the [B]Previous Versions[/B] tab, click the version of the file that you want to restore, and then click [B]Restore[/B]. A warning message about restoring a previous version will appear. Click [B]Yes[/B] to complete the procedure.
[B]Notes[/B]: Restoring a previous version will delete the current version. If you choose to restore a previous version of a folder, the folder will be restored to its state at the date and time of the version you selected. You will lose any changes that you have made to files in the folder since that time. If you do not want to delete the current version of a file or folder, use [B]Copy[/B] to copy the previous version to a different location.
If there are no previous versions listed, the file has not changed since the oldest copy was taken.
If you do not see the [B]Previous Versions[/B] tab, the client is not installed.
When you restore a previous version of a folder, files in the current folder that were not contained in the previous version of the folder will not be erased.
When you restore a file, the file permissions will not be changed; permissions will remain the same as they were before the restoration. When you copy a previous version of a file, the permissions will be set to the default permissions for the directory where the copy of the file is placed.
Restoring a large directory puts a heavy load on the file server and can result in previous versions being deleted. Try to restore individual files instead of entire directories whenever possible.[/LIST]
[B]To recover a file that was accidentally deleted[/B]
[LIST=1][*] Locate the folder where the deleted file was stored (on the network), right-click the folder, and then click [B]Properties[/B].[*] On the [B]Previous Versions[/B] tab, double-click the most recent version of the folder that contains the file that you want to recover. A list of files that are stored in that previous version will appear.[*] Right-click the file that was accidentally deleted, and then click [B]Copy[/B].[*] Right-click the location where you want to place the file, and then click [B]Paste[/B].
[B]Notes:[/B]When you copy a file, file permissions will be set to the default permissions for the directory where the copy of the file is placed.
When you recover a file that was accidentally deleted, you are copying a previous version. You will lose any changes made to the file after the last previous version was created.
To recover a deleted folder, go to a previous version of the parent folder to view and select the folder to copy.[/LIST]
[URL="http://technet.microsoft.com/en-us/library/cc875820.aspx#mainSection"]Top Of Page[/URL]
[B]Related Information[/B]
For more information about backing up and restoring data, see the following:
[LIST][*] "Backing up and recovering data" on the Microsoft TechNet Web site at [URL="http://go.microsoft.com/fwlink/?LinkId=22347"]Backing Up and Recovering Data: File and Storage Services[/URL].[*] "Repair overview" on the Microsoft TechNet Web site at [URL="http://go.microsoft.com/fwlink/?LinkId=22448"]Repair overview: File and Storage Services[/URL].[*] "Checklist: Recovering a system that will not start" on the Microsoft TechNet Web site at [URL="http://go.microsoft.com/fwlink/?LinkId=22449"]Recover from a system failure using Automated System Recovery: File and Storage Services[/URL].[/LIST]
For more information about Shadow Copies of Shared Folders, see the following:
[LIST][*] "Shadow Copies of Shared Folders" on the Microsoft TechNet Web site at [URL="http://go.microsoft.com/fwlink/?LinkId=22349"]Shadow Copies for Shared Folders: File and Storage Services; Data Recovery[/URL].[*] "Introduction to Shadow Copies of Shared Folders" on the Microsoft Web site at [URL="http://go.microsoft.com/fwlink/?LinkId=22350"]Volume Shadow Copy Service Technical Reference: Data Recovery[/URL].[*] "Shadow Copies of Shared Folders: Frequently Asked Questions" on the Microsoft Web site at [URL="http://go.microsoft.com/fwlink/?LinkId=22351"]Volume Shadow Copy Service Technical Reference: Data Recovery[/URL].[/LIST]
For more information about Backup technologies, see the following:
"Understanding Backup" on the Microsoft Web site at [URL="http://go.microsoft.com/fwlink/?LinkId=22348"]Understanding Backup: File and Storage Services[/URL]
[/LEFT]
Saving and restoring existing Windows shares
[LEFT][CODE]http://support.microsoft.com/kb/125996/en-us[/CODE]
If you need to complete any of the following procedures, you can save the share names that exist on the original Microsoft Windows installation, including any permissions assigned to those shares:
[LIST][*]Reinstall Windows over an existing installation (a clean install, not an upgrade).[*]Move all of your data drives from one server to another.[*]Install Windows to another folder or drive on a computer that already has Windows installed[/LIST]
For information on how administrators can migrate data safely and reliably from one file server to another file server, visit the following Microsoft Web site:
[URL="http://www.microsoft.com/windowsserver2008/en/us/fsmt.aspx"]Microsoft File Server Migration Toolkit[/URL] ([URL="http://www.microsoft.com/windowsserver2008/en/us/fsmt.aspx"]Windows Server 2008 R2: Microsoft File Server Migration[/URL])
[B]Important[/B] This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base: [URL="http://support.microsoft.com/kb/322756/"]322756[/URL] ([URL="http://support.microsoft.com/kb/322756/"]How to back up and restore the registry in Windows XP[/URL] ) How to back up and restore the registry in Windows
To save only the existing share names and their permissions on Windows follow these steps.
[B]Note[/B] This procedure applies only to NetBIOS shares and not to Macintosh volumes.
[LIST=1][*]On the existing Windows installation that contains the share names and permissions that you want to save, start Registry Editor (Regedt32.exe).[*]From the HKEY_LOCAL_MACHINE subtree, go to the following key:[B]SYSTEM\CurrentControlSet\Services\LanmanServer\Shares[/B][*]Save or export the registry key.
[LIST][*]For Windows NT and Windows 2000, click [B]Save Key[/B] on the [B]Registry[/B] menu.[*]For Windows Server 2003, click [B]Export[/B] on the [B]File[/B] menu.[/LIST]
[*]Type a new file name (a file extension is not necessary), and then save the file to a floppy disk.[*]Reinstall Windows.[*]Run Registry Editor (Regedt32.exe).[*]From the HKEY_LOCAL_MACHINE subtree, go to the following key:[B]SYSTEM\CurrentControlSet\Services\LanmanServer\Shares[/B][*]Restore or import the registry key.
[LIST][*]For Windows NT and Windows 2000, click [B]Restore[/B] on the [B]Registry[/B] menu.[*]For Windows Server 2003, click [B]Import[/B] on the [B]File[/B] menu.[/LIST]
[*]Type the path and file name of the file that you saved in steps 3 and 4.
[B]Caution[/B] This step overrides the shares that already exist on the Windows computer with the share names and permissions that exist in the file you are restoring. You are warned about this before you restore the key.[*]Restart the server.[/LIST]
[B]Note[/B] After you complete this procedure, if you decide that you should not have restored the Shares key, restart the computer and press the SPACEBAR to use the last known good configuration. After you restore the shares key, the shares can be used by network clients. If you run the [B]net shares[/B] command on the server, the server displays the shares; however, File Manager does not display the shares. To make File Manager aware of the newly restored shares, create any new share on the server. File Manager displays all of the other shares after you restart the server or stop and restart the Server service.
In Windows NT 3.5, if you click [B]Stop Sharing[/B] in File Manager, the restored shares are still displayed, but they are dimmed.
Only permissions for domain users are restored. If a local user was created in the previous Windows NT installation, that local user's unique security identifier (SID) is lost. NTFS permissions on folders and files are not affected when you save and restore the shares key.
[B]Note[/B]: This article does not apply to Windows Server 2008 or Windows Server 2008 R2.
[B]APPLIES TO[/B]
[LIST][*]Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)[*]Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)[*]Microsoft Windows Server 2003, Standard Edition (32-bit x86)[*]Microsoft Windows Server 2003, Web Edition[*]Microsoft Windows 2000 Server[*]Microsoft Windows 2000 Advanced Server[*]Microsoft Windows 2000 Professional Edition[*]Microsoft Windows 2000 Datacenter Server[*]Microsoft Windows NT Advanced Server 3.1[*]Microsoft Windows NT Server 3.5[*]Microsoft Windows NT Server 3.51[*]Microsoft Windows NT Server 4.0 Standard Edition[*]Microsoft Windows NT Workstation 3.1[*]Microsoft Windows NT Workstation 3.5[*]Microsoft Windows NT Workstation 3.51[*]Microsoft Windows NT Workstation 4.0 Developer Edition[/LIST]
[/LEFT]
