Re: FDR backups of Linux volumes?
Also - is it normal for the volume serial to be 0X followed by the device number? fdasd or dasdfmt, one, will by default set the volser to 0Xdevno. So, yes. :Warning ON VM Newbie Answering a question We do a dasdfmt command with the -l option to add a volume name. Example: dasdfmt -b 4096 -y -f /dev/dasdb -l vol001 Now when you view it from MVS it shows as vol001 :Warning OFF -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: FDR backups of Linux volumes?
Correct if you supply a volume serial it will use it. If you don't have the -l xx on the command then it will use 0Xdevno as the volume serial. [EMAIL PROTECTED] wrote: Also - is it normal for the volume serial to be 0X followed by the device number? fdasd or dasdfmt, one, will by default set the volser to 0Xdevno. So, yes. :Warning ON VM Newbie Answering a question We do a dasdfmt command with the -l option to add a volume name. Example: dasdfmt -b 4096 -y -f /dev/dasdb -l vol001 Now when you view it from MVS it shows as vol001 :Warning OFF -- Stephen Frazier Information Technology Unit Oklahoma Department of Corrections 3400 Martin Luther King Oklahoma City, Ok, 73111-4298 Tel.: (405) 425-2549 Fax: (405) 425-2554 Pager: (405) 690-1828 email: stevef%doc.state.ok.us -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: FDR backups of Linux volumes?
On Dec 13, 2006, at 10:20 AM, Mary Anne Matyaz wrote: Also - is it normal for the volume serial to be 0X followed by the device number? fdasd or dasdfmt, one, will by default set the volser to 0Xdevno. So, yes. :Warning ON VM Newbie Answering a question We do a dasdfmt command with the -l option to add a volume name. Example: dasdfmt -b 4096 -y -f /dev/dasdb -l vol001 Now when you view it from MVS it shows as vol001 :Warning OFF Yeah: if you care what the volser ends up as then you should always use the -l flag to set it as part of the DASD preparation step. If, on the other hand, you only care about it from a device address standpoint, the default is probably OK. Adam -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: FDR backups of Linux volumes?
:Warning ON VM Newbie Answering a question Welcome to the party...8-) We do a dasdfmt command with the -l option to add a volume name. Example: dasdfmt -b 4096 -y -f /dev/dasdb -l vol001 Now when you view it from MVS it shows as vol001 A much better approach than letting it default, esp since the addresses will change when he does the copy. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: FDR backups of Linux volumes?
I formatted these using YAST, I believe. Is there an option I should have looked for? This is an LPAR install, not VM so if there are VM commands involved I'm unable to perform those. Tim Hare Senior Systems Programmer Florida Department of Transportation (850) 414-4209 Linux on 390 Port LINUX-390@VM.MARIST.EDU wrote on 12/13/2006 10:35:35 AM: :Warning ON VM Newbie Answering a question Welcome to the party...8-) We do a dasdfmt command with the -l option to add a volume name. Example: dasdfmt -b 4096 -y -f /dev/dasdb -l vol001 Now when you view it from MVS it shows as vol001 A much better approach than letting it default, esp since the addresses will change when he does the copy. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: FDR backups of Linux volumes?
No, dasdfmt is a Linux/390 command. I don't recall if YaST gives you the option to specify a volser or not. You would probably have to issue the command from the command line. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Tim Hare Sent: Wednesday, December 13, 2006 11:00 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: FDR backups of Linux volumes? I formatted these using YAST, I believe. Is there an option I should have looked for? This is an LPAR install, not VM so if there are VM commands involved I'm unable to perform those. Tim Hare Senior Systems Programmer Florida Department of Transportation -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: FDR backups of Linux volumes?
I did FDR backups of a running system and they would not run when restored. Shut down the Linux system and they work fine. Lea Stahr Linux/Unix Team 630-753-5445 [EMAIL PROTECTED] -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Tim Hare Sent: Tuesday, December 12, 2006 10:10 AM To: LINUX-390@VM.MARIST.EDU Subject: FDR backups of Linux volumes? I realize it isn't the best practice for backing up Linux, but I will be having to move volumes to a new DASD array. I'd like to use FDR full-volume backups of my Linux volumes just for insurance (we will use FDRPAS to move the information, most likely). Has anyone had any issues taking full-volume backups of Linux-formatted 3390-3 volumes? Also - is it normal for the volume serial to be 0X followed by the device number? Thanks Tim Hare Senior Systems Programmer Florida Department of Transportation (850) 414-4209 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: FDR backups of Linux volumes?
On Dec 12, 2006, at 11:09 AM, Tim Hare wrote: I realize it isn't the best practice for backing up Linux, but I will be having to move volumes to a new DASD array. I'd like to use FDR full-volume backups of my Linux volumes just for insurance (we will use FDRPAS to move the information, most likely). Has anyone had any issues taking full-volume backups of Linux-formatted 3390-3 volumes? Also - is it normal for the volume serial to be 0X followed by the device number? Make sure your guests are DOWN when you do a full-volume backup. fdasd or dasdfmt, one, will by default set the volser to 0Xdevno. So, yes. Adam -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: FDR backups of Linux volumes?
I realize it isn't the best practice for backing up Linux, but I will be having to move volumes to a new DASD array. I'd like to use FDR full-volume backups of my Linux volumes just for insurance (we will use FDRPAS to move the information, most likely). Has anyone had any issues taking full-volume backups of Linux-formatted 3390-3 volumes? As long as the guests are *completely* down -- not just inactive -- you should be fine. Also - is it normal for the volume serial to be 0X followed by the device number? Hmm. Not normal, but permitted if the original creator so chose. Is this a LPAR installation? That would be more common there. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: FDR backups of Linux volumes?
Yes, this is in an LPAR. Management won't pay for z/VM until proof of concept and a use case are developed for virtualized Linux servers. I will be devoting more time to that after the first of the year, I hope. For now I just want to make sure I don't lose work I have already done. Tim Hare Senior Systems Programmer Florida Department of Transportation (850) 414-4209 David Boyes [EMAIL PROTECTED] Sent by: Linux on 390 Port LINUX-390@VM.MARIST.EDU 12/12/2006 12:06 PM Please respond to Linux on 390 Port LINUX-390@VM.MARIST.EDU To LINUX-390@VM.MARIST.EDU cc Subject Re: FDR backups of Linux volumes? I realize it isn't the best practice for backing up Linux, but I will be having to move volumes to a new DASD array. I'd like to use FDR full-volume backups of my Linux volumes just for insurance (we will use FDRPAS to move the information, most likely). Has anyone had any issues taking full-volume backups of Linux-formatted 3390-3 volumes? As long as the guests are *completely* down -- not just inactive -- you should be fine. Also - is it normal for the volume serial to be 0X followed by the device number? Hmm. Not normal, but permitted if the original creator so chose. Is this a LPAR installation? That would be more common there. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
