qqBazz
Dabbler
- Joined
- Nov 5, 2015
- Messages
- 34
I've got a ~550GB snapshot that I'm attempting to replicate offsite for the first time, and finding that when the job gets interrupted, all progress gets erased and requires restarting. In the last two weeks, I haven't managed to get the whole thing sent, and the multiple daily restarts are getting old. Once I get through this initial replication, the daily recurring delta on this dataset is a totally doable 40-50 MB... but I've got to get the initial snapshot completed, first.
Sending a bunch of files via rsync has always been much more resilient, in my experience, because even interrupted jobs can basically just resume once the network returns. Is there any way that I can do an initial in some way that'll be able to resume rather than restart?
After doing a little bit of research, I am seeing that perhaps this is coming down the pike in version 10, so ... maybe I just need to be patient, or else do the initial send myself, via the commandline, using the zfs resume options.
As a very last ditch effort, I guess I could buy a hard drive locally, do the initial replication, and then mail it to my destination like some kind of Neanderthal.
Sending a bunch of files via rsync has always been much more resilient, in my experience, because even interrupted jobs can basically just resume once the network returns. Is there any way that I can do an initial
Code:
zfs send
After doing a little bit of research, I am seeing that perhaps this is coming down the pike in version 10, so ... maybe I just need to be patient, or else do the initial send myself, via the commandline, using the zfs resume options.
As a very last ditch effort, I guess I could buy a hard drive locally, do the initial replication, and then mail it to my destination like some kind of Neanderthal.