A colleague asked me to post some more information about VCView, so here goes !
The first thing this is that you access this as the user you’re working with/on. It’s used primarily to see Vault Cache builds, downloads in progress and completed downloads for a user in Vault Cache “distress”. However, you *can* run the web page as the Vault Service Account, for example on the Enterprise Vault Server. If you do that you’ll see activity from ALL users.
Here is a screenshot showing the first DB file for my production account being built :
When the build is completed it will go to :
The interesting part of this is in the parameters section at the right hand side. Here you can see :
* The number of items
* The size (in bytes) of the .DB file
* The Archive ID where the download is from
* The DBID (which is stored in the databaselist.ini on the client machine)
* A “more” flag, to indicate whether there is another DB file to follow this one (for example if you have more than about 500 Mb in one quarter you’ll get another DB file which will belong to the same quarter).
Shortly after the job completes, the client (which is polling periodically) will start to download the .DB file using BITS, and the job will move to Current Active Downloads :
At this point the client will see the BITS temporary file increase in size to match the DB file size, and the download will begin. In addition, if you look at the Vault Cache status dialog on the client, it will show the Content Cache as Synchronising.
At a high level that’s what VCView will show you, and it can assist an administrator who is trying to troubleshoot Vault Cache issues on a users workstation.