Q
Get started Bring yourself up to speed with our introductory content.

How to troubleshoot VMware vSphere Replication issues

When problems occur with the tool you use to protect your data, it's imperative to track down the logs that can help restore order.

Logs are a principal source of troubleshooting information -- especially in complex environments with important...

hardware and software interdependencies. VMware's vSphere Replication is the company's hypervisor-based data protection product. A virtual appliance provides detailed logs that can help diagnose potential issues in-house or when communicating with support staff from VMware.

As an example, the hms-configtool.log file located in the /opt/vmware/hms/logs/ folder can reveal problems with vSphere Replication connecting to SQL Server. The same log might also show errors reporting problems supporting DB2 or other database applications. The boot.msg log can report start up problems, which might indicate system faults, connectivity problems or a host of other possible issues. Such logs can significantly shorten the time needed to isolate and resolve problems.

Logs can be accessed through the Replication appliance's management interface using a Web browser. After entering the URL for the appliance's interface, click the vSphere Replication Management (VRM) tab, select Support, and then click Generate. This creates a .zip file of all the current vSphere Replication logs and provides a downloadable link. The .zip file should contain multiple logs from locations including:

/opt/vmware/hms/logs/

/opt/vmware/var/log/lighttpd/

/var/log/vmware/

/var/log/boot.msg

It should be possible to access vSphere Replication log files individually, though administrators might need to set permissions to access the log folders or gather logs automatically.

Logs can become extremely large, so a bit of log storage management may become necessary. VMware's vSphere Replication creates new logs when the log file reaches about 50 MB. Replication will retain about 10 older log packages and will remove the oldest log packages to make space for newer ones. This should minimize the need for manual intervention, but you can also opt to delete older log packages as desired by clicking Delete next to the log package you want to remove.

This was last published in March 2015

Dig Deeper on Backing up VMware host servers and guest OSes

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Join the conversation

4 comments

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.

What tool do you use when troubleshooting VMware applications?
Cancel
We use logs as the principal mechanism for troubleshooting VMware issues especially if the surrounding environments are complex and a lot has been invested in the hardware as well as software integration. Mostly, we connect to SQL server to run down the source. Our virtual appliance is able to create detailed logs that assist in diagnosing potential issues.
Cancel
VSphere replication is a pretty good tool, but there are better third party tools on the market, quite frankly. Veeam leaps to mind, among others.
Cancel
I was hoping for a little more detail than "Look at the logs." Anything in particular we should be looking for? What sort of settings do we need to use to ensure we're logging the right stuff without drowning ourself?
Cancel

-ADS BY GOOGLE

SearchServerVirtualization

SearchVirtualDesktop

SearchDataCenter

SearchCloudComputing

Close