Skip Headers
Oracle® Exalogic Elastic Cloud Backup and Recovery Guide
Release EL X2-2 and X3-2

E40226-05
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
PDF · Mobi · ePub

6 Backup and Recovery of Customer vServers

This chapter provides the steps for backing up and recovering customer vServers. It contains the following sections:

6.1 Backing Up Customer vServers

All the artifacts for the customer vServers are stored in the ExalogicRepo share on the ZFS storage appliance. These artifacts can be backed up by either creating ZFS snapshots as described in Section 5.2.3, "Creating a ZFS Snapshot of the Exalogic Control repository," or by performing a full backup to an external storage device using your existing backup strategy (for example: agent-based backup, NDMP, or ZFS replication).

For more information, see the Exalogic Backup and Recovery Best Practices White Paper at http://www.oracle.com/technetwork/database/features/availability/maa-exalogic-br-1529241.pdf.

6.2 Restoring Customer vServers

A customer vServer can be recovered either from a ZFS snapshot or from the latest full backup.

Note:

You can only restore a vServer if the vServer exists in Enterprise Manager Ops Center. If you deleted the vServer in Enterprise Manager Ops Center, you cannot restore the vServer.

6.2.1 Restoring a Customer vServer from a ZFS Snapshot

To restore a customer vServer from a ZFS snapshot, do the following:

  1. Log in to the BUI of the ZFS storage appliance at http://storage_host:215 as the root user.

  2. Navigate to Shares and then to Projects, and select the ExalogicControl project.

  3. Under the ExalogicControl project, select the ExalogicRepo share.

  4. Navigate to Snapshots, select the required snapshot, and clone the snapshot.

    Note:

    If the vServer you are restoring hosts a critical application, ensure that you are using a snapshot which was taken when either the application was stopped or the virtual machine was shutdown.

  5. Select the location of the backup project, as defined in Chapter 2, "Backup and Recovery Locations."

  6. Enter a name for the clone (example: RepoClone_date).

  7. Note the mount point for the clone.

  8. Mount the clone on one of the compute nodes, as shown in the following example:

    mount -t storage_host:/export/Exalogic_Backup/RepoClone_Oct24 /backup
    
  9. Go to the /backup/VirtualMachines directory.

  10. Find the virtual machine configuration files for the customer vServer that you want to restore by using the following command:

    grep -i vmName /backup/VirtualMachines/*/vm.cfg
    

    Example:

    grep -i wls_vm /backup/VirtualMachines/*/vm.cfg
    0004fb000006000038a23e7e6d307e12/vm.cfg:OVM_simple_name = wls_vm
    
  11. Find the location and the name of the virtual-disk image file for the customer vServer that you want to restore.

    The location and name of the virtual-disk image file are indicated by the disk parameter in the vm.cfg file, as shown in the following example:

    cat 0004fb000006000038a23e7e6d307e12/vm.cfg | grep file
    disk = ['file:/OVS/Repositories/0004fb00000300007d5117500d92ae54/VirtualDisks/0004fb00001200003d3b8b4058ee7682.img,hda,w'
    ]
    
  12. Copy the vm.cfg files identified earlier to the /OVS/Repositories/*/VirtualMachines/vmGUID directory.

    Note that vmGUID is name of the directory in which the vm.cfg file is located. For example, the following was the previously identified location of the wls-vm vServer:

    0004fb000006000038a23e7e6d307e12/vm.cfg:OVM_simple_name = wls-vm
    

    In this example, 0004fb000006000038a23e7e6d307e12 is the vmGUID.

  13. Copy the virtual-disk image file identified earlier, to the location indicated by the disk parameter in the vm.cfg file.

  14. Log in to the Exalogic Control BUI, and start the customer vServer.

6.2.2 Restoring Customer vServers from a Full Backup

To restore customer vServers from a full backup, do the following:

Note:

In some cases, after the vServer is recovered, it may be necessary to run the fsck file check utility to fix any file system inconsistencies.

  1. Mount the backup location as defined in Section 5.2.4, "Creating a Full Backup of the Exalogic Control Artifacts."

  2. Identify the backup file from which you want to restore the customer vServer.

  3. Copy the backup files to a directory of your choice.

  4. Go to the directory in which you extracted the backup files.

  5. Copy the vm.cfg file to the /OVS/Repositories/*/VirtualMachines/vmGUID directory.

    Note that vmGUID is name of the directory in which the vm.cfg file is located. For example, the following was the previously identified location of the wls-vm vServer:

    0004fb000006000038a23e7e6d307e12/vm.cfg:OVM_simple_name = 'wls-vm'
    

    In this example, 0004fb000006000038a23e7e6d307e12 is the vmGUID.

  6. Copy the virtual-disk image file to the location indicated by the disk parameter in the vm.cfg file

  7. Log in to the Exalogic Control BUI, and start the customer vServers.

6.3 Re-creating vServers

To recover a vServer, do the following:

  1. Log in to the Exalogic Control BUI as a Cloud User.

  2. Identify the vServer that needs to be recovered.

    The vServer should already be shut down. If it is still running, stop it.

  3. Copy the required configuration files of the vServer to a location of your choice.

  4. Delete the vServer from the account.

  5. If the vServer should be restored with the same IP address, log in to the Exalogic Control BUI as the Cloud Admin user, allocate the entire network, and select the address you want.

    For more information about allocating IP addresses, see the Oracle Exalogic Cloud Administrator's Guide at http://docs.oracle.com/cd/E18476_01/doc.220/e25258/toc.htm.

  6. Create a vServer as described in the Oracle Exalogic Cloud Administrator's Guide.

    Note:

    Before creating a vServer, make sure that the required volumes, networks, and so on exist in the environment.

  7. After the vServer is created, mount the NFS directory containing the customer vServer backups and copy the configurations files you backed up in step 3 to the vServer.