Large Database workflow long backup times

[Anonymous]

Listerning to an AU lecture suggested a workflow of creating a new vault for every year.

I'm thinking:

With a database taking 10 hrs to backup would splitting the vault up into two - i.e one as an archive for jobs over 3 years old & a current working vault be an advantage?

Would the backup then only need to read the current vault & ignore the archive?

Thanks

MES

[paul.gunn]

Hi Mark,

An incremental backup would ignore the vault [assuming no changes have been made to it]. A full backup however would include all vaults.

It is possible to work around this though, if you were to detach the 'archive' vault prior to doing the backup. Detached vaults are ignored.

Paul

[ihayesjr]

Have you tried this:

http://crackingthevault.typepad.com/crackingthevault/2011/05/improving-performance-of-vault-server-b...