Dwarf Cavendish
Contributor
- Joined
- Dec 19, 2017
- Messages
- 121
Recently I tried making a back-up of my entire pool to an USB hard drive. What I used as a source of reference: this and this. I configured a weekly periodic snapshot that I want to use for incremental backups. These are recursive snapshots of my entire pool. The command that I ended up using for the initial backup:
And for subsequent incremental backups:
It all seemed pretty straight forward. However, when I attempted to do the first incremental backup I was surprised to get a message that my usbpool had changed since the last snapshot and hence the incremental backup could not be executed.
There is one thing that I remember doing that might be responsible for this: I have a cron job for executing cloud backups from an iocage jail. When that cron job triggered iocage told me that it had multiple active pools and didn't know what to do. In response to that I set my actual pool as active in iocage.
Now I want to try this all again from the start and avoid doing anything with iocage until the transfer has been completed. However, I am concerned that there may be other processes on my server that get confused by the presence of two identical pools. I can for example imagine that having two .system datasets during the time that the drive is plugged in is not exactly a great idea.
So basically my question is: is this a viable approach that I just messed up by setting the active pool for iocage or should I expect other things to get hairy when I attempt to do this again?
zfs send -R mypool@snapshot1 | zfs recv -F usbpool
And for subsequent incremental backups:
zfs send -R -i snapshot1 mypool@snapshot2 | zfs recv usbpool
It all seemed pretty straight forward. However, when I attempted to do the first incremental backup I was surprised to get a message that my usbpool had changed since the last snapshot and hence the incremental backup could not be executed.
There is one thing that I remember doing that might be responsible for this: I have a cron job for executing cloud backups from an iocage jail. When that cron job triggered iocage told me that it had multiple active pools and didn't know what to do. In response to that I set my actual pool as active in iocage.
Now I want to try this all again from the start and avoid doing anything with iocage until the transfer has been completed. However, I am concerned that there may be other processes on my server that get confused by the presence of two identical pools. I can for example imagine that having two .system datasets during the time that the drive is plugged in is not exactly a great idea.
So basically my question is: is this a viable approach that I just messed up by setting the active pool for iocage or should I expect other things to get hairy when I attempt to do this again?