07-14-2011 07:44 AM
Hi,
I will be rebuilding our existing puredisk server soon. My predecessor did not keep it up to speed and it just needs to be redone from scratch. I have 5 file servers that are remote office Windows file servers across the country. I am currently backing up these servers via robocopy to a local USB drive at each site. The average nightly change (via robocopy output) is around 100MB or so. Not much change at all. I would like to seed/stage/import this data into the new puredisk install (total data size will be around 4TB). I don't want to think about how long it would take to get all of this data via initial sync. I would much rather import 4TB and then have around 2 GB total data difference to get synced up after the initial seed/stage/import.
I have read a number of posts in the forum that talk about seeding, some say it is not possible, some say it is, some say "in theory" it should be. I have read the install manual, etc and found nothing that talks about seeding/staging/importing during or soon after the initial install. My questions to Symantec (or to a reader here who has done it) are:
Is there any documentation of a procedure that details how to seed the puredisk server via local LAN or import and then sync differences over a WAN?
Has anyone done this successfully? How did it work? Did you do it as instructed by Symantec or on your own?
Thanks,
Spencer Williams
"Never underestimate the bandwidth of a station wagon full of tapes hurtling down the highway." - Andrew S. Tanenbaum
07-18-2011 01:10 PM
Seeding data is not difficult at all, and not a special process in many cases. This applies to most all top backup apps that can leverage client-side dedupe and do hash lookups for comparisons.
PureDisk when scanning the remote clients, should compare file hashes and throw out the redundant segments.