Hi,
I've seen this happen a few times in our current configuration/setup.
It basically means that a volume contains two backups that are required
to create the new Full. For example, depending on the specifics of your
configuration, there is a possibility that you may get a restore
sequence like this:
Volume A - Last Full
Volume X - Differential
Volume Y - Incremental
Volume X - Incremental
It needs Volume X to get the last Differential but also the last
Incremental. Two "solutions" that don't involve configuration changes
are to either do a real Full and not a Virtual or remove the last
Incremental job and lose those most recent changes. You can always fire
off a new Incremental immediately after the Virtual Full finishes and
that will capture those changes.
cheers,
--tom
Hello,
Does anyone know what the error “Fatal error: Found a
volume cycle in the bootstrap, Virtual Full is not possible on this
Job” means?
Thanks,
Michel
Michel Figgins
IT Support
Atlas Transfer & Storage
858.344.0027
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
