We have a small network run by a NT 4.0 SP6 DC, with the domain name of "domain". This is a single name domain space, not domain.com or parent.child.com, just "domain". That's issue number one.
Issue number two is the DC is running two (2) SCSI drives with four (4) partitions on each drive and each partition is spanned across both drives. It was mirrored in at the start, but that was broken in favor of more space. Meaning C is seen as one partition but when you look at it with a partitioning utility; you see "C" on drive 1 using X space and "C" on drive 2 using X space.
We also have two (2) Linux servers, one red hat one I don’t know but its only command line. They run a single critical app (mirrored data between them) we will need to run for the next 7 years because the data archives and retrieval is required for legal reasons. That shoots our sign and seal communications for the network.
Issue four is the HD on the DC is too full, or too small depending on how you see it to allow for an in place upgrade to 2003. MS says you can in place upgrade from NT to 2003 with single name domain space if you do “x”. I haven’t gotten to “X” yet because I need options to migrate my data to a bigger drive. The “X” action will be completed via phone support I’ve already paid for and have an open ticket on.
I have cloned the drive using Acronis, but since the data on one partition spans two physical disks, the partition resize does me no good, because when you re-size the one partition on drive 1, you lose to makers for the data space on the other drive and the whole thing doesn’t boot.
I have a volume copy of 2003 server and virtual pc and MS virtual server and was going to attempt to make a virtual DC clone on a bigger HD, but an still limited because of the C part being spanned.
I know it seems like every possible option to keep the upgrade from happening has been done, and I’m out of ideas. Anyone have any ideas or suggestions?
July 22, 2009 1:13 PM
July 23, 2009 3:20 PM