I'm currently using Vault 2.0.0.2120 in Edit/Merge/Commit (CVS style) mode.
It seems that for every commit operation I make, Vault is backing up the file before committing it. This isn't necessary, because no other changes have been made to the baseline since the last get or commit.
All client options are set to their default values apart from setting the Edit/Merge/Commit concurrent development style.
Excessive local backups
Moderator: SourceGear
-
- Posts: 28
- Joined: Tue Feb 17, 2004 7:42 am
- Location: UK
- Contact:
Are you sure the backup is happening on commit, and not on checkout or Get? The backup is supposed to only happen on Get (which also happens on a Checkout) when the file status is Unknown, Edited, Renegade, or Needs Merge. Is it possible that you had a file with an Unknown status and didn't notice it?
If you can reliably reproduce this on checkin, can you send the exact steps (and the file status) for each one, so I can try to reproduce this here?
Thanks,
If you can reliably reproduce this on checkin, can you send the exact steps (and the file status) for each one, so I can try to reproduce this here?
Thanks,