Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Relocate Vault Store Partition after migration to NetBackup

Created: 28 Mar 2013 • Updated: 28 Mar 2013 | 7 comments
This issue has been solved. See solution.

Hi,

Is it ok to Relocate Vault Store Partition after migration to NetBackup? Restore should be fine after Vault Store Partition relocated to another location?

Many Thanks

Operating Systems:

Comments 7 CommentsJump to latest comment

TonySterling's picture

Yes, once you update SQL to point to the new partition path everything should be called back just fine.

SOLUTION
ia01's picture

Thanks Tony

Just one more question, we using EV 8.0.4 

All vault store partion has folder sharing as EVPartition01cb8d9a2d28f510$ and so on ...

When we move partition from one location to another we loose that share settings. Do we have to re-create that share?

Many Thanks

TonySterling's picture

EV will automatically create the share on the new partition when the Storage Service starts.  You should see an event in the EV Application log. 

Rob.Wilcox's picture

I had incline that there is an issue if you ever try to do a bulk restore back from NetBackup to EV... that it will use the same server name and partition / path-names as when it was pushed to Netbackup from EV.

I could be wrong though.

TonySterling's picture

Pretty sure he is talking about Collect and Migrate. 

Either way, if he is doing an actual backup restore he should be able to specifiy a new location, so either way it shouldn't be a problem.

ia01's picture

I'm doing Collect and Migrate to NetBackup.

Tested this earlier in one partition.

Collected and Migarted a partition from F:\ drive

Then relocated the partition to G:\ drive

Now tested restore of an item which retrieves cab file from Netbackup. Althugh NetBackup restore jobs shows old path /F/EVStores/ which can be scary to see at first glance.... it actually restores cab file to /G/EVStores/... I guess this is something cosmetic issue which needs to be fixed. However all working fine as expected.