- Joined
- Jul 3, 2015
- Messages
- 926
Hi All,
Historically when using replication if you either on purpose or mistakenly deleted a dataset on your primary systems when replication next ran it would delete the dataset on the secondary system. I was never a big fan of this and would have liked to have to actually delete the dataset on the secondary myself just incase it was a mistake. I know you can tell the primary to never delete snapshots but then you end up will millions so not ideal either.
Anyway it appears the behaviour is different and rather strange in TN13. If indeed you delete a dataset on the primary system the next time replication runs its appears to delete all but the most recent snapshot leaving the dataset in-place. At first I thought this was brilliant and exactly the behaviour I wanted however although the dataset is indeed there you can't access it. You can't cd to it on the server, you can't mount it but if you do zfs list its there and consuming disk space. I've even tried to clone the dataset and promote but still can get access to the data. So how would you actually get this data back if deleting the dataset on the primary was a mistake?
Not sure if this is a bug or I'm missing something but I would really appreciate your thoughts if any of you have any experience with this.
Thanks
Historically when using replication if you either on purpose or mistakenly deleted a dataset on your primary systems when replication next ran it would delete the dataset on the secondary system. I was never a big fan of this and would have liked to have to actually delete the dataset on the secondary myself just incase it was a mistake. I know you can tell the primary to never delete snapshots but then you end up will millions so not ideal either.
Anyway it appears the behaviour is different and rather strange in TN13. If indeed you delete a dataset on the primary system the next time replication runs its appears to delete all but the most recent snapshot leaving the dataset in-place. At first I thought this was brilliant and exactly the behaviour I wanted however although the dataset is indeed there you can't access it. You can't cd to it on the server, you can't mount it but if you do zfs list its there and consuming disk space. I've even tried to clone the dataset and promote but still can get access to the data. So how would you actually get this data back if deleting the dataset on the primary was a mistake?
Not sure if this is a bug or I'm missing something but I would really appreciate your thoughts if any of you have any experience with this.
Thanks