How to create AhsayCBS VM on 1&1 IONOS cloud platform

1&1 IONOS is a web hosting and cloud service provider established in UK. Because of their service quality, user friendly interface, and good pricing, we start seeing UK and European partners migrating their physical backup servers to its cloud platform.

Let’s see how you can easily create a Windows VM thru their drag-and-drop interface for running our AhsayCBS central management software.

1). After logging into 1&1 IONOS web interface, click Data Center.
1and1-01

2). Enter your data center info. The data center is a software defined (SDDC) in the public cloud, which is highly available, dynamically scalable virtual resources place with needs-based delivery and use-based billing. Within your data center, you can define multiple VMs. In this demo, we will be creating one Windows Server VM for running AhsayCBS software.

1and1-02

3). Select a region for this data center.

1and1-03

1and1-04

4). After the data center has been created, you can start creating a VM by dragging the Server icon to the canvas.

1and1-06

5). Connect this VM to the Internet by dragging the green dot to the “+” sign above the VM.

1and1-07

1and1-08

6). The VM has connected to the Internet through LAN 1.

1and1-09

7). You can setup the number of CPU cores and RAM size based on your requirement.

1and1-10

8). Then, add hard drive to the VM by dragging the HDD icon onto the VM.

1and1-11

1and1-12

9). A hard drive has been added to the VM. You can setup it’s size as needed.

1and1-13

10). 1&1 IONOS has got many common OS images for quick deployment. To use a readily available image, select 1&1 IONOS Images.

1and1-14

Then, select the image you need. In this demo, I have chosen Windows 2012 R2 Server.

1and1-15

11). Enter the password for the Windows Administrator that will be used for logging into the Windows OS.

1and1-16

12). Oops. Forgotten to give the hard drive a better name. No worries. Just click Resolve to modify it.

1and1-17

1and1-18

1and1-19

13). Click Provision Now to provision the VM.

1and1-20

1and1-21

1and1-22

14). After provision is  completed, click on the VM. You can either remote login to the VM through Remote Desktop Connection, or just click the Remote Control button in the web interface.

1and1-23

1and1-24

15). You can login to the Windows Server thru a web interface.

1and1-25

16). Send the Ctrl + Alt + Delete command to the Windows.

1and1-26

1and1-27

17). Use the password created in step 11). to login to the Windows Server as Administrator.

1and1-28

18). Done. Successfully logged in to the Windows Server. You can make any configuration to your Windows Server VM now.

1and1-29

19). For demo purpose, I just simply turn off Windows’ firewall. You can definitely make your own settings when you see fit.

1and1-30

1and1-31

20). Download the latest AhsayCBS software from Ahsay’s download page here.

1and1-32

21). Install AhsayCBS onto the Windows Server.

1and1-33

22). When completed, AhsayCBS web interface can be accessed through the local IP: 127.0.0.1.

1and1-34

23). You can also access the AhsayCBS console through the public IP provided by 1&1 IONOS.

1and1-35

1and1-36

1and1-37

1and1-38

1and1-39

1&1 IONOS offers free 30 days trial. Simply apply for a trial account to test it out.

Besides putting AhsayCBS on their cloud VM, you can also use their S3 compatible cloud object storage for storing your users’ backup data. See how it works with Ahsay through here.

in Tips | 500 Words

How to Create Windows System State Backup Set

BS_Create_sysstate







Requirements

Please ensure that the following requirements are met:



  • Software Requirement: MS System State backup can be run on Windows XP and Windows Server 2003/ 2008/ 2008 R2/ 2012/ 2012 R2/ 2016 or SBS 2008/ 2011.

For Windows XP and Windows Server 2003

!

Please kindly note that:


  • Windows XP home is not supported for the system state backup and restore by AhsayOBM.

  • As Windows XP and Windows Server 2003 are no longer supported by Microsoft any more, we will provide best effort support for backup and restore for these 2 Windows platforms.


  1. AhsayOBM Installation: Latest version of AhsayOBM must be installed on the computer to be backed up.

  2. Windows System State Add-on Module: Make sure that the Windows System State add-on module is enabled for your AhsayOBM user account.

  3. 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.

  4. Restore to Alternate Computer: You can restore a system state backup to the same physical computer from which the system state 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 state 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: http://support.microsoft.com/kb/249694

  5. NTBackup: NTBackup must be installed on the computer to be backed up. This can be confirmed either by searching if ntbackup.exe is found under C:\WINDOWS, or running the following command in an administrative command prompt:

    Microsoft Windows XP [Version 5.1.2600]

    (C) Copyright 1985-2001 Microsoft Corp.



    C:\Documents and Settings\support>ntbackup

    You can verify if NTBackup is installed or not by if the “Backup and Restore Wizard” pop out or not.


  6. System Volume: The system volume must be formatted with NTFS.

For Windows Server 2008 and Newer Releases


  1. AhsayOBM Installation: Latest version of AhsayOBM must be installed on the computer to be backed up.

  2. Windows System State Add-on Module: Make sure that the Windows System State add-on module is enabled for your AhsayOBM user account.

  3. Backup Quota Requirement: Make sure that your %edition_name% user account has sufficient quota assigned to accommodate the storage for the system state backup for the new backup set and retention policy. The size of a set of system state backup data is dependent on the role installed.

  4. Restore to Alternate Computer: You can restore a system state backup to the same physical computer from which the system state 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 state 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: http://support.microsoft.com/kb/249694

  5. Java Heap Size: 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).

  6. Windows Server Backup (WSB) Features: The following Windows Server Backup feature must be installed on the computer to be backed up:

    • Windows Server Backup

    • Command line Tool

    • Windows PowerShell


    This can be confirmed in the Server Manager. These features can be added by selecting Add Roles and Features.

  7. Windows Account Permission: To perform recovery using Windows Server Backup, the operating system account that you use must be a member of the Backup Operators or Administrators group.

  8. Latest Service Packs from Microsoft: Make sure that you have the latest service packs installed on the computer to be backed up. Update to the Windows operating system improve its performance and resolve known issues with Windows Server Backup.

  9. System Volume: The system volume must be formatted with NTFS.

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:


  1. Temporary Directory Folder Location: Temporary directory folder is used by %edition_name% 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.

    !

    Kindly noted that for Windows Server 2008 or newer releases, the restriction on temporary volume must also be considered.


  2. 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



  3. Backup Frequency: MS Windows System State backup should be performed at least once per week.

  4. 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.



Set the backup set

Name This is the name of the backup set. You can create a meaningful name for it.
Backup Type Enter the correct backup type from the drop down box.
Specify the temporary location for the system backup (For Windows Server 2008 and newer releases only) Select the location where you would like to store the system state image before generating the backup data.

To create a backup set:



  1. Type in a meaningful backup set name.

  2. Enter correct backup type, eg: MS Windows System State Backup.

  3. For Windows Server 2008 and newer releases, select the location where you would like to store the system state image before generating the backup data.

    !

    Kindly noted that for Windows 2008 Server, the temporary storage location cannot be set to a network path.


  4. Click [Next] button to start the verifying process and continue.



in Tips | 1,073 Words

How to Create Windows System Backup Set

BS_Create_winsys







Backup Requirements

For System backup of Windows 2008/ 2008 R2/ 2012/ 2012 R2/ 2016 or SBS 2011, please ensure that the following requirements or recommendations are met:



  1. AhsayOBM is installed on the computer to be backed up.

  2. Sufficient disk spaces are required for the temporary directory (actual size depending on the volume).

  3. The following Windows Features are installed on the client computer:


    Windows Server Backup Features




    • Windows Server Backup

    • Command line Tool

    • Windows PowerShell




  4. Limitations on the temporary directory:




    • Temporary directory must be a local or USB drive and local drive is preferred option.

    • Temporary directory can be a non-critical or critical drive.

    • Temporary directory can only be set to the root of a drive.

    • Shadow Copies storage location of temporary directory must be set to local.




  5. The Microsoft Windows System backup module (wbadmin start backup) uses the .vhd format for writing backups.

For System backup of Windows 7, Windows 2008/ 2008 R2/ SBS 2011 and Windows Home Server 2011, the current virtual hard disk specification limits the size of a virtual hard disk to be 2040 GB (2 TB), which can fit a volume of size 2040 GB minus 2 MB.


For details, please refer to:

http://blogs.technet.com/b/ranjanajain/archive/2010/03/23/virtual-hard-disk-vhd-architecture-explained.aspx

http://technet.microsoft.com/en-us/library/dd183729%28v=ws.10%29.aspx

Set the name of the backup set

Name This is the name of the backup set. You can create a meaningful name for it.
Backup Type Enter the correct backup type from the drop down box.

To create a backup set name:



  1. Type in a meaningful backup set name.

  2. Enter correct backup type, eg: MS Windows System backup.

  3. Click [Next] button to continue.



in Tips | 283 Words

How to Create Microsoft Exchange Mail Level Backup Set

BS_Create_exchange-mail







Overview

Mail Level Backup must be utilized in conjunction with full Information Store Backup as Mail Level backup for Microsoft Exchange Server is not designed to fully protect an Exchange Server, but to facilitate easy backup and fast restoration of individual emails, contacts, calendars or public folder, etc.

AhsayOBM supports standalone backup option and Database Availability Group (DAG) backup option for Exchange server mail level backup. From version 7.15.0.0 onwards, %edition_name% supports mail level backup and restore of Exchange Server 2016 by installing either on the Exchange server 2016 hosting the database or on the remote backup machine.

Exchange Server 2016

Requirements

You are strongly recommended to configure or check all the settings below to confirm all the requirements are met before you proceed with the Exchange Mail Level backup and restoration:


  1. AhsayOBM v7.15.0.0 or above must be installed either on the Exchange Server 2016 hosting the database or on the remote backup machine.
  2. Make sure the Microsoft Exchange Mailbox feature has been enabled as an add-on module in your AhsayOBM user account and there is sufficient Microsoft Exchange Mailbox license quota to cover the backup of your mailboxes.

  3. As AhsayOBM licenses are calculated on a per device basis:

    • For backup of mailboxes on a standalone Microsoft Exchange 2016 Server, one AhsayOBM license is required.

    • For backup of mailboxes on a Microsoft Exchange Server 2016 DAG setup, the number of %edition_name% licenses required is equal to the number of members (nodes) in the DAG. For example, if there are three members then three AhsayOBM licenses are required.



  4. Make sure that your AhsayOBM user account has sufficient storage quota assigned to accommodate the storage of additional Exchange mailbox and public folder items for the new mail level backup set and retention policy.

  5. The Continuous backup add-on module is required if would like to enable the continuous backup feature.

  6. The default Java heap size setting of AhsayOBM is 2048MB. For Exchange 2016 mail level backup, it is highly recommended to increase the Java heap size setting to be at least 4096MB to improve backup and restore performance. The actual heap size is dependent on amount of free memory available on your Exchange 2016 server.

  7. Temporary Directory folder is used by AhsayOBM for storing backup set index files and any incremental or differential delta files generated during a backup job. To ensure optimal backup/restoration performance, it is recommended that the temporary directory folder is located on a local drive with sufficient free disk space.

  8. Scheduled backup is required if you choose to back up in DAG option on Exchange server as AhsayOBM on all DAG members will base on the scheduled backup time to start backup on all the individual DAG member at the same time. However, scheduled backup is not required for backup and restore on the remote backup machine as the operation for single node can be done either manually or automatically.

  9. Ensure all the nodes have mailbox role by accessing the Exchange Admin Center (EAC).

  10. For AhsayOBM installed on the Exchange Server 2016, the operating system must be Windows Server 2012/ 2012 R2/ 2016 or above. For %edition_name% installed on the remote backup machine, the operating system must be Windows 7/ 8/ 8.1/ 10 or Windows Server 2008/ 2008 R2/ 2012/ 2012 R2/ 2016 or above.

  11. One Microsoft Exchange Mailbox license is required for the backup of each user mailbox. No license is required for public folder.

  12. MS Exchange Server 2016 Cumulative Update 4 (CU4) or above is supported.

  13. Windows User account used for the backup must be a member of the following security groups.

    • Discovery Management (including ApplicationImpersonation and Mailbox Search)

    • Organization Management

    • Public Folder Management



  14. Windows user account must have an Exchange Server mailbox. Refer to the URL below for more information: http://support.microsoft.com/kb/275636/en-us

  15. Ensure that the “Hide from address lists” option is unchecked for all mailboxes to be selected for backup. Mailbox hidden from the address list will not be shown in the backup source selection menu.

  16. As Exchange Server 2016 uses EWS API, please ensure port 443 is configured to allow communication between AhsayOBM and Exchange Server 2016.

  17. Ensure that all MS Exchange related services have been started, particularly the MS Exchange Information Store.

  18. Ensure the MS Exchange Mailbox and Public Folder databases are mounted.

  19. Ensure the Windows PowerShell 5.1 Engine is installed.

  20. Ensure .Net Framework 4.6.2 Features is installed. Please refer to the following URL for detailed information: https://technet.microsoft.com/en-us/library/aa996719(v=exchg.160).aspx

Supported Backup Source

Below is the supported backup source for mail level backup and restore of Exchange Server 2016.


  1. Mailbox Level: User mailbox, Public Folder mailbox, Public Folder, Room Mailbox, Equipment Mailbox, Shared Mailbox.

  2. Folder Level: Inbox, Drafts, Sent Items, Deleted Items, Archive, Clutter, Junk Email, RSS Feeds, Trash, Tasks, Calendar, Contacts, Notes.

Limitation


  1. For restore of Exchange 2016 Mail Level backup set to alternate location, there is some limitation:

    • If you are trying to restore item(s) form one mailbox to an alternate location mailbox, AhsayOBM will restore the item(s) to their respective destination folder(s) with the same name of the original folder(s).

      Example: Item from “Inbox” folder of Mailbox-A will be restored to the “Inbox” folder of the alternate location Mailbox-B; Item from “Drafts” folder of Mailbox-A will be restored to the “Drafts” folder of the alternate location Mailbox-B.


    • If you are trying to restore item(s) form several mailboxes to an alternate location mailbox, AhsayOBM will restore the item(s) to their respective destination folder(s) with the same name of the original folder(s).

      Example: Item from “Inbox” folder of Mailbox-A and Mailbox-B will be restored to the “Inbox” folder of the alternate location Mailbox-C.


    • Restore of public folder item(s) to an alternate location mailbox is not supported.

      Example: Restore of public folder items from Mailbox-A to alternate location Mailbox-B is not supported.




  2. Restore of mailbox items or public folder items is only supported if the according mailbox or public folder exists.

  3. Only Alternate Location is supported for restoring mailbox items to another domain.

  4. If you are trying to restore the mailbox item to a destination mailbox which has a different language setting than the original mailbox, AhsayOBM will restore mailbox item(s) to their respective destination folder based on the translation listed below. For folders such as ‘Calendar’ or ‘Notes’, a new folder ‘Calendar’ or ‘Notes’ will be created.

    Backup source (English) Action Destination mailbox with Chinese as default language settings
    Inbox Merge 收件箱
    Outbox Merge 寄件匣
    Sent Items Merge 寄件備份
    Deleted Items Merge 刪除的郵件
    Drafts Merge 草稿
    Junk E-Mail Merge 垃圾電郵
    Calendar Create new folder Calendar
    Notes Create new folder Notes


Best Practice and Recommendation

The following are some best practices or recommendations we strongly recommend you to follow before you start any Exchange Server 2016 Mail Level backup and restore:


  1. Mail Level Backup must be utilized in conjunction with Database Level Backup to fully protect an Exchange Server.

  2. Active Directory server should be protected by regular full Windows System Backup at least once every two weeks.

  3. For AhsayOBM installed on Exchange Server, enable scheduled backup jobs when system activity is low to achieve the best possible performance.

  4. The remote backup machine should be on the same LAN as the MS Exchange server for optimal backup and restore performance.


  5. 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



  6. 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.

  7. For backup of multiple or mass backup sets, to achieve better backup performance and to minimize any unnecessary loading on the Exchange server, please consider deploying AhsayOBM on remote backup machines as distributed backup solution instead of on the MS Exchange server.

  8. For backup of a large number of mailboxes, it is recommended to divide all mailboxes into multiple backup sets.

Create backup set

Field Description
Name This is the name of the backup set. You can create a meaningful name for it.
Backup set type Enter the correct backup type from the drop down box.
Version Enter the correct version of the Exchange server from the drop down box.
Host Hostname of the Exchange server. (for standalone backup option)
Host (DAG Member Server) Hostname of the DAG Member Server. (for DAG backup option)
Username Username of the Windows user account used for backup of the Exchange server.
Password Password of the Windows user account used for backup of the Exchange server.

