Just an FYI: changing disks to "independent" will also result in them being excluded from any VMware snapshots as well.
~Rick Adamson Jax, FL. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Paul van Dongen Sent: Wednesday, July 21, 2010 8:58 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] partial VM images. Hello Steve, I did something like this some time ago. I had the Vmware admin set the database disks as "Independent", as this type of disk is not included in the VCB snapshots. I used a script to interface with vcbmounter but I think the BACKUP VM command would work as well. Regards, Paul -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Steve Harris Sent: woensdag 21 juli 2010 3:58 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] partial VM images. Hi All I have a VMware windows VM that I do daily VCB incrementals and Monthly VCB fulls on. It is thin-provisioned and now the real disk usage has expanded to the point where it exceeds the capacity of my proxy server's landing area. This particular VM runs SQL Server which is backed-up by dump to disk, and thence to TSM via VCB. There is no point in backing up the disk containing the databases, so I'm looking to exclude those disks from the monthly image and just backup C: and the dump disk. I can see no way to do this. The BACKUP VM command has no option to specify particular volumes. I tried -DOMAIN.IMAGE but that option was rejected. 6.2 has DOMAIN.VMFULL but that specifies which machines to back up not which disks. Does anyone know how it can be done? TSM Server is 5.5.3.0 Solaris X86_64 client is Windows 2008 and TSM 6.1.3.0, but could go to 6.2.1.x if this will solve the problem. Thanks Steve Steven Harris TSM Admin Paraparaumu, New Zealand