Forum Discussion

CadenL's avatar
CadenL
Level 6
8 years ago

Quick way to populate vault cache?

Hi

Is there any quick ways to populate a users vault cache without having to synch over the network?

We have a single remote user with a very large archive that we want to enable for vault cache. The user is 'very' remote and can't get a fast link onto network so synching the vault cache over the slow link is simply not working. It's also not really an option for them to post their laptop to the office.

Can anything be done to export their archive to PST, send them the PST and somehow get the vault cache created using the PST file?

I think once the initial synch is done, we can use preemptive caching from their OST to keep the vault cache updated from then on.

cheers 

5 Replies

  • CadenL's avatar
    CadenL
    Level 6
    8 years ago

    Would it perhaps be an option to create their vault cache on a local system in the office and then copy the vault cache files to a USB stick to send to them. They can then copy the contents of the USB to the correct vault cache location on their laptop?

    • VirgilDobos's avatar
      VirgilDobos
      Moderator
      8 years ago

      Hi mate, I'm afraid that may not be possible. You can modify the default location of the Vault Cache both centrally from the EV server and on a per-user basis via the registry. See this article: https://www.veritas.com/support/en_US/article.100017134

      However, the Vault Cache must be completely rebuilt as changing the registry value does not affect any existing instance of the cache.

      One instance when the cache is not sent over the network is when doing PST migrations using the client-driven method. In that case, the data is first added to the local cache then sent over the network to the EV server.

      • CadenL's avatar
        CadenL
        Level 6
        8 years ago

        Hmmm ok - thanks

        I didn't think it would be a straight forward process. We wouldn't actually be changing the location of the offline vault and the cache header information synch's ok - it's just the content that takes too long...so I was hoping just to be able to physcially copy the files from a locally created vault cache (or the specific user) from the vault cache locaton. I'm not sure what else (outside of these files) vault cache needs to be able to open an item?

        I actually thought I read somewhere ages ago that vault cache is nothing more than a pst file anyway.

        But what you say about the PST file migration may be worth persuing. I could potentially export the users archive to PST, send it to them, ask them to do a client driven migration (without creating shortcuts) and isn't there an option to get rid of any duplicate items from within the archive that the PST migration would create?