Can't connect after cloning using VMWare standalone converter

  • I've created a P2V clone of a Windows 2008 server running SQL Server 2008 R2. I used VMWare Standalone Converter to do the clone. The intention was to use the clone as a backup in the event of a hardware failure with the physical server, so the clone would have the same machine name, IP address, etc.

    When I fire up the clone VM I can't connect to the database instance using SSMS - I get "cannot connect to (local)....A network-related or instance-specific error occurred..."

    I've done a little searching and there are references to doing a sysprep when cloning a SQL Server. Is this required to achieve what I want, or is there a workaround for the problem that I'm having connecting to the DB on the clone?

Viewing 0 posts

You must be logged in to reply to this topic. Login to reply