«

»

Sep 05

VMware Power On from 3PAR ZDB

This post will guide you through the basic configuration, backup and restore (Power On/Live Migrate) for VEAgent backups (VMware) hosted on 3PAR storage systems. This functionality has been introduced with Data Protector A.09.04 (b104). While this guide is considered as a good starting point you should also check the ZDBAdmin.pdf and ZDBIntegration.pdf for complete documentation, list of limitations and troubleshooting procedures.

Storage integration in Data Protector

There are a few steps that must be done once to make the ZDB work. The first step should be the installation of the required storage provider (HP P6000 / HP 3PAR SMI-S Agent) on your backup host. Of course the Virtual Environment Integration is required to perform VMware backups. This guide assumes that you’re familiar with the required procedures (installation, vCenter import).

Make sure that the CIM provider on your 3PAR system is started.

 

BLACKHAWK cli% showcim
-Service- -State- –SLP– SLPPort -HTTP– HTTPPort -HTTPS- HTTPSPort PGVer CIMVer
Disabled Active Enabled 427 Enabled 5988 Enabled 5989 2.9.1 3.2.1
BLACKHAWK cli% startcim
CIM server will start in about 90 seconds

BLACKHAWK cli% showcim
-Service- -State- –SLP– SLPPort -HTTP– HTTPPort -HTTPS- HTTPSPort PGVer CIMVer
Enabled Active Enabled 427 Enabled 5988 Enabled 5989 2.9.1 3.2.1
BLACKHAWK cli%

 

Once the provider is up and running you should be able to register the storage system with Data Protector. You should check the connection before proceeding.

 

C:\>omnidbzdb –diskarray 3PAR –ompasswd –add blackhawk.syncer.de –ssl –user 3paradm –passwd password
HP 3PAR provider authentication data updated for user 3paradm at host blackhawk.syncer.de.

C:\>omnidbzdb –diskarray 3PAR –ompasswd –list
User Host Port Ssl
—————-+——————–+—–+—–
3paradm blackhawk.syncer.de 5989 Yes

C:\>omnidbzdb –diskarray 3PAR –ompasswd –check
Starting configuration check on host wildfire.syncer.de.
[Normal] From: SMISA@wildfire.syncer.de “SMISA” Time: 05.09.2015 09:13:51
Checking the HP 3PAR provider using this connection data:
Host: blackhawk.syncer.de
User: 3paradm
Namespace: root/tpd
Port: 5989
SSL mode: TRUE

[Normal] From: SMISA@wildfire.syncer.de “SMISA” Time: 05.09.2015 09:13:51
This HP 3PAR provider has access to the following unit:
Name: BLACKHAWK
WWN: 2FF70002AC012345
Description: HP_3PAR 7200c, ID: 12345, Serial number: 1612345, InForm OS version: 3.2.1 (MU3)

Configuration check finished.

Create a VEAgent ZDB backup specification

Create a new VEAgent backup specification and make sure you select Snapshot or split mirror backup as Backup type.

The selections here are the same with one addition. You need to specify a mount host that is used for snapshot verification during the ZDB process. You can use one of your existing ESXi hosts for this task.

Add the Storage provider to the configuration. The defaults will work quite well in most of the cases.

To enable Power On, you need to select Keep the replica after backup and Track the replica for instant recovery. Specify the amount of replicas to retain based on your needs.

Select any VMs and options based on your requirements, including quiescing to allow application consistent snapshots.

In case of 3PAR the VMs should reside on datastores not presented to 3PAR host sets OR presented as 3PAR volume sets to the ESXi hosts. Hopefully this limitation is resolved in a future version, since especially host sets are quite common.

Before saving the specification remember to a backup device, a suitable data protection and other options required. Once saved you’re able to the perform the Zero Downtime Backup (ZDB) either to disk (Snapshot) and tape (Backup device) or just to disk (Snapshot).

While the ZDB is running you’ll notice a Snapshot created on the 3PAR. Based on your configuration those are kept for future Power On sessions.

The vCenter will report snapshot creation/deletion as well as some mount activity from the mount host.

Here is a session report for a disk + tape backup session on 3PAR for a single VM.

 

[Normal] From: BSM@wildfire.syncer.de “VEA_BLACKHAWK_ZDB” Time: 05.09.2015 21:01:27

    Backup session 2015/09/05-14 started.

[Normal] From: BSM@wildfire.syncer.de “VEA_BLACKHAWK_ZDB” Time: 05.09.2015 21:01:28

    OB2BAR application on “wildfire.syncer.de” successfully started.

