asked on
Finding Sql database files in use
Trying to minimize downtime that will occur during a P2V of a 6 year old SQL server
The SQL server was originally setup as a SQL 2005 2-node cluster, but one of the two physical servers died last month, so only one server is left in the cluster. It's been using a very slow SAN with 20 mapped drives with a total size of 3TB
My first attempts to virtualized with vCenter converter failed because the estimated time for the P2V was around 25 days over our wan link
I'm trying to find out which of the files on the server are actually being accessed/used by the database server once it boots and SQL services starts running
If I can find this list of files, I will do a P2V only with the necessary drives , and copy the rest (non-critical) files after the P2V is complete. I believe most of the server data on the mapped drives is backup data
Thanks
The SQL server was originally setup as a SQL 2005 2-node cluster, but one of the two physical servers died last month, so only one server is left in the cluster. It's been using a very slow SAN with 20 mapped drives with a total size of 3TB
My first attempts to virtualized with vCenter converter failed because the estimated time for the P2V was around 25 days over our wan link
I'm trying to find out which of the files on the server are actually being accessed/used by the database server once it boots and SQL services starts running
If I can find this list of files, I will do a P2V only with the necessary drives , and copy the rest (non-critical) files after the P2V is complete. I believe most of the server data on the mapped drives is backup data
Thanks
Microsoft SQL Server 2005Microsoft SQL ServerWindows Server 2003
Last Comment
Deepak Chauhan
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
What about adding a virtual node to the cluster? Then install the SQL Server there and make a failover from Physical node to the virtual one. Now you can get rid of the Physical node and add a 2nd virtual node to the cluster. Only downtime will be during the failover.
ASKER
Thanks deepakChauhan sounds exactly like what I'm looking for.
Vitor_montalvao, I can't do that as the new virtual nodes don't have access to the same old storage system , they use new storage
Vitor_montalvao, I can't do that as the new virtual nodes don't have access to the same old storage system , they use new storage
Hi sk391,
Have you done with it or need more help?
Have you done with it or need more help?