Backups network crunch

[nthnu]

We have Backup Exec 2010 R3. Our server uses dedupe and the dedupe folder is on a network storage device. We also duplicate the backups to external USB drives which are connected to the network storage device. Obviously dedupe dehydrates the data to the dedupe folder, then rehydrates to send to USB over the network. The total storage data sent and space used on the USB drive is 2TB. The backup jobs take almost a week from start to finish.

I'd like to do backups directly to the network storage device, then duplicated to the USB. No deduplication. This should be able to relieve our network, and the jobs should run faster over our network.

[pkh]

Sounds like a plan, go ahead

[CraigV]

...you're talking about doing away with the dedupe option and moving to a normal B2D?

Why not look at a NAS to duplicate too? Better than a USB and will hold more backups (depending on the size) allowing you to retain more information in a secondary location?

Thanks!

[nthnu]

Yes.

We'd use the network storage device (NAS) to backup to. Then duplicate the jobs to the USB for offsite storage.

We could backup to the NAS, and let the NAS duplicate the backups to USB. (is this what you're meaning?)

[CraigV · Accepted solution]

Backup Exec backs up to the NAS, and then duplicates to the USB drive...don't let the NAS do this, add a stage in to BE.

If you do a file-level copy from the NAS, then BE isn't aware of the data sitting on the USB drive and this will render that information irrecoverable. Allowing BE ti duplicate from the NAS to the USB drive keeps the catalogs intact, and if needed, you'll be able to restore from the USB drive.

Thanks!

[nthnu]

Ok, will give that a go. Thanks :)

[CraigV]

Sure thing!