Backing up System State

From SEPsesam
Jump to: navigation, search

Copyright © SEP AG 1999-2017. All rights reserved.

Any form of reproduction of the contents or parts of this manual is allowed only with the express written permission from SEP AG. When compiling and designing user documentation SEP AG uses great diligence and attempts to deliver accurate and correct information. However, SEP AG cannot issue a guarantee for the contents of this manual.

Docs latest icon.png Welcome to the latest SEP sesam documentation version 4.4.3. For previous documentation version(s), check documentation archive.


Overview

SEP sesam supports system state data backup and uses Microsoft Volume Shadow Copy Service (VSS) to back up system state components. These components include core files and registry settings and are related to various aspects of Windows operating system.

In the event of a system crash or corruption you can use the system state backup to restore Windows system settings and other critical system related components, such as registry, boot file, Active Directory etc. This way you do not have to manually reconfigure Windows back to its original state before the crash or corruption.

Up until SEP sesam version 4.4.3, the system state backup was known and selectable under the name System_recovery. This option is now renamed to System_state without change in functionality.

Information sign.png Note
System state backup may not be sufficient to recover your system after a failure and is not a replacement for a disaster recovery solution. To prepare your system for disaster recovery, use SEP sesam BSR Pro to create a boot image on the client which may be used to recover the client system.

System state backup type

The Windows system state is a selectable backup type which provides backup of all system state components as a unit. Note that system state elements are machine-specific and depend on each operating system installation version and configuration. SEP sesam allows for dynamic discovery of existing system state elements and backup.

At a minimum, the following components are backed up:

System state data
Registry, COM+ class registration database, boot and system files, DFS namespaces/replications
A domain controller system state
Active Directory Domain Services, Windows Registry, COM+ database, SYSVOL directory
System services components
Background Intelligent Transfer Service (BITS), Cluster Service information (cluster node only), Dynamic Host Configuration Protocol (DHCP), Microsoft Internet Information Services (IIS) meta-directory, Removable Storage Management Database (RSM), Remote Storage Service, Terminal Server Licensing, Windows Internet Name Service (WINS), Windows Management Instrumentation (WMI)

Prerequisites

Make sure that the following conditions are met when backing up system state data:

  • You must be an administrator or a backup operator to back up system state information.
  • On the SEP sesam Server, run a test to ensure that the SEP sesam file system backup of the corresponding client is working and that data can be restored.

Creating a system state backup task

Configuring a system state backup involves creating a System state backup task for your Windows client, setting up a backup schedule (specifying when you want to back up your data) and linking the schedule to a backup event (specifying how to back up the data and where to back it up to). For general information on backup configuration and prerequisites, see Standard Backup Procedure. This section deals only with system state backup specific information.

  1. In the Main Selection -> Tasks -> By clients, select your Windows client then click New backup task. The New backup task window appears.
  2. Now specify the Source: click the browse button and select System state. This specifies your system state data as the source and sets the System_state backup type and the task name automatically.
  3. System state backup.png


  4. Click OK to create the task.

You can group your backup tasks to task groups. For details, see Adding a Task to the Task Group. The final step in the backup configuration is creating a new backup event. For general information, see Creating a backup event. Then run your system state backup.

Information sign.png Note
Make sure that frequent system state backups of your servers are carefully planned:
  • The system state should be backed up regularly, at least before and after each major system update and on a weekly basis to ensure a copy which you could use to rollback.
  • You should have at least two versions of the system state backup to ensure recovery to any working version if the system state gets corrupted.
  • The age of the system state backup can be an issue for the domain controllers (the supported backup lifetime for the domain controllers is equal to the maximum tombstone age (60 days by default), which means that they can soon be out of sync) and for the Active Directory data, such as computer accounts. Restoring from an old system state backup can cause a number of problems, such as mismatched accounts within AD.
  • Run frequent restore tests of your backups to ensure that backups will work in case of need.

What is next?

Restoring Windows System State