Does anyone have any examples of scripts that can look at the mounted file
systems, mount them RO serially or in logical groupings and cause a backup
to run, then re-mount them RW?
My thought would be to have some automation product logon to Linux, take it
to single user mode with telnet running, and then remount filesystems RO
and do CDL backups of the volume that contain that file system, and after
it's done, re-mount the file system RW again. I am not currently into
anything like LVM.
I'd just like to see some scripting that would be able to analyze things
and determine what volume (dasdb1, c1 etc) goes with what file system then
handle the re-mount read-only stuff.
Also, it is my understanding that with the advent of os/390 2.10 or is it
z/os 1.2? you could have volumes bigger than a 3390-9 in a shark disk box?
Does Linux currently support those larger volumes?
|---------+---------------------------->
| | "McKown, John" |
| | <[EMAIL PROTECTED]|
| | tr.com> |
| | Sent by: Linux on|
| | 390 Port |
| | <[EMAIL PROTECTED]|
| | IST.EDU> |
| | |
| | |
| | 02/25/2003 03:31 |
| | PM |
| | Please respond to|
| | Linux on 390 Port|
| | |
|---------+---------------------------->
>------------------------------------------------------------------------------------------------------------------------------|
|
|
| To: [EMAIL PROTECTED]
|
| cc:
|
| Subject: Re: PLanning for Z/VM and Linux
|
>------------------------------------------------------------------------------------------------------------------------------|
I'm in the same situation, but I can answer some questions.
1) You cannot backup a LINUX disk to tape from outside of the LINUX system,
if the disk (filesystem) is mounted in WRITE mode. This would result in a
"fuzzy" backup since LINUX does not immediately write all disk updates to
the filesystem. The backup would likely be no good.
2) You cannot really share a single disk (filesystem) between multiple
Linux
systems unless all systems mount the disk in READ-ONLY mode. This is for
the
same reason as #1.
3) You can backup your Linux disk with DDR or your OS/390 (z/OS) backup
program. But only if the disk (filesystem) is either not in use by any
Linux
system or, again, is READ-ONLY to all Linux systems.
4) This is very similar to the standard CMS restriction about linking to
CMS
minidisks. With the added caveat that if even one system had the disk
(filesystem) mounted as Read/Write, then other systems cannot link to it
even in READ-ONLY mode. It just will not consistantly work properly.
> -----Original Message-----
> From: Duane Weaver [SMTP:[EMAIL PROTECTED]
> Sent: Tuesday, February 25, 2003 12:40 PM
> To: [EMAIL PROTECTED]
> Subject: PLanning for Z/VM and Linux
>
> We are in the planning stages of installing Z/VM with the intent of
> installing Linux.
>
>
> How do other sites handle the backups done of the Linux virtual
> machines? Are the backups done from the VM side using DDR?
> Or are the backups done within the Linux virtual machine, some how giving
> tape access to the virtual machine?
>
> It has been long enough since I worked with VM, that I never became
> familiar with the Share File System. The thing that I remember about
> VM is that your files were secure until you allow someone else to link to
> your minidisk. IS that still the case? Do I need a security system on
> installed on VM?
>
>
> Duane
