Hello Remco,

I had this very same problem when we implemented TSM for VE when 6.4 came 
out.  I found that, during the snapshot process, the datamover tried to 
create a snapshot of itself, which caused the process to crash.  By 
design, the datamover will attempt to remove stale snapshot data when 
backup operations are started, which means that it tries to remove all 
mounted disks from the system that were added by the snapshot process. 
Unfortunately, this includes the datamover's own disk, which causes 
another crash.

And so the loop continues.

Snapshot data is stored in the windows\temp\vmware-inc folder.  You'll 
have to reboot the datamover into recovery mode so you can delete this 
folder.  It's locked during regular Windows boots.  Once that folder is 
deleted, you should be able to reboot into standard mode and perform 
scheduled (or GUI-initiated) backups normally.

Good luck and let us know how it goes!
__________________________
Matthew McGeary
Technical Specialist - Infrastructure
PotashCorp
T: (306) 933-8921
www.potashcorp.com




From:   Remco Post <[email protected]>
To:     [email protected]
Date:   04/13/2015 09:30 AM
Subject:        [ADSM-L] TSM 4 VE proxy crash
Sent by:        "ADSM: Dist Stor Manager" <[email protected]>



Hi All,

I’ve been struggling with a TSM4VE issue for the past few weeks and so far 
IBM has been unable to help me. We’re running TSM4VE on a virtual machine 
and made the mistake of having that VM make a VM backup of itself. Ever 
since, even now the VM is no longer included in the VM backups TSM 
attempts to detach the VM’s own active disks from the VM. Of course this 
is successful, but a windows VM without a system disk crashes within 
seconds. This only happens during scheduled backups that run as ’local 
system’, not when I attempt a VM backup manually using my own user 
account.

My hypothesis is that TSM somehow retains information about which disks is 
has hot-added to the VE proxy, but I don’t know where or how. And 
apparently, nor does my support engineer. How do I, apart from completely 
reinstalling the VE proxy, cleanup this mess?

This all is TSM 6.4.2.0 and TSM4VE 6.4.2.0 on windows 2008 r2.

-- 

 Met vriendelijke groeten/Kind Regards,

Remco Post
[email protected]
+31 6 248 21 622


Reply via email to