In VMware - Clone a server for testing purpose -Powered on state or Poweroff state
Hi
We use VMware Vsphere 6.7 and have an application that runs on SQL database and unfortunately, we have problems with this database server.
I have been asked by the application vendor to run some patches and detach the database and again attach the database.
Rather than running these patches on the actual server, I thought of cloning the SQL server and run the patches and detach and attach the database on the cloned server and if the issue gets resolved, I can shut down the old server.
As it is Sunday today, no one will be using the server.
Do I need to clone or snapshot?
Also, do I need to do this while the server is powered on or in a shutdown state?
Please suggest appropriate steps and thank in advance.
ASKER
The issue we have is the application that is installed in the SQL server, has a system manager, and when resetting the user password, it throws an error.
The server nic is VMXNET 3
There is a DMZ and Testing network and I can clone it to this network and it isolates from the production network
I assume after cloning i can power on the server and run the patches and detach and attach the DB and open the application on the server and try a password reset.
If the application works ok, I can delete the old SQL server and move the cloned server to the production network?
Please advise...
Thanks
What is the error reported?
What does the patch patch?
Is it patching the appkication of the vendor?
ASKER
After cloning the SQL server -Detach the database and again attach the database.
The application works fine now :)
Thank guys again for your timely help and support, much appreciated.
SQL (Structured Query Language) is designed to be used in conjunction with relational database products as of a means of working with sets of data. SQL consists of data definition, data manipulation, and procedural elements. Its scope includes data insert, query, update and delete, schema creation and modification, and data access control.
TRUSTED BY
making a clone will create an additional vm of the current system
a snapshot will just create a checkpoint of the existing vm
if you don't have the ability to test patches in a test environment, then I would create a snapshot then install your patches
if something doesn't work, you can easily revert the snapshot and be back to where you were before
as far as powered on or off, doing it while powered off is obviously the cleanest though I have restored guests to a test environment with a powered-on snapshot with no issues
with a clone, you get an exact image of the vm though now you have a duplicate server with a duplicate address, etc. that you don't want on your production network to test with