Skip to main content

Configuration requirements to backup or restore Exchange 2007 with Backup Exec

 Document ID: 288777

http://support.veritas.com/docs/288777 E-Mail this document to a colleague

Exchange Agent How to: Configuration requirements to backup or restore Exchange 2007 and to perform Exchange GRT (Granular Recovery Technology) backups or restores with Backup Exec for Windows Servers (BEWS)

Details:


In Exchange 2003, the following security roles were available through the Delegation Wizard in Exchange System Manager:



  • Exchange Full Administrator
  • Exchange Administrator
  • Exchange View Only Administrator


Exchange 2007 has the following predefined groups that manage Exchange configuration data:



  • Exchange Organization Administrators
  • Exchange Recipient Administrators
  • Exchange View-Only Administrators
  • Exchange Server Administrators


The following tasks should be performed in order to connect to and back up the Exchange 2007 Information Store Databases using Backup Exec:



If the Exchange server is not locally installed on the Backup Exec media server, confirm the following:



  • The Backup Exec Remote Agent for Windows Servers is installed on the Exchange 2007 server.


  • The Microsoft Exchange 2007 Management Tools are installed on the Backup Exec media server.


32 bit Media Servers - (Note: Microsoft Windows 2008 x32 was not supported in the original release. The Exchange 2007 Management Tools from the SP1 package, E2K7SP1EN32.exe) must be installed. Download Exchange 2007 SP1 from the Microsoft Download Center: http://www.microsoft.com/downloads/details.aspx?familyid=6be38633-7248-4532-929b-76e9c677e802&displaylang=en



64 bit Media Servers - To download the 64-bit version of the management tools, use the same media or download that is used to install Exchange 2007



  • Microsoft Exchange Server MAPI Client and Collaboration Data Objects (MAPI/CDO) are installed on the Exchange 2007 Server.


Download the MAPI/CDO 1.2.1 Package from Microsoft Download Center: http://www.microsoft.com/downloads/details.aspx?FamilyID=e17e7f31-079a-43a9-bff2-0a110307611e&DisplayLang=en



  • Ensure the Backup Exec "Logon Account" (System Logon Account by default at Network > Logon Account in the Backup Exec Interface) being used to backup Exchange is:
  • A member of Domain Administrators
  • Is an explicit member of the Local Administrators group of the Exchange 2007 server (implied membership via Domain Admin group may not be sufficient)


For further details on creating a new account with the proper permissions, refer to the following instructions:



1. Go to Active Directory Users and Computers and go to the Users directory. Right-click on the Administrator account and select copy (Figure 1) and create an account for BACKUP EXEC.

Figure 1





2. Go to Network, Logon Accounts within the Backup Exec console. Click New... and enter the details of the account created in #1.

Figure 2





3. Open the Exchange Management Console.



4. In the Exchange Management Console, select Organization Configuration. (Figure 3)

Figure 3





5. Right click on Organization Configuration and select Add Exchange Administrator. (Figure 4)

Figure 4





6. On the Add Exchange Administrator page, click Browse and select the user that you want to delegate control to.



7. Select the Exchange Server Administrator Role radial button. (Figure 5)

Figure 5





8. Click Add and under Select the server(s) to which this role has access select the servers to which to delegate control.(Figure 6)

Figure 6



9. Click OK. Click Add.

10. On the Completion page verify that the delegation was successful and click Finish.

11. Define the jobs in Backup Exec by using the Resource Credentials pane to use the newly created "Logon Account".



Note: The requirements listed above only pertain to the basic configuration required to connect to and backup the Exchange 2007 Information Store databases, storage groups, etc... for the purpose of restoring these items in their entirety. To fully utilize the functionality of Exchange 2007 and prior GRT (Granular Recovery Technology) backups and restores, the following must be configured/confirmed:



  • The Exchange Administrator Account Backup Exec uses to attach to the Exchange Server must have a uniquely named mailbox within the Exchange organization that is not disabled or hidden from the Global Address List. For more information on this, review the following document:


How to confirm that an Exchange mailbox name is unique within the Exchange organization when configuring Backup Exec to backup mailboxes or if a GRT (Granular Restore Technology) based backup does not display individual mailboxes for restore http://support.veritas.com/docs/256537



How to remove the "Hidden" attribute from Exchange 2000 and Exchange 2003 mailboxes so that the mailboxes will be available to the Global Address List for backup purposes

