Lift and Shift Guide - Migrating Workloads from Oracle Solaris 10 SPARC Systems to Oracle Solaris 10 Branded Zones

Prepare the Shared Storage

In this procedure, a network file system (NFS) is exported from the target system and mounted by the source system. During the lift process, the file system archive file (FLAR) is created on the shared storage where it is accessible to both the source and target systems.

Requirements

• Shared storage – The location must be accessible to the source system and the target system.

• Sufficient storage space – The shared storage must have enough available storage space to temporarily store the FLAR.

For more information about networked file systems, refer to these resources:

• Oracle Solaris 10, Managing File Systems at: https://docs.oracle.com/cd/E23823_01/html/816-4555/rfsintro-2.html

• Oracle Solaris 11, Managing Network File Systems at: https://docs.oracle.com/cd/E23824_01/html/821-1454/rfsintro-2.html

1. Ensure that there is enough available storage capacity on the planned shared storage.

   Use the storage information gathered in Review the Source System Configuration.

   1. Calculate the space needed to store the source system FLAR.

      Take the source system's total used storage (obtained in Review the Source System Configuration) and divide by two. This calculation takes into account that the various data captured items will be compressed in the shared storage, yet is conservative enough to ensure adequate storage space for all the items.

      Item Calculation Total Source system's total used storage, divided by 2 (To account for a conservative compression ratio) 19.2 ÷ 2 9.6 GB If you are installing an Oracle Solaris patchset during the migration to the target system, add 14GB to the space allotment. This is mandatory for source systems running Oracle Solaris 10 Update 8 or earlier. Otherwise the patchset is optional. 9.6 + 14 23.6 GB Add 30% (To provide additional headroom for the creation of temporary files, uncompressing files, and so on.) 23.6 + 7 30.6 GB

      For this example scenario, a minimum of 12.8 GB of available space is required on the shared storage.

   2. Identify available storage in the target system.

      The command output shows that there is approximately 1.09 TB available storage capacity, which is sufficient space to contain the capture of source system for this example scenario.

      root@TargetGlobal# zpool list vpool
      NAME    SIZE    ALLOC   FREE    CAP   DEDUP   HEALTH   ALTROOT
      vpool   1.09T   24M     1006G   1%    1.00x   ONLINE   -

   3. (If needed) Add storage space to accommodate the storage space requirements.
2. On the target global zone, create and export a file system.

   root@TargetGlobal# zfs create -o mountpoint=/ovas vpool/ovas
   root@TargetGlobal# zfs set share.nfs=on vpool/ovas
   root@TargetGlobal# zfs set share.nfs.root=\* vpool/ovas
   root@TargetGlobal# zfs set share.nfs.rw=\* vpool/ovas
   root@TargetGlobal# exportfs
   vpool_ovas      /ovas   sec=sys,root,rw

3. As superuser on the source system, create a mount point and mount the shared storage.

   In this example, TargetGlobal:/ovas is an NFS share exported from the target system.

   root@SourceSystem# mkdir /ovas
   root@SourceSystem# mount -F nfs TargetGlobal:/ovas /ovas

4. (If needed) Download an Oracle Solaris patchset to the shared storage.

   If the source system is running Oracle Solaris 10 Update 8 or earlier, you must download a patchset. It will be used with the zoneadm install -P command, which will automatically install the patchset during the migration to the target system.

   If the source system is running Oracle Solaris 10 Update 9 (or later), you can choose to have a patchset automatically installed during the migration to the target system, or not.

   The particular patchset that you are able to obtain depends on your Oracle Service agreement. If possible, download the Recommended OS Patchset for Solaris 10 SPARC. Alternatively, you can download the CPU OS Patchset 2018/04 Solaris 10 SPARC patchset.

   To understand the support policies and to download a patchset, go to https://blogs.oracle.com/solaris/solaris-10-extended-support-patches-patchsets-released. Additional information is also provided in MOS knowledge article with Doc ID 1272947.1.

   Once downloaded, unzip the downloaded zip file.