In version 5 the process was very simple: create your replication at the remote site to local storage (UBS drive) then physically take to DC, copy the data to the correct datastore and then kick off the replication job again. This worked ok, and we saw throughput of around 10MB/s over our VPN's T1 connection.
With version 6 I have been seeing very slow initial seeding throughput of around 140Kb/s which is around the speed of the T1.
I have configured it per another post:
I know that the initial seeding will take longer but once it's done the actual replication job will speed up.1. Configure a backup job for the VM you want to perform initial seeding for.
2. Create and choose any local repository for the backup files.
3. Once you have backup files created, move them to a DR site and place them on the DR site repository (you should create it beforehand).
4. Scan DR site repository to populate backup files in the backup console.
5. After that just create a replication job with "Low connection bandwidth" checkbox enabled.
6. On the "Seeding" step of the replication job wizard specify DR site repository where you've placed VM backup files.
7. Finish configuration of replication job wizard and start replication job.
I have talked to tech-support. They confirmed that I had the job setup correctly and that this is normal for seeding under version 6 and could take days.
At this rate it will take me about 9 days to get my initial seed, which is about 150GB of data. Just not acceptable
Has anyone else seen these kind of results?