wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Add a second node for long term retention ======

Monthly backups of VMware guests (LogTerm retention)

===== Problem =====

This document provides information on the configuration of Monthly backups of VMware guests with Tivoli Storage Manager for Virtual Environmments.
Symptom

This document assumes that you already configured incremental forever incremental backups. The intent of this document is to provide instructions on how to perform Monthly backups in addition to the already configured daily backups.

===== Resolving The Problem ===== 

In this environment, the following configuration is used on the Tivoli Storage Manager server :

  Domain name          : VEDOMAIN
  vCenter node name    : TSMVE_VC
  Datacenter node name : TSMVE_DC
  Datamover node name  : TSMVE_DM
  VMCLI node name      : TSMVE_VMCLI

The above nodes are registered in the VEDOMAIN and the default management class in the VEDOMAIN uses the following backup copygroup settings :
<cli>
   Policy Domain Name: VEDOMAIN
      Policy Set Name: ACTIVE
      Mgmt Class Name: VEMGMT
      Copy Group Name: STANDARD
      Copy Group Type: Backup
 Versions Data Exists: 31
Versions Data Deleted: 1
Retain Extra Versions: 31
  Retain Only Version: 31
</cli>

The following proxy configuration is used :
<cli>
Target Node         Agent Node
---------------     ---------------------------------------------
TSMVE_DC            TSMVE_DM TSMVE_VMCLI
TSMVE_VC            TSMVE_DC TSMVE_VMCLI
</cli>

In order to use different backup retention settings for Monthly backups, it is necessary to use a different datamover node and different datacenter node. Use the below steps to implement this.

==== Step1 Create the new domain ====

First I created a new domain (VEMONTHLY) in which you can configure the backup copygroups to keep 12 backup versions and to keep them around for 365 days. Use the below Tivoli Storage Manager server administrative commands :
<cli>
define do VEMONTHLY
define po VEMONTHLY VEPOLICY
define mg VEMONTHLY VEPOLICY VEMGMT
define co VEMONTHLY VEPOLICY VEMGMT verexists=12 verdeleted=1 retextra=365 retonly=365
assign defmgmt VEMONTHLY VEPOLICY VEMGMT
activate po VEMONTHLY VEPOLICY
</cli>

==== Step2 Register new nodes in the new domain and grant proxy ==== 

Register the new datamover and datacenter client nodes in the new domain. For example :
<cli>
register node TSMVE_DCMONTHLY <password> do=VEMONTHLY
register node TSMVE_DMMONTHLY <password> do=VEMONTHLY
grant proxy target=TSMVE_DCMONTHLY agent=TSMVE_DMMONTHLY,TSMVE_VMCLI
grant proxy target=TSMVE_VC agent=TSMVE_DCMONTHLY
</cli>

==== Step3 Create a new schedule for Monthly backups ==== 

Define a client schedule and association using the following two Tivoli Storage Manager server administrative commands :

1) Create schedule :
  DEFINE SCHEDULE VEMONTHLY MONTHLY-IFFULL Type=Client ACTion=Backup SUBACTion=VM OPTions='-vmfulltype=vstor -vmbackuptype=fullvm -asnodename=TSMVE_DCMONTHLY -domain.vmfull="VM=MY-TEST-REDHAT" -MODE=IFFull' STARTDate=10/31/2014 STARTTime=08:00:00 SCHEDStyle=Enhanced WEEKofmonth=first DAYofweek=Sunday

2) Create association :
  DEFINE ASSOCIATION VEMONTHLY MONTHLY-IFFULL TSMVE_DMMONTHLY

Adjust the -domain.vmfull="VM=MY-TEST-REDHAT" parameter to backup the VM guests you want. In this example, the VM named "MY-TEST-REDHAT" will be backed up by the schedule. Also adjust the schedule date/time to meet your requirements. In this example, the VM guest will be backed up every the Sunday of the first week of the month at 08:00 AM.

Note that the schedule uses -MODE=IFFull to perform an "incremental forever full backup (IFFULL)" backup. This is necessary so not to interfere with the "Change Block Tracking (CBT)" mechanism used by the daily "incremental forever incremental backup (IFINCR)" backups.

==== Step4 Create the new services on the Windows datamover ==== 

First create a new options file (dsm.TSMVE_DMMONTHLY.opt) for the new datamover. The options file should use unique ports and log names and should use the newly created datamover node. For example :
<cli>
NODename TSMVE_DMMONTHLY
PASSWORDAccess generate
MANAGEDServices schedule webclient
TCPServeraddress <ip address>
TCPPort 1500
COMMMethod tcpip
ERRORLOGName "C:\Program Files\Tivoli\TSM\baclient\dsmerror.TSMVE_DMMONTHLY.log"
SCHEDLOGName "C:\Program Files\Tivoli\TSM\baclient\dsmsched.TSMVE_DMMONTHLY.log"
schedmode prompted
httpport 1584
webports 1585 1586
VMCHost <hostname>
VMCUser <user>
VMFULLTYPE VSTOR
VMBACKUPType FUllvm
</cli>

