Db2 Cloning Tool: What is Skeleton Cloning?
Unless you’ve seen a presentation on the Cloning Tool, you may not be aware of support for something called Skeleton Cloning. The only references to “skeleton” in the user guide are in the context of ISPF, and there’s no mention of it in the panels or profiles.
Skeleton Cloning is a subset of Subsystem Cloning, where a portion of the subsystem is cloned (not the entire subsystem). This can be accomplished via volume-based cloning, or using the COPY-BY-DS command. There may be several use cases where Skeleton Cloning could be beneficial. One such use case is when migrating Db2 to a new release or catalog level (V12 & beyond). This use case is the primary story used to explain what Skeleton Cloning is and how to accomplish it. It can be found in a Redpaper that was published in November 2018 (REDP-5473).
In this example, a clone of only the necessary components for migration, primarily the production Db2 catalog and directory, can be migrated away from the production environment to refine and prove your production migration processes and timing. Therefore, testing of the migration processes is done with a catalog and directory of the same size and pedigree of production, providing a higher degree of confidence that you are validating steps that will work in production. The example can be expanded to include application spaces, either via the Skeleton Cloning technique or with subsequent Application Cloning processes.
“DB2 Skeleton Cloning: Protecting Your Production Environment” is available for download here. At only 20 pages in length, it’s a quick read. Once you understand these concepts, you will have another cloning option at your disposal for the various requirements that come your way.
If this was helpful, please share it or comment below.