Using the SBS Backup Wizard


The simplest way to create a full System State Exchange aware backup that can be used to restore the SBS in the event of a catastrophic failure and, at the same time, configure shadow copies and Exchange deleted mail retention, is to use the wizard.

The SBS Backup Wizard can be accessed from a number of locations:

  • From the To-Do List

  • From the To-Do List on the Server Manager

  • From the Backup link on the Server Manager

When the wizard launches, click next in the Welcome to Small Business Server Backup Configuration Wizard page to get to the backup location. If the wizard found a compatible tape drive attached to the system, it will enable the Tape Drive option as a recommended default. You may also choose to back up to a location on the hard disk or to a network share.

Caution

You cannot back up to optical media such as CD-ROM or DVD-ROM.


After you make your selection, the Backup Data Summary page displays. The SBS Wizard selects all necessary drives and data for a full system backup by default. Should you want to exclude folders or drives, you can do so from this screen by clicking on the Exclude Folders button. From there, you would click the Add Folder button to select the additional folders you want to exclude from the backup.

In the Backup Data Summary page, you can click the Calculate Folder Sizes button to display the size of each item included or excluded from the backup.

Next, in the Define Backup Schedule page, you can set the time and dates you want the backup to run automatically. If you are backing up to tape, the wizard allows you to configure a notification to the tape changer. This sends an email to the person identified as the tape changer, reminding him to change the tape or run a cleaning tape on the drive.

The Storage Allocation for Deleted Files and Emails page appears next, as shown in Figure 18.1. You can set the number of days deleted messages and mailboxes will be retained and allocate space for shadow copies of files and folders.

Figure 18.1. Storage allocation for deleted files and emails.


The last page of the wizard appears showing a summary of the actions that will be taken. When you click Finish, the wizard builds the relevant backup files, scripts, schedules, and alerts and sets the Exchange and Shadow Copy settings while creating a BackupWizard.log file (by default located at C:\Program files\Microsoft Small Business Server\Support) that can be used for debugging.

Like all the wizards in SBS 2003, the Backup Wizard provides a simple interface to configure many settings scattered about the servers and services. It is often easier to rerun the wizard when these setting need to change than manually configure them and run the risk of misconfiguring them. That is not to say that manual settings aren't possible or even in some cases desirable.

Limitations of the SBS Backup Wizard

Although the wizard provides a wonderful wrapper around NTBackup to vastly simplify the process of creating a full System State backup, it is not a full-fledged backup application in itself, and it has limitations. The wizard is specifically designed to create a backup that can be used to recover the system in the event of a data disaster either in the form of physical failure of the system/hard disk(s) or corruption/deletion of the system files themselves.

The limitations of the SBS Backup Wizard are limitations of both what the wizard is designed to do and what NTBackup itself is designed to do. Although in some instances it may be desirable to have many additional features, those can be found in many of the dedicated and more up-to-date backup software applications and suites.

The SBS Backup Wizard

  • Can only create full Exchange aware System State backups

  • Is reliant on the VSS for file copy

  • Does not use VSS for Exchange backup

  • Does not allow for the disabling of the backup verify

  • Exclusions work at the drive and folder level only, not the file level

Limitations of NTBackup are as follows:

  • Has no remote console

  • Does not do software compression

  • Cannot do "brick level" (individual mailbox) Exchange backup

  • Does not contain a VSS Requestor

  • Cannot back up to writable CD-ROM or DVD

  • Does not support tape autoloaders/changers

  • Cannot create disk images

  • Cannot back up network/remote computers System State or Registry

  • Has limited error handling and reporting

  • Cannot email or print completed job logs

  • Cannot eject a tape after a backup

  • By design, can only back up directories when using a batch file or through a command prompt

  • Has no simple way to write a backup to an arbitrary tape without using the /um (unmanaged) option on the command line

  • Has no simple way to append backup information to an inserted tape because you must use either the /t (tape name) or /g (GUIDGlobally Unique Identifier) command-line option. Unmanaged mode won't work because you can only append to a specifically named tape.

  • Does not have an internal scheduler, so if the backup fails, it will not attempt to rerun until the next scheduled event.

Despite the limitations, within the framework of their stated goal, the wizard and NTBackup fulfill their roles well, and most SBS users do not require any additional functionality or backup software.

Settings Generated by the Wizard

As mentioned previously, in addition to creating a full System State Exchange aware backup of the SBS server, the SBS 2003 Backup Wizard configures several applications external to NTBackup itself that would otherwise need to be manually configured. These are

  • Exchange deleted item retention

  • Exchange circular logging turned off

  • Periodic shadow copy snapshots of shared folders

  • The scheduling of the backup action

  • Creation of backup reports in SBS Monitoring

  • Scheduled email reminders for the backup operator tape changer

  • Report generation

Excluding Data from the Backup Wizard

By default, the SBS Backup Wizard backs up all data and system files, including Exchange databases and logs. Drive and folder exclusions must be specifically set during the configuration process. Not all files and folders are backed up, however, as can be seen in Figure 18.2, the Registry key HKLM\System\CurrentControlSet\control\BackupRestore\FilesNotToBackup, and in Table 18.2. These files will be automatically re-created by the system itself if required after a restore.

