Ahsay now supports Microsoft Office 365 Modern Authentication

Ahsay v8.3.6 supports Microsoft Office 365 modern authentication and hybrid authentication

Microsoft Office 365’s basic authentication in Exchange Online uses a username and a password for client access requests. Such authentication method provided a loophole for hackers to hack into users’ accounts by using brute force or password spray attacks. Therefore, to help users better protect their accounts, Microsoft suggests users to enable modern authentication, and plans to:

  1. begin disabling Basic Authentication in existing tenants with no recorded usage as early as October 2020; and
  2. disable Basic Authentication for the EAS, EWS, POP, IMAP, and RPS protocols in the second half of 2021.

The good news is that starting from v8.3.6, Ahsay supports the use of Microsoft Office 365’s Modern Authentication when creating a Microsoft Office 365 backup set in AhsayOBM client backup software, as well as AhsayCBS web console. If users are still using Basic Authentication, we also support that until Basic Authentication is not supported anymore.

Ahsay v8.3.6 supports Microsoft Office 365 modern authentication

If you leave the Username and Account Password fields blank, and just click the Test button, you will be using the Modern Authentication mode, and a browser window will be brought up for you to perform authentication.

Ahsay v8.3.6 supports Office 365 Modern Authentication

Ahsay v8.3.6 supports Office 365 Modern Authentication

After successful authentication, an Authentication Code will be provided to you.

modern-authen-05

Copy and paste this code into Ahsay’s software and the software will be linked with your Office 365 account.

modern-authen-07

You can then proceed with the backup set configuration as usual.

Ahsay v8.3.6 supports Microsoft Office 365 modern authentication

To understand how to create a Microsoft Office 365 backup set to backup emails and files in an Office 365 domain, check out this Microsoft Office 365 Backup and Restore Guide.

in Tips | 249 Words

Why Ahsay Is an Ideal Tool for Office 365 backup

Why Ahsay Is Ideal for Office 365 Backup

Microsoft Office 365 is no doubt a great tool for businesses, allowing easy storage and access to business documents, improving productivity and collaboration among colleagues. However, there are many businesses which believe that after moving everything to there, no backup is ever required, as Microsoft will take care of that for them. This is utterly wrong. Guarantee of quick restore on currupted or permanantly deleted data is never included in Microsoft Office 365’s offerings. Microsoft will only be responsible for offering a highly available platform for users to use, and protecting their service against hardware failure and natural disaster. They do offer tools such as the recycle bin to let users recover temporarily deleted data, but that’s not a full backup protection.

Protection on data because of the following reasons are the responsibilities of users:

In Microsoft’s service agreement (https://www.microsoft.com/en-us/servicesagreement), you’ll find this clause: “We recommend that you regularly backup Your Content and Data that you store on the Services or store using Third-Party Apps and Services.”

Therefore, if you haven’t thought of backing up your Office 365’s data, you better start doing it before data loss disaster happens.

Why Ahsay is an ideal backup tool

There are many Office 365 backup solutions out there. Why choosing Ahsay? Well, yes, there are many tools, but each tool is different from the rest. These are the reasons that differentiate us from others:

What to do when you need to recover lost data

When you need to restore lost emails or files from the backup, simply choose to restore those data either from the latest point-in-time, or from an earlier point-in-time. Then, the lost data will be quickly restored back to your Office 365 domain effortlessly.

Interested in understanding more? Contact us to obtain a trial now!

in Tips | 597 Words

Need an Alternative to Acronis MSP Backup Solution?

Acronis alternative

If you are looking for an alternative to replace your current Acronis MSP backup solution, why not give Ahsay Cloud Backup Suite a try? These are the key reasons for you to switch:

A digram showing how Ahsay backup software's components connect to each others.

The whole Ahsay’s solution is with flexible client-server architecture. On the server side, our AhsayCBS server-side centralized management console can be installed on your own backup server hosted in your datacenter, on cloud VM such as Microsoft Azure, or on backup appliances deployed in your customers’ offices. Users’ backup data can be stored on your own backup server, or on cloud storage such as Microsoft Azure, Amazon S3, etc., or the locally deployed backup appliances. On the client side, AhsayOBM / ACB client agents are for installing on the servers, workstations that need to be backed up. With proper configuration, your customers’ data will be automatically backed up or replicated to your managed storage.

Unlike Acronis which offers you quite limited choices in storage, you can use a wide range of storage listed here for hosting your customers’ backup data with Ahsay. Backup to multiple destinations are also possible. The AhsayOBM / ACB client agents can simultaneously backup to multiple destinations. Also, you can replicate the data from your AhsayCBS server storage to another server or cloud for added redundancy. This storage flexibility might not be available from Acronis. Check out our 4 common deployment options here, and choose the one that fits your business objective most.

Besides product, our Support Service is much more helpful than theirs, because all of our support engineers know well about our product, and thus will be able to solve your questions quickly. Our near round the clock support can definitely have good coverage on your timezone.

If you have any product and sales related questions, just contact us.

in Tips | 314 Words

Configure your own color schemes for AhsayOBM / AhsayACB

Do you know that you can configure the color schemes for your AhsayOBM  and AhsayACB client backup software if you have Rebranding Option purchased? That’s right, you don’t have to use the default blue and red scheme for your branded AhsayOBM  and AhsayACB. Instead, you can choose to use the Predefined Scheme, or define your own Custom Scheme within your AhsayCBS web console > System Settings > Basic > Administrative Access > [Select your administrator] > Rebrand Clients > Color Scheme Settings – AhsayOBM / AhsayACB. Configure the color schemes for your AhsayOBM / AhsayACB backup software - 2

Configure the color schemes for your AhsayOBM / AhsayACB backup software - 1

For the details on the rebranding feature, please refer to the corresponding section of this AhsayCBS Administrator Guide.

in Tips | 103 Words

Termination of Support for Amazon Cloud Drive by Ahsay

We regret to inform partners that due to circumstances beyond our control, we have no option but to terminate all technical support relating to Amazon Cloud Drive with immediate effect. It is because we have confirmed that both the Amazon Drive Software Development Kit (SDK) and (Application Programming Interface) API have already been closed by Amazon.com Inc.

Applications will no longer be able to connect to and use features & resources on Amazon Cloud Drive, however users will still be able to login and access files on their storage accounts directly from the Amazon Drive portal.

The following Ahsay features will no longer function on both v7 and v8.

Any data already backed up cannot be restored directly from Amazon Cloud Drive using AhsayCBS/AhsayOBM/AhsayACB. For partners who wish to restore this data from Amazon Cloud Drive, we recommend they manually synchronize the data using third party tools to a local storage device and use the Utilities > Decrypt Backup Data feature on the AhsayOBM/AhsayACB client application.

To avoid confusion, we recommend that Amazon Cloud Drive option be removed from AhsayCBS > Policy Group > Default setting > Backup Set Setting > Standard Destination.

Please refer to page 185 “Destinations Visible to Users” of our AhsayCBS Administrator’s Guide for details: http://download.ahsay.com/support/document/v8/guide_cbs_admin_v8.pdf

Note: Amazon S3 and AWS S3 Compatible Cloud Storage are not affected.

in Tips | 282 Words

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