My rsync task runs on my Backup volume each night to another freenas server over SSH. The Backup volume is encrypted.
A few days ago the source server had a panic, I think because of a large CIFS transfer (9.2.1). This rebooted the server and locked the Backup volume. It took me a couple of days to notice this.
When I did I unlocked the volume in question and upgraded to 9.2.1.1 and the day after than noticed a huge amount of activity.
Upon investigation I found rsysnc replicating my entire Backup volume again to the remote freenas server.
Did rsync replicate when the volume was locked and wipe the remote copy? Should it have done that? I would have thought the mount path would be unavailable and it would simply fail?
A few days ago the source server had a panic, I think because of a large CIFS transfer (9.2.1). This rebooted the server and locked the Backup volume. It took me a couple of days to notice this.
When I did I unlocked the volume in question and upgraded to 9.2.1.1 and the day after than noticed a huge amount of activity.
Upon investigation I found rsysnc replicating my entire Backup volume again to the remote freenas server.
Did rsync replicate when the volume was locked and wipe the remote copy? Should it have done that? I would have thought the mount path would be unavailable and it would simply fail?