ShadowFolder debugging Guidelines

[Bill Bell]

We have recently implemented Vault 2.0.3 25 User License. A big factor in us purchasing Vault was the shadow folders. We have a web system which allows developers in Vault to make changes to development and test environments, our production control team make changes to QA and Production both groups rely on the use off Shadow Folders.

All was looking good until I got this request.

Opened by Martin Cxxxxxx 27/07/2004 (Today) 3:23 PM

23/7/04
23/7/04
Created new directories in Vault
Changes not reflected in TIMS_DEV

These directories were under the root shadow directory. TIMS_Dev is the file system that the shadow folder points to.

BreakOutCHARTTRAN.xls as group events
GGExpense.xls
TIMS_report_template_non batch_script.xls changes made it to the file system.

TIMS_report_template_non_batch_script.xls changes not reflected in TIMS_DEV file system.
The other changes checked in at the same seem to have taken though

Looks like some files were written to the file system and some were missed.

---------------------------------------------

Now I have looked up the shadow folder log, sgvault.log and web.config. I tried to attach them but the bbs software kept on saying there was an error uploading the txt file so have mailed it to support. The user within the shadowfolder web.config is an administrator in the domain of which the machine is part of. The machine is Windows 2000 Server.

My question is, does the product have logging that will tell me what files have been checked in, checked out and more importantly tell me that a file has been written to a shadow folder. i.e How do I prove that there is no problem with your product?

Regards,

Bill Bell
Department of Treasury & Finance
Western Australia

[jclausius]

My question is, does the product have logging that will tell me what files have been checked in, checked out and more importantly tell me that a file has been written to a shadow folder. i.e How do I prove that there is no problem with your product?

Bill:

The current version of Vault's Shadow Folders is lacking in this area.

We are currently working on improving the logging capability for Shadows in the Vault 2.0.5, which should be released in the very, very (very) near future.