shnurov
Explorer
- Joined
- Jul 22, 2015
- Messages
- 74
I currently have 2 servers replicating to each other - one issue I had was a lack of drives so here's what I'm trying to solve.
at work
6tb dataset (3.77tb used) - video. Replicated to 8tb drive called remote2
5tb dataset (1.46tb used) - archive-one. Replicated to 8tb drive called remote2
at home
3tb dataset (1.32tb used) - home. Replicated to 5tb dataset - the same one that hosts the dataset archive-one
So far it's not an issue, but I am foreseeing one coming by the end of the year and would like to solve it while I have time.
I want to add a 3tb drive to the 'work' server and have my home dataset be replicated directly there.
I also want to add a 4tb drive (already own it) to the 'home' server and have the archive-one dataset replicate there.
One thing I want to avoid is to have to resent EVERYTHING through WAN.
A quick calculation/previous attempts gives me: 35mbps upload = +/- 200gb/day... => 7-8 days of 100% saturation on the upload is not something I'm looking forward to.
Can I 'copy' the snapshots from one vdev to another and then repoint the replication to the new drive and it'll simply sync up? I did that already to move a dataset on the same server, but it wasn't a replication 'target'.
at work
6tb dataset (3.77tb used) - video. Replicated to 8tb drive called remote2
5tb dataset (1.46tb used) - archive-one. Replicated to 8tb drive called remote2
at home
3tb dataset (1.32tb used) - home. Replicated to 5tb dataset - the same one that hosts the dataset archive-one
So far it's not an issue, but I am foreseeing one coming by the end of the year and would like to solve it while I have time.
I want to add a 3tb drive to the 'work' server and have my home dataset be replicated directly there.
I also want to add a 4tb drive (already own it) to the 'home' server and have the archive-one dataset replicate there.
One thing I want to avoid is to have to resent EVERYTHING through WAN.
A quick calculation/previous attempts gives me: 35mbps upload = +/- 200gb/day... => 7-8 days of 100% saturation on the upload is not something I'm looking forward to.
Can I 'copy' the snapshots from one vdev to another and then repoint the replication to the new drive and it'll simply sync up? I did that already to move a dataset on the same server, but it wasn't a replication 'target'.