[Normal] From: VEPALIB_VMWARE@wildfire.syncer.de “/DC” Time: 05.09.2015 21:01:28

    Resolving objects for backup on aero ‘aero.syncer.de’ …

[Normal] From: VEPALIB_VMWARE@wildfire.syncer.de “/DC” Time: 05.09.2015 21:01:32

    Add Virtual Machine to the backup …

        Name: JETDCM02

        Path: /DC/vm/JETDCM02

        InstanceUUID: 503c437f-844a-6608-3b6b-9dc88c4be20b

[Normal] From: SMISA@wildfire.syncer.de “SMISA” Time: 05.09.2015 21:01:34

    Starting agent on wildfire.syncer.de.

[Normal] From: SMISA@wildfire.syncer.de “SMISA” Time: 05.09.2015 21:01:34

    Starting agent on wildfire.syncer.de.

[Normal] From: SMISA@wildfire.syncer.de “SMISA” Time: 05.09.2015 21:01:35

    Starting backup session with session ID 2015/09/05-14

        Snapshot source: Original volume

        Snapshot type: VSnap

        Number of replicas rotated: 4

        VRaid level: Same as source

        Track the replica for instant recovery

        Use the same mount points as on the application system.

[Normal] From: SMISA@wildfire.syncer.de “SMISA” Time: 05.09.2015 21:01:35

    Resolving backup objects on the application system.

[Normal] From: SMISA@wildfire.syncer.de “SMISA” Time: 05.09.2015 21:01:36

    Resolving of backup objects on the application system completed.

[Normal] From: SMISA@wildfire.syncer.de “SMISA” Time: 05.09.2015 21:01:37

    Checking the HP 3PAR provider using this

    connection data:

        Host:        blackhawk.syncer.de

        User:        3paradm

        Namespace:    root/tpd

        Port:        5989

        SSL mode:    TRUE

[Normal] From: SMISA@wildfire.syncer.de “SMISA” Time: 05.09.2015 21:01:37

    This HP 3PAR provider has access to the following unit:

        Name:        BLACKHAWK

        WWN:        2FF70002AC012345

        Description:    HP_3PAR 7200c, ID: 12345, Serial number: 1612345, InForm OS version: 3.2.1 (MU3)

[Normal] From: VEPALIB_VMWARE@wildfire.syncer.de “/DC” Time: 05.09.2015 21:01:41

    Virtual Machine ‘JETDCM02’: Locking vMotion …

[Normal] From: VEPALIB_VMWARE@wildfire.syncer.de “/DC” Time: 05.09.2015 21:01:42

    Creating folder O:\OmniBack\tmp\87617826-f627-4235-bdae-3e74df58933f …

[Normal] From: VEPALIB_VMWARE@wildfire.syncer.de “/DC” Time: 05.09.2015 21:01:43

    Virtual Machine ‘JETDCM02’: Backing up configuration file JETDCM02.vmx …

[Normal] From: VEPALIB_VMWARE@wildfire.syncer.de “/DC” Time: 05.09.2015 21:01:45

    Virtual Machine ‘JETDCM02’: Creating snapshot …

[Normal] From: SMISA@wildfire.syncer.de “SMISA” Time: 05.09.2015 21:01:47

    Creation of replica started on host wildfire.syncer.de.

[Normal] From: SMISA@wildfire.syncer.de “SMISA” Time: 05.09.2015 21:01:47

    Creating a replica as user “3paradm” for the following volume:

        Source volume:    VMFS_STORE_SSD_000

        Replica name:    DP-2015.09.05-14-055EB3C1B

        Replica type:    Demand allocated snapshot

        Raid level:        RAID5

        Target CPG:        CPG_SSD_R5

[Normal] From: SMISA@wildfire.syncer.de “SMISA” Time: 05.09.2015 21:01:48

    Creation of replica on host wildfire.syncer.de completed.

[Normal] From: VEPALIB_VMWARE@wildfire.syncer.de “/DC” Time: 05.09.2015 21:01:51

    Virtual Machine ‘JETDCM02’: Removing snapshot …

[Normal] From: SMISA@wildfire.syncer.de “SMISA” Time: 05.09.2015 21:01:55

    Creating a presentation as user “3paradm” for the following storage volume:

        Volume:            DP-2015.09.05-14-055EB3C1B

        Host:                neptun.syncer.de

        Presentation type:    Host Sees

        Array port:            –

