Automation of Import Export Tool

samward · Post by **samward** » Thu May 24, 2007 1:20 am

Hi,

I was just wondering if there was any ability to automate the execution of the import/export tool. We are planning on deploying Vault across the department, but currently some of the development is done in remote offices. So we would like for the developers to be able to use a local vault repository, and then overnight have it syncronised back to the main repository.

Cheers
Sam

lbauer · Post by **lbauer** » Thu May 24, 2007 5:49 am

I don't know of a way to automate the Export/Import Tool. The tool wasn't really designed for daily use. As your history in Vault grows, the export and import will take longer and longer, possibly several hours, as it must re-create the entire transaction history of the folder or folders being exported.

You say you have users working remotely--Vault was designed with the remote users in mind. Vault should be as effective for remote users as for users on the LAN. A better solution would be to have all users connected directly to your central Vault repositories.

Vault supports folder and repository security, so you can limit access only to those areas where you want users to work.

samward · Post by **samward** » Tue May 29, 2007 1:21 am

Thankyou for the prompt response.

The biggest problem our remote users face is the almost 500ms latency between them and us. Based on previous testing this takes quite a hit on the peformance of Vault (or anything else for the matter).

Given we were only really interested in having a readonly copy in the main office, we were trying to take the burden of the link off the end users. But maybe they will just have to work with it.

Cheers
Sam

Post by **jclausius** » Fri Jun 01, 2007 1:59 pm

Sam:

As of Vault 3.5.2, you can configure a client side option to eliminate some of the round trips between client and server.

You may want to just try it out to see if performance is acceptable.