public:module:windows_system_state:overview
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
|
public:module:windows_system_state:overview [2019/09/02 16:19] ronnie.chan |
public:module:windows_system_state:overview [2019/09/19 18:30] ronnie.chan |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Overview ====== | ====== Overview ====== | ||
| + | ---- | ||
| CloudBacko Pro allows you to backup the Windows System State data, including: | CloudBacko Pro allows you to backup the Windows System State data, including: | ||
| * Boot files, including the system files, and all files protected by Windows File Protection (WFP) | * Boot files, including the system files, and all files protected by Windows File Protection (WFP) | ||
| Line 15: | Line 15: | ||
| The size of a set of System State backup data is dependent on the role installed on the server. Please refer to the following article for more details: | The size of a set of System State backup data is dependent on the role installed on the server. Please refer to the following article for more details: | ||
| + | * For Windows XP and Windows Server 2003: https://msdn.microsoft.com/en-us/library/windows/desktop/aa381498 | ||
| + | * For Windows 2008 and newer releases: https://msdn.microsoft.com/en-us/library/windows/desktop/bb968830 | ||
| - | For Windows XP and Windows Server 2003: https://msdn.microsoft.com/en-us/library/windows/desktop/aa381498 | ||
| - | For Windows 2008 and newer releases: https://msdn.microsoft.com/en-us/library/windows/desktop/bb968830 | ||
| - | |||
| - | ---- | ||
| ===== Requirements and Limitation ===== | ===== Requirements and Limitation ===== | ||
| - | <WRAP> | + | <WRAP indent> |
| ==== For Windows XP and Windows Server 2003 ==== | ==== For Windows XP and Windows Server 2003 ==== | ||
| Line 31: | Line 29: | ||
| <WRAP info> | <WRAP info> | ||
| Please be noted that: | Please be noted that: | ||
| - | - Windows XP home is not supported for the system state backup and restore by AhsayOBM. | + | - Windows XP home is not supported for the system state backup and restore by CloudBacko Pro. |
| - | - As Windows XP and Windows 2003 are no longer supported by Microsoft any more, Ahsay will provide best effort support for backup and restore for these 2 Windows platforms. | + | - As Windows XP and Windows 2003 are no longer supported by Microsoft any more, CloudBacko Pro will provide best effort support for backup and restore for these 2 Windows platforms. |
| </WRAP> | </WRAP> | ||
| - | === AhsayOBM Installation === | + | === CloudBacko Pro Installation === |
| - | Make sure that the latest version of AhsayOBM is installed on the computer to be backed up. User should also stay up-to-date when newer version of AhsayOBM is released. | + | Make sure that the latest version of CloudBacko Pro is installed on the computer to be backed up. User should also stay up-to-date when newer version of CloudBacko Pro is released. |
| - | + | ||
| - | === Add-on Module Requirement === | + | |
| - | Make sure that the Windows System State add-on module is enabled for your AhsayOBM user account. | + | |
| - | + | ||
| - | {{public:cloudbacko_module_system_state_requirement_1.png?640}} | + | |
| - | + | ||
| - | === Backup Quota Requirement === | + | |
| - | Make sure that your AhsayOBM user account has sufficient quota assigned to accommodate the storage for the system state backup for the new backup set and retention policy. | + | |
| - | + | ||
| - | === AhsayOBM Licenses === | + | |
| - | AhsayOBM licenses are calculated on a per device basis: | + | |
| - | * To backup users with 1 backup client computer (e.g. 1 AhsayOBM installed), 1 AhsayOBM license is required. | + | |
| - | * To backup users with multiple backup client computers, the number of AhsayOBM licenses required is equal to the number of devices. For example, if there are 10 users to be backup with 3 backup client computers, then 3 AhsayOBM licenses are required. | + | |
| === Restore to Alternate Computer === | === Restore to Alternate Computer === | ||
| Line 78: | Line 63: | ||
| - | === AhsayOBM Installation === | + | === CloudBacko Pro Installation === |
| - | Make sure that the latest version of AhsayOBM is installed on the computer to be backed up. User should also stay up-to-date when newer version of AhsayOBM is released. | + | Make sure that the latest version of CloudBacko Pro is installed on the computer to be backed up. User should also stay up-to-date when newer version of CloudBacko Pro is released. |
| - | + | ||
| - | === Add-on Module Requirement === | + | |
| - | Make sure that the Windows System State add-on module is enabled for your AhsayOBM user account. | + | |
| - | + | ||
| - | {{public:cloudbacko_module_system_state_requirement_3.png?640}} | + | |
| - | + | ||
| - | === Backup Quota Requirement === | + | |
| - | Make sure that your AhsayOBM user account has sufficient quota assigned to accommodate the storage for the system state backup for the new backup set and retention policy. | + | |
| - | + | ||
| - | === AhsayOBM Licenses === | + | |
| - | AhsayOBM licenses are calculated on a per device basis: | + | |
| - | * To backup users with 1 backup client computer (e.g. 1 AhsayOBM installed), 1 AhsayOBM license is required. | + | |
| - | * To backup users with multiple backup client computers, the number of AhsayOBM licenses required is equal to the number of devices. For example, if there are 10 users to be backup with 3 backup client computers, then 3 AhsayOBM licenses are required. | + | |
| === Restore to Alternate Computer === | === Restore to Alternate Computer === | ||
| Line 100: | Line 72: | ||
| === Memory Setting === | === Memory Setting === | ||
| - | The default Java heap size setting of AhsayOBM is 2048MB. For Windows System State backup, it is highly recommended to increase the Java heap size setting to at least 4096MB to improve backup and restore performance. The actual heap size used will be dependent on amount of free memory available on the machine with AhsayOBM installed (machine that is running the backup). | + | The default Java heap size setting of CloudBacko Pro is 2048MB. For Windows System State backup, it is highly recommended to increase the Java heap size setting to at least 4096MB to improve backup and restore performance. The actual heap size used will be dependent on amount of free memory available on the machine with CloudBacko Pro installed (machine that is running the backup). |
| - | For best performance, consider increasing the memory allocation setting for AhsayOBM (Java heap space). Refer to this link for more details about [[public:8011_faq:how_to_modify_the_java_heap_size_of_ahsayobc|how to modify of the java heap size setting for AhsayOBM]]. | + | For best performance, consider increasing the memory allocation setting for CloudBacko Pro (Java heap space). Refer to this link for more details about [[https://forum.cloudbacko.com/viewtopic.php?f=2&t=1670|how to modify of the java heap size setting for CloudBacko Pro]]. |
| === Temporary Volume === | === Temporary Volume === | ||
| Line 115: | Line 87: | ||
| If by any chance the machine has only one (1) drive and it is his/her Local Disk C:, then one of the following options will need to be implemented | If by any chance the machine has only one (1) drive and it is his/her Local Disk C:, then one of the following options will need to be implemented | ||
| * An extra physical drive will need to be installed | * An extra physical drive will need to be installed | ||
| - | * The existing C: drive will need to be repartitioned to create an additional drive, i.e. D: | + | * The existing C: drive will need to be re-partitioned to create an additional drive, i.e. D: |
| * A USB drive needs to be connected | * A USB drive needs to be connected | ||
| * Setup a network drive | * Setup a network drive | ||
| - | |||
| - | Please refer to the following link for details on the [[public:5165_restrictions_on_the_temp_for_the_windows_system_state_and_system_backup|Restrictions on the temporary storage location for the Windows System State and System backup image file]] | ||
| === Windows Server Backup (WSB) Features === | === Windows Server Backup (WSB) Features === | ||
| Line 145: | Line 115: | ||
| ---- | ---- | ||
| - | |||
| - | ===== Best Practice and Recommendation ===== | ||
| - | The following are some best practices or recommendations that we strongly recommend, before you start any Microsoft System State backup and restore: | ||
| - | |||
| - | ==== Temporary Directory Folder Location ==== | ||
| - | Temporary directory folder is used by AhsayOBM for storing backup set index files and any incremental or differential backup files generated during a backup job. To ensure optimal backup/restoration performance, it is recommended that the temporary directory folder is set to a local drive with sufficient free disk space. | ||
| - | |||
| - | <WRAP info> | ||
| - | NOTE | ||
| - | Kindly noted that for Windows Server 2008 or newer releases, the restriction on temporary volume (Ch2.3.2) must also be considered. | ||
| - | </WRAP> | ||
| - | |||
| - | ==== 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 State backup should be performed at least once per week. | ||
| - | |||
| - | ==== Performance Recommendations ==== | ||
| - | Consider the following best practices for optimized performance of the backup operations: | ||
| - | * Enable schedule backup jobs when system activity is low to achieve the best possible performance. | ||
| - | * Perform test restores periodically to ensure your backup is set up and performed properly. Performing recovery test can also help identify potential issues or gaps in your recovery plan. 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. | ||
public/module/windows_system_state/overview.txt · Last modified: 2019/09/20 11:52 by ronnie.chan
Page Tools