[Normal] From: SMISA@wildfire.syncer.de “SMISA” Time: 05.09.2015 21:01:56

    Creating a presentation as user “3paradm” for the following storage volume:

        Volume:            DP-2015.09.05-14-055EB3C1B

        Host:                wildfire.syncer.de

        Presentation type:    Host Sees

        Array port:            –

[Normal] From: SMISA@wildfire.syncer.de “SMISA” Time: 05.09.2015 21:01:56

    Starting drive scan.

[Normal] From: SMISA@wildfire.syncer.de “SMISA” Time: 05.09.2015 21:02:30

    Drive scan has completed.

[Normal] From: VEPALIB_VMWARE@wildfire.syncer.de “/DC” Time: 05.09.2015 21:02:52

    Mounting datastores to host ‘NEPTUN.syncer.de …

[Normal] From: VEPALIB_VMWARE@wildfire.syncer.de “/DC” Time: 05.09.2015 21:03:34

    Virtual Machine ‘JETDCM02_DP’: Register VM …

[Normal] From: VEPALIB_VMWARE@wildfire.syncer.de “/DC” Time: 05.09.2015 21:03:36

    Virtual Machine ‘JETDCM02’: Getting Changed Blocks for disk scsi0:0.

[Normal] From: VEPALIB_VMWARE@wildfire.syncer.de “/DC” Time: 05.09.2015 21:03:49

    Virtual Machine ‘JETDCM02’ (UUID ‘423cd44d-82f5-9bf5-4842-f763db4f5994’): Starting full backup …

[Normal] From: BMA-NDMP@wildfire.syncer.de “B2D_ESX_wildfire [GW 48572:0:7712191451340901461]” Time: 05.09.2015 21:03:50

    STARTING Media Agent “B2D_ESX_wildfire [GW 48572:0:7712191451340901461]”

[Normal] From: BMA-NDMP@wildfire.syncer.de “B2D_ESX_wildfire [GW 48572:0:7712191451340901461]” Time: 05.09.2015 21:03:51

    Loading medium from slot \\COFC-CZ1234567801\B2D_ESX\4e3972f0_55eb3c97_17ec_021d to device B2D_ESX_wildfire [GW 48572:0:7712191451340901461]

[Normal] From: OB2BAR_VEPA_BAR@wildfire.syncer.de “/DC” Time: 05.09.2015 21:03:55

    Starting OB2BAR Backup: aero.syncer.de:/4/aero.syncer.de%2F503c437f-844a-6608-3b6b-9dc88c4be20b “VEAgent”

[Normal] From: VEPALIB_VMWARE@wildfire.syncer.de “/DC” Time: 05.09.2015 21:03:55

    Virtual Machine ‘JETDCM02_DP’: Backing up …

        Disk: scsi0:0

        Transport method: SAN

        Disk buffer: 8 MB

[Normal] From: VEPALIB_VMWARE@wildfire.syncer.de “/DC” Time: 05.09.2015 21:03:55

    Virtual Machine ‘JETDCM02_DP’: Disk ‘scsi0:0’ datastore information

        Datastore: snap-34256751-BLACKHAWK_VMFS_SSD_000

        Datastore type: VMFS

        Datastore Storage WWN: 60002ac0000000000000007b00014e9e

[Normal] From: BSM@wildfire.syncer.de “VEA_BLACKHAWK_ZDB” Time: 05.09.2015 21:12:20

    Target-side Deduplication Statistics for aero.syncer.de:/4/aero.syncer.de%2F503c437f-844a-6608-3b6b-9dc88c4be20b “VEAgent”.

    Using device: “B2D_ESX_wildfire [GW 48572:0:7712191451340901461]@wildfire.syncer.de”:

        Mbytes Total: …………….. 86700 MB

        Mbytes Written to Disk: ……. 500 MB

        Deduplication Ratio: ………. 173.4 : 1

[Normal] From: OB2BAR_VEPA_BAR@wildfire.syncer.de “/DC” Time: 05.09.2015 21:12:22

    Backup Profile:

        Run Time ……….. 0:08:28

        Backup Speed ……. 170,55 MB/s

[Normal] From: OB2BAR_VEPA_BAR@wildfire.syncer.de “/DC” Time: 05.09.2015 21:12:22

    Completed OB2BAR Backup: aero.syncer.de:/4/aero.syncer.de%2F503c437f-844a-6608-3b6b-9dc88c4be20b “VEAgent”

