Managing Windows Disks Backup and Restore.docx

1、Managing Windows Disks Backup and RestoreOperating SystemManaging Windows 2000 Disks, Backup and RestoreScenario Guide and WalkthroughAbstractThis scenario describes day-to-day administrative tasks to perform in a single domain Microsoft Windows2000-based network. Specifically, it focuses on disk ma

2、nagement and creating and implementing a backup and recovery plan. This scenario shows an administrator how to design a backup and restore strategy to ensure that the failure of a server or disk drive does not result in the loss of data. 2000 Microsoft Corporation. All rights reserved.THIS IS PRELIM

3、INARY DOCUMENTATION. The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Mic

4、rosoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication.This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT.Microsoft, Active Directory, Windows, Windows NT and the Windows logo a

5、re registered trademarks of Microsoft Corporation.Other product or company names mentioned herein may be the trademarks of their respective owners.Microsoft Corporation One Microsoft Way Redmond, WA 98052-6399 USA0200ContentsIntroduction 1Scenario Requirements 1Scenario Tasks 2Recovery Planning 3WIN

6、S/DHCP/DNS Server 3File and Print Servers 3Application Servers 3Other Considerations 4change management 5Disk management tasks 7Creating Dynamic Volumes 7Backup tasks 11Other administrative tasks 13Boot Recovery tasks 18Summary 20For More Information 20Additional Windows 2000 Web Site Resources 20In

7、troductionSystems for managing disks, backup, and disaster recovery are all critical needs for any company. Without the proper schedule for maintenance and proactive storage of data, a server may be down for days, weeks, or may not be able to recover critical data at all. The Microsoft Windows2000 o

8、perating system contains a variety of tools and management consoles to make these management tasks much easier and more centralized.Using the Disk Management snap-in of the Microsoft Management Console (MMC), administrators can quickly manage standard, fault tolerant, and volume sets and confirm the

9、 health of each volume. Disk management includes common Windows2000 administrative tasks such as creating volumes, creating partitions, adding disks, managing drive letters and paths, managing mirror sets, compressing files and folders, defragmenting the drive, as well as error checking. All are ava

10、ilable through one centralized utility.Other MMC administrative tools allow you to view the device configuration, take a device configuration snapshot, enable remote storage, save and monitor services, as well as review event logs in Event Viewer to make certain your systems are healthy. The Removab

11、le Storage snap-in allows administrators to fully manage tape drives, CD-ROM drives, and other removable storage devices.The Windows2000 Backup utility contains new, more flexible options, allowing users to back up selected volumes or folders to tape or to file. Backup can also be secured in order t

12、o protect valuable company data. Scheduling is built directly into Backup, so there is no need to use a separate scheduler.Adding an uninterruptible power supply (UPS) for power protection is as simple as following a wizard for identifying and configuring most UPS devices.When disaster does strike,

13、there are new safe mode boot options for restarting a server with and without various drivers, the Recovery Console for use by administrators in order to rename or replace individual files, as well as the Emergency Repair Disk. This tool also allows you to check and repair both the boot sector and t

14、he Master Boot Record.Each of these tools enable administrators to protect critical data, all of them together enable the administrator to implement and maintain a true enterprise disaster recovery plan.Scenario RequirementsThe administrative tools are installed by default on all Windows2000 domain

15、controllers. On Windows2000-based stand-alone servers or workstations, the Active Directory administrative tools are optional and can be installed from the Optional Windows2000 components package.This guide builds on the configuration achieved in earlier walkthroughs. Be sure you have successfully c

16、ompleted one of the following walkthroughs prior to proceeding.Upgrading a WindowsNT Domain to Windows2000 Active DirectoryAdding a New Windows2000 for File/Print and Web Server to Your Network Upgrading a WindowsNT File/Print and Web to Windows 2000 Full installation of Windows 2000 Server Installi

17、ng Windows 2000 Server Upgrading Windows NT-based network to Windows 2000Scenario TasksIn this walkthrough, you will perform the following tasks.Setup and Management Tasks Performing disk management, including common disk management tasks such as creating dynamic volumes, creating partitions, adding

18、 disks, managing drive letters and paths, managing mirror sets, compressing files and folders, defragmenting data. Backing up and restoring data, developing a backup and recovery strategy for data, scheduling regular backupRecovery PlanningPrior to reviewing tasks to perform, the planning stages nee

19、d to be outlined and discussed in detail. Different servers need to implement different fault tolerance and recovery options. The critical questions that need to be asked during the planning stage are as follows: How critical is the data or information on a server? Can automatic replication be set u

20、p quickly and easily? If the server went down, what would be the impact on your business? Is the server handling multiple functions? If the server is a core-networking server, that is, a DNS or WINS server, is all of the data being backed up on a daily basis?The role of the server will also be impor

21、tant to the type of recovery data required.Domain ControllersFor each domain controller, there needs to be an additional domain controller to serve as a replication partner and provide fault tolerance. An additional domain controller lets you reinstall the Windows 2000 operating system, and reinstat

22、e the server as a domain controller by selecting Restore Domain Controller from the boot menu, accessed by choosing F8 in the boot menu.On a domain controller, the primary partition containing the operating system and the registry information should be mirrored.Each domain controller should perform

23、a weekly tape backup and remove these tapes monthly to offsite storage. If the domain controller is also the primary Global Catalog Server, it should be backed up nightly and the tapes brought to offsite storage weekly.WINS/DHCP/DNS ServerEach server should be replicated to another WINS/DNS server o

24、n a separate network node. Every week the WINS/DHCP/DNS servers should be backed up and once a month one backup should be stored at an offsite location.File and Print ServersEach server should have a RAID-5 disk array for data fault tolerance. There should be nightly back up of these servers to pres

25、erve data and copies should be stored off site weekly.Application ServersOften these servers are the most critical in any Information System environment. Each server should have a mirrored system drive separate from the drives housing the data and the application. The application and data drives sho

26、uld be on a RAID-5 array.Backup of the system drive needs to be completed after any operating system upgrades, application upgrades, security changes, or changes to system configuration. Backup needs to be kept offsite. Backup of the data drives needs to be performed nightly and copies of the backup

27、 need to be stored off site weekly.Other ConsiderationsOther forms of fault tolerance and recovery that are not covered in this chapter, but which should be considered on these servers include clustering, using raid-5 volumes, hardware mirroring, and disk duplexing. Hardware fault tolerance, includi

28、ng RAID-5 and mirroring, is recommended if the company can afford it.Test Backup on a regular basis by performing a data restore to a nonfunctional directory. An untested backup is of little value to the organization.In mission critical development situations, Windows 2000 Professional-based systems

29、 should be treated in the same way as file and print servers.change managementThe other area that needs to be discussed when planning for basic server administration is change management. Very simply, this entails verifying that a change is needed, determining the change risk factors, testing the ch

30、ange to be made, and recording the change in the appropriate database and/or spreadsheet.There are three reasons to upgrade or in some way alter the configuration of your server hardware or software. First, the addition of functionality that adds value to your organization. Second, due to a fault in

31、 software, hardware, or the combined architecture, an application is failing or the server is unable to fulfill its role. Finally, when a change in functionality or in the role of a server or workstation occurs within the organization.One of the most critical aspects for change control is standardiz

32、ing hardware and software. By standardizing, you can manage servers from a central location as well as easily determine whether fixes and upgrades need to be applied to all servers or are applicable to only one situation or functionality.Even for tasks as simple as adding users, changing security, removing or adding TCP/IP addresses, or reconfiguring an application on a server, there must be change management. For these tasks, a Microsoft Access database or Microsoft Excel spreadsheet recor