To create a backup set for standalone backup option:



  1. Type in a meaningful backup set name.

  2. Enter correct backup type, eg: MS Exchange Mail Level Backup.

  3. Enter the version of Exchange server if AhsayOBM installed on remote backup machine, eg: Microsoft Exchange Server 2016. If installed on the Exchange Server, %edition_name% will detect the version of Exchange server automatically.

  4. Enter the hostname of the Exchange server.

  5. Enter the username of the Windows user account used for backup of the Exchange server.

  6. Enter the password of the Windows user account used for backup of the Exchange server.

  7. Check the box “Access the Internet through proxy” if required.

  8. Click [Next] button to continue.


To create a backup set for DAG backup option:



  1. Type in a meaningful backup set name.

  2. Enter correct backup type, eg: MS Exchange Mail Level Backup.

  3. Enter the version of Exchange server if AhsayOBM installed on remote backup machine, eg: Microsoft Exchange Server 2016 (DAG). If installed on the Exchange Server, AhsayOBM will detect the version of Exchange server automatically.

  4. Add the hostname of all the DAG Member Server.

  5. Enter the username of the Windows user account used for backup of the Exchange server.

  6. Enter the password of the Windows user account used for backup of the Exchange server.

  7. Check the box “Access the Internet through proxy” if required.

  8. Click [Next] button to continue.

Exchange Server 2007/ 2010/ 2013

Requirements

Please ensure that following requirements are met by the MS Exchange server / DAG:



  1. AhsayOBM is installed on the MS Exchange node with Mailbox role.

  2. If you are using Exchange server 2013 on Windows server 2012, please install “.Net Framework 3.5 Features” under Server Manager > Dashboard > Add Roles and Features Wizard > Feature Page.

  3. PowerShell 2.0 Engine is installed.

  4. LAN Manager authentication level is set to 3 or above. If the LAN Manager authentication level is not set to 3 or above, the error message will be prompted and AhsayOBM will ask for the reconfiguration. Server restart is required.


    To check on the setting, refer to this KB article from Microsoft..

  5. Microsoft Messaging Application Programming Interface (MAPI) is installed on the MS Exchange server. (Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1 (version 6.5.8320.0 or above) is installed)

  6. The operating system account to be running the Mail Level backup (e.g. administrator) must have a mailbox and is not hidden from the Global Mailbox List.

    Scheduled backup is performed using the operating system account configured in the “User Authentication for Windows” field.

    If such setting is not configured, the scheduled backup would precede with the default Local System account (default log on account for %edition_name% scheduler).

    In this case, the backup will most likely fail with permission denied error.

Granting Privileges:

Mail Level backup requires “Full Mailbox Access” permission for the user running %edition_name%.


Please refer to the following instruction for granting permission to the operating system account to be running the Mail Level backup:


For one specific mailbox

Use the following procedure to grant access to Exchange 2007 mailbox:



  1. Start the “Active Directory Users and Computers” applet.

  2. On the “View” menu, ensure that the “Advanced Features” option is selected.

  3. Right click the user whose mailbox you want to give permissions to and choose “Properties”.

  4. On the “Exchange” Advanced tab, click “Mailbox Rights”.

  5. Notice that the Domain Admins and Enterprise Admins have both been given Deny access to Full Mailbox access.

  6. Click “Add”, click the user or group who you want to have access to this mailbox, and then click [OK].

  7. Ensure that the user or group is selected in the Name box.

  8. In the “Permissions” list, click “Allow” next to “Full Mailbox Access”, and then click [OK].

  9. Click [OK] all the way out.

  10. Restart the “Microsoft Exchange Information Store” service.


For mailboxes located within a specific mailbox store

Use the following procedure to grant access to Exchange 2007 mailbox found on a specific mail store:



  1. Start the [Exchange System Manager] applet.

  2. Navigate to the server object within the appropriate Administrative Group.

  3. Expand the server object and find the required mailbox store within the appropriate Storage Group. Right click it and choose [Properties].

  4. In the [Properties] window, go to the [Security] tab.

  5. Click [Add], click the user or group who you want to have access to the mailboxes, and then click [OK].

  6. Be sure that the user or group is selected in the Name box.

  7. In the [Permission] list, check [Allow] next to [Full Control], and then click [OK].

  8. Click [Apply] and [OK].

  9. Restart the [Microsoft Exchange Information Store] service.


For Exchange 2007, please refer to the following instructions:



  1. Add an operating system account to the Exchange 2007 server.


    This account must be a member of the following groups:



    • Local Administrators (Built in)

    • Domain Admins group

    • Enterprise Admins group



  2. Enter the following command in Exchange Management Shell:

    Get-MailboxServer | Add-ADPermission -User “%USER%” -AccessRights GenericAll -ExtendedRights ms-exch-store-admin,receive-as,send-as -InheritanceType All

    Example, to grant the permission for local account “system”

    Get-MailboxServer | Add-ADPermission -User “system” -AccessRights GenericAll -ExtendedRights ms-exch-store-admin,receive-as,send-as -InheritanceType All

    To show added permission for an AD account

    Get-MailboxServer | Get-ADPermission -User “%USER%”

    Example, to show added permission for local account “system”

    Get-MailboxServer | Get-ADPermission -User “system”

    To remove permission from an AD account

    Get-MailboxServer | Remove-ADPermission -User “%USER%” -AccessRights GenericAll -ExtendedRights ms-exch-store-admin,receive-as,send-as -InheritanceType All

    Example, to remove permission from local account “system”

    Get-MailboxServer | Get-ADPermission -User “system”

    To remove permission from an AD account

    Get-MailboxServer | Remove-ADPermission -User “%USER%” -AccessRights GenericAll -ExtendedRights ms-exch-store-admin,receive-as,send-as -InheritanceType All

    Example, to remove permission from local account “system”

    Get-MailboxServer | Remove-ADPermission -User “minimal” -AccessRights GenericAll -ExtendedRights ms-exch-store-admin,receive-as,send-as -InheritanceType All



For Exchange Server 2010 and 2013, please refer to the following instructions:



  1. Add an operating system account to the Exchange 2010/2013 server.


    This account must be a member of the following security groups:



    • Microsoft Exchange Security\Organization Management

    • Users\Administrator

    • Users\Domain Admins

    • Users\Enterprise Admins



  2. For Exchange 2010, ensure that Update Rollup 3 for Exchange Server 2010 (KB981401) is installed.


    Please refer to the following article for more details: http://www.microsoft.com/download/en/details.aspx?displayLang=en&id=415 .


  3. Enter the following command in Exchange Management Shell:

    Get-Mailbox | Add-MailboxPermission -User “%OS_USERNAME%” -AccessRights FullAccess

    Example:

    Get-Mailbox | Add-MailboxPermission -User “system” -AccessRights FullAccess

    Other useful commands:


    Remove permission from an AD account

    Get-Mailbox | Remove-MailboxPermission -User “%OS_USERNAME%” -AccessRights FullAccess

    Example:

    Get-Mailbox | Remove-MailboxPermission -User “system” -AccessRights FullAccess

    To view the mailbox permission of a user

    Get-Mailbox | Get-MailboxPermission -User “%OS_USERNAME%”

    Example:

    Get-Mailbox | Get-MailboxPermission -User “SYSTEM”




in Tips | 2,520 Words

How to Create Microsoft Exchange Server Backup Set

BS_Create_exchange-server





Overview

For a complete Exchange server backup, backup for the following components must be performed.


System State:

For Exchange server with Active Directory installed, as part of the restore, the system state of the server must also be restored.


Running regular system state backups of the Exchange is therefore crucial, as it ensures that the system state data is synchronized with the Exchange database data.


Information Store (Exchange 2007):

The Information Store of Exchange 2007 contains both mailbox store and public folder store data.


The server stores data in two files, namely the .edb and the .stm file, that form an Exchange store repository.


The default mailbox store on an Exchange 2007 server uses filename Priv1.edb and Priv1.stm; the default public folder store uses the filename Pub1.edb and Pub1.stm.


The .edb file contains tables that hold metadata for all e-mail messages and other items in the Exchange store, while .stm stores native Internet content.


Information Store (Exchange 2010 / 2013 / 2016):

The Information Store of Exchange 2010/2013 contains data, data definitions, indexes, checksums, flags, and other information that comprise mailboxes in Exchange.


Mailbox databases hold data that is private to individual user and contain mailbox folders generated when a mailbox is created for that user. A mailbox database is stored as an Exchange database .edb file.


Public folder databases contain the data, data definitions, indexes, checksums, flags, and other information that comprise any public folders in your Exchange organization.


In Exchange Server 2010/2013, public folder is an optional feature.

Backup Requirements for Exchange Server 2007

Please ensure that the following requirements are met by the MS Exchange server:



  1. The Exchange databases selected for backup will be temporarily spooled to a temp directory before being uploaded to the backup server.

    It is recommended that the temporary directory that has a disk space of at least 120% of the total database size (e.g. total size of all .edb files found within the MS Exchange Server installation folder).

  2. It is recommended that the temporary directory is configured on a local drive.

  3. For Exchange server with Active Directory installed, a System State backup must be performed regularly with the MS Exchange server backup.

Backup Requirements for Exchange Server 2010

Please ensure that the following requirements are met by the MS Exchange server:



  1. The Exchange server 2010 backup does not require spooling the database to the hard disk, however the VSS Exchange backup still requires certain amount of disk space to operate. Microsoft suggested that some shadow copy mechanism may require to reserve the disk space of 100% of the original database.
    Reference: http://msdn.microsoft.com/en-us/library/exchange/aa579091%28v=exchg.140%29.aspx

  2. It is recommended that the temporary directory is configured on a local drive.

  3. For Exchange server with Active Directory installed, a System State backup must be performed regularly with the MS Exchange server backup.

Backup Requirements for Exchange Server 2013/2016

Please ensure that the following requirements are met by the MS Exchange server:



  1. If you are using Exchange server 2013/2016 on Windows server 2012, please install “.Net Framework 3.5 Features” under Server Manager > Dashboard > Add Roles and Features Wizard > Feature Page

  2. The Exchange server 2013/2016 backup does not require spooling the database to the hard disk, however the VSS Exchange backup still requires certain amount of disk space to operate. Microsoft suggested that some shadow copy mechanism may require to reserve the disk space of 100% of the original database.
    Reference: http://msdn.microsoft.com/en-us/library/exchange/aa579091%28v=exchg.140%29.aspx

  3. It is recommended that the temporary directory is configured on a local drive.

  4. For Exchange server with Active Directory installed, a System State backup must be performed regularly with the MS Exchange server backup.

Backup Requirements for Exchange Server 2010 DAG

Please ensure that the following requirements are met by the MS Exchange server:



  1. The Exchange server 2010 backup does not require spooling the database to the hard disk, however the VSS Exchange backup still requires certain amount of disk space to operate. Microsoft suggested that some shadow copy mechanism may require to reserve the disk space of 100% of the original database.
    Reference: http://msdn.microsoft.com/en-us/library/exchange/aa579091%28v=exchg.140%29.aspx

  2. It is recommended that the temporary directory is configured on a local drive.

  3. For Exchange server with Active Directory installed, a System State backup must be performed regularly with the MS Exchange server backup.
  4. Scheduled backup on DAG is required, as all the AhsayOBM on different Exchange servers will base on the scheduled backup time to activate all the backups at the same time, even all these Exchange servers are located in different timezones. When the backup on all Exchange servers are finished, a single email report will be generated.
  5. The scheduler refers to the timezone setting of the corresponding AhsayOBM account’s profile (instead of the system clock on the client machine for stand-alone Exchange server backup).
  6. Manual backup on individual node is not considered as a complete Exchange DAG backup.

  7. The backup module protects the Exchange at the database level. If full system backup is required, please run a full Windows system backup on each Exchange server within the DAG.

  8. To backup mailbox database within an Exchange DAG, AhsayOBM is required to be installed on each DAG member with Mailbox Role (e.g. servers that are hosting the mailbox databases). It is not necessary to install AhsayOBM on Exchange server with CAS (Client Access Server) Role only.

Backup Requirements for Exchange Server 2013/2016 DAG

Please ensure that the following requirements are met by the MS Exchange server:



  1. If you are using Exchange server 2013/2016 on Windows server 2012, please install “.Net Framework 3.5 Features” under Server Manager > Dashboard > Add Roles and Features Wizard > Feature Page

  2. The Exchange server 2013/2016 backup does not require spooling the database to the hard disk, however the VSS Exchange backup still requires certain amount of disk space to operate. Microsoft suggested that some shadow copy mechanism may require to reserve the disk space of 100% of the original database.
    Reference: http://msdn.microsoft.com/en-us/library/exchange/aa579091%28v=exchg.140%29.aspx

  3. It is recommended that the temporary directory is configured on a local drive.

  4. For Exchange server with Active Directory installed, a System State backup must be performed regularly with the MS Exchange server backup.
  5. Scheduled backup on DAG is required, as all the AhsayOBM on different Exchange servers will base on the scheduled backup time to activate all the backups at the same time, even all these Exchange servers are located at different timezones. When the backup on all Exchange servers are finished, a single email report will be generated.
  6. The scheduler refers to the timezone setting of the corresponding AhsayOBM account’s profile (instead of the system clock on the client machine for stand-alone Exchange server backup).
  7. Manual backup on individual node is not considered as a complete Exchange DAG backup.

  8. The backup module protects the Exchange at the database level. If full system backup is required, please run a full Windows system backup on each Exchange server within the DAG.

  9. To backup mailbox database within an Exchange DAG, AhsayOBM is required to be installed on each DAG member with Mailbox Role (e.g. servers that are hosting the mailbox databases). It is not necessary to install AhsayOBM on Exchange server with CAS (Client Access Server) Role only.

Set the name of the backup set

Key:

Field Description
Name This is the name of the backup set. You can create a meaningful name for it.
Backup Type Enter the correct backup type from the drop down box.
Version Version of the Exchange server.

To create a backup set name:



  1. Type in a meaningful backup set name.

  2. Select the correct backup type, eg: MS Exchange Server Backup.

  3. Select the version of Exchange server.

  4. Click [Next] button to continue.



in Tips | 1,281 Words

How to Create Office 365 Exchange Online Backup Set

BS_Create_o365





Office 365 Backup allows you to backup your mailbox, OneDrive and Sharepoint files from your Office 365 account.

Requirements

You are strongly recommended to configure or check all the settings below to confirm all the requirements are met before you proceed with the Office 365 backup and restoration:



  1. Make sure that the latest version of AhsayOBM is installed on your computer with Internet access for connection to your Office 365 account.

  2. Make sure that the Office 365 Backup feature has been enabled as an add-on module in your AhsayOBM user account and there is sufficient Office 365 Backup license quota to cover the backup of your mailboxes, OneDrive and Sharepoint files.

  3. As AhsayOBM licenses are calculated on a per device basis:

    • To backup mailboxes with 1 backup client computer / Exchange server (e.g. 1 AhsayOBM installed), 1 %edition_name% license is required.

    • To backup mailboxes with multiple backup client computers, the number of %edition_name% licenses required is equal to the number of devices. For example, if there are 10 mailboxes to be backup with 3 backup client computers, then 3 %edition_name% licenses are required.



  4. Make sure that your AhsayOBM user account has sufficient quota assigned to accommodate the storage of the Office 365 mailboxes, OneDrive and Sharepoint files for the new backup set and retention policy.

  5. The Continuous backup add-on module is required if you would like to enable the continuous backup feature.

  6. The default Java heap size setting on AhsayOBM is 2048MB. For Office 365 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 is dependent on amount of free memory available on the machine with AhsayOBM installed (machine that is running the backup).

  7. One Office 365 Backup license is required for the backup of each user mailbox. No license is required for public folder.

  8. The following subscription plans with Exchange Online email services are supported to run backup and restore on AhsayOBM: Office 365 Business Essentials, Office 365 Business Premium, Office 365 Education, Office 365 Enterprise E1, Office 365 Enterprise E3, Office 365 Enterprise E4, Office 365 Enterprise E5.

  9. Make sure your Office 365 subscription with Microsoft is active in order to enjoy all privileges that come along with our backup services. If your account has expired, renew it with Microsoft as soon as possible so that you can continue to enjoy the Office 365 backup services. When your account is expired, depending on your role, certain access restrictions will be applied to your account. Refer to the URL below for more details: https://support.office.com/en-us/article/What-happens-to-my-data-and-access-when-my-Office-365-for-business-subscription-ends-4436582f-211a-45ec-b72e-33647f97d8a3#BKMK_TrialEnds

  10. User account used for the backup must be a member of the following security groups:

    • Discovery Management

    • Public Folder Management



  11. User account used to list Personal Sites, OneDrive and Outlook data of other Office 365 users must have the following roles:

    • Exchange Mail Setting: Application Impersonation and Mailbox Search

    • OneDrive Setting: Global Administrator

    • Sharepoint Setting: Global Administrator


