Systems Management Server 2.0: Backup and Recovery Overview SMS Recovery Web Site location: Updated June 25, 2001

Backup and Recovery as of SMS 2.0 SP1 Automated backup is supported in SP1: Automated built-in task called Backup SMS Site Server (for primary sites only; secondary sites require a batch file to be written for each site) Automated built-in task called Backup SMS Site Server (for primary sites only; secondary sites require a batch file to be written for each site) Recovery is fully supported in SP1: Managing SMS recovery Managing SMS recovery

Sections in the Overview Core Concepts for Maintaining Integrity of Hierarchy Core Concepts for Maintaining Integrity of Hierarchy Recovery Life Cycle Recovery Life Cycle Managing SMS Recovery Managing SMS Recovery Supported Recovery Scenarios Supported Recovery Scenarios Supported Recovery Configurations Supported Recovery Configurations Your Backup and Recovery Plan Your Backup and Recovery Plan New Tools to Assist in Backup and Recovery New Tools to Assist in Backup and Recovery

Core Concepts for Maintaining Integrity of Hierarchy Always resynchronize serial numbers when re-installing a site. Always resynchronize serial numbers when re-installing a site. Always check for failed site recoveries before connecting to a parent site. Always check for failed site recoveries before connecting to a parent site. Always back up all four components of a site as a snapshot when backing up. Always back up all four components of a site as a snapshot when backing up.

Always Resynchronize Serial Number IDs When Re-installing an SMS Site Definition of SMS Site Recovery Definition of SMS Site Recovery  Any time an SMS site is installed using a site code or site server name previously used in a hierarchy, then in relationship to that hierarchy, an SMS site recovery has begun. Repairing data is the core task of a site recovery and is required to prevent interruption of operations and corruption of data in the hierarchy. Repairing data is the core task of a site recovery and is required to prevent interruption of operations and corruption of data in the hierarchy.

Always Check for Failed Site Recoveries Before Connecting to a Parent Site Check for failed site recoveries at the potential parent site, and all sites above it, before connecting a site to a new parent site. Check for failed site recoveries at the potential parent site, and all sites above it, before connecting a site to a new parent site. This check helps avoid corrupting software distribution objects at the connecting site and its child sites. This check helps avoid corrupting software distribution objects at the connecting site and its child sites.

Always Back Up All Four Components of a Site as a Snapshot Stop site services before backing up. Then back up: Stop site services before backing up. Then back up:  SQL Server databases for the site.  Site server files from the site directory (from share SMS_ ).  The SMS and NAL registry keys.  Windows and SQL Server configuration information.

Recovery Life Cycle Backing Up Data Implementing Procedures Failure Rebuilding Servers Restoring Data (optional) Repairing/Resync Verifying Success Understanding the Cause of Failure Planning for Maximum Uptime

Managing SMS Recovery Aspects of SMS that affect recovery: Distributed data and tasks Distributed data and tasks Multiple accounts Multiple accounts Regaining control of clients and child sites Regaining control of clients and child sites

Managing SMS Recovery Key Recovery Strategies: Restoring a site requires a backup. Restoring a site requires a backup. Recovering a site is possible without a backup. Recovering a site is possible without a backup. Serial numbers must be resynchronized. Serial numbers must be resynchronized.

Supported Recovery Scenarios The hardware fails. The hardware fails. The drive containing Windows, SQL Server, or SMS fails. The drive containing Windows, SQL Server, or SMS fails. Windows fails and must be restored. Windows fails and must be restored. The file system becomes corrupted. The file system becomes corrupted. SQL Server fails and must be restored. SQL Server fails and must be restored. The SQL Server databases become corrupted. The SQL Server databases become corrupted.

Supported Recovery Configurations SQL Server 6.5, SQL Server 7.0, and SQL 2000, local or remote SQL Server 6.5, SQL Server 7.0, and SQL 2000, local or remote Local or remote SMS Provider Local or remote SMS Provider No backup, old backup, or new backup No backup, old backup, or new backup Secondary or primary site, with or without a parent site Secondary or primary site, with or without a parent site Primary sites with or without child sites (primary, secondary, or a combination) Primary sites with or without child sites (primary, secondary, or a combination)

Your Backup and Recovery Plan Three Phases: Planning. Cover all potential issues. Planning. Cover all potential issues. Backup. Verify that your backup plan is working. Backup. Verify that your backup plan is working. Test. Verify that it is possible to recover if necessary. Test. Verify that it is possible to recover if necessary. Use the documentation on the Recovery Web site to make a plan for the specific needs of each SMS site.

Testing the Plan: Backup Use the Backup SMS Site Server task to: Back up site server’s files. Back up site server’s files. Back up the registry. Back up the registry. Back up SQL Server databases. Back up SQL Server databases. Backup secondary sites (optional). Copy the backup to tape and store it. Do not leave data on the site server. Do not leave data on the site server. Back up distribution points (optional). SMS can re-deploy packages, so this is optional. SMS can re-deploy packages, so this is optional.

