Search found 36 matches
- Sun Jan 04, 2004 10:21 pm
- Forum: Support (Vault)
- Topic: Suggestion: Database Backup Path
- Replies: 4
- Views: 11503
Suggestion: Database Backup Path
Just noticed that there appears to be no way to set the backup directory for the database (at least that I could find). The default is C:\Winsows\System32 which apart from being a strange choice is also a bit annoying, as my C: drive only have enough free space for about three backups.... Any possib...
- Sun Jan 04, 2004 10:05 pm
- Forum: Support (Vault)
- Topic: Moving Vault databases between servers
- Replies: 5
- Views: 22110
- Sun Jan 04, 2004 9:20 pm
- Forum: Support (Vault)
- Topic: Moving Vault databases between servers
- Replies: 5
- Views: 22110
Thanks Jeff. Am I going to run into dramas regarding the licencing? I neglected to mention that I have two complete Vault systems here. I'm not just moving the database to a different server - I have a second Vault server as well, which will become the primary Vault server, and that one machine will...
- Sun Jan 04, 2004 6:22 pm
- Forum: Support (Vault)
- Topic: Moving Vault databases between servers
- Replies: 5
- Views: 22110
Moving Vault databases between servers
Is there any special requirements for moving a vault database between two vault servers? I've got the Lonely Coder Edition, which I was using for testing and importing my existing VSS DB, as well as a starter pack for the actual operation. As far as I can tell, it's a case of detach the default Vaul...
- Sun Jan 04, 2004 6:10 pm
- Forum: Support (Vault)
- Topic: Client CAL Packs
- Replies: 4
- Views: 10887
Client CAL Packs
Would SourceGear consider selling Vault CAL's in blocks of five or ten at some sort of discount? It just seems like it's one thing missing from the product line.
- gaffa
- gaffa
- Sun Jan 04, 2004 5:54 pm
- Forum: Support (Vault)
- Topic: Tips for a successful VSS Import
- Replies: 45
- Views: 147354
Something else to consider
Something else that is worth doing if you have a large database, which I found speeds up the process substantially is to archive off sections of the source VSS db, then restore them to a fresh VSS DB on the import machine, and import that fresh DB. I had a large (> 2Gb) VSS DB, and progressively arc...