Dell PowerVault DP600 - Manual (Page 121)

121
DPM runs the pre-backup and post-backup scripts by using the local system account. As a best
practice, you should ensure that the scripts have Read and Execute permissions for the
administrator and local system accounts only. This level of permissions helps to prevent
unauthorized users from modifying the scripts.
On each protected computer, you should back up the scripting file, ScriptingConfig.xml, at
\Program Files\Microsoft DPM\DPM\Scripting, and all pre-backup and post-backup scripts.
See Also
Backing Up DPM by Using a Secondary DPM Server
Using Pre-Backup and Post-Backup Scripts
Backup of Protected Computer System State
System state is a collection of system-specific data maintained by the operating system that must
be backed up as a unit. It is not a backup of the entire system. The backup of a computer's
system state can be used when you need to return the computer to a known state, such as after
an installation that puts the computer in an undesirable state.
DPM can protect the system state for any computer on which a DPM protection agent can be
installed, except computers running Windows Vista or Windows Server 2008.
The system state of a protected computer can be added to a protection group. DPM leverages
the Windows Backup utility on the protected computer to back up the system state to a backup
(.bkf) file, which is saved to the DPM medium you specify for that protection group (disk, tape, or
both).
Because system state does not change frequently, consider placing system state in protection
groups separate from file and application data so that you can specify the most efficient
protection schedule for each data source.
Member Server and Desktop System State
When DPM backs up the system state of a member server or desktop, the following components
are protected:
• The boot files
• The COM+ class registration database
• The registry
Domain Controller System State
When DPM backs up the system state of a domain controller, the following components are
protected:
• Active Directory (NTDS)
• The boot files
• The COM+ class registration database
• The registry
• The system volume (SYSVOL)