Figure 18.2. FilesNotToBackup Registry setting.


Table 18.2. Automatic Backup Exclusions

ASR Error File

%SystemRoot%\repair\asr.err

ASR Log File

%SystemRoot%\repair\asr.log

BITS_metadata

C:\Documents and Settings\All Users.WINSBS\Application

Data\Microsoft\Network\Downloader\*

Catalog Database

%SystemRoot%\System32\CatRoot2\* /s

Client Side Cache

%SystemRoot%\csc\* /s

DNS Server

%SystemRoot%\system32\dns\backup\dns.log

C:\WINSBS\system32\dns\dns.log

DRM

C:\Documents and Settings\All Users.WINSBS\DRM\* /s

Internet Explorer

%UserProfile%\index.dat /s

Memory Page File

\Pagefile.sys

Microsoft Writer (Bootable State)

%SystemRoot%\Registration\*.clb

\*.crmlog /s

Mount Manager

\System Volume Information\MountPointManagerRemoteDatabase

MS Distributed Transaction Coordinator

C:\WINSBS\system32\MSDTC\MSDTC.LOG

C:\WINSBS\system32\MSDtc\trace\dtctrace.log

Netlogon

%SystemRoot%\netlogon.chg

NTDS

C:\WINSBS\NTDS*

C:\WINSBS\NTDS\*

NtFrs

c:\winsbs\ntfrs\jet\* /s

C:\WINSBS\debug\NtFrs\NtFrs*

c:\winsbs\sysvol\domain\DO_NOT_REMOVE_NtFrs_PreInstall_Directory\* /s

c:\winsbs\sysvol\domain\NtFrs_PreExisting___See_EventLog\* /s

:\winsbs\sysvol\staging\domain\NTFRS_*

Power Management

\hiberfil.sys

Task Scheduler

%SYSTEMROOT%\Tasks\schedlgu.txt

Temporary Files

%TEMP%\* /s

VSS Default Provider

\System Volume Information\*{3808876BC1764e48B7AE04046E6CC752} /s

VSS Service Alternate DB

\System Volume Information\*.{7cc467ef68654831853f2a4817fd1bca}ALT

VSS Service DB

\System Volume Information\*.{7cc467ef68654831853f2a4817fd1bca}DB

Winlogon debug

%WINDIR%\debug\*


Not all files need to be, or should be, backed up. Client application setup files can take up considerable space and are not essential for the restoration of the system. They can be easily copied back to the server from original media after a restore. Excluding these files can significantly reduce both the space required and the duration of the backup/verify and restore processes.

Business data that has been archived but retained on the server may be similarly excluded, as may the contents of antivirus and spam quarantine and backup folders provided that the applications will re-create the folders if they are not present after a restore rather than just fail.

If separate backups are made of line of business applications such as accounts contact management, inventory databases, and the like, these too can be excluded.

Because the SBS Backup Wizard is designed for full system recovery backup, you cannot exclude folders that are part of System folders, which are required for a system restore. Additionally folders within the Program Files directory are also locked from exclusion.

It may be necessary to reinstall or reconfigure some third-party applications if data stores and folders (such as antivirus quarantine files) that are by default stored in the Program Files folder are to be excluded from backup.

Best Practice: Planning the Server File Structure

It is good practice to store all variable data on a separate drive or partition. This makes locating files to be backed up and backup configuration simpler.

Restoration is also both simplified and speeded up because the whole drive/partition can be restored and fragmentation reduced.


SBS 2003 hides the Exchange virtual drive (M); however, if it is visible for any reason, it should be explicitly excluded from the backup.

If backing up to an external hard disk drive or a server disk prior to transferring to other media, the location of the backup must be excluded or the backup process will fail trying to back up its own active backup file.

Best Practice: SQL Databases in Simple Mode

Make sure that SQL Server and MSDE databases are set to Simple mode unless you are excluding them from the backup. SQL Server contains its own backup routine, and this can be configured to back up databases to a folder on the server that can be included in the server backup.


Changing the Backup Notification

The Small Business Backup Script file (by default located at C:\Program Files\Microsoft Windows Small Business Server\Backup) does not contain nearly as much information as is actually involved in the wizard process. This is only the .bks file that is run by NTBackup. Although the file can be opened and edited in Notepad, it is highly recommended that this not be done, and any changes required be made by rerunning the Backup Wizard. The .bks file is actually a Unicode file without the Unicode header bytes.

Best Practice: Change Backup Settings Only with the Wizard

Wherever possible in SBS it is always best to rerun the associated wizard if there is one, instead of making manual adjustments or file edits. This holds true for the Backup Wizard as well. The only way to make sure that the automated backup process runs correctly is to use the Backup Wizard; otherwise, you would have to configure all the backup steps using NTBackup, including scheduling, exclusions, and so on. The wizard is designed to take care of all these steps for you automatically.


To change the Tape Change and Tape Cleaner notification alerts to the backup operator, simply rerun the SBS Backup Wizard.




Microsoft Small Business Server 2003 Unleashed
Microsoft Small Business Server 2003 Unleashed
ISBN: 0672328054
EAN: 2147483647
Year: 2005
Pages: 253

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net