Zitat von Daniel Neuberger <[email protected]>:
Ah ok. Than you should rather use copy jobs instead of virtuall full. Cause the virtuall full is "synthetic fullbackup" and the last fullback is always the reference for a restore if you not use the exact jobid. You already have fullbackup on this so copy it to tape thats easier to handle. as long as there are the original full backups on disk it will not reference to the copies on tape during a restore. So actually i do not see the advantage of virtuall full in your setup cause a copy doesnt effect the fd as well. Or is there something i miss?
As far as i remember the virtual full approach was choosen because you don't have to care about the jobids you like to copy. If for example the virtual full starts only after another incremental it doesn't care and simply include that also. Our first idea indeed was to do a virtual full with the disk Pool and a subsequent copy to tape, but with this no longer needed files deleted in the original storage are still included in the backup even when using accurate mode, no?
What would be the easiest way to copy a disk based full to tape? Can we start a job at the end of a job?
Regards Andreas
smime.p7s
Description: S/MIME Cryptographic Signature
