stefanb
Patron
- Joined
- Dec 12, 2014
- Messages
- 200
hi,
I configured several replication tasks to backup my datasets on a second freenas system.
Yesterday I killed the replication :(
I identified that one user made tons of backups on the mail freenas system - about 1TB of personal data.
So, I have to remove these files from main and from replica freenas. Because snapshots are only used for replication issues, I did the following:
I destroyed all snapshots on push and pull, then I removed the files from both systems.
Then I enabled the snapshot and replication tasks again.
On pull, snapshots are created, but not sent to push. I receive no error messages:
The push system is FreeNAS-9.3-STABLE-201501090144
and the pull is also FreeNAS-9.3-STABLE-201501090144
Whats going on there? Why there is no send command and is it normal that each snapshot gets a hold?
Regards
Stefan
I configured several replication tasks to backup my datasets on a second freenas system.
Yesterday I killed the replication :(
I identified that one user made tons of backups on the mail freenas system - about 1TB of personal data.
So, I have to remove these files from main and from replica freenas. Because snapshots are only used for replication issues, I did the following:
I destroyed all snapshots on push and pull, then I removed the files from both systems.
Then I enabled the snapshot and replication tasks again.
On pull, snapshots are created, but not sent to push. I receive no error messages:
Code:
Jan 20 11:52:02 filer autosnap.py: [tools.autosnap:58] Popen()ing: /sbin/zfs snapshot -o freenas:state=NEW raid/orga@auto-20150120.1152-2d Jan 20 11:52:03 filer autosnap.py: [tools.autosnap:58] Popen()ing: /sbin/zfs hold freenas:repl raid/orga@auto-20150120.1152-2d
The push system is FreeNAS-9.3-STABLE-201501090144
and the pull is also FreeNAS-9.3-STABLE-201501090144
Whats going on there? Why there is no send command and is it normal that each snapshot gets a hold?
Regards
Stefan
Last edited: