Well, we just got back from OUR trip to Sterling Forest, and had a massively
successful test -- all primary objectives met, and just enough documentation
& procedure changes cropping up to fit the definition below. Like "Don't
start the TSM client on the EDI system until AFTER restoring the
filesystems" (for some reason, when we got around to the retore there
weren't any active files . . . :-)

The thing to keep in mind is that a run with nothing but problems is also a
'successfull' test, as it illustrates how wonderfully unprepared you are. We
walk in with a project plan and seperate procedures for each major function
on each system; I understand that SF still gets clients that walk in with a
bunch of tapes and say "We're here for a D/R test. What do we do now?".

(And I do a GREAT impersonation of a geek at parties :-)

Tom Kauffman
NIBCO, Inc

-----Original Message-----
From: Stapleton, Mark [mailto:stapleto AT BERBEE DOT COM]
Sent: Friday, April 18, 2003 3:05 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: DR Test Question


From: Kauffman, Tom [mailto:KauffmanT AT NIBCO DOT COM]
> And remember -- (mis-quoting an old software engineering
> book) "a test with no errors or problems is a failed test".

I'll bet *you're* fun at parties. ;o)

--
Mark Stapleton (mark.stapleton AT berbee DOT com)
Berbee Information Networks
Office 262.521.5627