http://support.veritas.com/docs/243328



  • Exchange 2007 and Outlook 2007 can not be installed on the same Windows 2003 Server.
  • For GRT Backups to tape, mailbox users must reside in the same domain as the Exchange Server. For more information, review the following:


Exchange Granular Recovery Technology (GRT) backup to tape does not display the mailboxes in the restore selections for users that reside in a domain other than the Exchange server(s) domain. http://support.veritas.com/docs/295627



  • For GRT Backups to disk (B2D), the Backup to Disk Test Tool - B2Dtest.exe should be run on the target disk first to ensure the basic file level functionality requirements are met. For more information, review and download the following:


Information regarding the Backup Exec Backup to Disk Test Tool - B2Dtest.exe

http://support.veritas.com/docs/321584



Note: If any of the above requirements cannot be confirmed, configured, etc... and there are any job failures or other issues, it is recommended to run at least one full test backup of Exchange with the Granular Recovery Option deselected prior to running another GRT Backup or opening a case with Symantec Technical Support.









Related Documents:

243328: Restore job fails while restoring a Mailbox -V-79-57344-33932 - 0xe000848c - Unable to attach to a resource. Make sure that all selected resources exist and are online, and then try again. \\Server name\Microsoft Information Store\Storage group name Unable to attach to \\Server name\Microsoft Information store\storage group name


256537: How to confirm that an Exchange mailbox name is unique within the Exchange organization when configuring Backup Exec to backup mailboxes or if a GRT (Granular Restore Technology) based backup does not display individual mailboxes for restore


261700: Backup Exec Products Disaster Recovery shortcut list


287804: Symantec Backup Exec 11d for Windows Servers Sets the Standard for Exchange 2007 Server Data Protection


287937: Microsoft Exchange Server MAPI Client and Collaboration Data Objects (MAPI/CDO) needs to be updated to support backup of Exchange 2007 with Backup Exec 11.0 for Windows Servers build 7170 and above


288005: Symantec Backup Exec (tm) for Windows Servers 11d revision 7170 Administrator's Guide (English)


294622: If Exchange 2007 is installed on a Windows 2008 Server and Granular Restore Technology (GRT) backups are performed, the backups complete with exceptions because the correct version of Microsoft Exchange Server MAPI Client and Collaboration Data Objects is not installed


295627: Exchange Granular Recovery Technology (GRT) backup to tape does not display the mailboxes in the restore selections for users that reside in a domain other than the Exchange server(s) domain.


299858: Setting default backup and restore options for Exchange data


301361: How to troubleshoot Exchange 2007 backups that may be failing due to VSS (Volume Shadow Copy Service) Issues


303457: Mailbox(s) may be missing from the restore selections of a backup set of an Exchange 2007 Information Store (IS) backup using Granular Restore Technology (GRT) to tape media


305383: Exchange Agent backup/restore: How to troubleshoot the error message "Access is denied" in Backup Exec for Windows Servers


310079: How Granular Recovery Technology works with the Exchange Information Store


310442: Disaster recovery for Exchange


311710: Best practices for Backup Exec 2010 Agent for Microsoft Exchange Server


312858: Restore of a mailbox from a GRT (Granular Restore Technology) backup of exchange 2007 fail with Final error: 0xe000ff00 - Unable to restore some Microsoft Exchange components because one or more of the databases are currently mounted or because the Recovery Storage Group is not properly configured.


313312: Granular Recovery Technology (GRT) enabled backup of Exchange 2007 Database fails with error "Final error: 0xe00084af - The directory or file was not found, or could not be accessed" when the Backup Exec Media Server is not a part of a domain.


320389: Granular Restore Technology (GRT) enabled Exchange 2007 database backup/restore fail even though the Microsoft Exchange Server MAPI Client and Collaboration Data Objects (MAPICDO) package is installed on the server."


321584: Information regarding the Backup Exec Backup to Disk Test Tool - B2Dtest.exe


325367: Unable to attach errors can occur because of options and limitations with restoring Exchange 2003 backups to Exchange 2007 servers


325552: How to restore individual Public Folder data from a Granular Recovery Technology enabled backup of Exchange 2007 Information Store.


326305: How to troubleshoot the error message: "V-79-57344-65072 - The connection to target system has been lost. Backup set canceled." when the Backup Exec Remote Agent for Windows Servers (RAWS) terminates during a backup or restore job


