Am 25.04.2020 um 20:54 schrieb Till Wegmüller:
Hi Oliver
I did some tests. Refquota does what it says in the docs but it simply
is not usable for replication. Which is not stated in the documentation
at all. I'll have a look with the devs if we want to add a note about
that. -x on the receive side did not work also, as the property might be
present otherwise. The only way I got a dataset with refquota to send
properly was without -p on the send side.
Hope this helps
Greetings
Till
On 23.04.20 21:07, Oliver Weinmann via illumos-discuss wrote:
Hi Till,
Thanks a lot for your good explanation. It is really confusing as in the manual
it states that refquota doesn’t take descendants or snaps into account. I might
play around with bookmarks later. For now I guess I can use:
zfs receive -x refquota to exclude the property?
How about I have started to recursively replicate a dataset and it failed on
one of the child datasets due to the refquota issue. Can I somehow resume the
replication of the parent dataset or do I have to replicate the child dataset
first using incremental snapshots?
Normally I only use the built in auto sync feature on our nexenta storage, but
this time I have to sync back the data Manually to the nexenta system.
Cheers,
Oliver
Von meinem iPhone gesendet
Am 23.04.2020 um 18:04 schrieb Till Wegmüller <[email protected]>:
Hi Oliver
This is a usage issue with the zfs commands. Every snapshot also counts
towards the quota. You may want to switch up and use bookmarks instead
of snapshots as send sources. If you are changing the Refquota on a
regular basis you will need to update both ends or use zfs send -p to
copy all properties as well before the snapshots on the source get too
huge again so you cannot send them any more. Another approach is not to
save the properties at all and have no quota on the backup servers. You
will need another script or config management to reapply the quota in
case of a full restore but that would stop you getting this error.
Hope this helps you get your backup process more streamlined
If you still need help let me know.
Greetings
Till
On 23.04.20 16:29, oliver.weinmann via illumos-discuss wrote:
Hi folks,
I'm currently trying to zfs send/recv using netcat between omnios
(sender) and nexenta (receiver). I usually get this error:
cannot receive incremental stream: destination
The source datasets have a refquota applied. I googled for the error but
it seems that there is no fix available yet?
Due to this i'm not able to complete the zfs send / recv. I always have
to adjust the refquota on src and dest in order to proceed. Which is
really annoying as there are huge amount of data that have to be copied. :(
Best Regards,
Oliver
*illumos <https://illumos.topicbox.com/latest>* / illumos-discuss / see
discussions <https://illumos.topicbox.com/groups/discuss> + participants
<https://illumos.topicbox.com/groups/discuss/members> + delivery options
<https://illumos.topicbox.com/groups/discuss/subscription> Permalink
<https://illumos.topicbox.com/groups/discuss/Tf2a07b0ee742a206-M6353a2efec2ba914bde49531>
------------------------------------------
illumos: illumos-discuss
Permalink:
https://illumos.topicbox.com/groups/discuss/Tf2a07b0ee742a206-Md32f5c6951064ba0a8c2d827
Delivery options: https://illumos.topicbox.com/groups/discuss/subscription
Hi Till,
thanks a lot for the testing. I can confirm that -x refquota on the
receiving side solves the problem and yes sening a child dataset
incremental also works. Unfortunately I can't modify this on nexenta and
so most of the auto-sync jobs get stuck. I have to run the job, wait for
it to get stuck, remove the dataset on the destination and repliate it
using netcat:
On the receiving side (Nexenta) I ran the following inside of a screen:
screen -mS recv
|nc -w ||120| |-l -p ||8023| || zfs receive -ev -x sharenfs -x
mountpoint -x sharesmb -x refquota infiniflash1/netshares/Projects|
On the sending side (omnios):
|zfs send -Rp
hgst4u60/infiniflash1/ProjectsYZ||@AutoSync||-0_2020-||04||-||03||-||23||-||45||-||05|
|| nc -w ||20| |nexenta-server-vip ||8023|
|I have a case open with Nexenta regarding the issue.|
|Best Regards,|
|Oliver
------------------------------------------
illumos: illumos-discuss
Permalink:
https://illumos.topicbox.com/groups/discuss/Tf2a07b0ee742a206-M4881a8eabc7987bbce774371
Delivery options: https://illumos.topicbox.com/groups/discuss/subscription
