Vault 3.52
our database server failed mid-day. we restored to a new server from the previous nights backup. Everything appears to be working OK.
What, if anything, do I need to have my client users do to their local systems? do they need to clear any client cache or anything, given that they may have "newer" versions of the files locally than what exists in the restored repository, since a few hours of work were lost?
please advise with links/procedures.
thanks!!!
question, post-restore operations
Moderator: SourceGear
Since there is a difference between the two, your users need to know that the things they have checked out are not currently checked out, and the items that were checked out at the time of that backup are.
If your users have changes, just to be on the safe side they can make a copy of their working folder and keep it off to the side.
Their baselines and other cache information will definitely be wrong. Information on what is stored in the cache can be found here: Client Side Cache. They will need to clear their cache. They can either just grab the entire vault_1 folder in their cache and delete it, or they can go through the folders in it and remove everything except CacheMember_WorkingFolderAssignments (that is their working folder settings).
After that, they can just perform a Get Latest using either the automatic merge or merge later option (don't overwrite) and check in items that are changed.
If one isn't using IDE integration, then an easy way to see what files on disk need to be updated in Vault, is to set Vault to CVS mode (Tools - Options - Concurrent Development) and then files that are different will show as edited and one can just check them all in.
If your users have changes, just to be on the safe side they can make a copy of their working folder and keep it off to the side.
Their baselines and other cache information will definitely be wrong. Information on what is stored in the cache can be found here: Client Side Cache. They will need to clear their cache. They can either just grab the entire vault_1 folder in their cache and delete it, or they can go through the folders in it and remove everything except CacheMember_WorkingFolderAssignments (that is their working folder settings).
After that, they can just perform a Get Latest using either the automatic merge or merge later option (don't overwrite) and check in items that are changed.
If one isn't using IDE integration, then an easy way to see what files on disk need to be updated in Vault, is to set Vault to CVS mode (Tools - Options - Concurrent Development) and then files that are different will show as edited and one can just check them all in.