EWWW!
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Kelly
J. Lipp
Sent: Friday, September 17, 2010 11:38 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Validate backup and archives.
Fertilized by Microsoft...
Kelly J.
Fertilized by Microsoft...
Kelly J. Lipp
Cuerno Verde Consulting, Inc.
O: 719-531-5574 C: 719-238-5239
kellyjl...@yahoo.com
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Prather, Wanda
Sent: Friday, September 17, 2010 8:53 AM
To: ADSM-L@VM.MA
- *"Rogue" servers never got registered to TSM*
- Gartner says this problem has escalated lately with VMware machines
popping up everywhere.
I'm convinced they breed, at night, when no one's minding themzillions
and zillions
Be aware that there are many reasons why you won't be able to restore, even
if the backup DID work successfully. For example:
**
**
- *Tapes are damaged or unavailable*
- It's easy to damage tapes when you transport them to your off-site DR
tests.
**
- Critical files are exclude
In general computing you will want to have your production data center with
all your production servers and your remote site data center functioning as
your production fix / test / development / disaster recovery data center.
Wise processing practice is to perform monthly production fix refreshes f
The client log from the operation is your receipt and evidence of the data
transfer.
Should you wish to verify it, you can perform queries from the client.
The ultimate verification is a restoral, which you can perform to temp space.
Richard Sims
