Give him some slack. He is from Kentucky where they attempt to saddle and ride 
most anything that runs.

Regards, 
Richard Schuh 

 

> -----Original Message-----
> From: The IBM z/VM Operating System 
> [mailto:[email protected]] On Behalf Of Martin, Terry 
> R. (CMS/CTR) (CTR)
> Sent: Tuesday, June 02, 2009 2:05 PM
> To: [email protected]
> Subject: Re: What we must do before we claim the zlinux 
> server is in production stage?
> 
> If that was to happen with me on the mainframe
> 
> Wow, and all of this time I thought z/VM ran on the mainframe.
> 
> Thank You,
>  
> Terry Martin
> Lockheed Martin - Information Technology z/OS & z/VM Systems 
> - Performance and Tuning Cell - 443 632-4191 Work - 410 
> 786-0386 [email protected] -----Original Message-----
> From: The IBM z/VM Operating System 
> [mailto:[email protected]] On Behalf Of Dodds, Jim
> Sent: Tuesday, June 02, 2009 1:30 PM
> To: [email protected]
> Subject: Re: What we must do before we claim the zlinux 
> server is in production stage?
> 
> Bravo,
> 
> It is amazing that Opies here think that if you can back it 
> up you can restore. I don't know how many times they have not 
> been able to restore files and their solution is to change 
> backup software. If that was to happen with me on the 
> mainframe side I would be unemployed. I agree with Adam you 
> should test a restore of a sample size of files from your 
> backups in my opinion at least quarterly and whenever the 
> backup parameters change. 
> 
> Jim Dodds
> Systems Programmer
> Kentucky State University
> 400 East Main Street
> Frankfort, Ky 40601
> 502 597 6114
> 
> -----Original Message-----
> From: The IBM z/VM Operating System 
> [mailto:[email protected]] On Behalf Of Adam Thornton
> Sent: Tuesday, June 02, 2009 1:16 PM
> To: [email protected]
> Subject: Re: What we must do before we claim the zlinux 
> server is in production stage?
> 
> On Jun 2, 2009, at 11:51 AM, Tom Duerbusch wrote:
> 
> > A lot of it also depends on local practices.
> >
> > 1.  Backups....scheduled..and monitored.
> 
> And RESTORED, whether you need to or not, on some schedule.  
> A good test, I'd say, is to pick ten files at random from the 
> backup catalogue every so often and restore them to a 
> temporary location, and then verify those files.  (Assuming 
> you can spare your tape library long enough, because ten 
> random files is a lot of loading/unloading/
> seeking.)
> 
> Seriously: your backup regimen is USELESS if you cannot 
> restore the files you backed up, and "when you need them" is 
> NOT the time to find out that the tapes haven't been being 
> written correctly.
> 
> Adam
> 

Reply via email to