I am looking for a way to backup Vault and any necessary files etc. so as if in an act of God the entire server where Vault resides is lost, that i can sucessfully install vault to a new server and restore it to its prior state, retaining all history, files, users, etc.
Can somebody tell/ refer me to a "Best Practices" as far as what should be backed up regarding Vault. I know there is a SQL Database, and a backup utiilty (backs up to ".sgvbak" files) but is backing these up enought to restore Vault to it prior working state? Are there any physical files that need to be backed up in addition? and if so, is there any automation inside Vault itself to shedule backups?
Thanks,
Tom
Disaster Recovery and Backup
Moderator: SourceGear
Almost everything is exclusively stored in the database.
My recommendation would be to :
1) On a regular basis, make a "verifiable" backup of the sgvault database.
2) Also, you may want to backup Vault's vault.config file, as well as Vault's Shadow Folders web.config
In the case of a catastophe:
a) Rebuild the machine ( or designate a new machine for the Vault server)
b) Install SQL Server ( and service packs )
c) Restore sgvault database
d) Install Vault server
e) Compare Vault's new vault.config and Vault's Shadow Folders web.config against the backup. Merge in any changes to the files.
As for regular backups, standard SQL Server has a built in job scheduler for backing up the database. Also, one can use the built in Windows scheduler to run a SQL BACKUP DATABASE command as well.
My recommendation would be to :
1) On a regular basis, make a "verifiable" backup of the sgvault database.
2) Also, you may want to backup Vault's vault.config file, as well as Vault's Shadow Folders web.config
In the case of a catastophe:
a) Rebuild the machine ( or designate a new machine for the Vault server)
b) Install SQL Server ( and service packs )
c) Restore sgvault database
d) Install Vault server
e) Compare Vault's new vault.config and Vault's Shadow Folders web.config against the backup. Merge in any changes to the files.
As for regular backups, standard SQL Server has a built in job scheduler for backing up the database. Also, one can use the built in Windows scheduler to run a SQL BACKUP DATABASE command as well.
Jeff Clausius
SourceGear
SourceGear
Just for further clarification, when you are backing up Vault through the Admin Tool, all it is really doing is creating a Sql server backup file? None of the files/ folders mentioned get backed up with it? Is the .sgvbak just a virutal file name that maps to the actual Sql Server backup file?
thx...
Tom
thx...
Tom
That is correct. A backup in the Admin Tool is merely asking SQL Server to create a backup of the sgvault database.Thalko wrote:Just for further clarification, when you are backing up Vault through the Admin Tool, all it is really doing is creating a Sql server backup file? None of the files/ folders mentioned get backed up with it?
No. The .sgvbak file is the actual SQL Server backup file.Thalko wrote: Is the .sgvbak just a virutal file name that maps to the actual Sql Server backup file?
Jeff Clausius
SourceGear
SourceGear