ADSM-L

Re: [ADSM-L] Restore Testing stories

2008-12-15 10:53:26
Subject: Re: [ADSM-L] Restore Testing stories
From: Bob Levad <blevad AT WINNEBAGOIND DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 15 Dec 2008 09:49:50 -0600
Our biggest restore failure was for a small windows domain controller.  It
was not replicated and we were slightly backleveled on the client.  When the
vmware disk became corrupted, we had to rebuild the client list as we were
not able to correctly restore the active directory.  The moral is to keep
your TSM clients up to date and read the release notes on what the product
will NOT do.  Another good practice is to back things up in more than one
way.  Then, when your primary restore method fails, you will have another
option.  Don't forget to test!

Bob.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Lindsay Morris
Sent: Monday, December 15, 2008 8:57 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Restore Testing stories

Wow, good point, Andy: gotta have the same Service Pack level before trying
a bare metal restore.

But our whitepaper doesn't address that, because we don't (yet) help with
full, bare-metal DR tests.
We help with the 99% of systems you DON'T have time to do a DR test on, by
random-sampling the backed-up files and restoring one or two of them.
Glad you found it intriguing.  I don't think anybody has ever tried to do
this before.

So I continue to ask for horror stories about restores that failed, and why.
(Keep the customer anonymous, please - some stories could be
embarassing!)

Come on, folks: got more?

------
Lindsay Morris
Principal
www.tsmworks.com
919-403-8260
lindsay AT tsmworks DOT com



On Dec 12, 2008, at Dec 12, 5:53 PM, Huebner,Andy,FORT WORTH,IT wrote:

> The product looks intriguing.  The paper did not address my biggest
> problem, restoring the Windows OS.  Our issue is verifying the SP
> level of the server prior to restore.  We have had very little success
> restoring the OS if the target OS is a different SP level than the
> backup.
>
> Andy Huebner
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of lmorris99
> Sent: Friday, December 12, 2008 3:17 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: [ADSM-L] Restore Testing stories
>
> Would you be so kind as to share your stories about why restores fail,
> when they do?
>
> We are working on a way to prevent such failures.
> (Our whitepaper is at
> http://www.tsmworks.com/downloads/art-whitepaper.pdf
> , if you're curious.)
>
> Your real-world anecdotes are helpful!
> Stories like:
>
>    * "we found that the node had not been backed up in 3 months"
>    * "the user's exclude list had excluded the file he needed"
>    * "the tape volume TSM needed was missing / damaged / etc."
>
> are what we're looking for. Got some?
>
> Respond here, mail me, call me - all good.
> Thanks!
> -----------
> Lindsay Morris
> Principal
> TSMworks, Inc.
> lindsay AT tsmworks DOT com
> 919-403-8260
>
> +
> ----------------------------------------------------------------------
> |This was sent by lindsay.morris AT tsmworks DOT com via Backup Central.
> |Forward SPAM to abuse AT backupcentral DOT com.
> +
> ----------------------------------------------------------------------
>
>
> This e-mail (including any attachments) is confidential and may be
> legally privileged. If you are not an intended recipient or an
> authorized representative of an intended recipient, you are prohibited
> from using, copying or distributing the information in this e-mail or
> its attachments. If you have received this e-mail in error, please
> notify the sender immediately by return e-mail and delete all copies
> of this message and any attachments.
> Thank you.

This electronic transmission and any documents accompanying this electronic 
transmission contain confidential information belonging to the sender.  This 
information may be legally privileged.  The information is intended only for 
the use of the individual or entity named above.  If you are not the intended 
recipient, you are hereby notified that any disclosure, copying, distribution, 
or the taking of any action in reliance on or regarding the contents of this 
electronically transmitted information is strictly prohibited.

<Prev in Thread] Current Thread [Next in Thread>