Hi all,
We have a bunch of VMs that we back up twice a day, to 2 different destinations: once to PBS and once to NFS.
I had expected the dirty-bitmap to become invalid because of the alternating backup destinations, but apparently, that's not an issue because one uses vzdump and the other PBS.
But here's my issue/conundrum: One of the VMs gets backed up a third time, to the aforementioned PBS. This backup happens several hours after the backup where all VMs get backed up to PBS. Because of this I'd expect the dirty-bitmap status to be OK, but instead it consistently reports ' dirty-bitmap status: existing bitmap was invalid and has been cleared'.
Why is this?
EDIT: never mind... I realized the answer seconds after clicking 'post', but apparently I can't delete the post.
It's because of different namespaces
We have a bunch of VMs that we back up twice a day, to 2 different destinations: once to PBS and once to NFS.
I had expected the dirty-bitmap to become invalid because of the alternating backup destinations, but apparently, that's not an issue because one uses vzdump and the other PBS.
But here's my issue/conundrum: One of the VMs gets backed up a third time, to the aforementioned PBS. This backup happens several hours after the backup where all VMs get backed up to PBS. Because of this I'd expect the dirty-bitmap status to be OK, but instead it consistently reports ' dirty-bitmap status: existing bitmap was invalid and has been cleared'.
Why is this?
EDIT: never mind... I realized the answer seconds after clicking 'post', but apparently I can't delete the post.
It's because of different namespaces
Last edited:
