• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

How hard would it be to move a SCO Unix box to ESX?

Red Squirrel

Red Squirrel

No Lifer
We have a VMware server 1.0 box running some legacy system running on SCO Unix. How hard would it be to move that to ESX with vmware converter? I have no clue about anything Unix so I would not even know where to start as far as troubleshooting it. I know Linux will rarely transition smoothly and require some kind of playing around to get it work on different hardware, so wondering about Unix.
 
Originally posted by: RedSquirrel
We have a VMware server 1.0 box running some legacy system running on SCO Unix. How hard would it be to move that to ESX with vmware converter? I have no clue about anything Unix so I would not even know where to start as far as troubleshooting it. I know Linux will rarely transition smoothly and require some kind of playing around to get it work on different hardware, so wondering about Unix.
Click to expand...

I've used VMWare Converter on Windows and Linux boxes and have not had any problems. You'll just have to try it for yourself. If it doesn't "just work" then you can always continue running it in it's original location while you figure out what went wrong with the conversion.
 
We have a VMware server 1.0 box running some legacy system running on SCO Unix. How hard would it be to move that to ESX with vmware converter?
Click to expand...

I don't even know if you'd need a converter. Since it's already running on VMware it'll proabably be fine, just make sure that the presented NIC and SCSI controller are the same.

I know Linux will rarely transition smoothly and require some kind of playing around to get it work on different hardware, so wondering about Unix.
Click to expand...

I guess that depends on your definition of smooth. I consider being able to untar a full back into a VM, maybe take 5 minutes to fixup the initrd and fstab and have it work to be pretty smooth.
 
Some of the older Virtual Machine files arent compatible with newer versions of ESX. A VM on Server 1.0 probably wont be compatible with newer versions of ESX. VMware Converter will copy the files and update them for the new version.
 
I just gave it a try now. Nope wont boot. Wanted to check if unix has something similar like a fstab file but the filesystem is propiatory so I can't actually mount it with a linux cd. Kind of figured as Unix is a totally different world. File system shows up as "GNU HURD or SysV". Any possible way to mount such a file system so I can see the files?
 
Oh yeah, there is, should I run that command on sda1? I'll do that when I get to work (this is a work machine). They built it on a non redundant VMware Server 2.0 box and I want to see if I can move it to ESX where they should of did it in first place.
 
Yep just that one partition. Also just one drive on that VM. I'll probably end up leaving the VM on the old server unless I can find more info on how to convert, but i have a feeling even if i do gain access to the data, it wont be very easy to do. Even with linux, I usually find myself reinstalling if the disk controller changes, especially from IDE to sata. In some cases it's just an edit of fstab though, so if unix has such file it will be worth a shot.
 
Even with linux, I usually find myself reinstalling if the disk controller changes, especially from IDE to sata.
Click to expand...

If you took the time to learn how the bootup process works so that you could fix those you'd probably know enough to have converted the SCO box already.

In some cases it's just an edit of fstab though, so if unix has such file it will be worth a shot.
Click to expand...

It does, but the SCSI controller support will be the main issue.
 
I decided to put off the move and put the suggestion that we should upgrade that box later on as a special project. Probably not going to happen though, that is one huge project and whatever software that runs on there is probably outdated and impossible to port on another Os. Nobody actually even knows the password to it, it just has to stay up for payroll to work. Hate systems like that. If it craps out we're screwed.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top