Testing the Plan: Recovery Verify that the backup plan works: Ensure that essential data was backed up. Ensure that essential data was backed up. Ensure that plan can be used to recover site. Ensure that plan can be used to recover site. Ensure that plan supports a timely recovery. Ensure that plan supports a timely recovery. Rebuild, restore, and repair: Rebuild SQL Server and SMS servers. Rebuild SQL Server and SMS servers. Restore data to the rebuilt servers. Restore data to the rebuilt servers. Repair site and hierarchy data. Repair site and hierarchy data. Adjust transaction IDs and serial numbers: In databases, registries, and files. In databases, registries, and files.

New Tools to Assist in Backup and Recovery SMS 2.0 Backup and Recovery Planning Document: Explains how to plan for a recovery. Explains how to plan for a recovery. Site Recovery Expert: Queries administrator for site information and then displays required steps for recovery. Queries administrator for site information and then displays required steps for recovery. Site Recovery Wizard: Assists in repairing a failed site. Assists in repairing a failed site. Will be incorporated into the Topaz release Will be incorporated into the Topaz release

Recovery Expert Used with: Recovery Planning document Recovery Planning document Security Essentials document Security Essentials document Recovery Tools Recovery Tools Asks questions about your site Generates a list of tasks required for rebuild, restore, and repair: Links to each task Links to each task Tasks can be printed Tasks can be printed

Recovery Expert: Required Information Configuration information about: Configuration information about:  Windows  SQL Server Availability of a backup Availability of a backup Changes made since backup Changes made since backup Site server and other site system information Site server and other site system information Hierarchy information Hierarchy information

Recovery Expert: Required Information SMS Configuration SMS Configuration  Components  Client installation methods  Discovery methods  Client agents  Status summarizers  Software metering

Recovery Expert: Recovery Tasks (Tasks are performed manually.) Prepare: Disable software metering enforcement. Disable software metering enforcement.Rebuild: New SQL Server, re-install SMS. New SQL Server, re-install SMS.Restore: Restore files, database, registry. Restore files, database, registry.Repair: Synchronize with the rest of the hierarchy, increment IDs, install QFEs. Synchronize with the rest of the hierarchy, increment IDs, install QFEs.

Recovery Wizard Runs after site Recovery Expert: You must manually perform most rebuilding tasks before running the Recovery Wizard. You must manually perform most rebuilding tasks before running the Recovery Wizard. Helps perform repair tasks Can be restarted: From beginning or from last operation. From beginning or from last operation.Supports: SMS 2.0 SP1 or later SMS 2.0 SP1 or later Windows NT or Windows 2000 Windows NT or Windows 2000 Availability information: Read the Backup and Recovery FAQ Read the Backup and Recovery FAQ

Recovery Wizard: Wizard Phase Informs you of mandatory steps: Stop SMS services on the recovering site Stop SMS services on the recovering site Queries for: Last backup date and date of failure Last backup date and date of failure Site hierarchy information Site hierarchy information Checks parent for connectivity Checks for reference site Requests object ID padding values

Recovery Wizard: Site Repair Phase Removes client access point (CAP) and logon point files: Forces site server to refresh them Forces site server to refresh them Pulls site control file from parent: Retrieves current settings Retrieves current settings Software metering set to Offline: No interaction with servers No interaction with servers

Recovery Wizard: Hierarchy Repair Phase Assists in child site address rebuilds Assists in child site address rebuilds Deletes orphaned parent site data Deletes orphaned parent site data Updates transaction IDs and serial numbers Updates transaction IDs and serial numbers Regenerates lost software object definitions to prevent orphaned data on child sites Regenerates lost software object definitions to prevent orphaned data on child sites

Recovery Wizard End of Repair Phase Can force package refresh to local distribution point Can force package refresh to local distribution point Checks each package source Checks each package source Restarts SMS services Restarts SMS services Lists tasks to be verified: Lists tasks to be verified:  Software Metering  Child reporting  Missing orphaned data  Package deployment

For More Information SMS Backup and Recovery Feedback: Reading Material: Microsoft Windows Server Resource Kit Microsoft Windows Server Resource Kit  Installing and configuring  Editing and restoring registry keys Microsoft SQL Server Administrator’s Guide Microsoft SQL Server Administrator’s Guide  Installing and configuring  Restoring databases  Updating SQL Server tables Microsoft SMS 2.0 Administrator’s Guide Microsoft SMS 2.0 Administrator’s Guide SMS 2.0 Security Essentials document SMS 2.0 Security Essentials document

Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the example companies, organizations, products, people and events depicted herein are fictitious and no association with any real company, organization, product, person or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property. © 2001 Microsoft Corporation. All rights reserved. Microsoft, MS-DOS, Windows, and Windows NT are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. The names of actual companies or products mentioned herein may be the trademarks of their respective owners.