BUE 21.4 & GRT with Exchange 2016 on Server 2019
New server with Windows 2019 Standard install, clean install of BUE 21.4 (will attempt using the Veritas BUE Migration Assistant to bring over catalogs, etc.) and questions regarding restoring GRT-enabled Exchange 2016 mailboxes/emails. I guess the biggest question is what are the requirements for the above scenario? Is Exchange Management Tools still required for GRT mailbox restores like it was for Exchange 2010? The system requirements pages I've found make no mention of Exchange Management Tools so I'm not sure. I do remember in the past when we were running BUE 16, and Exchange 2010 that I had to do some special configuration for GRT restores to work, and it has continued to work after we migrated to Exchange 2016 and updated BUE to our current 21.4.878Views0likes1CommentBackup Exec 16 Exchange GRT backup error with deduplication
After windows in place upgrade from windows server 2012 R2 to 2016, and BE services started normally and all job are running successfully, except Exchange and VMware GRT backup failed with the following error. Final error: 0xe0001203 - An error occurred while creating or accessing the directory specified for this operation. Check to make sure that the B2D folder and/or the temporary path specified for this operation are valid. V-79-57344-4611 - An error occurred creating or accessing the directory \\.pdvfs\servername\2\BEData specified for this operation. Ensure that the directory is accessible and can be written to. I changed storage from deduplication disk to tape drive and job success . FP 2 and latest HF 128051are installed .Solved3KViews0likes3CommentsExchange 2016 CU5 Support
Recently Microsoft released Cumulative Update 5 for Exchange 2016. This update made significant changes to the Mailbox Database structure. When CU5 is applied to Exchange 2016, Backup Exec is no longer able to restore individual items from a GRT-based backup of Exchange 2016. If restoring individual items is important to you, you may want to wait to apply CU5. If CU5 is applied, the current workaround should you need to restore individual items is to restore to a recovery database and then use the tools in Exchange 2016 to restore the individual items. For more information see technical Article 000126392. The Veritas Backup Exec team is currently working on a fix to address this issue and will release an On-Demand Patch (ODP) as quickly as possible. To stay up-to-date on this issue and be notified when the ODP is available, please subscribe to technical Article 000126392 BackupMikko3.4KViews5likes2Comments