Oct 4

I’ve been researching Tivoli Storage Manager a bit lately and have some good information to report. VMware API for Data Protection, or VADP for short, is VMware’s replacement for VCB. In some ways this is completely new and in others it is going to be very familiar.

You have to still use a proxy both ways. For full images you use a hardware proxy and vcb. For file level you can use a Windows Virtual Machine with the 6.2.1 client to backup other Windows VM’s. The last row in this table is incredibly vague in all honesty. http://www-01.ibm.com/support/docview.wss?uid=swg21426059.

If you are only interested in file level backups of your vm’s, you will likely be happy with TSM’s integration to date with VADP. You’ll want the 6.2.1 windows client loaded on a windows VM. I used Windows 2008 R2. In this proxy machine you have to do some configurations. You cannot use the GUI to do the actual backup. The backup has to be ran just like VCB “dsmc backup vm”. At this point in vCenter you should see a snapshot made for the machine you are backing up. You also will soon see the proxy machine reconfigured with that machines vmdk mounted. To see some of the configs in the GUI open the 6.2.1 GUI (i’m using windows). Click on Edit, client preferences, vm backup. You will see on the right where you point it to virtual center. List vm’s to backup and select the style. Once this is done you can operate this new proxy vm just as you did your VCB box. Some nice features are backup all windows vm’s and then the ability to do a minus vm “-vm ” to exclude some vm’s.

Some missing features are things like auto detecting new VM’s and backing them up. The “All-Windows” selection in TSM will catch the new VM’s but it will fail to back them up because they do not have a node in the TSM server. Also your proxy node has not been granted access to back them up in TSM server. I am playing with some ways to script this but hopefully this is already on Tivoli’s roadmap.

Now if you want image level backups you are in for a surprise. TSM does not currently support VADP for image level backups. I currently do not do image level backups for production (that’s what replication is for I always said). I am now thinking of doing them simply to have another method to protect data.

If you have any issues please feel free to post a comment. I would love to hear how others are using TSM and VADP.


Jul 26


It seems I am always upgrading tape formats in an effort to keep up with my growth. I have decided it would be best for the procedure I follow to be well documented. I use Atape for the drives and I use the Tivoli Storage Manager driver for the library. This is the method I follow for configuring the drives.

1) From TSM:
Save the output from the device queries, and save the current device configuration (the filename is optional):

query library
query drive f=d
query path f=d
query devclass f=d
backup devconfig [ filename=devconfig.bak ]

2) From AIX:
List the tape devices:

lsdev -Cc tape

Remove the drive and library device names:

rmdev -dl

For example, if the drive device name is /dev/rmt1:

rmdev -dl rmt1

3) Upgrade Atape
Ftp the Atape driver in binary mode from ftp://index.storsys.ibm.com/devdrvr/AIX or ftp://ftp.software.ibm.com/storage/devdrvr/AIX

Remove the older Atape driver (optional):

installp -u Atape.driver

Install and commit the Atape driver. For example, if you downloaded the file to /tmp/Atape.12.0.8.0.bin:

installp -acXd /tmp/Atape.12.0.8.0.bin all

Configure the tape device:

cfgmgr -v

(-v is not required but will show where it hangs if it does)

Verify the new devices are Available:

lsdev -Cc tape

(Note: While not always absolutely necessary, it is strongly recommended to reboot the system after upgrading the Atape.driver)

4) From TSM:
While it is recommended to remove and redefine the paths after any hardware change, including upgrading Atape.driver, sometimes it is not necessary to do anything else after upgrading Atape. If the activity log reports I/O errors for the library or drives, sometimes it is only necessary to force the TSM server to communicate with the drives to resolve them:

update path srctype=server desttype=drive library= device= online=yes

If this does not resolve the I/O errors, then continue with steps 5-7.

5) Delete the drive and library paths
For each drive:

delete path srctype=server desttype=drive library=

For the library:

delete path srctype=server desttype=library

6) Redefine the drive and library paths

define path srctype=server desttype=library device=/dev/ online=yes
define path srctype=server desttype=library library= devicename=/dev/ online=yes

(Use the devconfig file as a guide for the definitions.)

References:
IBM Tivoli Storage Manager for AIX Administrator’s Reference
Atape device driver README ftp://index.storsys.ibm.com/devdrvr/AIX/README


Apr 14

If you are using the new 6.1 client you can use the 5.5 odbc driver. Tested and working on vista x64.


« Previous Entries