Hyper-V Backup - How to bind to a specific management class?

[cmoeller]

Hi everyone!

I have not been a 'TSM guy' for a long time but ever since then adsm.org has always provided me with valuable answers. For the problem at hand however I could not find anything so it was finally time to register. So hi!

We are using Server 2008 R2 based Hyper-V proxies. I am now trying to implement the BA client's Hyper-V backup capability (which I have just discovered) but have run in to a (seemingly) simple problem I have not found a solution for - how in the world can I bind Hyper-V backups to a specific management class?

I really, really don't want this on the default management class and the parameter VMMC applies only to VMWare backups (so says the reference).

Is this correct? Can Hyper-V backups indeed be backed up only to the TSM server's default management class? Or did I miss something?

Thank you!

Regards,
Chris

*edit* Damn I missed there's a sub forum for virtual machines. Could a mod move my topic? Sorry for that!

[cmoeller]

Oh the cruelty when hope for enlightenmend is crushed by spam.


On topic though, I have not found a way yet. Letting in run into the default management class and define a maxsize of ~20GB to it is not a solution I'd call clean. Maybe it is, I don't know, yet I appears wrong somehow ...

Guess I have to wait and see what future updates bring.

[pbarnard]

You have probably found a solution to this by now, but I can share what I have done in the past...but it still may not be the best solution. I ended up creating a new policy domain specifically for the virtual host servers that utilize Hyper V. I created a default management class that met my needs on space requirements and then configured my host servers to use that new policy domain.

Like I said, probably not the best solution, but for the most part has worked for us.

[cmoeller]

You have probably found a solution to this by now, but I can share what I have done in the past...but it still may not be the best solution. I ended up creating a new policy domain specifically for the virtual host servers that utilize Hyper V. I created a default management class that met my needs on space requirements and then configured my host servers to use that new policy domain.

Like I said, probably not the best solution, but for the most part has worked for us.

Hm I like your idea a lot better than mine. I've not been using TSM's "hyper-v backup" method by the way. Some virtual machines, for whatever reason, seem to have some sort of problem with VSS - in which case TSM suspends the machine to back it up. I cannot have that on production machines so for now I'm still doing the dirty file-level backup of the virtual disks.

I have not found a switch for TSM to just skip and report these so that I could "dirty-backup" only those.

Well what can you get for not using VMWare I suppose ...