Right, I should have specifically mentioned the use of FLASHCOPY/snap as the much preferred method to copying LIVE fullpack volumes with z/OS. As well as the need to determine compatibility, with respect to any COTS/vendor products and OS's.
Good point in regards to another LOCAL backup approach...DB admins should definitely consider using the backup software that is included with the DB product. That would fit well in conjunction with the other methods (which would then backup these local backups). The rationale for the multi-method approach is to protect (i.e. CYA) with redundancy, using various methods that may be more suitable for zLinux, DB's and the z/VM and CMS storage. Doug Ponte U.S. Department of Justice - OCIO/SDS/zVM Contractor - z/VM + zLinux Senior Systems Programmer Leidos/Ingersoll Consulting [email protected] 1-202-307-6722 -----Original Message----- From: Linux on 390 Port [mailto:[email protected]] On Behalf Of Alan Altmark Sent: Friday, November 11, 2016 09:35 To: [email protected] Subject: Re: zLinux backup solutions On Thursday, 11/10/2016 at 09:12 GMT, "Ponte, Douglas C. (JMD)" <[email protected]> wrote: > Fullpack volume backups ---- can be run daily, weekly and monthly, > using JCL with automation tools > (existing on z/OS already, e.g. BMC Control-M or Tivoli Automation). This should be done with all > z/VM and zLinux volumes. > > In the full volume backup cases, stopping/shutting down is not always necessary, albeit it may be > good practice to at least quiesce when it comes to DB?s and heavy use servers. (e.g. DB2, Oracle, > etc) WARNING: To do this reliably, you need software that is capable of establishing an I/O consistency group. If you want to FLASHCOPY the volumes and sequentially backup the volume copies, that's ok, but do NOT just sequentially copy the live volumes of a running z/VM system. (If you wouldn't do it to a running z/OS system, don't do it to any other system.) This process is intimately tied to your DR strategy, too, so get it right. If you have databases, use the backup software for the database. If you're using hardware replication, be sure that it's supported by the database vendor. Some people take a too-casual approach to backups and DR. I too often hear "Don't worry, I'm doing it from z/OS." as though z/OS has magical powers over z/VM and Linux. Don't fall into that trap. That way there be dragons. Alan Altmark Senior Managing z/VM and Linux Consultant Lab Services System z Delivery Practice IBM Systems & Technology Group ibm.com/systems/services/labservices office: 607.429.3323 mobile; 607.321.7556 [email protected] IBM Endicott ---------------------------------------------------------------------- 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/
