07-04-2017 11:42 PM
Dear All,
We just finishing installing and configuring Enterprise Vault in our environment. Before archiving is applied through the enterprise, I would like to have a proper working backup procedure in place. Brief of the configuration is below;
Everything is working as expected. Only thing is I'm a lot confused of a proper backup procedure. Help I get is not very comprehensive, thus confused. I would like to take EV in backup mode before taking database, store, index backups. I'm planning to do database backup following this document https://www.veritas.com/support/en_US/article.000040169. My confusions are;
Thank you
Solved! Go to Solution.
07-05-2017 10:49 AM
Thanks Virgil.
But this wasn't exactly I was expecting. I did read all these docs and white papers while searching for best practice on EV backup. These docs are not very comprehensive on the steps to do complete EV backup in sync though it does explain in detail how to do each part.
The more I read, the more I get an impression that there is no way to backup EV in following pseudo order in a single script/job. (I believe I can very well comprise all these in a powershell script from active node of EV cluster with few r&d. For some reason, I don't feel comfortable with this approach, which involves invoking tasks remotely on db server and BE server);
I might end up doing above as separate jobs in different servers in different times within a specified time assigned for EV backup. Any advice if there is a better way? Btw, I do not have EV Agent for BE.
07-05-2017 10:58 PM
If you do not have a license for the BE EV agent, then that approach looks ok. Just make sure the archiving window does not overlap with the backup window. By the way, it is recommended to run the backup after the archiving, so if your archiving window is, say 5pm - 12AM, your backups should ideally start immediately after.
07-04-2017 11:49 PM - edited 07-04-2017 11:58 PM
Hi mate,
EV has several components that must be backed up for an effective data protection strategy. The minimum are:
1) Indexes
2) Vault Stores
3) SQL Databases
When you use BE or NBU EV agent, the agent takes care of everything, including setting/clearing backup-mode. See here BE EV best practices: http://www.veritas.com/docs/000068221
Besides this, you or your DBA will have to do SQL maintenance on a regular basis. That is documented in the article you mentioned (second part): http://www.veritas.com/docs/000040169
You may want to have a look on this article as well: Backing Up Enterprise Vault White Paper: http://www.veritas.com/docs/000010873
Hope this helps.
07-05-2017 10:49 AM
Thanks Virgil.
But this wasn't exactly I was expecting. I did read all these docs and white papers while searching for best practice on EV backup. These docs are not very comprehensive on the steps to do complete EV backup in sync though it does explain in detail how to do each part.
The more I read, the more I get an impression that there is no way to backup EV in following pseudo order in a single script/job. (I believe I can very well comprise all these in a powershell script from active node of EV cluster with few r&d. For some reason, I don't feel comfortable with this approach, which involves invoking tasks remotely on db server and BE server);
I might end up doing above as separate jobs in different servers in different times within a specified time assigned for EV backup. Any advice if there is a better way? Btw, I do not have EV Agent for BE.
07-05-2017 10:58 PM
If you do not have a license for the BE EV agent, then that approach looks ok. Just make sure the archiving window does not overlap with the backup window. By the way, it is recommended to run the backup after the archiving, so if your archiving window is, say 5pm - 12AM, your backups should ideally start immediately after.
07-06-2017 03:27 AM
Okay. Already made sure archiving window doesn't overlap backup. Good idea to start backup immediately after archiving. Thanks again Virgil.