Well in a perfect world, I'd be able to do file level backup of a z/linux
guest from z/os and write that backup to a tape managed by RMM in the 3494.
This is an imperfect world, however.
It is important that whatever backup method I employ be able to be tracked
by RMM, because in a disaster recovery, we would be using z/os to restore
z/VM and z/linux. Currently I have been doing Compatible Disk Layout
backups of the volumes used by z/linux, but some of those volumes are
logically carved into minidisks. (Such as 1200 cyl /tmp directories).
So backing up a mod-9 with 5 1200 cyl minidisks and one 4017 cyl minidisk
on it, is the granularity level of the mod-9.
I was looking at the possibility of something from the VM side of things
that can simply backup a minidisk so that the restore can be put anywhere,
at minidisk granularity but still catalog stuff in the z/os RMM database.
Probably a kludge at best, impossible at worst.
What I have currently for linux volumes is this: The LXC volumes are 1200
cyl mod-3 layout custom volumes. End of string leftovers from carving up
the shark, basically. The LXC volumes are full sized mod-9's
|------------------------------------+------------------------------------|
|Available Linux Volumes |Typical Guest layout |
|------------------------------------+------------------------------------|
|DASD A23E CP SYSTEM LXC001 DASD |00: DASD 0200 3390 LXC003 R/W |
|A23F CP SYSTEM LXC002 |1200 CYL ON DASD A242 |
|DASD A242 CP SYSTEM LXC003 DASD |00: DASD 0201 3390 LXF903 R/W |
|A243 CP SYSTEM LXC004 |5000 CYL ON DASD B216 |
|DASD B213 CP SYSTEM LXF901 DASD |00: DASD 0202 3390 LXF903 R/W |
|B214 CP SYSTEM LXF902 |5017 CYL ON DASD B216 |
|DASD B216 CP SYSTEM LXF903 DASD |00: DASD 0203 3390 LXF904 R/W |
|B217 CP SYSTEM LXF904 |1200 CYL ON DASD B217 |
|DASD B218 CP SYSTEM LXF905 DASD | |
|B219 CP SYSTEM LXF906 |In the above, 200 is always swap, |
|DASD B21A CP SYSTEM LXF907 |201 is always root, 202 is always |
| |opt and 203 is always /tmp |
|------------------------------------+------------------------------------|
So you can see that these systems are very small. The are not designed to
hold data files. We're doing that on DB2/IMS in z/os. Just big enough for
websphere and some other stuff.
Someone suggested that I do cyl/track backups that correspond to the
starting and ending cyl/track for each minidisk, still keeping things
within the DFDSS realm, and that would be satisfactory and give me the
minidisk granularity levels.
Ultimately, I would love to be able to ship file level backup images via
amanda to z/o to be migrated via HSM, but that is deep weeds rocket science
to me. My understanding of such a theorettical scenario is that amanda
would manage the archive contents and HSM/RMM manage the archive dataset
and the tape that it is on.
Dave Jones
<[EMAIL PROTECTED]
e.net> To
Sent by: Linux on [EMAIL PROTECTED]
390 Port cc
<[EMAIL PROTECTED]
IST.EDU> Subject
Re: Backups - CDL Via Z/os or
options under VM itself.
07/14/2004 01:12
PM
Please respond to
Linux on 390 Port
<[EMAIL PROTECTED]
IST.EDU>
Hi, James.
There are certainly ways of doing VM minidisk backups (and, at no extra
charge, restores as well....), using the standard set of tools that come
with z/VM.
Could you be a little more specific when you say you want to do a "DFDSS
style backup", for those of us not completely familiar with that product?
DJ
James Melin wrote:
> I am currently doing volume backups of CDL layout volumes via z/OS and
> DFDSS. Some volumes are actually 4 minidisks within VM, and I don't have
> mini-disk level backup granularity with the CDL method. Is there an
> equivalent to DFDSS within VM or does this have to be purchased
ala-carte?
> I would very much like to just do the equivalent of VM mini-disk backups
> using a DFDSS style backup from within VM but we're neophytes in the VM
> realm, so I don't really know what is possible and what is not.
>
> If anyone has suggestions I'd be happy to hear them.
>
> Thanks
>
> -J
>
>
--
Dave Jones
Houston, TX 281.578.7544
----------------------------------------------------------------------
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
