Running Patrick's script this morning, manually, I never saw anything like this before:
- Code: Select all
gpes3e-gjp4:2013-06 gjp22$ cd ~/Documents/com/github/jollyjinx/ZFS-TimeMachine/2013-06 && sudo ./zfstimemachinebackup.perl --sourcedataset=zhandy --destinationdataset=tall/backups/zhandy --createsnapshotonsource --recursive --verbose --snapshotstokeeponsource=48
Found Keytime: 86400 Valuetime: 300
Found Keytime: 604800 Valuetime: 3600
Found Keytime: 7776000 Valuetime: 86400
Found Keytime: 31471200 Valuetime: 604800
Found Keytime: 314712000 Valuetime: 2635200
cannot create snapshot 'zhandy@2013-11-17-054625': dataset already exists
no snapshots were created
Could not create snapshot:zhandy@2013-11-17-054625
Could not create snapshot on zhandy at ./zfstimemachinebackup.perl line 76.
gpes3e-gjp4:2013-06 gjp22$
When I listed today's snapshots of that dataset …
- Code: Select all
gpes3e-gjp4:2013-06 gjp22$ zfs list -t snapshot | grep zhandy@2013-11-17-
tall/backups/zhandy@2013-11-17-002147 8Ki - 386Gi -
tall/backups/zhandy@2013-11-17-012147 8Ki - 386Gi -
tall/backups/zhandy@2013-11-17-013823 868Ki - 386Gi -
tall/backups/zhandy@2013-11-17-021430 8Ki - 386Gi -
tall/backups/zhandy@2013-11-17-021741 0 - 386Gi -
zhandy@2013-11-17-002147 0 - 386Gi -
zhandy@2013-11-17-012147 0 - 386Gi -
zhandy@2013-11-17-013823 860Ki - 386Gi -
zhandy@2013-11-17-021430 0 - 386Gi -
zhandy@2013-11-17-021741 0 - 386Gi -
zhandy@2013-11-17-024626 0 - 386Gi -
zhandy@2013-11-17-034626 0 - 386Gi -
zhandy@2013-11-17-044625 0 - 386Gi -
zhandy@2013-11-17-054625 1.12Mi - 386Gi -
gpes3e-gjp4:2013-06 gjp22$
… the answer became clear: an automated snapshot got there first (in my case, hourly by com.getgreenbytes.zfs.autosnapshots).
Nice work by Patrick. The conflict is handled properly.