Help needed to expand virtual C drive in version 3.2.10

I have a client running Virtualbox v3.2.10  The host is Windows 7 pro and the guest is Windows 2000.
  The client has an ancient medical records system which stores data into Microsoft sql server 2000 database.

The virtual C drive in Virtualbox is running out of room.  Virtualbox v3.2.10 has no resize command.  Resize was introduced in version 4.

So, I upgraded the Virtualbox 3.2.10 to v4.2.18.  Virtualbox v4.2.18 would not open the v3.2.10 vdi file.  I had to clone the v3.2.10 vdi drive and mount the clone to allow Virtualbox v4.2.18 to run  Windows 2k.   When the users opened the application using the sql server 2000 database, there were records missing.

My understanding is Virtualbox changed their file structure when v4 was released.

Q1.)  I’m wondering if the Virtualbox data structure change has damaged the sql server 2000 database in some way. Please share your thoughts.

Q2.) If it is impossible to upgrade to Virtualbox 4, what other way is there to create more room on the virtual C drive?

Q3.) How might I backup the virtual C drive within Virtualbox 3.2.10, create a new larger virtual C drive and somehow convince Virtualbox v3.2.10 to recognize the larger C drive?

Q4.) Since the guest is Win2k, the only backup program is the Win2k backup.  Before moving the sql server 2000 database to a new virtual drive I would want to backup the sql server 2000 database .  How well can Win2k backup do this?
   Or should I create  a shared folder between Virtualbox Win2k guest and Windows 7 host and run sql server 2000 backup to backup all the mdf files in the sql server 2000 database and have the sql server 2000 backup files be stored on the Windows 7 host before the sql server 2000 application is moved?
Who is Participating?
R@f@r P@NC3RConnect With a Mentor Virtualization SpecialistCommented:

I answer each one of your questions.

Question 1:

-During the cloning process, if it is a server with a database, I recommend that you download all the services in the database, to protect your data.

- Then export the vm to your local machine, so you have a backup of the server in good condition.

-Then carry out the cloning process, with the database below, so as not to affect it.

Question 2:

Option 1:
-You can turn off the vm, and expand the disk size in the properties of the vm.

- Turn on the vm and extend the volume on unit C with the new space you assigned.

Option 2:
-Release space at disk level.
-Defragment disk.
-Eliminate temporary files.
-Compress folders (Do not compress the windows folder of the operating system)

Question 3:

Export the vm to an OVA or OVF template to your local machine, so that you have a good server backup.

Question 4:

You can use the backup of Windows to do the backup, if it is a database, the backup time would take depending on the size of the database.

You can do the test with the shared folder between the host and the host to evaluate the results.

I remain attentive to your comments.

donpickAuthor Commented:
Your answer is not helpful.  It's not the best answer.
I tried cloning the vdi file in version 3.2.10 in order to resize it .   I upgraded Virtualbox 3.2.10 to v4.2.18.  This was a total disaster!!   I lost huge amounts of data.

You wrote:  “I recommend that you download all the services in the database, to protect your data. “  How do you download a service?  You mean stop all services ?  Which service???

Here is what I did to solve the problem:
  First, remember:  the host is Windows 7 and the guest is Windows 2000.
  There was a large SQL Server 2000 database which was  occupying large amounts of space on the C drive in Virtualbox
  I tried to detach the large SQL Server 2000 database .  When I viewed the database using spwho it told me the database was in multi user mode.  So, in the Enterprise Manager, I changed the database to single user.  When I viewed the database using spwho, it told me the database was in multi user mode.  

So  I finally shut down the SQL Server 2000 service and started the SQL Server 2000 service in single user mode.  When I viewed the large database using spwho it still said the database was in multi user mode.  I decided to detach the database anyway and it detached successfully.

Windows 2000 only knows about IDE and SCSI controllers.  There were 4 drives on the IDE controller .  I created a SCSI controller and added a large vdi file.  I moved the large databases to this new large vdi file.  I reattached the databases to SQL Server 2000  .  I then started SQL Server 2000 in multi user mode.  This has solved the problem.
☠ MASQ ☠Commented:
Do you need the question re-opened?

It sounds from your comment that the best answer is your post at
You are able to accept your own comments as the correct solution.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.