|
|
|
I copy from my pc to my "nas" i.e. very low spec computer with hard drives at around 800-900 Mbps basically full speed gigabit for a large file 2GB+
Something is wrong or very under powered somewhere.
Pay attention to if you are talking bit or Bytes?
CPU: AMD 5900x | RAM: GSKILL Trident Z Neo RGB F4-3600C16D-32GTZNC-32-GB | MB: Asus X570-E | GFX: EVGA FTW3 Ultra RTX 3080Ti| Monitor: LG 27GL850-B 2560x1440
Quic: https://account.quic.nz/refer/473833 R473833EQKIBX
mentalinc:
I copy from my pc to my "nas" i.e. very low spec computer with hard drives at around 800-900 Mbps basically full speed gigabit for a large file 2GB+
Something is wrong or very under powered somewhere.
Pay attention to if you are talking bit or Bytes?
Crash plan uses Mbps which is bits isn't it?

timmmay: Is that copy direct with your operating system, or crash plan?
Crashplan

The good news is that it has finished the NAS backup overnight.
The bad news is that it has moved on to the Cloud backup and says that will take .............................. 61 days!

That's not bad actually, for a TB or two.
I also discovered something it can do called link aggregation (yes, I know you all knew that already!) so I connected two Ethernet cables to the switch and bridged them, and it now does 2gb/s for the network connection. That may help.

well your cloud backup depends on your internet connection, and in all the cloud backups ive done, ive never had one sit at more than half of the upload line speed
Geektastic:
I also discovered something it can do called link aggregation (yes, I know you all knew that already!) so I connected two Ethernet cables to the switch and bridged them, and it now does 2gb/s for the network connection. That may help.
They may help if your source can supply at 2Gbps... otherwise it will only benefit if you're using the NAS for other duties (servicing other clients) at the same time.
Assuming that your Mac is connected via Gigabit Ethernet - Bear in mind that at theoretical maximum throughput, it will take 2600 * 8 = 20800 seconds to shift 2.6TB. That's close to 6hrs.
My expectation would be that your setup should move it in more like 12hrs... (barring there being a problem (a.k.a. resource contention) with the application "pushing" out the data)
What hard drives have you got in the NAS? If it's the Seagate Archive drives they have a slower continuous write speed than your standard consumer drives.
meesham:
What hard drives have you got in the NAS? If it's the Seagate Archive drives they have a slower continuous write speed than your standard consumer drives.
They are Seagate NAS-Specific but I cannot recall exactly.
I wish they were all as fast as the SSD in my iMac which returns 1510MB/s write and 1860MB/s read....!

timmmay:
It could be the CrashPlan app that's a bit slow, it does a lot of things like versioning, compression, and maybe de-duplication.
CrashPlan also encrypts your backup.
Other factors that come into play is that CrashPlan is a JRE. Maybe look at custom start up / RAM parameters for CrashPlan and large data sets.
I have a USB 2.0 SATA drive attached to my FritzBox and and 160GB will take a total of 13hrs to copy over the 1Gbps NIC connection.
If this delay in time is unacceptable, have you considered pre-seeding the backup? Create a local backup on your PC and copy that in the fastest possible way to the NAS, then tell CrashPlan that the NAS is a secondary location. Once CrashPlan is fully sync'ed with the NAS (within minutes) delete the local backup.
Please keep this GZ community vibrant by contributing in a constructive & respectful manner.
IcI:
timmmay:
It could be the CrashPlan app that's a bit slow, it does a lot of things like versioning, compression, and maybe de-duplication.
CrashPlan also encrypts your backup.
Other factors that come into play is that CrashPlan is a JRE. Maybe look at custom start up / RAM parameters for CrashPlan and large data sets.
I have a USB 2.0 SATA drive attached to my FritzBox and and 160GB will take a total of 13hrs to copy over the 1Gbps NIC connection.
If this delay in time is unacceptable, have you considered pre-seeding the backup? Create a local backup on your PC and copy that in the fastest possible way to the NAS, then tell CrashPlan that the NAS is a secondary location. Once CrashPlan is fully sync'ed with the NAS (within minutes) delete the local backup.
CP completed the NAS backup fast enough not to be a PITA. The cloud part will be taking a very very very very long time....!
It's a shame CP is not flexible enough to allow you to schedule backups to different places at different times. It appears to only allow one set of scheduling and then tries to back up to all locations at once in that period.

Geektastic:
CP completed the NAS backup fast enough not to be a PITA. The cloud part will be taking a very very very very long time....!
It's a shame CP is not flexible enough to allow you to schedule backups to different places at different times. It appears to only allow one set of scheduling and then tries to back up to all locations at once in that period.
Make a second backup set, even if it has the same files in it and you can give it its own destination and time schedule.
I have 4TB to go to the cloud and its months and months, so I have a set for the old HDD images that I have running overnight and my stuff I care about at other times, since I have the HDD images on multiple PCs here and I think one copy offsite still.
|
|
|