Hello Wanda

Have you verified that the account you're using on vCenter has all the 
necessary permissions/roles?

http://www-01.ibm.com/support/docview.wss?uid=swg21497028

Best regards,

Michael Ryder
Senior Systems Infrastructure Administrator

Roche Molecular Systems, Inc.
Information Technology
1080 US Highway 202S 
Building 500/2532
Branchburg, NJ 08876-3733, USA
Phone: +1 908 253 7942
Fax: +1 908 253 7651
mailto: michael_s.ryder AT roche DOT com
www.roche.com

Confidentiality  Note: 
This message is intended only for the use of the named recipient(s) and may 
contain confidential and/or proprietary information. If you are not the 
intended recipient, please contact the sender and delete this message. Any 
unauthorized use of the information contained in this message is prohibited.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Prather, Wanda
Sent: Monday, December 10, 2012 11:17 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] VE 6.4 Testing - think & thin

Testing VE 6.4 on TSM server 6.3.2 Win2K64.  ESX hosts are VSphere 5.

So on the first VE backup we see as expected:

12/10/2012 05:18:22 TSM for Virtual Environments TDP VMware 6.4.0.00
12/10/2012 05:19:01 ANS1711W Incremental backup selected for 'HHHHH', but a 
Full backup has not yet been performed. Performing a Full backup instead.
.
Then we see
.
.
12/10/2012 05:20:14 ANS9384W Unable to get VMware Changed Block Tracking(CBT) 
data for virtual machine 'HHHHH'. Full VM backup continues, and includes both 
used and unused areas of the disk.

The "unable to get VMWare CBT data" is also expected on the first backup.  But 
I thought with VE it was supposed to be smart enough not to include unused 
areas of the disk?

We've checked with show VM all:  CBT is enabled, and subsequent backups are 
true incrementals.
We've also tried blowing the filespace away and starting over with the same VM, 
same results.

The problem is that these are thin-provisioned disks.
When you get this first full including all the unused space, then when you 
restore the VM, it comes back as full sized, no longer thin-provisioned, with 
the possibility of blowing out the datastore and causing a nasty outage.

Anybody got a solution?

Wanda


Wanda Prather  |  Senior Technical Specialist  | Wanda.Prather AT icfi DOT com  
|  www.icfi.com
ICF International  | 401 E. Pratt St, Suite 2214, Baltimore, MD 21202 | 
410.539.1135 (o)