WINDOWS 1002000 PROFESSIONAL RESOURCE KIT [Electronic resources] نسخه متنی

Using the Backup Tool

Backup is a graphical tool that is used with a variety of storage media to back up and restore files on volumes using any file system supported by Windows 2000. Backup also simplifies archiving and allows you to use the Windows 2000 Job Scheduler for automating backup jobs.

Tasks such as mounting and dismounting a tape or disk are done by Removable Storage. It tracks and controls backup cartridges, which are usually organized into pools, on storage devices and allows applications such as Backup to share robotic changers and cartridge libraries. After it is started, Removable Storage is transparent, so you only need access to it when you change cartridges, not when you perform a backup or restore operation.

NOTE

---

Backing up to files on random access media, such as hard or removable disks, is not managed by Removable Storage.

Because of the use of Removable Storage technology, the target media of Backup is not drive-oriented in Windows 2000 as it is in versions of Backup that are included in Windows NT. In the past, backup data was written to drives (for example, tape or disk drives).

In Windows 2000, Backup uses cartridges in media pools to store backed up data. Backup still writes backup data to tapes or files on disks; however, the media is managed by Removable Storage, which references media instead of drives. Backup recognizes each cartridge to which it gains access as either a member of an existing media pool or as unallocated media. The significance of this change can be seen when a user sets up a regular backup schedule.

In the past, users scheduled Backup to run on specified days, and they could use any cartridge for that day's job. Removable Storage tracks the use of all cartridges, so it does not allow indiscriminate use of unrecognized cartridges in the applications it manages.

Each cartridge that is used by Backup must be added to Backup's application media pool and it requires its own scheduled job to be automated. If you choose to backup your data to a different cartridge each night over the course of a week, you have to create seven scheduled jobs, or one job for each tape. This is because the Job Scheduler feature included with Backup requires that you specify a particular cartridge name in the scheduled job. (Each cartridge has a unique name recorded in the header of the data area.) If you place the Tuesday cartridge in the recording drive on Friday, the scheduled job fails because not all of the required criteria for completing the job were met.

You can avoid this potential problem in one of two ways. You can run the backup job manually the first time the cartridge is used and assign the cartridge a unique name (such as "Monday") in the process. You can also use the Removable Storage console to assign a unique name to the cartridge and place that cartridge in Backup's application media pool. After the cartridge has a unique name assigned to it, you can create a set of scheduled backup jobs, one for the name of each cartridge that is to be used. As long as the specified cartridge is used with the correct scheduled job, all scheduled backups can run normally.

NOTE

---

If you use a multicartridge library drive (such as a tape drive that contains a magazine of tapes) and set Backup to always draw cartridges from the free media pool, you only need to schedule one job. However, each previously used cartridge must be erased, which places it back into the free media pool, before it can be used again.

Selecting Backup Media

Backup displays a list of all available storage devices on the Backup destination list in the Backup tab. If no external devices are detected, you can back up to a file on disk. If you want to back up to media that is not managed by Removable Storage, make sure that the disk is loaded in an appropriate storage device.

NOTE

---

If you are backing up to cartridges that are managed by Removable Storage, the Removable Storage system service must be running (you can confirm this in the Services console). To back up to new cartridges, first make the cartridges available in the media pool. If you want to back up to an existing media pool, the cartridges must be loaded in the library. For more information about using Removable Storage, see "Removable Storage Service" earlier in this chapter.

Files Skipped During Backup

Backup skips the following types of files during the backup and restore processes:

Files that are skipped by default by backup.

Files that are held open by other applications.

Backup skips certain files by default, including the following:

Files that you do not have permission to read. only users with backup rights can copy files that they do not own.

Files that are temporary in nature, such as pagefile.sys, hiberfil.sys, win386.swp, 386spart.par, backup.log, and restore.log. these files are neither backed up nor restored by backup. the list of skipped files is embedded in backup and cannot be changed.

Registry files on remote computers. windows 2000 backs up only local registry files.

Windows 2000 lets you back up local files that are exclusively locked by the operating system, such as event logs and registry files. However, Backup skips those files that are held open by other processes. It is a good practice to avoid running applications while Backup is running to minimize the number of files that are not backed up.

Encrypted Files

If the files to be backed up are encrypted, they remain encrypted when they are backed up. Therefore, it is important to ensure that user keys, particularly the recovery agent keys, are also stored safely on backup cartridges. The Certificates console provides methods for exporting keys to floppy disks or to other removable media so that they can be secured in a trusted location.

For information about Encrypting File System (EFS), see "File Systems" in this book.

Backing Up Files on Your Local Computer

Backup lets you back up any file on your local disk system.

Most changes on a server occur as users add, modify, or delete files from their computers. It is recommended that you back up changes to users' folders daily.

Some users keep most of the files that they want backed up on network shares. Other users require that data on local computers be backed up. Your backup procedures need to take into account both situations.

Network users primarily use applications such as Microsoft® Word. You can reinstall the executable files from the original distribution media, but the time and productivity that is lost doing this make the approach less than ideal. In addition, if you have customized the applications to suit the needs of your organization, reproducing those settings can be more difficult than reloading the programs themselves. Because the applications rarely change, backing them up as part of your backup procedure ensures that the latest version is always available without using a lot of offline storage space.

Backing Up Files On Remote Computers

You can use Backup to back up files on any computers to which you can connect remotely. This allows a single media drive to be shared across an entire network and one backup policy to be in effect for the entire network.

You can only back up files and folders on a remote computer by using a shared folder. It is not possible to back up System State data from a remote computer directly by using Backup. If you want to back up the System State data of a remote computer, run Backup locally on the remote computer to save the System State data to a file on a shared volume; then back up the System State data file remotely on the shared volume. To restore the remote computer's System State data, restore the System State data file remotely to the shared volume, and then restore the System State data locally on the local computer.

NOTE

---

Backup does not recognize computers that are running MS-DOS or Windows 3.1.