On Thu, 6 Jan 2011 14:20:23 +0100
Uwe Schuerkamp uwe.schuerk...@nionex.net wrote:
You can simply set the archived volumes to status archive (update
voluume in bconsole).
Excuse me for jumping a bit late into the thread, but we're back to
Bacula after using Amanda for some time...
Our use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thomas Mueller wrote:
Am Thu, 06 Jan 2011 13:48:40 -0300 schrieb Kleber Leal:
I do it at last 31th december.
I created a Full backup (VirtualFull) to a tape and purged the volume.
But, you should not to do differential ou incremental backups
Once a year, I need to create a full backup that will be stored
off-site. This backup will not be readily available for normal
restores. The obvious approach would be to delete that backup (and
its volumes) from the catalog so they will not be considered when
performing future
From what I've read, that means the volumes will not be recycled. But
will they still be considered as the base from which an inc/diff
backup can be built?
That is why you need a separate job with the same fileset.
John
On Wed, Jan 05, 2011 at 11:06:52AM -0600, Ben Beuchler wrote:
Once a year, I need to create a full backup that will be stored
off-site. This backup will not be readily available for normal
restores. The obvious approach would be to delete that backup (and
its volumes) from the catalog so
I do it at last 31th december.
I created a Full backup (VirtualFull) to a tape and purged the volume. But,
you should not to do differential ou incremental backups between you full
and purge.
You can use bscan to repopulate the catalog again if you need.
Kleber
2011/1/5 Ben Beuchler
2011/1/6 Kleber Leal kleber.l...@gmail.com:
I do it at last 31th december.
I created a Full backup (VirtualFull) to a tape and purged the volume. But,
you should not to do differential ou incremental backups between you full
and purge.
You can use bscan to repopulate the catalog again if you
Once a year, I need to create a full backup that will be stored
off-site. This backup will not be readily available for normal
restores. The obvious approach would be to delete that backup (and
its volumes) from the catalog so they will not be considered when
performing future backups/restores.
On Wed, Jan 5, 2011 at 12:06 PM, Ben Beuchler ins...@gmail.com wrote:
Once a year, I need to create a full backup that will be stored
off-site. This backup will not be readily available for normal
restores. The obvious approach would be to delete that backup (and
its volumes) from the
