![]() Recommended that you perform System State backups before and after any major change is made to your server. ![]() We recommended that you always have a recent backup of your System State and that you should perform System Stateīackups on a regular basis, even daily, to ![]() A System State backup is therefore particularly important for disaster recovery purpose as it eliminates you having to reconfigure Windows back to its original state before the system failure occurred. Why is a System State backup useful?įrom a System State backup you can restore your Windows system settings in the event of a system failure or corruption. This data does not need to be copied on subsequent backups, which reduces backup times and saves storage space on your destination. If you are backing up the System State using the File Replication Engine or the Rsync Engine and have Single Instance Store enabled, only a single copy of each multiply linked file will be stored on your backup destination. Many files in the Windows directory have multiple hard links. System State backups for Vista and Server 2008 are usually between 7GB and 15 GB and for XP and Server 2003, they are generally much smaller, being between 200MB and 300 MB. ![]() A System State backup generally includes a copy of any installed device drivers and related files, most of the Windows directory, the Windows Registry, the Active Directory configuration (where applicable) and system files under Windows File Protection. The exact system components that make up your machine's System State depend on the operating system installed and how it is has been configured. System State backup and restore What's included in a System State backup? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |