www.bobcloud.net
Ahsay Online Backup Manager v7
Microsoft Exchange Database Backup &
Restore Guide
Ahsay Systems Corporation Limited
26 November 2018
This is the original Ahsay manual
Depending on the service you have with us, some of the content won’t be applicable to you.
Note:
We don’t supply the following services, Open direct, Run Direct,or Run on Server on our
BOBcloud service. These are only provided on our System Provider service.
All accounts must be created on our reseller portal https://portal.data-stor.net
Any Ahsay professional services are provided by them and not us.
Definitions:
Our Desktop version is named ACB \ AhsayACB in this manual.
Our Server version is named OBM \ AhsayOBM in this manual.
The AhsayCBS Web Console is mapped to our own portal https://portal.data-stor.net
www.bobcloud.net
Copyright Notice
© 2018 Ahsay Systems Corporation Limited. All rights reserved.
The use and copying of this product is subject to a license agreement. Any other use is prohibited. No part of this publication
may be reproduced, transmitted, transcribed, stored in a retrieval system or translated into any language in any form by any
means without prior written consent of Ahsay Systems Corporation Limited. Information in this manual is subject to change
without notice and does not represent a commitment on the part of the vendor, Ahsay Systems Corporation Limited does not
warrant that this document is error free. If you find any errors in this document, please report to Ahsay Systems Corporation
Limited in writing.
This product includes software developed by the Apache Software Foundation (http://www.apache.org/).
Trademarks
Ahsay, Ahsay Cloud Backup Suite, Ahsay Online Backup Suite, Ahsay Offsite Backup Server, Ahsay Online Backup Manager,
Ahsay A-Click Backup, Ahsay Replication Server, Ahsay BackupBox Firmware, Ahsay Universal Backup System, Ahsay NAS
Client Utility are trademarks of Ahsay Systems Corporation Limited.
Amazon S3 is registered trademark of Amazon Web Services, Inc. or its affiliates.
Apple and Mac OS X are registered trademarks of Apple Computer, Inc.
Dropbox is registered trademark of Dropbox Inc.
Google Cloud Storage and Google Drive are registered trademarks of Google Inc.
Lotus, Domino, Notes are registered trademark of IBM Corporation.
Microsoft, Windows, Microsoft Exchange Server, Microsoft SQL Server, Microsoft Hyper-V, Microsoft Azure, One Drive and
One Drive for Business are registered trademarks of Microsoft Corporation.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective
owners.
Oracle, Oracle 10g, Oracle 11g and MySQL are registered trademarks of Oracle Corporation.
Rackspace and OpenStack are registered trademarks of Rackspace US, Inc.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo and JBoss are registered trademarks of Red Hat, Inc.
www.redhat.com in the U.S. and other countries. Linux is a registered trademark of Linus Torvalds.
ShadowProtect is registered trademark of StorageCraft Technology Corporation.
VMware, ESX, ESXi, vCenter are registered trademarks of VMware, Inc.
All other product names are registered trademarks of their respective owners.
Disclaimer
Ahsay Systems Corporation Limited will not have or accept any liability, obligation or responsibility whatsoever for any loss,
destruction or damage (including without limitation consequential loss, destruction or damage) however arising from or in
respect of any use or misuse of reliance on this document. By reading and following the instructions in this document, you
agree to accept unconditionally the terms of this Disclaimer and as they may be revised and/or amended from time to time by
Ahsay Systems Corporation Limited without prior notice to you.
www.bobcloud.net
Revision History
Date
Descriptions
Type of modification
15 July 2016
First Draft
New
3 February 2017
Added instructions and screen shots for
Encryption key handling in Ch. 2.1 & Ch. 4.2
New
5 April 2017
Added Encryption Type option in Ch.2.1 & Ch.
4.2
New
14 September 2018
Added requirement of Antivirus Exclusion for
Ch.1.2;
New
www.bobcloud.net
Table of Contents
1 Getting started ................................................................................................................................1
1.1 Introduction ................................................................................................................................1
1.2 Antivirus Exclusion Requirement ...............................................................................................1
1.3 General Best Practices and Recommendations ........................................................................1
1.4 Best Practices and Recommendations for Exchange Server in Data Availability Group (DAG)
only 4
1.5 Overview of MS Exchange Database Backup Process .............................................................6
2 Backing up Microsoft Exchange Database 2007/2010/2013/2016 .................................................7
2.1 Creating a MS Exchange Server Backup Set for Exchange Server 2007/2010/2013/2016 ......7
2.2 Running Backup Job for Microsoft Exchange Server 2007/2010/2013/2016 ..........................14
3 Restoring Microsoft Exchange Server 2007/2010/2013/2016 ......................................................16
3.1 Pre-restoration Requirements..................................................................................................16
3.2 Restoring Exchange Database for Microsoft Exchange Server 2007/2010/2013/2016...........17
4 Backing up Microsoft Exchange Server in Database Availability Group (DAG)............................21
4.1 License Requirement to Backup all Exchange Server 2010/2013/2016 in DAG environment 21
4.2 Creating Backup Set for Microsoft Exchange Server 2010/2013/2016 (DAG) ........................21
5 Restore Microsoft Exchange Server 2010/2013/2016 in Database Availability Group (DAG)......28
5.1 Pre-restoration requirements ...................................................................................................28
5.2 Restore Exchange Database to the Exchange with the active database ................................28
6 Technical Assistance ....................................................................................................................33
7 Documentation..............................................................................................................................34
Appendix...............................................................................................................................................35
Appendix A Exchange Server Backup Type....................................................................................35
Appendix B Restore Activities Log...................................................................................................37
www.bobcloud.net 1
1 Getting started
1.1 Introduction
This user guide aims at providing detailed information for backing up and restoring Microsoft
Exchange Database with AhsayOBM.
1.2 Antivirus Exclusion Requirement
To optimize performance of AhsayOBM on Windows, and to avoid conflict with your antivirus
software, refer to the following KB article the list of processes and directory paths that should
be added to all antivirus software white-list / exclusion list:
http://wiki.ahsay.com/doku.php?id=public:5352_suggestion_on_antivirus_exclusions
NOTE
For AhsayOBM version 7.17 or above, the bJW.exe process is automatically added to Windows
Defender exclusion list for Windows 10 and 2016, during installation / upgrade via installer or upgrade
via AUA.
1.3 General Best Practices and Recommendations
Please ensure that the following requirements are met by the Microsoft Exchange Server:
1. The latest version of AhsayOBM is installed on the Exchange server / DAG member
services. For Exchange Server 2010/2013/2016, Database Availability Group (DAG)
backup option is available, please refer to Backing up Microsoft Exchange Server in
Database Availability Group (DAG) for details.
2. Ensure that all MS Exchange related services have been started, particularly the MS
Exchange Information Store and MS Exchange System Attendant Services.
To verify this setting, launch Services in Windows by clicking Start then typing
“Services” in the search box. All Exchange related services should be started by default,
in case if it is not, turn it on by right clicking the item then selecting Start.
www.bobcloud.net 2
3. AhsayOBM must be installed on the Exchange server with mailbox role.
4. Make sure the Exchange Server has been updated to the latest roll-up patch of that
specific service pack.
5. Make sure that circular logging is disabled for all Information Store(s) or Public Folder
selected for backup.
6. Make sure that the Microsoft Exchange Server add-on module has been enabled for
your AhsayOBM user account. Contact your backup service provider for more details.
7. The Exchange Server 2010/2013/2016 database files are no longer stored in the
temporary directory during backup. However, the VSS-based Exchange backup will still
require certain amount of disk space to operate. Microsoft suggested that certain shadow
copy mechanism may require free space around 100% of the original database. Refer to
the following URL for more information.
http://msdn.microsoft.com/enus/library/exchange/aa579091%28v=exchg.140%29.aspx
8. 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 that the folder is located on a
local drive with plenty of free disk space.
9. Ensure that the Microsoft Exchange Writer is installed and running on the Exchange
Server, and the writer state is Stable. This can be verified by running the vssadmin list
writers command.
Example:
C:\Users\Administrator>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative
command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
www.bobcloud.net 3
Writer Instance Id: {a2f2507d-b348-493a-9685-da3f20959e9d}
State: [1] Stable
Last error: No error
Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {60b9b261-ab81-4c4d-be0f-5d432a4dea64}
State: [1] Stable
Last error: No error
Writer name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance Id: {1aab9829-3b91-46bc-a7f1-ae9e1123c2fe}
State: [1] Stable
Last error: No error
Writer name: 'Microsoft Exchange Writer'
Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
Writer Instance Id: {2e8409fa-1dd8-483c-ba95-5c9277be0509}
State: [1] Stable
Last error: No error
Writer name: 'IIS Metabase Writer'
Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
Writer Instance Id: {3303e28e-afae-4c99-8f1a-2ce23e6455a7}
State: [1] Stable
Last error: No error
Writer name: 'FRS Writer'
Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
Writer Instance Id: {d35e3901-f9b9-4fa6-86af-36b8a4872933}
State: [1] Stable
Last error: No error
Writer name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance Id: {8e19e851-95ca-4c97-813d-4bc51898c7ac}
State: [1] Stable
Last error: No error
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {0619e684-14f3-495b-be59-e35fc0ec212b}
State: [1] Stable
Last error: No error
Writer name: 'BITS Writer'
Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
Writer Instance Id: {94991e66-e5c7-47a4-a0c9-3771e4761262}
State: [1] Stable
Last error: No error
Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {73c66436-c2e8-4d46-b88a-d866617eb95d}
State: [1] Stable
Last error: No error
Writer name: 'NTDS'
Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
Writer Instance Id: {14cedc8b-4c51-4a12-85c4-8cf8aa3545b6}
www.bobcloud.net 4
State: [1] Stable
Last error: No error
Writer name: 'IIS Config Writer'
Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
Writer Instance Id: {5939e29f-bf43-4a39-a6b7-e3a838e75e3e}
State: [1] Stable
Last error: No error
10. For Exchange server with Active Directory installed, a Windows System State backup
must be performed regularly with the MS Exchange Server backup.
11. (Applicable to Microsoft Exchange Server 2013/2016 only)
If you are using Microsoft 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.
1.4 Best Practices and Recommendations for Exchange Server in
Data Availability Group (DAG) only
1. System State backup must be performed regularly for the domain controller of the
Exchange DAG setup.
2. Scheduled backup is required if you choose to back up with DAG option, as AhsayOBM
on all DAG members will base on the scheduled backup time to start backups on
individual DAG member at the same time.
A DAG backup cycle is considered complete only when scheduled backup on all DAG
members have been carried out. An email report will be generated when a complete
DAG backup cycle is taken place.
Please keep in mind that manual backup will only be considered as individual mail-level
backup, and therefore will not be counted as part of the DAG backup cycle.
www.bobcloud.net 5
3. The MS Exchange Server Backup module will protect the Exchange server at the
database level. If a full system backup (for bare-metal recovery) is required, please
consider setting up a MS System Backup for each DAG member server.
4. To back up 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.
www.bobcloud.net 6
1.5 Overview of MS Exchange Database Backup Process
The following steps are performed during an Exchange Database backup job:
www.bobcloud.net 7
2 Backing up Microsoft Exchange Database
2007/2010/2013/2016
2.1 Creating a MS Exchange Server Backup Set for Exchange
Server 2007/2010/2013/2016
1. Click the Backup Sets icon on the main interface of AhsayOBM.
2. Create a new backup set by clicking the “+” icon next to Add new backup set.
3. Select the Backup set type as MS Exchange Server Backup. The system will
automatically detect and select the Exchange Server version, make sure the version
selected is correct. Name your new backup set and then click Next to proceed.
www.bobcloud.net 8
4. In the Backup Source menu, select the Information Store for backup. Click Next to
proceed.
5. In the Schedule menu, you can configure a backup schedule for backup job to run
automatically at your specified time interval. Click Add to add a new schedule, then click
Next to proceed when you are done with the settings.
Note: By default, a database backup scheduled for every Friday at 22:00 and a log
backup scheduled daily (except Friday) at 22:00 are created automatically.
www.bobcloud.net 9
6. In the Destination menu, select a backup destination where the backup data will be
stored. Click the “+” icon next to Add new storage destination / destination pool.
7. Select the destination type and destination storage, then click OK to proceed.
www.bobcloud.net 10
8. When you are done with settings, click Next on the Destination menu page to proceed.
9. In the Encryption window, the default Encrypt Backup Data option is enabled with an
encryption key preset by the system which provides the most secure protection.
You can choose from one of the following three Encryption Type options:
Default – an encryption key with 44 alpha numeric characters will be randomly
generated by the system
User password – the encryption key will be the same as the login password of
your AhsayOBM at the time when this backup set is created. Please be reminded
that if you change the AhsayOBM login password later, the encryption keys of the
backup sets previously created with this encryption type will remain unchanged.
www.bobcloud.net 11
Custom – you can customize your encryption key, where you can set your own
algorithm, encryption key, method and key length.
Note: For best practice on managing your encryption key, refer to the following KB
article. https://forum.ahsay.com/viewtopic.php?f=169&t=14090
Click Next when you are done setting.
10. If you have enabled the Encryption Key feature in the previous step, the following pop-up
window shows, no matter which encryption type you have selected.
www.bobcloud.net 12
The pop-up window has the following three options to choose from:
Unmask encryption key – The encryption key is masked by default. Click this
option to show the encryption key.
Copy to clipboard – Click to copy the encryption key, then you can paste it in
another location of your choice.
Confirm – Click to exit this pop-up window and proceed to the next step
11. Enter the Windows login credentials for user authentication. Click Next to proceed.
www.bobcloud.net 13
12. The following screen shows when the new backup set is created successfully.
13. You can click Backup now to start a backup immediately, or you can run a backup job
later by following the instructions in Running Backup Job for Microsoft Exchange Server
2007/2010/2013/2016.
www.bobcloud.net 14
2.2 Running Backup Job for Microsoft Exchange Server
2007/2010/2013/2016
1. Log in to AhsayOBM.
2. Click the Backup icon on the main interface of AhsayOBM.
3. Select the backup set which you would like to start a backup for.
www.bobcloud.net 15
4. If you would like to modify the In-File Delta type, Destinations and Retention Policy
settings, click Show advanced option.
Refer to Appendix A Exchange Server Backup Type for more information regarding the
backup set type. .
5. Click Backup to start the backup.
www.bobcloud.net 16
3 Restoring Microsoft Exchange Server
2007/2010/2013/2016
3.1 Pre-restoration Requirements
Before you get started with restoring your database using the AhsayOBM, there are a couple
of steps you may need to perform first.
1. Prepare the operating system for the Exchange Server restore (if required). Install the
original version of Windows and Exchange Server (with the same level of service pack
installed as in the original system).
2. Restore Windows Active Directory (if required). Restore the System State data from the
backup server, and then restore the System State using WBAdmin.exe.
3. Install AhsayOBM (if required). Refer to the Ahsay Online Backup Manager v7 Quick
Start Guide for Windows via the URL below.
http://ahsay.com/download/download_document_obm-quickstart-windows.jsp
4. Make sure the Microsoft Exchange Information Store services from Windows
Services is started.
Launch Services in Windows by clicking Start then typing “Services” in the search box.
After launching the Services window, look for Microsoft Exchange Information Store
and check the Status column to confirm if it is started. If it is not, right click the item then
select Start.
www.bobcloud.net 17
3.2 Restoring Exchange Database for Microsoft Exchange Server
2007/2010/2013/2016
1. Make sure you have followed the steps in Section 3.1 before proceeding to this section.
2. In the AhsayOBM main interface, click the Restore icon.
3. Select the backup set that you would like to restore database from.
4. Select the backup destination that contains the database you would like to restore.
www.bobcloud.net 18
5. Click to expand the menu tree to select which Information Store to restore. You can also
select individual database file to restore by clicking the Restore raw file checkbox at the
left bottom corner.
In addition, you can also choose to restore backup item(s) from a specific backup job
using the drop-down menu at the top. Click Next to proceed when you are done with the
selection.
6. Select to restore the database to its Original location, or to an Alternate location.
Restore to Original location
Select the Original location option, then press Next to proceed.
www.bobcloud.net 19
Restore to Alternate location
a) Select the Alternate location option, then press Next to proceed.
b) Select the locations where you would like to restore the database to. Name
the new mailbox store, then click Browse to modify the database, log and
checksum file location if necessary. Click Next to proceed when you are
done with the settings.
7. Select the temporary directory for storing temporary files, such as delta files when they
are being merged, click Restore to start the restoration.
www.bobcloud.net 20
8. The following screen with the text Restore Completed Successfully shows when the
restoration is completed.
For details regarding verifying the restoration activities log between
AhsayOBM and the Exchange Server, refer to Appendix B Restore Activities
Log.
www.bobcloud.net 21
4 Backing up Microsoft Exchange Server in
Database Availability Group (DAG)
4.1 License Requirement to Backup all Exchange Server
2010/2013/2016 in DAG environment
One AhsayOBM license CAL with one Exchange Server Add-on Module is deducted from
each installation of the AhsayOBM on the DAG environment. Please check with your backup
service provider if more AhsayOBM with Exchange backup is required.
4.2 Creating Backup Set for Microsoft Exchange Server
2010/2013/2016 (DAG)
1. Click the Backup Sets icon on the main interface of AhsayOBM.
2. Create a new backup set by clicking the “+” icon next to Add new backup set.
3. Select the Backup set type as MS Exchange Server Backup. Make sure you choose
the correct Exchange Server version with “Database Availability Group”. Name your new
backup set and then click Next to proceed.
www.bobcloud.net 22
4. In the Backup Source menu, select the Information Store for backup. Click Next to
proceed.
In the Schedule menu, you can configure a backup schedule for backup job to run
automatically at your specified time interval. Click Add to add a new schedule, then click
Next to proceed when you are done setting.
Note: By default, a database backup scheduled for every Friday at 22:00 and a log
backup scheduled daily (except Friday) at 22:00 are created.
www.bobcloud.net 23
5. In the Destination menu, select a backup destination where the backup data will be
stored. Click the “+” icon next to Add new storage destination / destination pool.
6. Select the destination type and destination storage, then click OK to proceed.
www.bobcloud.net 24
7. When you are done with the settings, click Next on the Destination menu page to
proceed.
8. In the Encryption window, the default Encrypt Backup Data option is enabled with an
encryption key preset by the system which provides the most secure protection.
You can choose from one of the following three Encryption Type options:
Default – an encryption key with 44 alpha numeric characters will be randomly
generated by the system
User password – the encryption key will be the same as the login password of
your AhsayOBM at the time when this backup set is created. Please be reminded
that if you change the AhsayOBM login password later, the encryption keys of the
backup sets previously created with this encryption type will remain unchanged.
www.bobcloud.net 25
Custom – you can customize your encryption key, where you can set your own
algorithm, encryption key, method and key length.
Note: For best practice on managing your encryption key, refer to the following KB
article. https://forum.ahsay.com/viewtopic.php?f=169&t=14090
Click Next when you are done setting.
9. If you have enabled the Encryption Key feature in the previous step, the following pop-up
window shows, no matter which encryption type you have selected.
www.bobcloud.net 26
The pop-up window has the following three options to choose from:
Unmask encryption key – The encryption key is masked by default. Click this
option to show the encryption key.
Copy to clipboard – Click to copy the encryption key, then you can paste it in
another location of your choice.
Confirm – Click to exit this pop-up window and proceed to the next step
10. Enter the Windows login credentials for user authentication. Click Next to proceed.
www.bobcloud.net 27
11. The following screen shows when the new backup set is created successfully. Backup
will run automatically at the configured scheduled time.
12. On all other Exchange Servers within the same DAG, logon to AhsayOBM using the
same login account. Click the same backup set, and make sure the Run scheduled
backup for this backup set is turned on the Backup Schedule menu page. Make sure
you save the setting before exiting the application.
www.bobcloud.net 28
5 Restore Microsoft Exchange Server
2010/2013/2016 in Database Availability Group
(DAG)
5.1 Pre-restoration requirements
Refer to the following instructions to restore your Exchange database in Database Availability
Group (DAG).
The database restoration is required to restore on the active database only. You can identify
the Exchange server with the active database from the Exchange Management Shell.
Type the following command in the Exchange Management Shell.
Get-MailboxDatabase | ft name, server
It will show which Exchange server is hosting the active mailbox database, i.e. Mailbox
Database 01 and 03 are hosted on EX1, while Mailbox Database 02 and 04 are hosted on
EX2.
[PS] C:\>Get-MailboxDatabase | ft name, server
Name Server
---- ----
Mailbox Database 02 EX2
Mailbox Database 01 EX1
Mailbox Database 03 EX1
Mailbox Database 04 EX2
When you can identify which Exchange server is hosting the active database, you can logon
to that Exchange server to restore the database.
5.2 Restore Exchange Database to the Exchange with the active
database
1. In the AhsayOBM main interface, click Restore.
www.bobcloud.net 29
2. Select the backup set that you would like to restore data from.
3. Select the backup destination that contains the files or folders that you would like to
restore.
www.bobcloud.net 30
4. Click to expand the menu tree to select which Information Store to restore. You can also
select individual database file to restore by clicking the Restore raw file checkbox at the
left bottom corner.
In addition, you can also choose to restore backup item(s) from a specific backup job
using the drop-down menu at the top. Click Next to proceed when you are done with the
settings.
5. Select to restore the files to their Original location, or to an Alternate location.
Restore to Original location
Select the Original location option, then press Next to proceed.
www.bobcloud.net 31
Restore to Alternate location
a) Select the Alternate location option, then press Next.
b) Select the locations where you would like to restore the database to. Name
the new mailbox store, then click Browse to modify the database, log and
checksum file location if necessary. Click Next to proceed.
6. Select the temporary directory for storing temporary files, such as delta files when they
are being merged, then click Restore to start the restoration.
www.bobcloud.net 32
7. The following screen with the text Restore Completed Successfully shows when the
restoration is completed.
For details regarding verifying the restoration activities log between
AhsayOBM and the Exchange Server, refer to Appendix B Restore Activities
Log.
www.bobcloud.net 33
6 Technical Assistance
To contact Ahsay support representatives for technical assistance, visit the following website:
https://www.ahsay.com/jsp/en/contact/kbQuestion.jsp
Also use the Ahsay Knowledge Base for resource such as Hardware Compatibility List,
Software Compatibility List, and other product information:
https://forum.ahsay.com
www.bobcloud.net 34
7 Documentation
Documentations for all Ahsay products are available at:
https://www.ahsay.com/jsp/en/home/index.jsp?pageContentKey=ahsay_downloads_document
ation_guides
You can send us suggestions for improvements or report on issues in the documentation, by
contacting us at:
https://www.ahsay.com/jsp/en/contact/kbQuestion.jsp
Please specify the specific document title as well as the change required/suggestion when
contacting us.
www.bobcloud.net 35
Appendix
Appendix A Exchange Server Backup Type
AhsayOBM utilizes the Volume Shadow Copy Service and the Microsoft Exchange Server 2010
Writers for backup of MS Exchange 2010 databases. It offers the following types of backup options:
Database backup
Backs up the databases (EDB), transaction logs (LOG), checkpoint files (CHK), and then
truncates the transaction logs for a specific database.
A full backup of an Exchange database creates and stores a complete copy of the database
file, transaction logs, and checkpoint files. A Microsoft Exchange Server 2010 database has
one set of transaction log files dedicated to that one database.
After the database has been backed up, the transaction log files on the disk are truncated
so that only database changes that occur after the backup was made will remain. During
this process, either the Store Writer or the Replication Service deletes all log entries up to
the checkpoint, based on the assumption that the databases have now been backed up in a
consistent state that contains all changes up to the most recent checkpoint.
If the database being backed up is dismounted during the backup operation, Exchange
Server 2010 will not truncate the transaction logs and the result will be the equivalent of a
copy backup operation, not a Full backup operation.
At the completion of Full or Incremental backups, the headers of the active mounted
database get updated with the current backup information. A Full backup is required in order
to run Incremental or Differential backups. There is no restriction as to which copy the Full
backups are taken from as long as it is a backup.
www.bobcloud.net 36
Full backups are used in the following restoration scenarios:
A database becomes corrupted or is lost, but the transaction log files on disk are
intact. In this scenario, the affected database files can be restored from the Full
backup, and then recovered by replaying the transaction logs that are still on disk.
Transaction log files, as well as the database file on disk, are lost. In this scenario,
the transaction log files that were backed up at the time of the Full backup are
restored together with the database.
Log File backup
Backs up the transaction logs (LOG) to record changes since the last full or incremental
backup, and then truncates the transaction logs.
An Incremental backup of Microsoft Exchange Server 2010 database saves changes to the
database that have occurred since the last Full or Incremental backup. When all the
database files and log files are restored to the system, they can be recovered to the state
they were in at the time of the last Incremental backup. The data stored in an Incremental
backup includes only the transaction log files up to the current time.
When the backup is completed, the Exchange Server truncates the log files and marks the
backup time in the database headers. Using an Incremental backup to recover a database
requires the restoration of at least two data sets: the last Full backup, and then every
Incremental backup taken after the last Full backup. The benefit of using Incremental
backup is that an individual Incremental backup is much smaller than a Full backup and an
individual Incremental backup is often smaller than an individual Differential backup.
The disadvantage of using Incremental backups is that if there are many Incremental
backups made between Full backups, recovering the storage group may involve recovering
many Incremental backups. Exchange does not allow an Incremental backup to occur when
there has been no previous Full backup to establish the starting point for the incremental
changes.
www.bobcloud.net 37
Appendix B Restore Activities Log
The information below demonstrates how you can verify the restoration activities log between the
AhsayOBM and the Microsoft Exchange Server.
To verify the restoration activities log, open both the Restore Report in AhsayOBM and the Event
Viewer in the Microsoft Exchange Server.
Opening Restore Report in AhsayOBM
1. Open AhsayOBM, then click the Report icon on the main interface page.
2. Click the Restore option on the left, then click the restore report you want to verify on the right.
Click the View Log button to show all the restoration activities log.
www.bobcloud.net 38
Opening Event Viewer in Microsoft Exchange Server
1. Click the Start button on the left bottom corner in the Exchange Server, then type Event Viewer
in the search bar at the bottom.
2. When the Event Viewer is opened, click Windows Log on the left to expand the menu tree,
then select Application. All Application activities logs are shown on the right now.
=
www.bobcloud.net 39
Cross-checking activities log on AhsayOBM Restore Report and
Exchange Server Event Viewer
Each restoration action item initiated by AhsayOBM represented by individual activity log in the
Restore Report in AhsayOBM, and the corresponding action taken place in the Exchange Server is
shown in the Event Viewer as well.
There are 5 major parts to take place during the database restoration progress as shown below.
s
2. Dismount Exchange Server Database
Event Viewer in Exchange Server
AhsayOBM Restore Report
1. Download files from AhsayCBS to Temp Folder
3. Restore files to Exchange Server Database
AhsayOBM Restore Report
Event Viewer in Exchange Server
www.bobcloud.net 40
4. Remount Exchange Server Database
AhsayOBM Restore Report
Event Viewer in Exchange Server
5. Delete files from Temp Folder
By default, temporary files will be deleted from the temp folder after backup. This feature can
be turned on or off by following the steps below.
1. Open AhsayOBM, then click the Backup Set icon on the main interface.
2. Select the backup set you would like to change this setting.
3. Click “Show advanced settings” on the left, then select “Others”.
4. Use the “Remove temporary files after backup” checkbox to enable or disable this
feature.