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?