Then, use the newly created options file and encrypt the client password. Run the following command from the "C:\Program Files\Tivoli\TSM\baclient" directory :

  dsmc q fi -optfile=dsm.TSMVE_DMMONTHLY.opt

Make sure to specify the newly created options file name on the -optfile parameter. You will be prompted for the node password. Once this is done, rerun the same command again to confirm you are no longer prompted for the password.
Then, create the datamover services. From the "C:\Program Files\Tivoli\TSM\baclient" directory, run the below commands.

1) Create the client acceptor service
<cli>
dsmcutil install cad /name:"TSM CAD - TSMVE_DMMONTHLY" /node:TSMVE_DMMONTHLY /password:XXX /optfile:"C:\Program Files\Tivoli\TSM\baclient\dsm.TSMVE_DMMONTHLY.opt" /cadschedname:"TSM Sched - TSMVE_DMMONTHLY" /autostart:yes
</cli>

2) Create the agent service
<cli>
dsmcutil install remoteagent /name:"TSM Agent - TSMVE_DMMONTHLY" /node:TSMVE_DMMONTHLY /password:XXX /optfile:"C:\Program Files\Tivoli\TSM\baclient\dsm.TSMVE_DMMONTHLY.opt" /partnerName:"TSM CAD - TSMVE_DMMONTHLY" /startnow:no
</cli>

3) Create the scheduler service
<cli>
dsmcutil install scheduler /name:"TSM Sched - TSMVE_DMMONTHLY" /node:TSMVE_DMMONTHLY /password:XXX /optfile:"C:\Program Files\Tivoli\TSM\baclient\dsm.TSMVE_DMMONTHLY.opt" /autostart:no /startnow:no
</cli>

In above commands, provide the node password for node TSMVE_DMMONTHLY in /password:XXX.
This completes the Monthly backup configuration.

In order to restore a Monthly backups, follow the steps below.

Restoring using the Backup-Archive client GUI or command line.

To achieve this, you would create a new options file (dsm.TSMVE_DCMONTHLY.opt) based on the previous one created in previous steps. This new options file would include the ASNODENAME option to specify the newly created datacenter node name. For example :
<cli>
NODename TSMVE_DMMONTHLY
asnodename TSMVE_DCMONTHLY
PASSWORDAccess generate
MANAGEDServices schedule webclient
TCPServeraddress <ip address>
TCPPort 1500
COMMMethod tcpip
ERRORLOGName "C:\Program Files\Tivoli\TSM\baclient\dsmerror.TSMVE_DCMONTHLY.log"
SCHEDLOGName "C:\Program Files\Tivoli\TSM\baclient\dsmsched.TSMVE_DCMONTHLY.log"
schedmode prompted
httpport 1587
webports 1588 1589
VMCHost <hostname>
VMCUser <user>
VMFULLTYPE VSTOR
VMBACKUPType FUllvm
</cli>

Then, you would start the TSM Backup-Archive client GUI from the "c:\program files\tivoli\tsm\baclient" directory using the following command :

  dsm -optfile=dsm.TSMVE_DCMONTHLY.opt

From the GUI, you would select "Actions/Restore VM" from the GUI menu. From there, you will be to select the IFFULL backup to restore.
You can also create a shortcut for the GUI on your desktop. You would use the following parameters in the shortcut tab :

    Target
    "C:\Program Files\Tivoli\TSM\baclient\dsm.exe" -optfile=dsm.TSMVE_DCMONTHLY.opt
    Start in :
    "C:\Program Files\Tivoli\TSM\baclient"


Restoring using the VMware vSphere client, VMware Web client or TSM for VMware UI

To achieve this, you would need to update the vmcliprofile file prior to starting any
of the above interfaces. The file is located here :

  C:\Program Files (x86)\Common Files\Tivoli\TDPVMware\VMwarePlugin\scripts

You would comment out the current VE_DATACENTER_NAME option and add a new VE_DATACENTER_NAME option using the TSMVE_VEMONTHLY datacenter name. For example :

  # VE_DATACENTER_NAME DATACENTERNAME::TSMVE_DC
  VE_DATACENTER_NAME DATACENTERNAME::TSMVE_DCMONTHLY

The Data Protection for VMware vSphere GUI does not support data centers with the same name in the vCenter so this is why it is necessary to update the vmcliprofile.

You would then start the VMware vSphere client, VMware Web client or TSM for VMware UI client and do the restore. When the restore is done, update the vmcliprofile file again to specify the original VE_DATACENTER_NAME option used.
wiki

User Tools

Site Tools

Page Tools
