>Ideally when a linux is ready for production. I would like to stop it,
>save all the MDISKs and restart it.
>So if something gets corrupted or worse I can restore the MDISK's and have
>a linux "production ready".
>
>My idea would be to use only CMS RESERVE MDISK and ftp these files to a
>server where I can save them with TSM.
>and of course, ftp back if I need them.
No problem. You can read that single file on the disk with CMS tools and
send it to z/OS or whatever you want. Writing can be done for example
with the CMS Pipelines 'mdiskblk' stage. And if you use CMS Pipelines
for writing you can use it for reading too and take advantage of it.
Suppose the disk is accessed as M and reserved with LINUX FILE
PIPE < LINUX FILE M | spec recno 1.10 ri 1-* n | strip trailing 00
| pack | > linux backup a
Now you can do what you need with that (smaller) file. And to restore
it you RESERVE the disk again and then
PIPE < linux backup a | unpack | pad 4106 00 | diskupdate LINUX FILE M
If that disk was bootable then you need to copy the IPL records too (we
did that with 'mdiskblk').
PS Be careful not to use the diagnose driver when you go to 2.4.7
Rob
