how to write network path in log shipping

In the event of a disaster affecting your database, you can recover the secondary database (recover is a fancy word for “make it active and available for changes”) and point your vCenter server to it. Those transactions are then restored to the secondary database on another defined interval. Both a cost effective and relatively easy way to provide both a backup of the database and hot spare of the SQL instance, Log Shipping is basically what it sounds like – transaction logs are copied over to a staging folder on a defined interval.

While there are many different ways to accomplish this, I thought it was worth covering one of the more simple methods: Log Shipping. Now, with all sorts of various plugins (such as VAAI for NFS) and applications (such as VMware View) relying on vCenter, it may be a good time to analyze your vCenter’s availability and adjust your plans.

Outages were not that big of a deal, and impacted (mostly) the Admin team. To me, vCenter was traditionally more of a management tool that provided central administration of the cluster. As VMware vCenter continues to rise in importance in most people’s data center stack, the need to protect it from disaster becomes more important.

How to write network path in log shipping