Supported Backup Source

Below is the supported backup source for Office 365 Backup and Restore.


  1. Mailbox Level: Outlook, OneDrive and Personal Site.

  2. Folder Level: Inbox, Drafts, Sent Items, Deleted Items, Archive, Calendar, Contacts, Junk Email, Notes and Tasks.

Limitation


  1. For restoration of Office 365 backup set to alternate location, there is some limitation:

    • Only administrator account or user account with administrative authority can restore backup mailbox items to an alternate location.

    • If you are trying to restore item(s) from one mailbox to an alternate location mailbox, AhsayOBM will restore the item(s) to their respective destination folder(s) with the same name of the original folder(s).

      Example: Item from “Inbox” folder of Mailbox-A will be restored to the “Inbox” folder of the alternate location Mailbox-B; Item from “Drafts” folder of Mailbox-A will be restored to the “Drafts” folder of the alternate location Mailbox-B.


    • If you are trying to restore item(s) from several mailboxes to an alternate location mailbox, AhsayOBM will restore the item(s) to their respective destination folder(s) with the same name of the original folder(s).

      Example: Item from “Inbox” folder of Mailbox-A and Mailbox-B will be restored to the “Inbox” folder of the alternate location Mailbox-C.


    • Restore of public folder item(s) to an alternate location mailbox is not supported.

      Example: Restore of public folder items from Mailbox-A to alternate location Mailbox-B is not supported.




  2. Restore of mailbox items or public folder items is only supported if the according mailbox or public folder exists.

  3. If you are trying to restore the mailbox item to a destination mailbox which has a different language setting than the original mailbox, AhsayOBM will restore mailbox item(s) to their respective destination folder based on the translation listed below. For folders such as ‘Calendar’ or ‘Notes’, a new folder ‘Calendar’ or ‘Notes’ will be created.

    Backup source (English) Action Destination mailbox with Chinese as default language settings
    Inbox Merge 收件箱
    Outbox Merge 寄件匣
    Sent Items Merge 寄件備份
    Deleted Items Merge 刪除的郵件
    Drafts Merge 草稿
    Junk E-Mail Merge 垃圾電郵
    Calendar Create new folder Calendar
    Notes Create new folder Notes


Best Practice and Recommendation

The following are some best practices or recommendations we strongly recommend you to follow before you start any Office 365 backup and restore.


  1. 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.

  2. 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.



  3. Office 365 service has set a size limit for individual mail object to be uploaded. Considering the size of the mail object may become larger as a result of the transcoding process when it is being sent out, we strongly recommend you to keep individual mail object no larger than 80MB if you definitely want it to be backed up.

  4. 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



  5. For backup of a large number of mailboxes, it is recommended to divide all mailboxes into multiple backup sets.

Creating an Office 365 Backup Set

Name This is the name of the backup set. You can create a meaningful name for it.
Backup set type Enter the correct backup type from the drop down box.
Username Username of the Office 365 account used for backup of mailbox, OneDrive and Sharepoint files.
Password Password of the Office 365 account used for backup of mailbox, OneDrive and Sharepoint files.
Region Region where the Office 365 account is registered.

To create a backup set:



  1. Type in a meaningful backup set name.

  2. Enter correct backup type, eg: Office 365 Backup.

  3. Enter the login details on the current page, then click Test to verify your account information. A confirmation text Test completed successfully will be shown when %edition_name% is connected to the Office 365 service account successfully.

  4. Enter correct region, eg: Global.

  5. Check the box “Access the Internet through proxy” if required.

  6. Click [Next] button to continue.



in Tips | 1,268 Words

How to Create Hyper-V Backup Set

BS_Create_hyperv







Backup Requirements

AhsayOBM Requirements

Please ensure that the following requirements are met by the AhsayOBM



  1. AhsayOBM is installed on the Hyper-V server. For Hyper-V Cluster environments AhsayOBM is installed on all Cluster nodes.

  2. The operating system account for setting up the Hyper-V / Hyper-V Cluster backup set must have administrator permission (e.g. administrative to access the cluster storage).

  3. AhsayOBM user account has sufficient Hyper-V add-on modules or CPU sockets assigned. Hyper-V Cluster backup sets will require one %edition_name% license per node.

  4. Storage destination has sufficient quota assigned to accommodate the storage of the guest virtual machines.

    Hyper-V guest virtual machines contain three types of virtual disks:

    • Fixed Hard Disk.

    • Dynamic Hard Disk.

    • Differencing Hard Disk.


    When AhsayOBM backs up a Hyper-V guest virtual machines for an initial or subsequent full backup jobs:

    • Using Fixed Hard Disks will back up the provisioned size, i.e. for a 500GB fixed virtual hard disk, 500GB will be backed up to the storage designation.

    • Using Dynamic Hard Disk or Differencing Hard Disk will back up the used size, i.e. for a 500GB dynamic virtual hard disk, 20GB will be backed up to the storage designation if only 20GB is used.


  5. The default Java heap size setting on %edition_name% is 2048MB. For Hyper-V backups it is highly recommended to increase the Java heap size setting to improve backup and restore performance. (The actual heap size is dependent on amount of free memory available on your Hyper-V server).
    Delta generation of large VHD file is a memory intensive process, therefore, it is recommended to increase the Java heap size to be at least 4096MB. The actual required Java heap size is subject to various factors including files size, delta mode, backup frequency, etc.

  6. The temporary directory folder is used by AhsayOBM for storing backup set index files and any incremental or differential delta files generated during a backup job. To ensure optimal backup/restore performance, it is recommended to be located on a local drive with plenty of free disk space but not on the Windows system C:\ drive.
    For Hyper-V 2008 R2, 2012, and 2012 R2, the temporary directory folder can only be set to local drive, and neither network or CSV path can be supported which is determined by the limitation of AhsayOBM CBT service. Only Hyper-V 2016 supports local, network and CSV volumes for temporary directory folder.

  7. AhsayOBM UI must be running when a guest virtual machine is started using Run Direct Restore or when migration process is running.

  8. For local, mapped drive, or removable drive storage destinations with Run Direct enabled, the compression type will always be set to No Compression and data encryption is disabled to ensure optimal backup and restore performance. The compression type and data encryption settings of backup set will only be applied to AhsayCBS, SFTP/FTP, or Cloud storage destinations.

  9. For ease of restore, it is recommended to back up the whole guest machine (all the virtual disks) rather than individual virtual disks.

  10. MS Windows system Backup is unable to create image of drives that are greater than 2TB on Windows 2008, 2008 R2 & 2011, due to the limitation of MS wbadmin using VHD format that is used in creating the image. The limitation in Windows 2012 has been increased to 64TB.

    For details, please refer to:
    https://support.microsoft.com/en-us/help/2696906/backup-fails-in-windows-7-when-trying-to-create-a-system-image

  11. Make sure NFS service has started for Run Direct to operate. If Run Direct is running on network drive, the login must have sufficient permission to access the network resources.

Hyper-V Server Requirements

Please ensure that the following requirements are met by the Hyper-V server



  1. The Hyper-V management tools are installed on the server. For Hyper-V Cluster environments, Hyper-V management tools is installed on all Cluster nodes.

  2. The Hyper-V services are started on the server. For Hyper-V Cluster environments the Hyper-V services are started on all Cluster nodes.

  3. The Microsoft Hyper-V VSS Writer is installed and running on the Hyper-V server and the writer state is Stable. This can be verified by running the vssadmin list writers command.

    vssadmin list writers

    Look for the script:

    Writer name: ‘Microsoft Hyper-V VSS Writer’
    Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
    Writer Instance Id: {a51919e3-0256-4ecf-8530-2f600de6ea68}
    State: [1] Stable
    Last error: No error


  4. If Integration services is not installed / updated on a guest virtual machine or the guest operating system is not supported by Integration Services, the corresponding virtual machine will be paused or go into a saved state during the snapshot process for both backup and restore, and resume when the snapshot is completed. Furthermore, the corresponding virtual machine uptime will also be reset to 00:00:00 in the Hyper-V Manager.

  5. Installing or updating Integration Services guest virtual machine(s) may require a restart of the guest virtual machine to complete the installation.

  6. For Hyper-V 2008 R2 server in order to use Run Direct restore feature, the “Microsoft Security Advisory 3033929″ security update must be installed.

    For details, please refer to:
    https://support.microsoft.com/en-us/kb/3033929

  7. For Run Direct Hyper-V Cluster backup sets, the storage destination must be accessible by all Hyper-V nodes.

  8. For Hyper-V Cluster backup sets, the guest virtual machines must be created and managed by the Failover Cluster Manager.

