cancel
Showing results for 
Search instead for 
Did you mean: 

SQL Database Migration - How long should we hold old databases?

OldEmployee
Level 5

We have successfully migrated vault store databases as per:

https://www.veritas.com/support/en_US/article.TECH35744

I understand that once successful, new database will be used for all transactions. But is there a point to holding on to the old database? Or can they be removed once migration is successful?

1 ACCEPTED SOLUTION

Accepted Solutions

GertjanA
Moderator
Moderator
Partner    VIP    Accredited Certified

Hello,

You'll see issues with the new databases soon enough, mainly in the eventlog for EV. Monitor close. If you are satisfied with the new ones functioning, detach the old databases, don't delete. then keep them for a month. That way, you'll see quick enough if a connection is made to an old db.

Regards. Gertjan

View solution in original post

2 REPLIES 2

GertjanA
Moderator
Moderator
Partner    VIP    Accredited Certified

Hello,

You'll see issues with the new databases soon enough, mainly in the eventlog for EV. Monitor close. If you are satisfied with the new ones functioning, detach the old databases, don't delete. then keep them for a month. That way, you'll see quick enough if a connection is made to an old db.

Regards. Gertjan

ChrisLangevin
Level 6
Employee

Good advice from Gertjan about detaching the old ones for a period before deleting them. It's easy enough to tell quickly whether you migrated the important stuff correctly (Directory, VSDB, Fingerprint), but the detach will help you notice the Audit database or that one random FSA Reporting database from 2013 that you forgot all about....

--Chris