TSM backing up additonal filespcae for VM's

[oguinna]

Hello:

We run our VM backups from a Windwos proxy server and we continue to see additional file spaces being backed up under the VM beyond c$,d$.

They tend to show as \\servername\1$ or 2$, 3$ and end up filling our disk storage pool.
The previous admin had been deleting them and I suspect this just causes TSM to increment the filespace from 0$ to 1$ etc.

Environment
Server 5.5
TSM client 6.2.4
ESX 4.0
Any suggestions would be greatly appreciated.

 

[TykneeTym]

If you're talking about using the Backup-Archive client on your vStorage proxy, you'll need to back it up when it's not running VMware backups. If you're using a VM as a proxy and using HotAdd you may need to go into the VM's properties and clean some things up as well. Also, don't do VM backups of your VM proxy server.

If you're saying that a "backup VM" operation is picking up other filesystems, that seems very strange. What transport are you using (SAN, HOTADD, NDB)? Are you doing FULLVM or FILEVM backups?

 

[oguinna]

In this case, we are doing filevm backups from our proxy server which isn't is VM. IBM is suggesting the use of CBT which I thought was only used for Fullvm backups. We are going to change a few VM's to use CBT and do some additional testing. We are also using SAN for transport.