Given the proper environment, though, you can talk / coerce DirMaint into using the DASD FlashCopy function to quickly copy one minidisk to the new location (if I remember correctlyŠ Now that I think about it though, when I built my Linux cloning engine, I used DirMaint to allocate the disks, and FlashCopied the contents to the new disks myself.)
Getting old is such a painŠ -- Robert P. Nix | Sr IT Systems Engineer | Data Center Infrastructure Services 507-284-0844 | [email protected] Mayo Clinic| 200 First Street SW | Rochester, MN 55905 Mayo Clinic, a mission-driven worldwide leader in health care for 150 years. http://150years.mayoclinic.org/ On 7/7/14, 2:15 PM, "Mark Post" <[email protected]> wrote: >>>> On 7/6/2014 at 07:19 PM, Cameron Seay <[email protected]> wrote: >> Es claro. For my edification, how does the system handle the cloning of >> the minidisks of the cloned-from guest? Are they physically the same >> ones? Does it grad available DASD for the cloned user? Thanks! > >DIRMAINT will use available space from the various DASD volumes you've >told it to manage. That means the cloning does involve actual copying, >and not some sort of thin provisioning. > > >Mark Post > >---------------------------------------------------------------------- >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 more information on Linux on System z, visit >http://wiki.linuxvm.org/ ---------------------------------------------------------------------- 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 more information on Linux on System z, visit http://wiki.linuxvm.org/