[Normal] From: VEPALIB_VMWARE@wildfire.syncer.de “/DC” Time: 05.09.2015 21:12:27

    Virtual Machine ‘JETDCM02_DP’: Unregister VM …

[Normal] From: VEPALIB_VMWARE@wildfire.syncer.de “/DC” Time: 05.09.2015 21:12:37

    Virtual Machine ‘JETDCM02’: Unlocking vMotion …

[Normal] From: BSM@wildfire.syncer.de “VEA_BLACKHAWK_ZDB” Time: 05.09.2015 21:12:49

    OB2BAR application on “wildfire.syncer.de” disconnected.

[Normal] From: SMISA@wildfire.syncer.de “SMISA” Time: 05.09.2015 21:12:49

    Resuming the backup system.

[Normal] From: SMISA@wildfire.syncer.de “SMISA” Time: 05.09.2015 21:12:49

    Removing a presentation as user “3paradm” for the following storage volume:

        Volume:    DP-2015.09.05-14-055EB3C1B

        Host:        WILDFIRE

[Normal] From: SMISA@wildfire.syncer.de “SMISA” Time: 05.09.2015 21:12:50

    Removing a presentation as user “3paradm” for the following storage volume:

        Volume:    DP-2015.09.05-14-055EB3C1B

        Host:        NEPTUN

[Normal] From: SMISA@wildfire.syncer.de “SMISA” Time: 05.09.2015 21:12:51

    Starting drive scan.

[Normal] From: SMISA@wildfire.syncer.de “SMISA” Time: 05.09.2015 21:13:41

    Drive scan has completed.

[Normal] From: SMISA@wildfire.syncer.de “SMISA” Time: 05.09.2015 21:13:42

    The backup system was successfully resumed.

[Normal] From: SMISA@wildfire.syncer.de “SMISA” Time: 05.09.2015 21:13:42

    COMPLETED SMIS-Application agent on wildfire.syncer.de.

[Normal] From: SMISA@wildfire.syncer.de “SMISA” Time: 05.09.2015 21:13:42

    COMPLETED SMIS-Backup agent on wildfire.syncer.de.

[Normal] From: BMA@wildfire.syncer.de “B2D_ESX_wildfire [GW 48572:0:7712191451340901461]” Time: 05.09.2015 21:13:50

    Unloading medium to slot \\COFC-CZ1234567801\B2D_ESX\4e3972f0_55eb3c97_17ec_021d from device B2D_ESX_wildfire [GW 48572:0:7712191451340901461]

[Normal] From: BMA@wildfire.syncer.de “B2D_ESX_wildfire [GW 48572:0:7712191451340901461]” Time: 05.09.2015 21:13:50

    COMPLETED Media Agent “B2D_ESX_wildfire [GW 48572:0:7712191451340901461]”

[Normal] From: BSM@wildfire.syncer.de “VEA_BLACKHAWK_ZDB” Time: 05.09.2015 21:13:50

    Backup Statistics:

        Session Queuing Time (hours) 0,00

        ——————————————-

        Completed Disk Agents …….. 1

        Failed Disk Agents ……….. 0

        Aborted Disk Agents ………. 0

        ——————————————-

        Disk Agents Total ……….. 1

        ===========================================

        Completed Media Agents ……. 1

        Failed Media Agents ………. 0

        Aborted Media Agents ……… 0

        ——————————————-

        Media Agents Total ………. 1

        ===========================================

        Throttled Gateways ……….. 0

        Gateways Total …………… 1

        ===========================================

        Overall Deduplication Ratio .. 173.4 : 1

        ===========================================

        Mbytes Total …………….. 86700 MB

        Used Media Total …………. 1

        Disk Agent Errors Total …… 0

Perform a Power On Restore

Compared with the preparation the Power On is quite simple. Select the VM from the list of available backups. In case the VM is located on a Smart Cache device OR it was backed up in a ZDB session with Instant Recovery option additional VM Options are displayed. You will be able to Restore, Power On or Live Migrate the VM. The Restore button will change accordingly to Power On or Live Migrate to indicate your selection. You don’t need to change the destination or VM name, since the VM will be made available with a temporary name and network disconnected. The Power On will just take a few seconds to present and register the VM in vCenter.

A VM that has been Powered On will be removed automatically after 24 hours in case it was not migrated elsewhere. This is done as a general cleanup procedure triggered by daily maintenance. Information is logged to the poweronvms_cleanup.log on the Cell Manager.