We currently have a VM/Linux LPAR configured for a Proof of Concept [POC]. Our other LPARs are zOS. We plan on using the Linux images to host some Oracle DBs. There are currently no tape drives online to the VM LPAR.
During the install of VM and Linux we used a number of methods to initialize and format the DASD [contracted assistance]. We are using minidisks for the Linux images. On some of the volumes we have a zOS VTOC. These volumes cause us to get messages on the zOS system. IEE498I ...LSPACE NON STANDARD OS VOLUME I found on the listserve an item that tells us how to remove the zOS VTOC which should eliminate the message. Our backup and restore [DR] process on zOS is completely automated. We would like the same on VM and Linux. >From this I am questioning how we got here and what is the 'best' way to >operate in the future. 1. What is the best way to initialize and format volumes to be used for VM and Linux minidisks. 2. What is the best way [considering the Oracle DBs] to backup and restore the VM and Linux images for disaster recovery. 3. Should we use TSM [already installed on zOS] to backup the Linux images to zOS. I know these topics have been discussed on the listserve before but I am looking for what actual users are doing. Ruddy A. Melancon IT Systems Specialist, Senior Alabama Department of Transportation 334-353-6323 ---------------------------------------------------------------------- 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