Hyper-V Backup Methods

AhsayOBM v7 supports two methods for Hyper-V guest VM backup, VM Snapshot and Saved State.



  1. VM Snapshot
  2. The VM snapshot method is the preferred backup option, as it supports live guest VM backups. This means guest VM will not be put into a saved state when a VSS snapshot is taken during a backup job. So it will not affect the availability of any application or services running on the guest VM every time a backup job is performed.

    !

    If the VM Snapshot method cannot be used, %edition_name% will automatically use the Saved State method.

    VM Snapshot Method Requirements


    • The guest VM must be running.

    • Integration services must be enabled on the guest VM.

    • The Hyper-V Volume Shadow Copy Requestor service is running on the guest VM installed with Windows operating system.

      For details, please refer to:
      https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/reference/integration-services#hyper-v-volume-shadow-copy-requestor

    • For guest VMs installed with Linux/FreeBSD operating systems, the VSS Snapshot daemon is required for live backups, not all Linux/FreeBSD versions support live backup on Hyper-V. For example, only FreeBSD 11.1 supports live backup; while for Ubuntu, version 14.04 LTS to 17.04 LTS supports live backups.

      For details, please refer to:
      https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/supported-linux-and-freebsd-virtual-machines-for-hyper-v-on-windows

    • The guest VM volumes must use a file system which supports the use of VSS snapshots, for example NTFS.

    • The guest VMs snapshot file location must be set to the same volume in the Hyper-V as the VHD file(s).

    • The guest VM volumes have to reside on basic disks. Dynamic disks cannot be used within the guest VM.
    • !

      Some older Windows operating systems installed on guest VM’s which do not support either Integration Services or the Hyper-V Volume Shadow Copy Requestor Service, will not support VM snapshot method, for example, Microsoft Windows 2000, Windows XP, or older Linux/FreeBSD versions.


  3. Saved State
  4. When the Saved State method is used, the guest VM is placed into a saved state while the VSS snapshot is created (effectively shut down), and the duration depends on the size of guest VM. The downside is it may affect the availability of any application or services running on the guest VM every time a backup job is performed.

CBT Requirement

Since AhsayOBM version 7.9, a new service CBT Cluster Services (Ahsay Online Backup Manager) is installed and enabled upon installation / upgrade to version AhsayOBM v7.9.0.0 or above.

Since AhsayOBM v3.1.0.0, a new service CBT Cluster Services (CloudBacko Pro) is installed and enabled upon installation / upgrade to AhsayOBM v3.1.0.0 or above.


  1. CBT (Changed Block Tracking) is used to optimize incremental backups of virtual machines by keeping a log of the blocks of data that have changed since the previous snapshot. When AhsayOBM performs a backup, CBT feature can request transmissions of only the blocks that changed since the last backup, or the blocks in use.
  2. !

    From version 7.15.0.0 onwards, CBT service is supported on all the backup destinations for AhsayOBM instead of only RunDirect related local destination.

  3. CBT cluster service is only installed on Windows x64 machine.

  4. Check if CBTFilter is enabled. This can be verified by running the net start CBTFilter command.

    C:\Users\Administrator>net start CBTFilter
    The requested service has already been started.
    More help is available by typing NET HELPMSG 2182.


  5. CBT Cluster Service and CBTFilter will NOT be installed on Windows Server 2016 where a built-in system called Resilient Change Tracking (RCT) will be used instead.

Windows Server 2016 Requirement


  1. RCT Requirement


  2. Guest VM Dependencies Requirements
  3. To get full use of Hyper-V, install the appropriate linux-tools and linux-cloud-tools packages to install tools and daemons, i.e. VSS Snapshot Daemon, for use with virtual machines.

    For details, please refer to: https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/supported-linux-and-freebsd-virtual-machines-for-hyper-v-on-windows

Limitations

The followings are the limitations of the MS Hyper-V backup module:



  1. Backup of guest machines located on a SMB 3.0 shares is not supported.

  2. Backup of virtual machine with pass through disk (directly attached physical disk) is not supported.

  3. For backup of individual virtual disk, the restored virtual machine does not support the reversion of previous snapshots, if the snapshot contains disks which are not previously backed up by AhsayOBM.

  4. A guest virtual machine can only be restored to the Hyper-V server with the same version, i.e. backup of a guest on Hyper-V 2012 R2 server cannot be restored to Hyper-V 2008 R2 Server, and vice versa.

  5. The guest virtual machine will not start up if the virtual disk containing the guest operating system that is not restored.

  6. Restore of individual virtual disks is only supported using the Restore raw file option for a virtual disk with no snapshots.

    !

    This will require modification of Hyper-V guest configuration files, and this only should be done if you have in-depth knowledge and understanding of Hyper-V, otherwise the guest virtual machine may not startup properly.


  7. Restore to an Alternate location can only be performed on one guest virtual machine at a time.

  8. Restored guest virtual machines using Run Direct containing a saved state will not automatically power on. The saved state must be manually deleted in Hyper-V Manager and the guest must be powered on manually.

  9. For Run Direct enabled backup sets, the storage destination is restricted to Local, Mapped, or Removable Drive.

  10. When a guest virtual machine is started in a Run Direct instance being stopped, any changes made within the guest environment will be lost, if the guest virtual is not migrated to the Hyper-V Server using the “Auto migrate after Run Direct is running” option.

  11. When a guest virtual machine is started using Run Direct Restore, all backup jobs (manual, scheduled, and continuous) for the related backup set will be skipped.

  12. When a guest virtual machine is started using Run Direct Restore, the following features are not available for the backup set: Data Integrity Check, Space Freeing Up, or Delete Backup Data.

  13. Granular Restore is NOT supported on “Windows 7 SP1″ or “Windows Server 2008 R2 SP1″.

Granular Restore Requirements

