Do you have a backup of your Vault Databases?

A collection of information about Vault, including solutions to common problems.

Moderator: SourceGear


Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear
PostPosted: Wed Apr 07, 2010 3:34 pm
Do you have a recent backup of your Vault, Vault Pro or Fortress databases?

What if you experience a server failure, hard drive failure or SQL Server catastrophic failure? These types of hardware/system failures can damage your Vault Pro and Vault databases. (Note: Fortress is now called Vault Pro.)

If a database is damaged, it may not be recoverable. If it is recovered with data loss, your database may still be unusable for source control or item tracking operations in Vault or Vault Pro.

You may think you have a recent backup. Are you sure? Maybe the backup job ran out of disk space or perhaps something on the network has changed and the backup isn’t happening.

These are all real issues that customers have reported to us in the past year.

It's extremely important to back up your sgvault, sgmaster and (if you’ re using Vault Pro) sgdragnet databases on a regular basis to prevent downtime
for your production team and possible loss of your source code and item tracking information.

Backing up your SQL Server databases.

The Backup function the Vault Admin Web Client allows you to backup and restore the entire Vault/Vault Pro database. Since Vault/Vault Pro uses SQL Server’s backup tool, this is merely an interface to manually create backups of the Vault database. You can also do manual backups using SQL Server tools.

However, it's best to have an automated backup plan which you can create using your own scripts or by using a SQL Server maintenance plan.

STORE BACKUPS ON A DIFFERENT MACHINE
You should store your backups on a different machine/drive than your live data. If your machine or disk crashes, your could lose your backups as well as the live data.


TEST YOUR BACKUPS
Once you've established a backup routine, it's crucial that you test your backups.

Every couple of months, restore your most-recent backup to a separate SQL Server - which is the situation you'll be in if you really need the backup. Make sure the backups are intact and accessible, and that you know the steps to restore a working SQL Server database.

For a good overview of SQL Server backup, see this Microsoft article:
http://msdn.microsoft.com/en-us/library/ms191239.aspx

For more specific information see these links for each of the versions of SQL Server:

SQL 2000 with Enterprise Manager
http://technet.microsoft.com/en-us/library/cc966495.aspx
http://msdn.microsoft.com/en-us/library/aa196685(v=SQL.80).aspx

SQL Server 2005 Management Studio Backup and restore:
http://msdn.microsoft.com/en-us/library/ms187048(SQL.90).aspx

SQL Server 2008 Backup and Restore and Maintenance Plan Topics:
http://msdn.microsoft.com/en-us/library/ms187048.aspx
http://msdn.microsoft.com/en-us/library/ms189621.aspx
http://msdn.microsoft.com/en-us/library/ms189953.aspx

You can also use a simple script to backup your database. For instance if you are backing up sgmaster and sgvault to a directory named Backups on the C:\ drive, your script might look like this:

BACKUP DATABASE sgmaster
TO DISK = 'C:\Backups\sgmaster.BAK'
BACKUP DATABASE sgvault
TO DISK = 'C:\Backups\sgvault.BAK'

For more information on scripting backups using Transact SQL see this link:
http://msdn.microsoft.com/en-us/library/ms186865.aspx
Linda Bauer
SourceGear
Technical Support Manager

Return to Knowledge Base (Vault)

Who is online

Users browsing this forum: No registered users and 2 guests

cron