I would like to verify that our backup procedure is sound. What I would like to do is something like the following:
Restore a backup to a new database, then point vault at it and verify it works. Without disturbing the active vault DB. I'm ok with the active vault being unavailable for a short period of time.
Anyone have any experience? Is there some way to easily point vault at a db called sgvaulttest vs. sgvault on the same DB server?
Testing Backup Procedure
Moderator: SourceGear
I would recommend restoring to another instance of SQL server. You can also download a demo to set up a test Vault server so you don't have to disturb your live one.
If don't mind your live server down, you can always detach your database, rename it so it doesn't get touched, and then restore your back-up. In order for everything to work in the restore in this case, such as user accounts, you would need to perform a reinstall of your Vault server. When done, you can drop the restored database, rename the previous one back to sgvault, and then reattach the original.
I believe the name of the database that Vault would attach to is hard-coded in. I've heard of one user changing the name after the connection was already made, but I can't say if it worked really well for that user or not. I would say one could have unexpected results, and we don't really support renaming the database.
If don't mind your live server down, you can always detach your database, rename it so it doesn't get touched, and then restore your back-up. In order for everything to work in the restore in this case, such as user accounts, you would need to perform a reinstall of your Vault server. When done, you can drop the restored database, rename the previous one back to sgvault, and then reattach the original.
I believe the name of the database that Vault would attach to is hard-coded in. I've heard of one user changing the name after the connection was already made, but I can't say if it worked really well for that user or not. I would say one could have unexpected results, and we don't really support renaming the database.