In order to have a sand box machine that I could use to test some system changes before going to production state, I'd like to duplicate a working system to a virtual one. Ideally, I'd like to manage to do it this way :
Make a full system backup excluding the user file system (this system is used as mail and file server)
Being able to send the data directly to the virtual machine by using the network. (no intermediate backup disk) :rolleyes:
We will need to know the operating system as each does it it's own way, e.g. mksysb for AIX, Ignite for HP-UX etc.
Is the user filesystem you allude to /usr ? If so, you will need a good dollop of the content of this to allow the machine to boot. If it is something else (/usr/home, /data etc.) is it on the same disk as the base operating system was installed or in the same volume group?
If not either of these, then a backup that you can use for disaster recovery should ignore it anyway. If it would normally be included, there are usually some exclude flags, but again they are operating system specific.
Write back with a bit more information and I'm sure someone will help.
Nobody ? I guess this question may sound a bit newbie, but the challenge is that one should find a way to make system image (easy), with exclusions (easy), and without intermediate media (easy), all three at the same time (more difficult ?)
I suppose so, look at the way knoppix live CD works, its debian based, and you can install from (and becomes a debian...) so the idea would be to do something similar
Unless both machines have the same hardware configuration, restoring an image of the root file system of one machine on another is probably not going to work well. You probably don't want all the user ids and passwords, and have to change the system name and ip address, etc.
Better to do a fresh install on the test machine, and then transfer the data files on a (regular) basis.
Recommend: Cold build the sandbox system, install whatever software is strictly necessary, create test user accounts. Then copy selected data as required taking serious precautions against live output leaking out through printers, email or whatever. It is normal to change all personal data on test system to test values during the copy process.
Personal data includes Names, Addresses and email addresses.
Then if you have a bad test run all that happens is your test site gets more correspondence than usual.
Given identical hardware you can sometimes work with cloned systems provided that they are on a ring-fenced network in a secure building and all printed output is shredded. By definition this environment would not allow you to copy data across a network.