AhsayACB Windows System Best Practices

Best Practices and Recommendations

The following are some of the best practices and recommendations that we strongly recommend, before you start any Microsoft System backup and restore:

Temporary Directory Folder Location

For best performance, it is recommended that the temporary storage location of an MS Windows System backup set is set to a supported local volume, and not to a network volume (e.g. to improve I/O performance). The temporary storage location is highly recommended to be set in a directory with sufficient free disk space and located in another location other than Drive D: (e.g. Drive E:).

Backup Destination

To provide maximum data protection and flexible restore options, it is recommended to configure:

• At least one offsite or cloud destination
• At least one local destination for fast recovery

Backup Frequency

MS Windows System backup should be performed at least once per week.

Performance Recommendations

Consider the following best practices for optimized performance of the backup operations:

• Enable scheduled backup jobs when system activity is low to achieve the best possible performance.
• It is highly recommended to enable the Include all critical volumes option to select all critical volumes for backup automatically.

This will ensure that the backup image can be used for full system / bare-metal recovery.

Not a Replacement for File Backup

An image-based / bare-metal backup should never be considered a replacement for a nightly data backup plan.

Firstly, image-based backups do not lend themselves easily to recovery of a single file. The nature of image-based backup requires a complete restore of the system image file, even if you only want to recover a single file.

System Recovery Plan

Consider performing routine system recovery tests to ensure your system backup is set up and performs properly. Performing system recovery test can also help identify potential issues or gaps in your system recovery plan.

For best results, it is recommended that you should keep the test as close as possible to a real situation. Often, when a recovery test is to take place, administrators will plan for the test (e.g. reconfiguring the test environments, restoring certain data in advance). For real recovery situations, you will not get the chance to do that.

It’s important that you do not try to make the test easier, as the objective of a successful test is not to demonstrate that everything is flawless. There might be flaws identified in the plan throughout the test and it is important to identify those flaws.

Restore to Alternate Computer

You can restore a system backup to the same physical computer from which the system backup was created, or to a different computer that has the same make, model, and configuration (identical hardware). Microsoft does not support restoring a system backup from one computer to a second computer of a different make, model, or hardware configuration.

Please refer to the following article for more details:

Reinstalling Windows

Periodic Backup Schedule

The periodic backup schedule should be reviewed regularly to ensure that the interval is sufficient to handle the data volume on the machine. Over time, data usage pattern may change on a production server, i.e. the number of new files created, the number of files which are updated/deleted, and new users may be added etc.

Consider the following key points to efficiently handle backup sets with periodic backup schedule.

• Hardware – to achieve optimal performance, compatible hardware requirements is a must. Ensure you have the backup machine’s appropriate hardware specifications to accommodate frequency of backups.
  • so that the data is always backed up within the periodic backup interval
  • so that the backup frequency does not affect the performance of the production server
• Network - make sure to have enough bandwidth to accomodate the volume of data within the backup interval.
• Retention Policy - also make sure to consider the retention policy settings and retention area storage management which can grow because of the changes in the backup data for each backup job.