VMware server 2.0.1 backups w or w/o backupexec? or w/vmrun.exe?

backup exec 12.5 (the VMware agent) crashes the guest OSs running in VMware server 2.0.1 with the following msg:
msg.vmxaiomgr.retrycontabort.rudeunplug:operation - see screenshot below

we are now considering vmrun.exe

can we use it to suspend or pause the VMs before backexec runs?   which is most appropriate?

or is there any east way to do this.

unfortunately the VMware agent for backup exec wont recognize VMware server 2.0.1 guest OSs
Who is Participating?
rastafarayConnect With a Mentor Author Commented:
thank you all.

we decided to use vmrun to suspend the VMs and start them after the backup has completed.

thanks again for your input
vmrun execute commands in the virtual machine, isn't? So you can't stop, start, suspend virtual machines with it. Use vmware-cmd command instead, like:
vmware-cmd <vm.vmx> suspend
to suspend the virtual machine.
rastafarayAuthor Commented:
i understand.   i guess my Q is more General.  how do VMware server users backup their VMs in w/BackupExec ?

so they simply suspend the VM prior to BackupExec starting the job and later resume once it ends?

Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

A customer of my once used vmware server for production servers (i normally advice ESX and VCB -or tools which uses the same techniqeus-). THis customer suspended the virtuals with vmware-cmd and then backupped the whole server. One configuration used pre and post backupjobs (suspend and start), the other suspended the vm's at 18:00 and the backup started 15 minutes later, after the backup the server rebooted and with a scheduled job the vm's were started.
In one of the customer i supported, they have dedicated NIC & dedicated ip network to backup the VMs managed by a cell server
Instead of backup the vm files, each vm is configured to have its own backup agent and backup thru network
No problem with this method as the backup is running within each guest OS
Traditional backup that works fine
If a backup agent is installed in the virtual machine, a good thing is to work with a dedicated backup lan. But if you have a large server with a lot of data, everything is transported over the lan (much traffic) you should keep in mind of congestion in the network. And offcourse create a good backup schedule (not all the virtuals on the same host at once, but on different times).
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.