Since Exchange 2010 Microsoft moved the writing behavior for DBs to be sequential thus offering a lot simplified deployment option by placing the DB/Logs on the same LUN, however for some reasons this wasn’t popular, but WHY?! If you don’t know, in previous version of Exchange the recommendations was to place logs on its own LUN and DB on its own LUN this was because Logs was using sequential writing and DB was using random writing (more information in my blog posts here and ). of DBs, also this breaks the benefits that comes with Exchange 2010 where we can place logs/DB on the same LUN, so what is the story?! Whenever I went to a customer location, I found that they placed Logs on a LUN nad DB on another LUN, This of course is not optimum for some customers with large no. You need to pay a careful attention to permissions needed to backup and restore the Exchange server. Finally, for Exchange 2010 the account must also have the Administrator role on the AD Domain for AD access as part of the GRT operations. On Exchange 20 servers the account must be granted the Exchange Organization Administrator role.
For Exchange 2003 the account must also be granted the Exchange Administrator, or Exchange Full Administrator role. In addition, the logon account must have a unique mailbox and the mailbox can NOT be hidden from the Global Address List. For GRT backups to a tape device and ALL GRT restore operations, from tape or disk, the logon account specified must be a member of the local Administrators group on the Exchange server. For GRT (Granular Restore Technology) enabled backups to disk (where the disk device is local to the BE Media Server and in the same domain) the logon account specified must be a member of the local Administrators group on the Exchange serverĤ.
For database only restores (database only with no granular restore functionality) the logon account specified must be a member of the local Administrators group on the Exchange serverģ.
For non-GRT backups (database only with no granular restore functionality) the logon account specified must be a member of the local Backup Operators group on the Exchange serverĢ. 1 source of errors on forums.Īlthough Symantec documented it pretty well here a lot of people still missing it, thus let us mention it again (I have highlight in bold some important permissions)ġ. 1 BE server that has media server and backup to disk configured.īefore we start in the actual steps, let me explain to you some fundamentals before you try configuring or using your BE to backup and restore your Exchange server:ġ- Permissions required to backup and restore Exchange 2010 Servers:īackup Exec server will not be able to backup your Exchange server out of the box, you need to grant the logon account used to access the Exchange server some permissions, this is the No.
In this blog series we will explore the options and methods to backup and restore Exchange 2010 either single server or DAG using Symantec Backup Exec 2010, the reason I chose BE that there are a lot of questions about how to use BE to backup Exchange server and a lot of confusion about the different ways of backup and restore available with different products including DPM 2010, BE and other products. Part2 of this article can be found here: įor Backup Exec 2012 version of this series, check my article: