Hello,
we have as of now daily incremental to disk and a weekly disaster backup to tape for about 20 machines with some 2TB of data. The backup to disk does one weekly full as basis and daily incrementals for the rest of the week, the disaster tape backup runs on weekend. We now like to replace the disaster to tape backup by virtual full backups derived from the disk backups. Therefore we need to know the following:
1.) What should we set as FileSet in the virtual? Does it need to be the same as in the original backup or does it matter at all?
2.) What concurrency do we get if multiple virtual fulls are started concurrently? As of now we do data spooling with all jobs running concurrently, but i suspect for virtual full to tape the jobs will be running one by one, no?
3.) Is it possible to run another backup to disk (one pool) while the virtual fulls are still running?
4.) Is a virtual full a fully usable independant backup or are there any special considerations like for migration/copy jobs?
Any other hints and tweaks are also welcome, because documentation about virtual full is somewhat short.
Thanks Andreas
smime.p7s
Description: S/MIME Cryptographic Signature
