Shadow Folder

[Busboy]

Hi,
I'm using Vault 3.0.1 on a Windows 2003 server (member of a domain). I know there are some topics in this forum regarding shadow folders on “remote” computers (not the same computer as the Vault server). I’m trying to use shadow folders on the same computer as the Vault server.

The “C:\Inetpub\wwwroot\VaultService\bin\vaultlib.dll” was missing so I copied this file from “C:\Program Files\SourceGear\Admin Tool\” I’m able to set up everything in the Vault admin tool, but none of my files are copied to the shadow folder. The folder remains empty.

Are there any special user accesses to the local files that I must specify? If so: who is the user, and what access is needed?

[czacharias.logisoft]

I too experienced something similar in the last week, where my shadow folders appeared configured properly and some new folders had been shadowed, but they were all empty in the shadow location. However, the files finally began shadowing after a while and appeared in the previously empty folders. I wonder if you may be experiencing the same issue? For us, it appears that it simply took a long time to download and populate the shadow folders.

[lbauer]

To Busboy:

On Windows 2003, using IIS6, you still need to do additional configuration for Shadow folders, even if they are on the same machine:

http://support.sourcegear.com/viewtopic.php?t=536

[mlippert]

I was wondering how long I should expect it to take to start populating a shadow folder after it has been set up.

I think I've followed all of the steps in the various KB articles about setting up shadow folders on Windows 2003 server for a UNC path.

However, it's been a while since I added the shadow folder for the repository, and nothing is showing up in the destination.

Does something actually have to be checked in to the path in the repository being shadowed, before the initial populate process starts?

Mike

[jclausius]

Mike:

You should see something within seconds of creating the Shadow Folder association.

Let's see if logging the Shadow Folder service will gain any useful information.

Within Shadow Folder's web.config, you will see a classesToLog attribute on one of the xml elements. Add "shadowfolderdebug" to the value, so the line looks like the following:

<add key="classesToLog" value="shadowfolderdebug" />

Finally, save the file.

Now, re-try to add a small shadowed folder to a local drive's folder. When you have finished, you should find a VaultShadowFolderService.txt log file in either %windir%\Temp\ or if you are using identity impersonation - your Custom .Net's %TEMP%\.

Is there anything in the log file, which suggests there may be a problem?

[mlippert]

Boy do I feel foolish.
Sorry Jeff, and thanks for your help.
It turns out (and if I had checked this last night before posting, I'd feel much better!) that I shadowed the wrong project's "Trunk" folder, and the one I chose really didn't have any files in it. I noticed that today as soon as I started trying Jeff's test.

I just shadowed the correct folder, and files did start populating pretty much immediately.

Thanks again,
Mike