Backup and Restore to Skytap on Azure using Mksysb

This guide is provided “as-is”. Information and views expressed in this document, including URL and other Internet website references, may change without notice and usage of the included material assumes this risk.

This document does not provide you with any legal rights to any intellectual property in any product. You may copy and use this document for your internal, reference purposes.

Table of Contents

Prechecks

  1. Error logs for any OS level issues.

  2. Check Software inconsistencies using # lppchk -v.

  3. Resolve any operating system level issue to take a healthy system backup.

  4. Enough free space to backup all files in a filesystem.

Back to the Top

Backing up On-Prem System using Mksysb Backup Execution

  1. Populate the /tmp/exclude.rootvg file for excluding the file systems from the backup.

  2. Use command # mksysb -ipX /<FS>/<hostname>.mksysb.

Note: It may take some time to complete the backup

  1. Verify content of mksysb using # lsmksysb -lf > /<FS>/<hostname>.mksysb.

Back to the Top

Transferring Mksysb to Skytap

Option 1 - Direct Connectivity

Pros:

  • VPN or ExpressRoute

  • Network planning is required ahead of time

  • Secured and fast data transfer

  • Future proof

Option 2 - Published Service

Pros:

  • Fastest and cheapest to deploy

  • Native Skytap support

  • Only the NIM server in Skytap is required to start data transfer

  • Encrypted data transfer over public Internet

  • Only recommended for proof-of-concept

Option 3 - Azure Blob

Pros:

  • Azure Blob Storage

  • Secured and fast data transfer

  • Additional VM for AZ copy required

  • Future proof

  • Data can be copied over even before Skytap service is started

Back to the Top

Restore In Skytap

Initiate a NIM server in Skytap

  1. Deploy a new NIM AIX template using public templates (latest AIX level recommended).

  1. Rename the LPAR to NIM server.

  1. Set up the desired network and attach the network to the LPAR.

  1. Set the desired hostname in Adapter setting.

  1. Power on the LPAR and logon with root access.
Back to the Top

Set up Client on NIM Server to Restore Mksysb

  1. Set Hostname and /etc/hosts to exact name as the hostname used when configuring the LAPRs Network Adapter settings.

  1. Update the /etc/hosts file with the client hostname.

  1. Verify hostname is resolved.

  1. Add the Client in NIM config # smitty nim_mkmac and enter the client hostname.

  1. Change the setting as shown below and press Enter.

  1. NIM Client is defined and can be verified in # lsnimn nimclient.

  1. Copy the Source Mksysb in a new filesystem /export/mksysb.

  2. Create the filesystem # crfs -v jfs2 -m /export/mksysb -A > yes -a size=10G -r rootvg.

  1. List the mksysb file content lsmksysb -lf.

  1. Create the two NIM resources required for restoration.

10a. Mksysb resource

10a-1. Mksysb - # smitty nim_res > define a resource and select mksysb and press enter.

10a-2. Fill in the Name, Server of resource and location of resource (absolute path for location of the mksysb file).

10b. Spot resource

10b-1. Define spot from mksysb resource # smitty nim_res -> define a resource select spot and press enter (make sure > you have enough space in /export/spot filesystem ~2 > GB).

10b-2. Enter Name, Server of resource, Source of Install images and Location (absolute Path for the resource “/export/spot sapaix_spot”).

10b-3. Creation of spot will take some time approximately 15 to 30 minutes.

  1. Assign resources to nimclient machine: # smitty nim_mac_res.

  2. Allocate Network Install resources and select nimclient from the list and press Enter.

  3. Use F7 or Esc+7 to select the sapmksysb and sapaix_spot and press Enter.

  1. Command output will be as below exit using F10 or esc+0.

  1. Enable Bos installation for the client # smitty nim_mac_op nimclient.

  1. Select bos_inst and press Enter.

  1. Select the options shown below for mksysb restore (Use Arrow keys and F4 > or Esc+4).

  1. The setup is now complete.

  1. Verify the client Status # lsnim -l nimclient.

Back to the Top

Setup New LPAR and restore the Mksysb

  1. From the Skytap dashboard, add a new LPAR in your existing Environment.

  1. Select Templates and choose any AIX template and add VM.

  1. Edit the setting on VM and Set Hostname and IP.

  1. From hardware setting assign the disks as per Source LPAR rootvg.

4a. Delete the existing disk and add new disk.

4b. Add new disk.

4c. Update the CPU/RAM if required and start the LPAR and open the console.

Note: System will enter in SMS menu.

  1. Set up NIC/Ethernet to boot using NIM server using the below sequence.

    a. " 2 - Setup Remote IPL"

    b. " 1 - Interpartition Logical LAN"

    c. " 1 - IPv4 – Address Format"

    d. " 1 - BOOTP"

    e. " 1 – IP Parameters"

  2. Configure the IPS to match the IP as shown below.

  1. Press esc to return to previous Menu and run “3 - Ping Test” -> press 1 and enter to execute.

  1. On successful ping press enter and return to main menu using “M”.

  2. Press “X” to exit and server should start boot using the LAN adapter.

  1. It will take approximately 10 to 20 mins. to restore Mksysb and server will reboot with the Mksysb restored.

Savevg Backup and Restore in Skytap

  1. Backup and restore data volumes using savevg

a. Prechecks:

  • Minimize active read/writing to disk to avoid file or database corruption
  • Verify enough free space to backup volume group to your filesystem

b. Backup execution - verify volume group has desired volumes:

  • Run # lsvg and #lsvg - an app to review volumes to be backed up

  • Run backup to location with sufficient space with the command # savevg -r -f /tmp/backup/app.image app

c. Copy backup to Skytap LPAR (see copy methods above for mksysb)

d. Prepare system in Skytap to restore volumes. Note: if you want to shrink your volumes when restoring, you should pick smaller sizes that are still sufficient for the data in the volume group.

  • Identify physical volumes associated with the volume and their sizes

Run # lspv and # lspv hdisk1 to confirm the size in megabytes of any necessary disks

  • In Skytap, add disks to your restore target of sufficient size

e. Shut down the restore LPAR in Skytap, go to edit VM and add disks

f. Pick how much storage you need and select “Save”

g. Repeat for any additional physical disks you need to add

h. Start LPAR when disks added

  1. Run restores for savevg

a. Identify the sizes of your disks to make sure you are restoring to the correct locations with # lspv and # bootinfo -s hdisk1

b. Run # ls savevg -f app.image -l to confirm contents of savevg file

c. Run restore # restvg -f app.image hdisk1 (add flag -s to restore with minimum size, you can specify multiple disks if desired)

d. Finished

Next steps

Main Overview

Skytap Well-Architected Framework

Operational Excellence

Skytap Operational Excellence Pillar

Resiliency

Skytap Resiliency Pillar

Migration Solutions

Design

Security

Skytap Security Pillar