Go to main content

Lift and Shift Guide – Migrating Application Data From Older SPARC Systems to Newer SPARC Systems

Exit Print View

Updated: February 2020
 
 

Configure the Target's Virtual Storage (Logical Domain Virtualization)

Target system storage space is needed for the incoming application data. In this procedure, storage space is prepared on a target system that supports virtualization using Oracle Solaris logical domains. If the target system uses zone virtualization, instead see Configure the Target's Virtual Storage (Zone Virtualization).

In this example, a LUN (virtual disk) is provisioned for the target guest domain in preparation of the incoming application data. Only one LUN is provisioned, but the commands can be repeated to provision additional LUNs.

  1. Log into the target control domain as superuser.
  2. Provision a virtual disk .

    Repeat these two steps for each virtual disk that you want to provision.

    1. Export the virtual disk backend from a service domain.

      ldm add-vdsdev disk_pathname vol_name@vdisk_server

      Where:

      • disk_pathname is the path name of the physical device.

      • vol_name is a unique name of the device being added to the virtual disk server.

      • vdisk_server is the name of the virtual disk server to which this device is added.

      Example:

      root@Target# ldm add-vdsdev /dev/rdsk/c0t600144F09F2C0BFD00005BE4A9A90005d0s2 data-vol2@vds0
    2. Assign the virtual disk to a guest domain.

      ldm add-vdisk vdisk_name vol_name@vdisk_server guest_domain

      Where:

      • vdisk_name is the name of the new vdisk.

      • vol_name is the name of an existing volume in which to connect.

      • vdisk_server is the name of the virtual disk server to which this device is added.

      • guest_domain is the name of the guest domain to which this vdisk is added.

      root@Target# ldm add-vdisk vdisk2 data-vol2@vds0 data-gdom
  3. Verify the disk configuration.
    root@Target# ldm list -o disk primary
    
    NAME             
    primary          
    
    VDS
        NAME         VOLUME         OPTIONS     MPGROUP     DEVICE
        vds0         solaris-vol0                           /dev/rdsk/c0t600144F09F2C0BFD00005BE4A8500003d0s2
                     solaris-vol1                           /dev/rdsk/c0t600144F09F2C0BFD00005BE4A90F0004d0s2
                     data-vol2                              /dev/rdsk/c0t600144F09F2C0BFD00005BE4A9A90005d0s2
  4. List the virtual disk bindings.
    root@Target# ldm ls -o disk data-gdom
    NAME             
    solaris10        
    
    DISK
        NAME         VOLUME             TOUT ID   DEVICE    SERVER         MPGROUP
        vdisk0       solaris-vol0@vds0      0     disk@0    primary             
        vdisk1       solaris-vol1@vds0      1     disk@1    primary             
        vdisk2       data-vol2@vds0         2     disk@2    primary