Insufficient data.
You don't say anything about off-site storage or DR requirements. I
assume there must be RPOs and RTOs. Are these the same for all clients
and all sites? Or are some animals more equal than others?
You also don't say anything about the distribution of the client
systems, other than the aggregate size and they're all over the globe.
How many sites are there? Are all the clients concentrated in a few
major data centers? Or is there a mix of major data centers, server
rooms of various sizes and some teeny tiny remote offices?
How are the various sites staffed? Are there technicians on-site 24x7?
8x5? On call? Or are your "remote eyes and hands" the secretary with the
least seniority? What happens when the secretary is out ill or on
vacation?
All of these factors -- and probably numerous others that just don't
come to mind instantly -- will figure into the design of the backup
approach.
Good luck, Eddie!
"We now return control of your backup environment to you, until next
week at this same time when the Control voice will take you to ... The
Outer Limits."
Conrad Macina
Pfizer, Inc.
-----Original Message-----
From: Albert, Eddie - JACKSONVIL FL
[mailto:eddie.albert AT BANKOFAMERICA DOT COM]
Sent: Tuesday, March 29, 2011 8:35 PM
Subject: Big Design concepts for fun and discussion?
This is intended to be a fun exercise to discuss new technology and
software, if you do not want to play... then don't. /grin
You unlock this design with the key of imagination. Beyond it is another
design - a design of speed, a design of reliability, a design of mind.
You're moving into a LAN of both shadow and substance, of things and
ideas. You've just crossed over into the Data Protection Zone... There
is a fifth dimension beyond that which is known to man. It is a
dimension as vast as space and as timeless as infinity. It is the middle
ground between light and shadow, between science and superstition, and
it lies between the pit of man's tape silo and the summit of his virtual
tape. This is the dimension of imagination. It is an area which we call
the Data Protection Zone.
Imagine if you will, Eddie has just hit the big job lottery. His
assignment... he has just inherited an environment where you receive a
mulligan a do over and are starting over from SCRATCH. You have no old
hardware to concern yourself with, no software base... you may buy
whatever is needed, but he is still required to spend this money as if
it belonged to stock holders... so we need to be practical.
For this exercise we are purposely using round numbers; you need to
backup 25,000 client servers, there is a mix of Solaris, Linux (many
versions), Windows (many versions)... You will be backing up on an
average 4 Petabytes per month. With a weekly average between 1 & 2
Petabytes. The locations are multiple dedicated data centers AROUND THE
WORLD in various countries. The data is private and must remain
protected at all times (read that as encrypted) and while being stored.
You must have 10 year, 5 year, 1 year, 60 day & 30 day pools. Keep in
mind, you want to have WORLD CLASS SLAs in place. As close to 99.999%
backup success rate as possible with backups completing as fast as
possible, but more important... is the restore speed.
Again you are starting from scratch, you want the best of everything,
while NOT spending foolishly. How do you proceed?
Semper fidelis, /ALE
----------------------------------------------------------------------
This message w/attachments (message) is intended solely for the use of
the intended recipient(s) and may contain information that is
privileged, confidential or proprietary. If you are not an intended
recipient, please notify the sender, and then please delete and destroy
all copies and attachments, and be advised that any review or
dissemination of, or the taking of any action in reliance on, the
information contained in or attached to this message is prohibited.
Unless specifically indicated, this message is not an offer to sell or a
solicitation of any investment products or other financial product or
service, an official confirmation of any transaction, or an official
statement of Sender. Subject to applicable law, Sender may intercept,
monitor, review and retain e-communications (EC) traveling through its
networks/systems and may produce any such EC to regulators, law
enforcement, in litigation and as required by law.
The laws of the country of each sender/recipient may impact the handling
of EC, and EC may be archived, supervised and produced in countries
other than the country in which you are located. This message cannot be
guaranteed to be secure or free of errors or viruses.
References to "Sender" are references to any subsidiary of Bank of
America Corporation. Securities and Insurance Products: * Are Not FDIC
Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank
Deposit * Are Not a Condition to Any Banking Service or Activity * Are
Not Insured by Any Federal Government Agency. Attachments that are part
of this EC may have additional important disclosures and disclaimers,
which you should read. This message is subject to terms available at the
following link:
http://www.bankofamerica.com/emaildisclaimer. By messaging with Sender
you consent to the foregoing.
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
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
|