326416: Unable to see Exchange 2007 Information Store when browsing the backup selection list on a local Small Business Server Windows 2008


327019: How to troubleshoot "Unable to attach to one of the drives" or "unable to attach to a resource" errors that occur (a000848c HEX or e000848c HEX) when a backup or restore job fails with Backup Exec for Windows Servers




Products Applied:
Backup Exec 11d (11.0), 11d (11.0) 7170, 12.0, 12.5


Last Updated: August 24 2009 08:32 AM GMT
Expires on: 08-24-2010
Subscribe to receive critical updates about this document


Subjects:
Backup Exec
Agent For Exchange: Backup-Restore, Troubleshoot

Languages:
English (US)

Operating Systems:
Windows Server 2003
DataCenter, Enterprise Server, R2, Standard Server, Standard Server SP1 (x64)

Windows Small Business Server 2003
Standard Edition, Standard Edition (x64)

Windows Server 2008 Standard (x64-64bit) SP2

Comments

Popular posts from this blog

Recreating a missing VMFS datastore partition in VMware vSphere 5.x and 6.x

    Symptoms A datastore has become inaccessible. A VMFS partition table is missing.   Purpose The partition table is required only during a rescan. This means that the datastore may become inaccessible on a host during a rescan if the VMFS partition was deleted after the last rescan. The partition table is physically located on the LUN, so all vSphere hosts that have access to this LUN can see the change has taken place. However, only the hosts that do a rescan will be affected.   This article provides information on: Determining whether this is the same problem Resolving the problem   Cause This issue occurs because the VMFS partition can be deleted by deleting the datastore from the vSphere Client. This is prevented by the software, if the datastore is in use. It can also happen if a physical server has access to the LUN on the SAN and does an install, for example.   Resolution To resolve this issue: Run the  partedUtil  command on the host with the issues and verify if your output

ما هى ال FSMO Roles

  بأختصار ال FSMO Roles هى اختصار ل Flexible Single Operation Master و هى عباره عن 5 Roles فى ال Active Directory و هما بينقسموا لقسمين A - Forest Roles 1- Schema Master Role و هى ال Role اللى بتتحكم فى ال schema و بيكون فى Schema Master Role واحد فى ال Forest بيكون موجود على Domain Controller و بيتم التحكم فيها من خلال ال Active Directory Schema Snap in in MMC بس بعد ما يتعمل Schema Register بواسطه الامر التالى من ال Cmd regsvr32 schmmgmt.dll 2-Domin Naming Master و هى ال Role المسئوله عن تسميه ال Domains و بتتأكد ان مفيش 2 Domain ليهم نفس الاسم فى ال Forest و بيتم التحكم فيها من خلال ال Active Directory Domains & Trusts B- Domain Roles 1-PDC Emulator و هى ال Role اللى بتتحكم فى ال Password change فى ال domain و بتتحكم فى ال time synchronization و هى تعتبر المكان الافتراضى لل GPO's و هى تعتبر Domain Role مش زى الاتنين الاولانيين و بيتم التحكم فيها من خلال ال Active directory Users & Computers عن طريق عمل كليك يمين على اسم الدومين و نختار operations master فى تاب ال PDC Emu

Unlock the VMware VM vmdk file

  Unlock the VMware VM vmdk file Kill -9 PID Sometimes a file or set of files in a VMFS become locked and any attempts to edit them or delete will give a device or resource busy error, even though the vm associated with the files is not running. If the vm is running then you would need to stop the vm to manipulate the files. If you know that the vm is stopped then you need to find the ESX server that has the files locked and then stop the process that is locking the file(s). 1. Logon to the ESX host where the VM was last known to be running. 2.  vmkfstools -D /vmfs/volumes/path/to/file  to dump information on the file into /var/log/vmkernel 3.  less /var/log/vmkernel  and scroll to the bottom, you will see output like below: a. Nov 29 15:49:17 vm22 vmkernel: 2:00:15:18.435 cpu6:1038)FS3: 130: <START vmware-16.log> b. Nov 29 15:49:17 vm22 vmkernel: 2:00:15:18.435 cpu6:1038)Lock [type 10c00001 offset 30439424 v 21, hb offset 4154368 c. Nov 29 15:49:17 vm22 vmkernel: gen 664