Hi
I'm after a bit of advice from anyone doing this in the real world.
Sorry if this gets long...
We are about to implement a Data Domain setup at each of our 4 sites for
backup/DR purposes.
3 of the DataDomains will replicate their data to our central site, and the
central site will replicate its data (just that sites backup data) to one of
the other sites. So, we have 2 copies of each sites data (one local, one
remote).
We aim to keep 3 months backups on line on each Data Domain system.
Partly (I think) due to perhaps an 'old way of thinking' - ie tape gives a warm
friendly feeling that it's safe ;-) but mainly because management would like
the ability to go back up to 12 months - for example someone can come along and
say that file I had 9 months ago - I'd like it back! (we're partly to blame for
this as we do take monthly snapshot backups to tape which are stored for 12
months, and while this facility has been used a handful of times - it has been
very much appreciated when it's been called on). There's been a bit of a
blurring of backups for DR and an archive system I fear!
So, the problem - I'm at a remote site and I need some file(s) back from up to
12 months ago.
We were intially thinking that at the central site, we would clone to tape and
store these off-site. To do this, we'd need a client licence for each client
at each site on this central system I believe?
What concerns me more is the logistics of getting this data back.
As I see it, we're going to have to set aside a heck of a lot of space on the
DD to leave in reserve so that we can get back the largest saveset, and
correspondingly we'd need to do the same at each of the remote sites to get
their largest saveset replicated back up to the site in question. Would that be
correct? or is there some way we can do that at the central site, bearing in
mind we need to retain all ownership/permissions on these files.
Would implementing the backup servers at each remote site as storage nodes help
in any way? We've never used storage nodes so I don't know what added
functionality they may give us (over the fact that backups would be controlled
centrally).
We're open to any / all suggestions, but I don't think 'buy a proper archive
system' is an option I'm afraid.
Thanks for reading... Allan.
--
This message (and any attachments) is for the recipient only. NERC
is subject to the Freedom of Information Act 2000 and the contents
of this email and any reply you make may be disclosed by NERC unless
it is exempt from release under the Act. Any material supplied to
NERC may be stored in an electronic records management system.
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|