Please ensure that the following requirements are met for Granular Restore to use:


  1. Granular restore is only supported on Hyper-V backup sets created and backed up using AhsayOBM v7.13.0.0 or above on Windows platforms with Granular Restore feature enabled.
  2. Granular restore is only supported on Hyper-V backup sets created and backed up using AhsayOBM v3.1.0.0 or above on Windows platforms with Granular Restore feature enabled.
  3. OpenDirect / Granular Restore add-on module is required per backup set for this feature to work. Contact your backup service provider for more details.
  4. Both compression and encryption are not enabled for Granular restore backup sets. To optimize restore performance the storage quota required will be higher than non-Granular Restore backup sets. Contact your backup service provider for details.

  5. Temporary Directory Folder should have at least the same available size as the backup image to be restored.

  6. One spare drive letter must be available for the Granular restore process as the VHD image is mounted on Windows as a logical drive by AhsayOBM and it will automatically take the next available drive letter in alphabetical order for the mounted volume. (Drive letters A, B, and C will not be used.)

  7. Recommended minimum network speed is at least 100Mbits per second download speed. Network bandwidth should be increased in proportion to the guest virtual machine size and the incremental delta chain length to ensure optimal performance. Working with limited network bandwidth may severely affect the Granular restore performance.
    You can use an online speed connection testing site (e.g. http://www.speedtest.net) to test your connection speed.

  8. The following dependencies are restore related and therefore they will be checked by AhsayOBM only when an Granular restore is performed. Absence of these elements will not affect the backup job but would cause the restore to fail.


  9. The Windows login account used for installation and operation of the %edition_name% client machine requires Administrator privileges
  10. Create a MS Hyper-V Backup Set

    Field Description
    Name This is the name of the backup set. You can create a meaningful name for it.
    Backup Type Select the backup set type from the drop down box.
    Version Select the version of the Hyper-V server.

    Steps:


    1. Type in a meaningful backup set name.

    2. Select the backup set type as MS Hyper-V backup.

    3. Select the correct version of the Hyper-V Server.

    4. Click [Next] button to continue.


    Setup example for MS Hyper-V cluster:

    Assumption:


    1. There are 3 nodes in the Hyper-V cluster setup, in the following example, we called it node1, node2 and node3.

    2. All the 3 nodes are located in the same timezone.

    3. They can connect to the same backup location, eg: a local shared destination with the same access permission.

    Notes:


    1. As the same backup set setting is needed to apply on all the machines when

      • the backup set is created or

      • any changes is applied to the backup set,

        eg:

        • change backup schedule

        • backup source selection

        • backup destination


        It is required to export the settings from the node with the last changes and then import to all other nodes.
        Otherwise, the backup set settings are not synchronized.

        eg:

        If the backup schedule is changed on node1, if the backup set is not synchronized, other nodes will keep running on an old backup schedule and may cause the backup job does not reflect to the actual servers status at the backup moment.



    2. When the settings is imported from other nodes, all the backup set settings on the node will be overwritten.

    Steps:


    1. Create/modify Hyper-V cluster backup set in node1, make sure the schedule backup is turned on.

    2. Export settings from node1 in [Utilities] > [Ex/Import Settings]

    3. Import the node1 settings into node2 in [Utilities] > [Ex/Import Settings]

    4. Enable the Schedule backup in node2.

    5. Export settings from node2 in [Utilities] > [Ex/Import Settings]

    6. Import the node2 settings into node3 in [Utilities] > [Ex/Import Settings]

    7. Enable the Schedule backup in node3.

    8. Export settings from node3 in [Utilities] > [Ex/Import Settings]

    9. Import the node3 settings into node1 and node2 in [Utilities] > [Ex/Import Settings]


in Tips | 2,689 Words

How to Create VMware Backup Set

BS_Create_vmware







Backup Requirements for


Backup Requirements for VMware ESX or ESXi server/vCenter

Backup Requirements for Hypervisor

Please ensure that the following requirements are met by the Hypervisor:


  1. ESXi / vCenter Patch Release: Make sure that the latest supported patch release is installed on the vCenter / ESXi hosts to prevent critical issue, such as corruption to change tracking data in certain situation.
    Please refer to the following article for details: https://kb.vmware.com/kb/2090639

  2. License Specification

    • Paid License (VMware Essentials License or above): VMware ESXi and vCenter v5, v6 and v6.5

    • Free License: VMware ESXi v5, v6 and v6.5



  3. ESXi Shell Access: ESXi Shell access must be enabled on the ESXi servers. Please refer to the following article for details: https://kb.vmware.com/kb/2004746

  4. SSH must be enabled on the Hypervisor. To enable root SSH login on an ESX/ESXi host, please follow the below instructions from VMware:http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=8375637

  5. The root account must be enabled as AhsayOBM ESX / ESXi backup set requires the root account for backup and restore.

  6. The following TCP ports must be opened on the hypervisor: Port 22, 80, 111, 443, 902.
    Please refer to the following articles for details:

    https://kb.vmware.com/s/article/2012773

    https://kb.vmware.com/s/article/2106283

    https://kb.vmware.com/s/article/2039095

    https://kb.vmware.com/s/article/2131180

    !

    Please kindly note that:


    • Ports 443 and 902 are default ports for VMware.

    • If these have been changed from the default in your VMware environment, the firewall requirements will change accordingly.


  7. It is recommended that the datastore have disk space of the largest sized virtual machine to be backed up.


Backup Requirements for Backup Account and Backup Client Computer:

AhsayOBM cannot be installed on the hypervisor (ESX or ESXi server). For best performance, AhsayOBM should be installed on a separate dedicated physical machine – Backup Client Machine – for backup of your virtual machines.

Please ensure that the following requirements are met by the backup client computer:


  1. Add-on Module Requirement: Make sure that the VMware VM backup add-on module is enabled for your AhsayOBM user account, and that sufficient number of guest / socket is assigned. Please contact your backup service provider for more details.

  2. Backup Quota Requirement: Make sure that your AhsayOBM user account has sufficient quota assigned to accommodate the storage for the guest virtual machines. Please contact your backup service provider for details.


  3. Port Requirement:






  4. For better performance, AhsayOBM is recommended to be installed on a 64 bit computer, with multiple CPUs and cores.

  5. Consider to increase the JVM (Java Virtual Machine) memory allocation to improve performance of the backup operation.

  6. Sufficient disk space must be allocated for the temporary directory, and the formula of calculation of disk space is as following:

    (Total File Size * Delta Ratio) * number of backup destinations = Maximum Free Space Required
  7. !

    The calculation is based on the current guest VM size, and it does not take into account guest VM growth over time. It is recommended for fast growing guest VM the maximum free space required should be reviewed on regular basis to avoid potential backup problems.

  8. It is recommended that the temporary directory be configured on a local drive.

  9. It is recommended that the temporary directory is not configured on the same partition which the operating system is installed on.

  10. For backup of virtual machine with snapshot, backup of the whole VM instead of individual disk is highly recommended.

  11. Consider to perform routine recovery test to ensure your backup is setup and performed properly.

  12. Please consider the maximum file size allowed for different ESX/ESXi version.


    For ESXi 5.0, error will be displayed if any individual flat .vmdk file selected for backup exceeds 2,181,972,430,848 bytes. This is the size generated when ‘Adding a virtual disk’ with size of 1.984492366201720 TB is specified.


    For different block size setting on VMFS, the maximum file size may be different, please refer to the following articles for details:



    http://kb.vmware.com/kb/1012384

    http://kb.vmware.com/kb/1003565


    The absolute maximum snapshot file size is limited to roughly 2 TB. However, different block size setting on the VMFS datastore may have a smaller size limit, adjust the block size setting when necessary.



  13. Consider to disable the memory snapshot or quiesce guest options when taking snapshot for VMware VM backup, to shorten the time required for the process.




    • Snapshot the virtual machine’s memory

    • Quiesce guest file system (Needs VMware Tools installed)





Backup with VDDK mode

AhsayOBM supports VDDK backup mode (Virtual Disk Development Kit) for ESX/ESXi and vCenter setup. The backup speed is enhanced because the generation of the delta file of the VM are performed directly by the ESX/ESXi or vCenter itself. With VDDK backup mode, it supports:



  • Backup / restore of the resource pool and ‘roles’ settings, and support of restoration to another name or alternation location on the ESX/ESXi platform.

  • VM hardware version upgrade, change tracking option and change tracking data option when a new backup set is created.

  • Add or remove VM hard disk without uploading the existing hard disk again on the vCenter backup.


Limitations

The following are limitations of the VMware VM backup module:



  1. VMware ESX or ESXi Server with Raw Device Mapping (RDM) is not supported.


    Snapshots are not available when the Raw Device Mapping (RDM) is used in physical compatibility mode.



  2. For backup of individual virtual disk, the restored virtual machine does not support the reversion of previous snapshots, if the snapshot contains disks which are not previously backed up by AhsayOBM.

  3. For virtual machines with Independent Disks:




    • If Independent Disks are to be included in the virtual machine backup, the virtual machine must be powered off first, before running the backup job.

    • If the virtual machine is powered on, the Independent Disk will not be backed up.



    AhsayOBM will skip the snapshot creation of any Independent Disk on the virtual machine.



  4. If the file name of the virtual machine contains the following special characters, https access to the files will fail:


    ` ^ ~ = ; ! / ( [ ] { } @ $ \ & # % +


    This is due to the percent-encoding specified in the URL standard is not supported for ESXi based HTTP(S) file access. To resolve the issue, please rename the corresponding file to avoid special characters. For instructions on renaming a virtual machine, please refer to the following knowledge base article from VMware:



    https://kb.vmware.com/s/article/2031763



  5. For the VDDK mode, no VM’s snapshot, memory or the suspend status will be able to backup and restore. If the backup and restore of the snapshot, memory or the suspend status is required, do not turn on the ‘Change Block Tracking’ option when you create the ESX/ESXi or vCenter backup set, select [No] for the creating the backup set in non-VDDK mode which allows the backup and restore of the snapshot, memory or the suspend status.

  6. VDDK mode will not be enabled if the independent disk or raw disk is configured in the VM.

  7. VDDK backup mode does not support ESX/ESXi server with free license.

  8. Once the backup job executed on a VM which change block tracking option was enabled by the VDDK, please do not off this option in the VM for consequence backup jobs. If you need to disable this option, you are suggested to create a new backup set with requires to disable this option.


Backup Requirements for VMware Server/Player/Workstation

As the backup and restore procedures for VM running on VMware Player and Workstation are very similar to that of VM running on VMware Server, the description in this section is mainly based on the VMware Server.


Backup Requirements for VMware Server

Please ensure that the following requirements are met by the VMware Server:


  1. AhsayOBM must be installed on the hypervisor.

    !

    Resource allocation for both VM hosting and backup operation must be taken into consideration.


  2. The following TCP ports must be opened on the hypervisor:

    • Port 902

    • Port 912

    • Port 8222

    • Port 8333


    Please refer to the following articles for details:
    https://kb.vmware.com/s/article/2012773

    https://kb.vmware.com/s/article/2106283

    https://kb.vmware.com/s/article/2039095

    https://kb.vmware.com/s/article/2131180

  3. Consider to increase the JVM (Java Virtual Machine) memory allocation to improve performance of the backup operation.

  4. It is recommended that the datastore have disk space of the largest sized virtual machine to be backed up.

  5. Sufficient disk space must be allocated for the temporary directory, and the formula of calculation of disk space is as following:

    (Total File Size * Delta Ratio) * number of backup destinations = Maximum Free Space Required
  6. !

    The calculation is based on the current guest VM size, and it does not take into account guest VM growth over time. It is recommended for fast growing guest VM the maximum free space required should be reviewed on regular basis to avoid potential backup problems.

  7. It is recommended that the temporary directory be configured on a local drive.

  8. It is recommended that the temporary directory is not configured on the same partition which the operating system is installed on.

  9. Consider to perform routine recovery test to ensure your backup is setup and performed properly.


Limitations

The following are limitations of the VMware VM backup module:



  1. For backup of individual virtual disk, the restored virtual machine does not support the reversion of previous snapshots, if the snapshot contains disks which are not previously backed up by AhsayOBM.


  2. Independent Disk is not supported. For virtual machines with Independent Disks, those disks will not be backed up.


Run Direct Requirements

Run Direct is a feature introduced since AhsayOBM version 7.5.0.0, that helps reduce disruption and downtime of your production VMs.

To utilize the Run Direct feature, ensure that the following requirements are met:


  1. VDDK Backup Mode: Run Direct restore is only supported for virtual machine that is backed up in VDDK mode. Make sure that the VDDK backup mode requirements are met.

  2. Backup Destination Requirement

    • When a Run Direct restore is performed, the backup destination containing the guest VM files is mounted on the VMware host as NFS datastore.

    • Please ensure that the following requirements are met by the backup destination of the VMware VM backup set:

      • Destination Type of the backup destination must be set to a Single storage destination.

      • Destination must be accessible to the VMware host.

      • Destination must have sufficient disk space available for the Run Direct restore. There should be 1.5 x total provisioned size of all VMs selected for backup.

      • For Run Direct restore of 1 VM with provisioned size of 100GB, there should be 150GB (e.g. 1.5 x 100GB) of free space available in the Destination.





  3. No Compression and Encryption: Data backed up to a Run Direct enabled destination is not compressed or encrypted to optimize restore performance as Run Direct will make the VM restored by running the data directly from the backup files in the backup destination.

  4. Restore to Alternate Location:

    • When performing a Run Direct restore to Alternate Location, only one VM can be selected per restore session.

    • Consider to create separate VMware VM backup set for each VM that you intend to perform Run Direct restore (e.g. VMs that you may restore to alternate location).



  5. Dedicated NFS Service

    Starting from AhsayOBM version 7.9.0.0, a dedicated AhsayOBM NFS Windows service is introduced to allow Run Direct session to continue even if the AhsayOBM user interface is closed.

    By default, the AhsayOBM NFS service is started as Local System, which does not have sufficient permission to access any network resources (e.g. the AhsayOBM NFS service does not have sufficient permission to access the VM backup files on network drive).

    Make sure that the Log on setting of the according NFS Service is configured with an account with sufficient permission to access the network backup destination where the backed up VM data are stored.


Granular Restore Requirements

Please ensure that the following requirements are met for Granular Restore to use:


  1. Granular restore is only supported on VMware backup sets created and backed up using AhsayOBM v7.13.0.0 or above on Windows platforms with Granular Restore feature enabled.
  2. Granular restore is only supported on VMware backup sets created and backed up using AhsayOBM v3.1.0.0 or above on Windows platforms with Granular Restore feature enabled.
  3. Granular Restore add-on module is required per backup set for this feature to work. Contact your backup service provider for more details.
  4. Both compression and encryption are not enabled for Granular restore backup sets to optimize restore performance, so the storage quota required will be higher than non-Granular Restore backup sets. Contact your backup service provider for details.

  5. AhsayOBM must be installed on a 64 bit Windows machine as libraries for VMware Granular restore only supports 64bit Windows.

  6. Temporary Directory Folder should have at least the same available size as the backup image to be restored.

  7. One spare drive letter must be available for the granular restore process as the VMDK or VDDK image is mounted on Windows as a logical drive by %edition_name% and it will automatically take the next available drive letter in alphabetical order for the mounted volume. (Drive letters A, B, and C will not be used.)

  8. Recommended minimum network speed is at least 100Mbits download speed per second. Network bandwidth should be increased in proportion to the delta chain to ensure optimal performance. Working with limited network bandwidth may severely affect the granular restore performance. You can use an online speed connection testing site (e.g. http://www.speedtest.net) to test your connection speed.

  9. The following dependencies are restore related and therefore they will be checked by AhsayOBM only when an granular restore is performed. Absence of these elements will not affect the backup job but would cause the restore to fail.


  10. The Windows login account used for installation and operation of the %edition_name% client machine requires Administrator privileges.
  11. Set the name of the backup set

    Name This is the name of the backup set. You can create a meaningful name for it.
    Backup Type Enter the correct backup type from the drop down box.
    Version This is the version of the VMware product.
    Username This is the username with system or sufficient privilege to access the VMware product.
    Password This is the password for the user login.
    Host This is the host of the VMware product.
    Port This is the listening port of the VMware product.
    SSH Port This the SSH port of the VMware product.

    To create a backup set name:



    1. Type in a meaningful backup set name.

    2. Enter correct backup type, eg: VMware Backup.

    3. Enter the version of VMware product.

    4. Enter the username.

    5. Enter the password.

    6. Enter the host.

    7. Enter the port.

    8. Enter the SSH port.

    9. Click [Next] button to continue.
    10. Note: Click [Next] button will start the verifying process.




in Tips | 2,610 Words

[Video] How to backup Office 365 data thru AhsayCBS web console

Run Office 365 from AhsayCBS web console

With the latest Ahsay Backup Software, you can create Office 365 backup set on both AhsayOBM client backup agent, and AhsayCBS web console. In this video, you’ll see how an Office 365 admin can configure and run backup on the AhsayCBS web console.

The admin is able to backup Exchange Online, SharePoint Online, and OneDrive data for all users, or selected users thru Ahsay’s Office 365  module.

For more details, check out the guide here: download.ahsay.com/support/document/v8/guide_obm_user_O365_win_v8.pdf#page=49

in Tips | 96 Words

[Video] How to use public cloud (e.g. Microsoft Azure, Amazon S3, Google Cloud, etc.) for hosting clients’ backup data (Predefined destination explained)

msp-cloud-storage-01

The latest Ahsay backup software suite allows MSPs as well as users to leverage public cloud storage for storing backup data. AhsayOBM / AhsayACB client agent’s user is able to back up data from server, desktop, NAS device to either:
1). user’s own public cloud storage, or
2). an MSP’s public cloud storage (meaning MSP’s Azure, S3, or Google Cloud storage account).

If you’re an MSP and want to leverage public cloud for hosting customers’ data, you most likely want your customers to back up to your public cloud storage account instead of letting them to back up to their own cloud storage, because this way the storage fee will go to your pocket instead of cloud providers’. You may also want to make the actual storage transparent to your users.

Ahsay allows you to easily achieve the above goals by using the Predefined Destinations feature in the latest AhsayCBS central web management console. Just 2 simple steps will do. Check out this video for details:

in Tips | 173 Words