02-21-2016 08:45 PM
I have an Exchange 2013 with a 6GB mailbox EDB file. I just installed BE 15 (trial) with database option and agent on the exchange server.
I created a backup job which is supposed to backup the entire MS information store from the Exchange server. The job succeeds 100%. But the byte count is 10MB.
What could be going wrong here?
Solved! Go to Solution.
02-21-2016 09:44 PM
Make sure your BE Service Account has permissions to Exchange as per the TN below:
https://www.veritas.com/support/en_US/article.TECH130255
Also, if you have turned on AOFO, turn it off and let BE use VSS natively to do the snapping of Exchange.
Do you have Exchange on a VM or a physical server, and if a VM, how are you doing your backups?
THanks!
02-21-2016 09:44 PM
Make sure your BE Service Account has permissions to Exchange as per the TN below:
https://www.veritas.com/support/en_US/article.TECH130255
Also, if you have turned on AOFO, turn it off and let BE use VSS natively to do the snapping of Exchange.
Do you have Exchange on a VM or a physical server, and if a VM, how are you doing your backups?
THanks!
02-22-2016 12:14 AM
Please make sue that you are backing up using Microsoft information store, EDB files will skip if you are backing from directory
If your exchange is a standalone server, on the selection list you should see Drive (C,D), system state, and MIS (Microsoft Information Store) , you need to backup the EDB using MIS. If you are running Trail version make sure application and Database option is checked in Installing and Licenses Wizard.
Please find the document below
https://www.veritas.com/support/en_US/article.HOWTO99184
If you Exchange is in DAG: Configure the backup given as per TN given below
https://www.veritas.com/support/en_US/article.000076124
02-22-2016 12:25 AM
Please make sure you read what the OP states before commenting:
OP is using BE 15 in trial mode with the DB license invoked and active. The OP is backing up via the Information Store.
02-22-2016 12:59 AM
@craig V: my apoligies, I didnt read it.
02-22-2016 01:09 AM
Please do so in future...
04-02-2016 10:32 AM
Well - a reboot and it was solved. I can't explain the cause beyond that...