Avamar 5.0 Exchange Client User Guide.pdf - EMC Community ...
Avamar 5.0 Exchange Client User Guide.pdf - EMC Community ... Avamar 5.0 Exchange Client User Guide.pdf - EMC Community ...
Capabilities and LimitationsINTRODUCTIONFor this reason, initial backup progress bytes reported by Avamar Administratorwill be larger than the size reported by Exchange; Progress bytes reported bysubsequent backups will be more in line with the Exchange sizes.Additionally, when browsing backups to restore message folders, sizes reported byAvamar Administrator will be the size required to restore that folder insideExchange, not the amount of storage space actually consumed on the Avamarserver.NOTE: This limitation applies to the Exchange Messageplug-in only.Database Service Requires Manual Intervention. The Database service,shown in the cluster administrator, does not automatically return to online statusimmediately following a database restore. The interim solution is to manuallybring the Database service online following the restore.NOTE: This limitation applies to the Exchange Server2007Exchange Server 2003 Database plug-in.Messages in Outbox Might Not Be Backed Up. Messages in the Outboxfolder might not be backed up. This can occur for a number of reasons, but all areinherent limitations of Microsoft Exchange, for which there are no known interimsolutions.NOTE: This limitation applies to the Exchange Messageplug-in only.Incorrect Initial Reporting of Folder Sizes. There is a known limitation withthe Windows Exchange Message plug-in which all folder sizes are initially reportedto be zero bytes. However, expanding a folder causes the folder size to becorrectly updated and all contents to be shown. This does not affect actual restorebehavior.NOTE: This limitation applies to the Windows ExchangeMessage plug-in. It does not apply to the Exchange Databaseplug-in.AVAMAR 5.0 • AVAMAR EXCHANGE CLIENT USER GUIDE 16
Capabilities and LimitationsINTRODUCTIONKnown Limitations with Region Profiles. If you are performing messagelevelbackups, the Region Profile for the AvamarBackupUser account must be thesame as the Exchange Server Region Profile. Otherwise, when you attempt torestore message-level backups, Exchange might incorrectly translate certainextended characters, which will corrupt the mailbox. This is a limitation ofMicrosoft Exchange.NOTE: This limitation applies to the Exchange MessagePlug-in only.Recovery of Large Message-Level Backups Might Fail. If you attempt torecover a large message-level backup, the restore may fail even though thebackup itself was successful. There is a known limitation with the MSExchangeISservice in which it can run out of resources during a MAPI restore involving a largenumber of folders or mailboxes (that is, typically 500 or more). When this occurs,the following error message is returned:CreateFolder failed 80004005 MAPI_E_CALL_FAILEDThis issue is addressed in Microsoft Knowledge Base articles 830829 and 830836and an interim solution is offered. Refer to the Microsoft Knowledge Base articlesfor additional information.NOTE: This limitation applies to the Exchange MessagePlug-in only.Windows Server 2000 support. Avamar Exchange Server Client 5.0 does notsupport Microsoft Exchange 2000 running on Windows 2000 Server. For MicrosoftExchange 2000 SP3 or later running on Windows 2000 Server SP3 or later, useAvamar Exchange Server Client 4.1.Activate physical nodes of cluster on Avamar server before configuringthe Avamar Cluster Client. When configuring a Window cluster with theAvamar Cluster Configuration tool, all physical nodes of the cluster must beactivated on the Avamar server before running the tool.In Active/Active Cluster, Simultaneous Database Restores of BothExchange Virtual Servers Will Fail In a two node cluster, when one nodefails both Exchange Virtual Servers run on a single node. If you try to restore bothExchange Virtual Servers at the same time, both restores will start together, butthe restore initiated last will fail. This occurs because both are using the samedefault log path. To prevent a failure, specify in the Windows Exchange DatabasePlugin Restore Command Line options a different log path for each EVS.AVAMAR 5.0 • AVAMAR EXCHANGE CLIENT USER GUIDE 17
- Page 1 and 2: EMC ® AVAMAR ®5.0AVAMAR EXCHANGE
- Page 3 and 4: TABLE OF CONTENTSForeword . . . . .
- Page 5 and 6: FOREWORDScope and Intended Audience
- Page 7 and 8: FOREWORDNotes, Tips, and WarningsTh
- Page 9 and 10: Standalone and High-Availability De
- Page 11 and 12: System RequirementsINTRODUCTIONCCR
- Page 13 and 14: Capabilities and LimitationsCapabil
- Page 18 and 19: INSTALLING/UNINSTALLING AVAMAR EXCH
- Page 20 and 21: Quick Reference (Road Map)INSTALLIN
- Page 22 and 23: Installing the Avamar Exchange Clie
- Page 24 and 25: Configuring an Exchange Server 2007
- Page 26 and 27: Configuring an Exchange Server 2007
- Page 28 and 29: Configuring an Exchange Server 2007
- Page 30 and 31: Configuring an Exchange Server 2003
- Page 32 and 33: Configuring an Exchange Server 2003
- Page 34 and 35: Configuring the Avamar Cluster Clie
- Page 36 and 37: Configuring the Avamar Cluster Clie
- Page 38 and 39: Uninstalling and Upgrading the Avam
- Page 40 and 41: Uninstalling an Older Version of Cl
- Page 42 and 43: Exchange Backup and RecoveryUSING T
- Page 44 and 45: Backing Up an Entire Exchange Datab
- Page 46 and 47: Backing Up an Entire Exchange Datab
- Page 48 and 49: Backing Up One or More Message Fold
- Page 50 and 51: Backing Up One or More Message Fold
- Page 52 and 53: Backing Up One or More Message Fold
- Page 54 and 55: Backing Up One or More Message Fold
- Page 56 and 57: Backing Up One or More Message Fold
- Page 58 and 59: Backing Up One or More Message Fold
- Page 60 and 61: Recovering an Entire Exchange Datab
- Page 62 and 63: Recovering an Entire Exchange Datab
- Page 64 and 65: Restoring to a RSG with the Windows
Capabilities and LimitationsINTRODUCTIONFor this reason, initial backup progress bytes reported by <strong>Avamar</strong> Administratorwill be larger than the size reported by <strong>Exchange</strong>; Progress bytes reported bysubsequent backups will be more in line with the <strong>Exchange</strong> sizes.Additionally, when browsing backups to restore message folders, sizes reported by<strong>Avamar</strong> Administrator will be the size required to restore that folder inside<strong>Exchange</strong>, not the amount of storage space actually consumed on the <strong>Avamar</strong>server.NOTE: This limitation applies to the <strong>Exchange</strong> Messageplug-in only.Database Service Requires Manual Intervention. The Database service,shown in the cluster administrator, does not automatically return to online statusimmediately following a database restore. The interim solution is to manuallybring the Database service online following the restore.NOTE: This limitation applies to the <strong>Exchange</strong> Server2007<strong>Exchange</strong> Server 2003 Database plug-in.Messages in Outbox Might Not Be Backed Up. Messages in the Outboxfolder might not be backed up. This can occur for a number of reasons, but all areinherent limitations of Microsoft <strong>Exchange</strong>, for which there are no known interimsolutions.NOTE: This limitation applies to the <strong>Exchange</strong> Messageplug-in only.Incorrect Initial Reporting of Folder Sizes. There is a known limitation withthe Windows <strong>Exchange</strong> Message plug-in which all folder sizes are initially reportedto be zero bytes. However, expanding a folder causes the folder size to becorrectly updated and all contents to be shown. This does not affect actual restorebehavior.NOTE: This limitation applies to the Windows <strong>Exchange</strong>Message plug-in. It does not apply to the <strong>Exchange</strong> Databaseplug-in.AVAMAR <strong>5.0</strong> • AVAMAR EXCHANGE CLIENT USER GUIDE 16
Change language