This is an old revision of the document!
AhsayOBM allows you to back up the whole Windows System with the Windows System Backup Module. This module of AhsayOBM provides you with a set of tools to protect your mission critical systems / personal computers on Windows operating system platforms. This includes an image-based / bare-metal backup feature, that leverages Microsoft’s native Wbadmin command-line tool (http://go.microsoft.com/fwlink/?LinkId=140216), and recovery feature, to ensure that your servers and computers are protected even if they are lost or destroyed entirely. The image can be recovered onto a new device if necessary.
For the list of hardware requirements for AhsayOBM, refer to: Ahsay Hardware Requirement List (HRL)
For the list of compatible Windows operating systems platforms refer to: Ahsay Software Compatibility List (SCL)
To optimize performance of AhsayOBM on Windows, and to avoid conflict with your antivirus software, refer to Suggestion on antivirus exclusions to improve performance of Ahsay software on Windows for the list of processes and directory paths that should be added to all antivirus software white-list / exclusion list.
Make sure that AhsayOBM is installed on the computer to be backed up.
Make sure that the Windows System Backup add-on module is enabled for your AhsayOBM user account.
Make sure that your AhsayOBM user account has sufficient quota assigned to accommodate the storage for the system backup. Please Contact your backup service provider for details.
AhsayOBM licenses are calculated on a per device basis:
For Windows server platforms, the Windows Server Backup feature must be installed in order for either the system backup to take place. Confirm in the Server Manager, the feature can be added by selecting Add Roles and Features.
Ensure that you have the latest service packs installed. Updates to the Windows operating system improve its performance and resolve known issues with Windows Server Backup.
Make sure that the storage location configured for the system image is set to a supported location.
The temporary storage location is required by the WBADMIN utility to temporary store the image file during the backup set.
The machine requires an additional drive to accommodate the spooling of the System State image file. As you can on our sample screen shot above, we have three (3) drives in total, Local Disk C:, Temp1 E:, and Temp2 F:
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
i. An extra physical drive will need to be installed ii. The existing C: drive will need to be repartitioned to create an additional drive, i.e. D: iii. A USB drive needs to be connected iv. Setup a network drive
Refer to here for more details about the restrictions: Restrictions on the temporary storage location for the Windows System State and System backup image file
Make sure that there is sufficient disk space available in the storage location for the backup set. For a system backup, it will typically require disk space of the total used size of all volumes selected for backup.
NOTE Used space, not free space of all volumes selected for backup.
For Windows Vista, or 2008 / 2008 R2 Server, source volumes with size greater than 2 TB (e.g. 2040 GB - 2 MB = 2088958 MB) are not supported. This limitation is related to the .vhd file size limit.
NOTE This limitation does not apply to Windows 8 or newer releases of Windows platforms.