Okay, I have a PC here which was implemented by the last sysadmin, and it runs any number of mission critical Perl scripts that keep the company going. While most are documented alright, what isn't documented is what is required on the backend for these perl scripts to run.
As in, the required modules and anything else.
I've spent some time trying to replicate the environment on another PC and while I've got some of them to work, others just keep crashing because of missing modules, and the modules aren't exactly well named ('Email' for example.. there's like 12 Email modules for Perl).
What I want to do until the day comes when I can rebuild the system and document what's required to make everything run is to create a virtual box.
The machine itself is an AMD XP of some caliber, Compaq box. It's one of the oldest machines in the building actually. I don't have another machine of similiar specs that I can ghost to as a hard backup. I'm not even sure I have another AMD box. This one is just kind of an analomy from before my time.
My question is this: what do I use to image the machine, and then how to use that image on a more modern machine and/or a backup machine should this one?
I know how to use VMware to create a NEW sandbox and install Windows and whatnot, but what would I use to take a current setup and be able to use it without Windows shitting out from mismatched hardware?
I really have limited exposure to virtualization.




Reply With Quote