I believe one should not try to backup running VMs from the 'outside' without the proper tools that support that. You will not get a valid backup (just like you should not try to do a file backup from a SQL server database in that way).
Exclude the drive(s) holding the VM drives, memory maps etc, and backup the VM from within the server itself (just as you would with a physical server). No problems here, except for the odd VSS hang now and then. Cheers, Rick On Thu, Mar 14, 2013 at 4:42 PM, Vandeventer, Harold [BS] < [email protected]> wrote: > Yes..... significant hangs. > > TSM Server at 6.2.4. > TSM Client is 6.3.0. > > I'm not the HyperV manager, but I do know that D$ on that host holds the > virtual servers. > > If TSM client attempts to backup D$ the process stalls and never finishes. > > I don't know what, if any, work has been done by the node manager other > than exclude D$ as the immediate solution. The exclusion allows the backup > to complete, but obviously the virtual servers aren't in the backup. > > I just saw the advice re "vssadmin list writers". > > > > -----Original Message----- > From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf Of > Tim Brown > Sent: Thursday, March 14, 2013 8:57 AM > To: [email protected] > Subject: [ADSM-L] tsm and hyperv servers > > Is anyone experiencing an issue with using TSM to back up HyperV servers, > These servers seem to stop during the scheduled backups for no apparent > reason. > > > Thanks, > > Tim Brown > Supervisor Computer Operations > Central Hudson Gas & Electric > 284 South Ave > Poughkeepsie, NY 12601 > Email: [email protected]<mailto:[email protected]> <<mailto: > [email protected]>> > Phone: 845-486-5643 > Fax: 845-486-5921 > Cell: 845-235-4255 > > > "This message contains confidential information and is only for the > intended recipient. If the reader of this message is not the intended > recipient, or an employee or agent responsible for delivering this message > to the intended recipient, please notify the sender immediately by replying > to this note and deleting all copies and attachments." > > [Confidentiality notice:] > *********************************************************************** > This e-mail message, including attachments, if any, is intended for the > person or entity to which it is addressed and may contain confidential > or privileged information. Any unauthorized review, use, or disclosure > is prohibited. If you are not the intended recipient, please contact > the sender and destroy the original message, including all copies, > Thank you. > *********************************************************************** >
