Archiving By Date Range

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
Guest

Archiving By Date Range

Post by Guest » Sun Mar 28, 2004 7:00 am

Hey,
I'm thinking of purchasing Vault for my company instead of our existing VSS.
After I import my VSS DB to a Vault's one, can I archive Or BackUp my Vault's DB by a ranged date -
In Example: I want to backup Only the files that were last accessed/updated in the past month, is this possible?
Note: This feature is NOT supported by the VSS admin tools...
Answer needed ASAP please!
Thanks ahead!

-- Joey

jeremy_sg
Posts: 1821
Joined: Thu Dec 18, 2003 11:39 am
Location: Sourcegear
Contact:

Post by jeremy_sg » Sun Mar 28, 2004 7:42 am

This is not possible out of the box with Vault, nor would it be possible to back up a portion of the Vault database in order to restore it later.

It would be possible to write an app using the Vault Client API which would find every file modified in the last month and download it. Is that close to what you were expecting?

Guest

Ranged Date Archiving

Post by Guest » Sun Mar 28, 2004 7:59 am

First, Thanks for the reply jeremy_sg!
Second, what do you mean by "Download"?
Can I make a new DB for only the files that were updated in the past month?
In VSS, this could NOT be made even manually because of the VSS's DB architecture - VSS builds its files and version in a pyramid way - meaning a new version keeps only the changes that were made from the past Version.
Does Vault works the same or every Version is a "Stand Alone"?
Thanks again?

-- Joey

jeremy_sg
Posts: 1821
Joined: Thu Dec 18, 2003 11:39 am
Location: Sourcegear
Contact:

Re: Ranged Date Archiving

Post by jeremy_sg » Sun Mar 28, 2004 12:47 pm

Anonymous wrote: Second, what do you mean by "Download"?
This would be identical to doing a get latest operation for every version from the last month.
Anonymous wrote: Can I make a new DB for only the files that were updated in the past month?
Only if you take the versions that were downloaded as described above and committed them to a different repository or a different Vault Server. To sum up, what you're asking for is not easily done, but can be aproximated if you're willing to work with the Client API.

Post Reply