E-Vault coverage Q&A
I am looking for input on how to provide coverage to an Enterprise Vault 10 (with historical data from as far back as v6) via NetBackup 22.214.171.124
I have reviewed article TECH176623 and found it easy to implement steps 1 & 2 (Full schedules only; SQL data is on separate/SQL servers which handle their own t-logs and truncations). Step 3 I am finding to be 'iffy'; we have over 1.5TB of Index data, most of which is from older versions of EV and it appears that these jobs (Fulls) will not complete in a timely enough manner. Step 4 I think is pretty much a long shot currently due to being multiple TB in size.
- The article above strongly suggests not overlapping the runs of any of the jobs; exactly how critical is this?
- If a step 3 (or 4) job is still running, what would be the impact of having a step 1 or 2 job run at the same time?
- If the Index and Closed Partition data is just flat-file in nature, could I not just back them up via a standard MS-Windows policy? Unless overlapping 1&2 jobs doesn't matter?
- If overlapping jobs is a critical issue, how do people engineer their schedules exactly? I'm fine with running a full infrequently, but how do people typically prevent the other steps from running while the full is in progress?
EV: version 10 on Windows 2008 R2 (SQL on an alternate/dedicated server)
NBU: version 126.96.36.199 on an AIX6 master and WIndows 2008 R2 media servers