Re: Dual Mode Reboot
I'm not sure about the exact process for a dual boot server but you can reboot SUSE Linux with with the 'reboot' command or with a form of 'shutdown -r'. Use the 'man shutdown' for the options for the third parameter. To reboot immediately, issue 'shutdown -r now' (without the quotes). Harley -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Jake Anderson Sent: Monday, August 03, 2015 5:39 AM To: LINUX-390@VM.MARIST.EDU Subject: Dual Mode Reboot Hello, I am looking for an assistance on how to reboot a running linux server with SUSE OS ? The server is a DUAL boot server. Jake -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ *** The information contained in this communication is confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please resend this communication to the sender and delete the original message or any copy of it from your computer system. Thank You.
Re: SLES12 - yast does not create a udev rule
Larry, Check out https://www.mail-archive.com/linux-390@vm.marist.edu/msg66460.html. I found this issue when I was initially testing SLES 12 (still haven't implemented SLES 12 in production). Your new devices may need to be added to the cio_ignore file. Harley -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Davis, Larry (National VM Capability) Sent: Tuesday, November 10, 2015 7:08 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: SLES12 - yast does not create a udev rule I have the same problem with Network and DASD devices that I add, I am not sure of the proper procedure but I had to add the network device to the Rules files in /etc/udev/rules.d/70-persistent-net.rules I have also had to add rules for each new DASD device so it is available after an IPL or reboot Larry Davis, VM Capability -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Christer Solskogen Sent: Tuesday, November 10, 2015 4:58 AM To: LINUX-390@VM.MARIST.EDU Subject: SLES12 - yast does not create a udev rule Hi! I've setup the network in YaST, but the device does not start automagicly when I reboot the machine (running as a guest in z/VM). I was pretty sure that YaST would create a file under /etc/udev/rules.d called 51-qeth-0.0.0603.rules (or something) - the address is 603,604 and 605. I can get the device to work if I run znetconf -a 603 manually. Help, please! -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ *** The information contained in this communication is confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please resend this communication to the sender and delete the original message or any copy of it from your computer system. Thank You.
Re: Documentation for Linux on z Systems and KVM - new
Mark, Very nice, informative, post. Harley Linker Jr. -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Mark Post Sent: Monday, September 28, 2015 3:39 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Documentation for Linux on z Systems and KVM - new >>> On 9/28/2015 at 02:25 AM, Sergey Korzhevsky <s_korzhev...@iba.by> wrote: > Alan Altmark wrote: >>> What is it about z that makes virtualization work better? >>50 years of work on it? > > That is interesting answer. One thing came to my mind is the live > guest relocation. As far as i could find, VMware introduced that > feature > (vMotion) in 2003, z/VM - in 2011. The same regarding network > (GuestLAN/VSwitch). > So, looks like z/VM slept all that years and was wake up by x86 world > recently. Having been an active participant and observer of the community for a while now, I think I can contribute some perspective. (From what I can tell, you have been also so I find your comment a little surprising.) When Linux for the mainframe was first introduced, a lot of facilities we take for granted today didn't exist. Guest LANs, VSWITCHes, cooperative memory management and so on. That started to change pretty quickly. Things that actually helped running more than just a few instances of Linux were introduced and made life much easier. Live Guest Relocation wasn't needed then, because not many shops were running huge amounts of guests. That pain came along later. Even then, it wasn't for the same reason that the x86 world wanted it. Mainframe shops running Linux on z/VM didn't worry much about hardware failures and migrating workload to relieve overloaded servers usually wasn't an issue because of decades of performance and capacity management. What "we" wanted it for was because z/VM was so reliable it could run for years but sometimes various maintenance was important to put on the system. Trying to get multiple customers of the service to agree on a maintenance window was becoming nearly impossible, because although they wanted High Availability, they weren't willing to actually invest in it, so the workload couldn't be failed over to another server in a cluster. There was another factor, although not a technical one. Many customers have become checklist driven. If your product doesn't allow them to put check marks in all the boxes on the list, it's obviously not a good product and not worthy of consideration. So, z/VM development was getting reports from Sales that this function was needed, just to be "in the game." And, being the group that they are, z/VM development wanted to approach the development needed in a more "system of systems" oriented way than just bolting on a feature. Thus, Single System Image was born, and it took quite a while and a lot of people to bring to the market. Taking into account the various diversions that were forced on them during the same period of time, it's amazing they got it out as quickly as they did. I think most people that have been in the z/VM world for a long time would agree that having Linux available on the mainframe has breathed new life into z/VM. Since then, they've been working hard to introduce things that make sense for the mainframe environment. What new items they work on, and what priority they have, _can_ be influenced by current and potential customers. I encourage anyone who has thoughts on what those new items should be to speak up, whether here or in the IBMVM mailing list, or at SHARE. There are people in these mailing lists and at SHARE that have a direct line into the z/VM and Linux development groups at IBM. Take advantage of that. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ *** The information contained in this communication is confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please resend this communication to the sender and delete the original message or any copy of it from your computer system. Thank You. -- For LINUX-390
Re: Script after full system is up
You can add an entry in a crontab where the line is prefixed with '@reboot'. Check out the man page for the crontab file. -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Michael Weiner Sent: Monday, February 08, 2016 2:09 PM To: LINUX-390@VM.MARIST.EDU Subject: Script after full system is up Hi all I am running SLES 11 SP3 and I want a script to run after the full system is up. How can I achieve this? I am looking and browsing but I haven't had any luck with rc.local. Thank you! Sent from my iPhone -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ © 2016 Ensono, LP. All rights reserved. Ensono is a trademark of Ensono, LP. The information contained in this communication is confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please resend this communication to the sender and delete the original message or any copy of it from your computer system.
Re: How many shops... ?
I work for an outsourcer, Ensono, and we have a several CEC's, two of them have GP and IFL engines. One is a LAB (test) box with several lpars: 1 running z/OS on a GP engine, and 2 more running z/VM on IFL's. The other is a production box with 3 lpars running z/OS and 1 with 6 IFL's running z/VM and roughly 25 Linux on System z servers. We don't have any IFL-only CEC's. Harley -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Dave Jones Sent: Monday, March 14, 2016 11:19 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: How many shops... ? Hi, Thomas. I doubt very much that that information is publicly available anywhere. Actual, hard numbers of this sort are considered proprietary marketing information by IBM, think. The best you can do, I think, is to poll the members of this list and others like it, e.g., the VM list, and see what they report. Have a good one, too. DJ On 03/14/2016 10:29 AM, Ambros, Thomas wrote: > My searches of the archives are not productive, probably ill formed. > Likewise, general internet searches not coming up with much useful. > > We've asked this question of our IBM account team, in the range of their > territory, and are waiting for an answer. > > I've seen statements at conferences and presentations where we are told "x% > of all new zSeries hardware shipped includes IFLs, moreover y% are IFL-only", > but that doesn't necessarily reflect production implementations (though one > would think it'd be reasonably close). > > To start to contest the perception that Linux on system Z is a 'one-off', > where would one find out for themselves roughly how many shops in North > America are running production implementations of Linux on system Z and what > proportion of all zSeries sites that might be? > > Thomas Ambros > zEnterprise Operating Systems > zEnterprise Systems Management > 518-436-6433 > > > > This communication may contain privileged and/or confidential information. It > is intended solely for the use of the addressee. If you are not the intended > recipient, you are strictly prohibited from disclosing, copying, distributing > or using any of this information. If you received this communication in > error, please contact the sender immediately and destroy the material in its > entirety, whether electronic or hard copy. This communication may contain > nonpublic personal information about consumers subject to the restrictions of > the Gramm-Leach-Bliley Act. You may not directly or indirectly reuse or > redisclose such information for any purpose other than to provide the > services for which you are receiving the information. > > 127 Public Square, Cleveland, OH 44114 If you prefer not to receive > future e-mail offers for products or services from Key send an e-mail > to mailto:dnereque...@key.com with 'No Promotional E-mails' in the > SUBJECT line. > > -- > For LINUX-390 subscribe / signoff / archive access instructions, send > email to lists...@vm.marist.edu with the message: INFO LINUX-390 or > visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > -- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ > -- Dave Jones V/Soft Software www.vsoft-software.com Houston, TX 281.578.7544 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ © 2016 Ensono, LP. All rights reserved. Ensono is a trademark of Ensono, LP. The information contained in this communication is confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please resend this communication to the sender and delete the original message or any copy of it from your computer system.
Re: zswap missing?
I am running SLES 11 SP4 on System z and the kernel is 3.0.101-65-default. According to several Google search results, zswap is available in the 3.11 kernel. I don't have a SLES 12 system so I can't tell what kernel is running there. -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Christer Solskogen Sent: Thursday, March 10, 2016 6:21 AM To: LINUX-390@VM.MARIST.EDU Subject: zswap missing? Hi! Isn't zswap available for s390x? I can't find anything on either SLES11 or SLES12. -- chs -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ © 2016 Ensono, LP. All rights reserved. Ensono is a trademark of Ensono, LP. The information contained in this communication is confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please resend this communication to the sender and delete the original message or any copy of it from your computer system.
Re: Simple DASD question
Did you run command 'fdasd -a /dev/dasdb' to create the partition? /dev/dasdb1 doesn't exist unless you run the command. Harley Linker Jr. -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Tom Huegel Sent: Friday, April 22, 2016 9:08 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Simple DASD question So far I have failed with my feeble attempts to add the second disk dasdb (0251) to the btrfs filesystem. This is what I have fresh after my re-re-re-re-install. It seems "btrfs device add /dev/dasdb1 /" would be a good thing to do but I get message about dasdb1 not existing... sles12:~ # lsdasd Bus-ID Status Name Device Type BlkSz Size Blocks == 0.0.0250 active dasda 94:0ECKD 4096 7042MB1802880 0.0.0251 active dasdb 94:4ECKD 4096 7042MB1802880 sles12:~ # btrfs filesystem show Label: none uuid: d8b46146-19c1-48d8-b024-80547e728787 Total devices 1 FS bytes used 2.74GiB devid1 size 5.71GiB used 3.53GiB path /dev/dasda3 Btrfs v3.16+20140829 sles12:~ # df -h Filesystem Size Used Avail Use% Mounted on /dev/dasda3 5.8G 3.0G 2.5G 55% / devtmpfs439M 8.0K 439M 1% /dev tmpfs 446M 0 446M 0% /dev/shm tmpfs 446M 7.0M 439M 2% /run tmpfs 446M 0 446M 0% /sys/fs/cgroup /dev/dasda3 5.8G 3.0G 2.5G 55% /var/tmp /dev/dasda3 5.8G 3.0G 2.5G 55% /var/spool /dev/dasda3 5.8G 3.0G 2.5G 55% /var/opt /dev/dasda3 5.8G 3.0G 2.5G 55% /var/log /dev/dasda1 194M 24M 161M 13% /boot/zipl /dev/dasda3 5.8G 3.0G 2.5G 55% /var/lib/pgsql /dev/dasda3 5.8G 3.0G 2.5G 55% /var/lib/named /dev/dasda3 5.8G 3.0G 2.5G 55% /var/lib/mailman /dev/dasda3 5.8G 3.0G 2.5G 55% /usr/local /dev/dasda3 5.8G 3.0G 2.5G 55% /tmp /dev/dasda3 5.8G 3.0G 2.5G 55% /var/crash /dev/dasda3 5.8G 3.0G 2.5G 55% /srv /dev/dasda3 5.8G 3.0G 2.5G 55% /opt /dev/dasda3 5.8G 3.0G 2.5G 55% /home /dev/dasda3 5.8G 3.0G 2.5G 55% /boot/grub2/s390x-emu sles12:~ # On Thu, Apr 21, 2016 at 2:37 PM, Mark Post <mp...@suse.com> wrote: > >>> On 4/21/2016 at 05:33 PM, Grzegorz Powiedziuk > >>> <gpowiedz...@gmail.com> > wrote: > > then pvcreate, vgextend, lvextend and filesystem resize. > > No, we're trying to get him set up with LVM, just btrfs. > > > Mark Post > > -- > For LINUX-390 subscribe / signoff / archive access instructions, send > email to lists...@vm.marist.edu with the message: INFO LINUX-390 or > visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > -- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ > -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ © 2016 Ensono, LP. All rights reserved. Ensono is a trademark of Ensono, LP. The information contained in this communication is confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please resend this communication to the sender and delete the original message or any copy of it from your computer system.
Re: IPL using LOADPARM bypasses SALIPL screen
I haven't started on 6.4 yet but found this page, https://www.ibm.com/support/knowledgecenter/SSB27U_6.4.0/com.ibm.zvm.v640.hcpa7/iplsec.htm. I don't know if it matters but the page shows a 'set machine esa' command just before the IPL command. Harley -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Will, Chris Sent: Wednesday, February 15, 2017 12:55 PM To: LINUX-390@VM.MARIST.EDU Subject: IPL using LOADPARM bypasses SALIPL screen Installing/customizing a z/VM 6.4 system and have got to the point of starting RACF. So I need the SALIPL screen to change the device number. However even when I use the LOADPARM parm it goes right to the "warm,noauto, etc." prompt. This is a second level system. Here are the commands I use. SYS CLEAR TERM CONMODE 3270 IPL 3C30 CLEAR LOADPARM 009 13:51:01 13:51:01 HCPZCO6718I Using parm disk 1 on volume CV3C33 (device 3C33). 13:51:01 HCPZCO6718I Parm disk resides on cylinders 1 through 120. 13:51:01 Start ((Warm|Force|COLD|CLEAN) (DRain) (DIsable) (NODIRect) 13:51:01 (NOAUTOlog)) or (SHUTDOWN) I don't get the stand alone loader program screen. Chris Will Systems Software (313) 549-9729 Cell cw...@bcbsm.com The information contained in this communication is highly confidential and is intended solely for the use of the individual(s) to whom this communication is directed. If you are not the intended recipient, you are hereby notified that any viewing, copying, disclosure or distribution of this information is prohibited. Please notify the sender, by electronic mail or telephone, of any unintended receipt and delete the original message without making any copies. Blue Cross Blue Shield of Michigan and Blue Care Network of Michigan are nonprofit corporations and independent licensees of the Blue Cross and Blue Shield Association. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ © 2016 Ensono, LP. All rights reserved. Ensono is a trademark of Ensono, LP. The information contained in this communication is confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please resend this communication to the sender and delete the original message or any copy of it from your computer system.
Re: Best way to edit Linux files in z/VM 3270
The only option that I'm aware of is the 'sed' command. Harley Linker -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Diep, David (OCTO-Contractor) Sent: Tuesday, September 20, 2016 2:02 PM To: LINUX-390@VM.MARIST.EDU Subject: Best way to edit Linux files in z/VM 3270 Hi everyone, I've searched everywhere and I cannot find for editing Linux files while logged in with 3270. Vi will just get me stuck. I looked at 'ed', but I get stuck as well... any recommendations?? Thanks David Diep -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ © 2016 Ensono, LP. All rights reserved. Ensono is a trademark of Ensono, LP. The information contained in this communication is confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please resend this communication to the sender and delete the original message or any copy of it from your computer system.
Re: Anyone running IBM BigFix client on z?
I am. The team that manages BigFix on the x86 server tweaked a setting so that it didn't check the z servers quite as often. The change they made, which they didn't tell me what it was, reduced the CPU percentage to .7 per server. Harley -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Marcy Cortes Sent: Friday, June 02, 2017 12:54 PM To: LINUX-390@VM.MARIST.EDU Subject: Anyone running IBM BigFix client on z? aka BESClient We're seeing 1-2% cpu per guest. While that's not a big deal on a x86 standalone box, it's a big deal on a box with 400 servers on it. Hoping it's tunable... Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ © 2017 Ensono, LP. All rights reserved. Ensono is a trademark of Ensono, LP. The information contained in this communication is confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please resend this communication to the sender and delete the original message or any copy of it from your computer system.
Re: Upgrade of SLES 11 SP4 to SLES 12 SP2 on System z
Aria, Thank you! That parameter for the PARMFILE is not in the deployment manual but has changed the installation screens that are presented. I did find it there to be added to the GRUB legacy configuration file. The update=1 PARMFILE parameter is exactly what I was looking for. Thank you. Harley -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Aria Bamdad Sent: Thursday, August 24, 2017 11:37 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Upgrade of SLES 11 SP4 to SLES 12 SP2 on System z Hi Harley, My environment is not the same as yours and I don't use a complete parameter file like you do but I noticed that you said you are upgrading from 11 to 12, but I don't see the 'upgrade=1' parameter among your parameter list. The SUSE upgrade manual for z says you need that parameter when you upgrade rather than install from scratch. Perhaps that's why yast wanted to format your volumes. Also, when you don't use a more complete param file, you do get that initial menu. When you are upgrading an existing system, I select 'Install' on the first menu and then 'Upgrade' on the next menu. This second menu is the menu you describe below. Perhaps what you are missing is just the 'upgrade=1' parameter in your param file. Aria -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Harley Linker Sent: Thursday, August 24, 2017 12:23 PM To: LINUX-390@VM.MARIST.EDU Subject: Upgrade of SLES 11 SP4 to SLES 12 SP2 on System z Hi, I am looking to upgrade some of my z/VM based servers from SLES 11 SP4 to SLES 12 SP2 and am wondering if this is possible on System z. My guest is defined as: PROFILE LNXDFLT LOGONBY ... IPL CMS PARM AUTOCR CONSOLE 009 3215 T SPOOL 00C 2540 READER A SPOOL 00D 2540 PUNCH A SPOOL 00E 1403 A LINK MAINT 190 190 RR LINK MAINT 19D 19D RR LINK MAINT 19E 19E RR LINK LNXMAINT 191 191 RR USER SYSSOFT1 3074M 3074M G INCLUDE LNXDFLT NICDEF 1F00 TYPE QDIO LAN SYSTEM VSWINT1 MDISK 200 3390 001 10016 LN150D MR ALL SOME FEW / MDISK 201 FB-512 V-DISK 524288 WV SWAP MDISK 990 3390 001 10016 LN150E MR ALL SOME FEW /OPT MDISK 991 3390 001 10016 LN150F MR ALL SOME FEW /OPT The 200 disk is the boot volume, 201 is a virtual swap disk, and 990 and 991 are an LV mounted to /opt. I am using a PARMFILE containing the following (sanitized): ramdisk_size=131072 root=/dev/ram1 ro init=/linuxrc term=dumb vmpoff=logoff hostname= mf-syssoft1 hostip=10.17.1.xxx gateway=10.17.1.129 nameserver=999.24.8.126 instnetdev=osa osainterface=qdio layer2=1 portno=0 netmask=255.255.255.192 broadcast=10.17.1.255 readchannel=0.0.1f00 writechannel=0.0.1f01 datachannel=0.0.1f02 install=nfs://10.17.1.yyy/media/s390x/sles12sp2/dvd1 ssh=1 ssh.password= linuxrclog=/dev/console manual=0 I begin the installation by logging onto the SYSSOFT1 guest (which already has SLES 11 SP4 installed). I interrupt the Linux boot with #cp I cms acc (noprof I then run the SLES12 EXEC which pulls in the PARMFILE above. The only prompts I received on the console are for Specifying a MAC address is optional. In most cases letting it default is the correct choice. Provide one only if you know it is truly necessary. Optional MAC address. (Enter '+++' to abort). When the installation system finished booting, I PuTTYed into another test server and 'ssh -X root@10.17.1.156<mailto:root@10.17.1.156>', replied with the password (the one specified in the PARMFILE), then invoked YaST. I went thru all of the screens and specified what I needed to but when I got to the last screen and selected [Install] I received a pop-up that my disk would be reformatted and I would lose all of the data that was on it. I am asking in that I was working with Novell support yesterday and we terminated the YaST portion of the install by slecting [Abort]. On the console (the VM screen) we received the following: Start Installation 0) <-- Back <-- 1) Installation 2) Upgrade 3) Rescue System 4) Boot Installed System 5) Network Setup Is there a way to modify the PARMFILE to specify that I wasn't to perform an upgrade-in-place? Do I need to use a PARMFILE with a minimal set of parameters? I tried to change the install=nfs://10.17.1.yyy/media/s390x/sles12sp2/dvd to upgrade=nfs://10.17.1.yyy/media/s390x/sles12sp2/dvd1. The installation system couldn't find the SLES 12 repository. Thank you. Harley Harley Linker Jr. Sr. Systems Programmer Ensono e: harley.lin...@ensono.com<mailto:harley.lin...@ensono.com> o: 630.944.5111 www.ensono.com<http://www.ensono.com/> (c) 2017 Ensono, LP. All rights reserved. Ensono is a trademark of Ensono, LP. The information contained in this communication is confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notifie
Upgrade of SLES 11 SP4 to SLES 12 SP2 on System z
Hi, I am looking to upgrade some of my z/VM based servers from SLES 11 SP4 to SLES 12 SP2 and am wondering if this is possible on System z. My guest is defined as: PROFILE LNXDFLT LOGONBY ... IPL CMS PARM AUTOCR CONSOLE 009 3215 T SPOOL 00C 2540 READER A SPOOL 00D 2540 PUNCH A SPOOL 00E 1403 A LINK MAINT 190 190 RR LINK MAINT 19D 19D RR LINK MAINT 19E 19E RR LINK LNXMAINT 191 191 RR USER SYSSOFT1 3074M 3074M G INCLUDE LNXDFLT NICDEF 1F00 TYPE QDIO LAN SYSTEM VSWINT1 MDISK 200 3390 001 10016 LN150D MR ALL SOME FEW / MDISK 201 FB-512 V-DISK 524288 WV SWAP MDISK 990 3390 001 10016 LN150E MR ALL SOME FEW /OPT MDISK 991 3390 001 10016 LN150F MR ALL SOME FEW /OPT The 200 disk is the boot volume, 201 is a virtual swap disk, and 990 and 991 are an LV mounted to /opt. I am using a PARMFILE containing the following (sanitized): ramdisk_size=131072 root=/dev/ram1 ro init=/linuxrc term=dumb vmpoff=logoff hostname= mf-syssoft1 hostip=10.17.1.xxx gateway=10.17.1.129 nameserver=999.24.8.126 instnetdev=osa osainterface=qdio layer2=1 portno=0 netmask=255.255.255.192 broadcast=10.17.1.255 readchannel=0.0.1f00 writechannel=0.0.1f01 datachannel=0.0.1f02 install=nfs://10.17.1.yyy/media/s390x/sles12sp2/dvd1 ssh=1 ssh.password= linuxrclog=/dev/console manual=0 I begin the installation by logging onto the SYSSOFT1 guest (which already has SLES 11 SP4 installed). I interrupt the Linux boot with #cp I cms acc (noprof I then run the SLES12 EXEC which pulls in the PARMFILE above. The only prompts I received on the console are for Specifying a MAC address is optional. In most cases letting it default is the correct choice. Provide one only if you know it is truly necessary. Optional MAC address. (Enter '+++' to abort). When the installation system finished booting, I PuTTYed into another test server and 'ssh -X root@10.17.1.156<mailto:root@10.17.1.156>', replied with the password (the one specified in the PARMFILE), then invoked YaST. I went thru all of the screens and specified what I needed to but when I got to the last screen and selected [Install] I received a pop-up that my disk would be reformatted and I would lose all of the data that was on it. I am asking in that I was working with Novell support yesterday and we terminated the YaST portion of the install by slecting [Abort]. On the console (the VM screen) we received the following: Start Installation 0) <-- Back <-- 1) Installation 2) Upgrade 3) Rescue System 4) Boot Installed System 5) Network Setup Is there a way to modify the PARMFILE to specify that I wasn't to perform an upgrade-in-place? Do I need to use a PARMFILE with a minimal set of parameters? I tried to change the install=nfs://10.17.1.yyy/media/s390x/sles12sp2/dvd to upgrade=nfs://10.17.1.yyy/media/s390x/sles12sp2/dvd1. The installation system couldn't find the SLES 12 repository. Thank you. Harley Harley Linker Jr. Sr. Systems Programmer Ensono e: harley.lin...@ensono.com<mailto:harley.lin...@ensono.com> o: 630.944.5111 www.ensono.com<http://www.ensono.com/> (c) 2017 Ensono, LP. All rights reserved. Ensono is a trademark of Ensono, LP. The information contained in this communication is confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please resend this communication to the sender and delete the original message or any copy of it from your computer system. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Upgrade of SLES 11 SP4 to SLES 12 SP2 on System z
Aria, The deployment guide I refenced is the one I obtained from the SLES 12 SP2 DVD1 iso file. I did find the parameter in https://www.suse.com/documentation/sles-12/singlehtml/book_sle_deployment/book_sle_deployment.html#sec.appdendix.parm.general. Thanks again! Harley -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Aria Bamdad Sent: Thursday, August 24, 2017 11:37 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Upgrade of SLES 11 SP4 to SLES 12 SP2 on System z Hi Harley, My environment is not the same as yours and I don't use a complete parameter file like you do but I noticed that you said you are upgrading from 11 to 12, but I don't see the 'upgrade=1' parameter among your parameter list. The SUSE upgrade manual for z says you need that parameter when you upgrade rather than install from scratch. Perhaps that's why yast wanted to format your volumes. Also, when you don't use a more complete param file, you do get that initial menu. When you are upgrading an existing system, I select 'Install' on the first menu and then 'Upgrade' on the next menu. This second menu is the menu you describe below. Perhaps what you are missing is just the 'upgrade=1' parameter in your param file. Aria -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Harley Linker Sent: Thursday, August 24, 2017 12:23 PM To: LINUX-390@VM.MARIST.EDU Subject: Upgrade of SLES 11 SP4 to SLES 12 SP2 on System z Hi, I am looking to upgrade some of my z/VM based servers from SLES 11 SP4 to SLES 12 SP2 and am wondering if this is possible on System z. My guest is defined as: PROFILE LNXDFLT LOGONBY ... IPL CMS PARM AUTOCR CONSOLE 009 3215 T SPOOL 00C 2540 READER A SPOOL 00D 2540 PUNCH A SPOOL 00E 1403 A LINK MAINT 190 190 RR LINK MAINT 19D 19D RR LINK MAINT 19E 19E RR LINK LNXMAINT 191 191 RR USER SYSSOFT1 3074M 3074M G INCLUDE LNXDFLT NICDEF 1F00 TYPE QDIO LAN SYSTEM VSWINT1 MDISK 200 3390 001 10016 LN150D MR ALL SOME FEW / MDISK 201 FB-512 V-DISK 524288 WV SWAP MDISK 990 3390 001 10016 LN150E MR ALL SOME FEW /OPT MDISK 991 3390 001 10016 LN150F MR ALL SOME FEW /OPT The 200 disk is the boot volume, 201 is a virtual swap disk, and 990 and 991 are an LV mounted to /opt. I am using a PARMFILE containing the following (sanitized): ramdisk_size=131072 root=/dev/ram1 ro init=/linuxrc term=dumb vmpoff=logoff hostname= mf-syssoft1 hostip=10.17.1.xxx gateway=10.17.1.129 nameserver=999.24.8.126 instnetdev=osa osainterface=qdio layer2=1 portno=0 netmask=255.255.255.192 broadcast=10.17.1.255 readchannel=0.0.1f00 writechannel=0.0.1f01 datachannel=0.0.1f02 install=nfs://10.17.1.yyy/media/s390x/sles12sp2/dvd1 ssh=1 ssh.password= linuxrclog=/dev/console manual=0 I begin the installation by logging onto the SYSSOFT1 guest (which already has SLES 11 SP4 installed). I interrupt the Linux boot with #cp I cms acc (noprof I then run the SLES12 EXEC which pulls in the PARMFILE above. The only prompts I received on the console are for Specifying a MAC address is optional. In most cases letting it default is the correct choice. Provide one only if you know it is truly necessary. Optional MAC address. (Enter '+++' to abort). When the installation system finished booting, I PuTTYed into another test server and 'ssh -X root@10.17.1.156<mailto:root@10.17.1.156>', replied with the password (the one specified in the PARMFILE), then invoked YaST. I went thru all of the screens and specified what I needed to but when I got to the last screen and selected [Install] I received a pop-up that my disk would be reformatted and I would lose all of the data that was on it. I am asking in that I was working with Novell support yesterday and we terminated the YaST portion of the install by slecting [Abort]. On the console (the VM screen) we received the following: Start Installation 0) <-- Back <-- 1) Installation 2) Upgrade 3) Rescue System 4) Boot Installed System 5) Network Setup Is there a way to modify the PARMFILE to specify that I wasn't to perform an upgrade-in-place? Do I need to use a PARMFILE with a minimal set of parameters? I tried to change the install=nfs://10.17.1.yyy/media/s390x/sles12sp2/dvd to upgrade=nfs://10.17.1.yyy/media/s390x/sles12sp2/dvd1. The installation system couldn't find the SLES 12 repository. Thank you. Harley Harley Linker Jr. Sr. Systems Programmer Ensono e: harley.lin...@ensono.com<mailto:harley.lin...@ensono.com> o: 630.944.5111 www.ensono.com<http://www.ensono.com/> (c) 2017 Ensono, LP. All rights reserved. Ensono is a trademark of Ensono, LP. The information contained in this communication is confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination,
Re: BESCLIENT
When it was first installed on my zLinux servers, BESCLIENT used 2-5% of the CPU available to each guest. We didn't have the extra CPU for this increase on 26 guests. I contacted the team that implemented it and they were able to tweak a parameter that reduced the CPU overhead to less than 1%. That was several years ago and I don't know more than that. The person who made that change is no longer with the company and I doubt that anyone else knows what he changed. I believe the change was made outside of the zLinux guests, at the server that gathers all of the information. I actually installed BESCLIENT as I have root access and the person who made the change did not have any access to the servers. Harley Linker Jr. Sr. Systems Programmer Ensono e: harley.lin...@ensono.com o: 630.944.5111 www.ensono.com -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Victor Echavarry Sent: Tuesday, February 27, 2018 7:47 AM To: LINUX-390@VM.MARIST.EDU Subject: BESCLIENT A couple of days ago our VM's begin a sustained increase in CPU usage. We began an investigation checking recently changes on the LPAR's and the guests. The only thing we found is that inside all the guests the BESCLIENT was installed. Although it the process doesn't show high CPU utilization, we turn it off and the VM's stabilized. Do anyone has similar issue with this product? Regards, Victor Echavarry System Programmer Operating Systems EVERTEC, LLC -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.marist.edu%2Fhtbin%2Fwlvindex%3FLINUX-390=02%7C01%7Charley.linker%40ENSONO.COM%7C625f3a2a8b19423397e808d57e143fab%7Cd483ed84f7bf4078a58ffb250feccf8f%7C0%7C1%7C636553547797429945=vH6LrO8oBhSB0dUtX6CRRSRuzuSDw5axQ1tGaygyuZI%3D=0 -- For more information on Linux on System z, visit https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwiki.linuxvm.org%2F=02%7C01%7Charley.linker%40ENSONO.COM%7C625f3a2a8b19423397e808d57e143fab%7Cd483ed84f7bf4078a58ffb250feccf8f%7C0%7C1%7C636553547797429945=WxOS3wq6Ax4ghCOEPZXVK%2Fl4jYBkOtqh9NzOeOTtfaY%3D=0 © 2018 Ensono, LP. All rights reserved. Ensono is a trademark of Ensono, LP. The information contained in this communication is confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please resend this communication to the sender and delete the original message or any copy of it from your computer system.
Re: Problem running zypper upgrade
If the root is under btrfs, then the output of 'df' is misleading as the space could be tied up by snapshots. Below are commands that I used last week to find and free space in a root filesystem. Command to list info about snapshots: snapper -c root list Command to delete a snapshot: snapper -c root delete 2 Command to list space in a btrfs filesystem: btrfs fi df . Commands to list info about a single filesystem: btrfs fi show / Commands to display info about all btrfs filesystems: btrfs fi show Command to move data out of block (i.e. defrag): btrfs balance start -dusage=50 / Note: dusage is a percentage. Start at 5 and increase by 5 until data gets moved. Command to balance the metadata area of a btrfs filesystem (/ is for root): btrfs balance start -m / Command to balance the data area of a btrfs filesystem (/ is for root): btrfs balance start -d / I hope this helps. Harley Linker Jr. Sr. Systems Programmer Ensono e: harley.lin...@ensono.com o: 630.944.5111 www.ensono.com -Original Message- From: Linux on 390 Port On Behalf Of Neale Ferguson Sent: Monday, October 22, 2018 4:16 AM To: LINUX-390@VM.MARIST.EDU Subject: Problem running zypper upgrade I probably don’t understand BTRFS enough to work this out, but running zipper upgrade fails with a no space left condition but according to df I have heaps of free space: ( 82/245) Installing: kernel-source-4.4.156-94.61.1.noarch ..[error] Installation of kernel-source-4.4.156-94.61.1.noarch failed: Error: Subprocess failed. Error: RPM failed: error: unpacking of archive failed on file /usr/src/linux-4.4.156-94.61/Documentation/devicetree/bindings/mfd/atmel-gpbr.txt: cpio: rename failed - No space left on device error: kernel-source-4.4.156-94.61.1.noarch: install failed Abort, retry, ignore? [a/r/i] (a): A Problem occurred during or after installation or removal of packages: Installation aborted by user Please see the above error message for a hint. lneale4:~ # df -h /usr/src Filesystem Size Used Avail Use% Mounted on /dev/dasdb2 52G 23G 30G 44% / What am I missing? -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.marist.edu%2Fhtbin%2Fwlvindex%3FLINUX-390data=02%7C01%7Charley.linker%40ENSONO.COM%7C1ebaae2be79644d0728808d637ff9ea8%7Cd483ed84f7bf4078a58ffb250feccf8f%7C0%7C0%7C636757968359360480sdata=5EubMTXCPlnjrH2KCBK2WeaP6kD5W0fyna2UhI4rShU%3Dreserved=0 -- For more information on Linux on System z, visit https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwiki.linuxvm.org%2Fdata=02%7C01%7Charley.linker%40ENSONO.COM%7C1ebaae2be79644d0728808d637ff9ea8%7Cd483ed84f7bf4078a58ffb250feccf8f%7C0%7C0%7C636757968359360480sdata=yVjP%2Fk1EUUuxKar7IVIu5HpSak54RfIx2vT60IHjdUE%3Dreserved=0 © 2018 Ensono, LP. All rights reserved. Ensono is a trademark of Ensono, LP. The information contained in this communication is confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please resend this communication to the sender and delete the original message or any copy of it from your computer system. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Problem running zypper upgrade
You have about 30G of data space available but the available metadata is close to being full. That could be your problem, but I am new to btrfs. I reformatted your output to make it more readable: # btrfs filesystem df / Data, single: total=50.02GiB, used=20.89GiB System, RAID1: total=32.00MiB, used=16.00KiB Metadata, RAID1: total=79.06MiB, used=73.30MiB Metadata, DUP: total=725.50MiB, used=638.70MiB GlobalReserve, single: total=69.91MiB, used=64.00KiB You can try to balance the metadata area using ' btrfs balance start -m /'. My filesystem was low on data space but when I ran the command to balance the metadata area, over 700MB was freed up (according to the 'df' command). I ended up balancing the metadata and data areas, then ran the command to defrag the data blocks. I ran ' btrfs balance start -dusage=5 /' and increased the 'dusage' value by 5 until it said that it did anything. It was up to 'dusage=50' when this happened. Harley Linker Jr. Sr. Systems Programmer Ensono e: harley.lin...@ensono.com o: 630.944.5111 www.ensono.com -Original Message- From: Linux on 390 Port On Behalf Of Neale Ferguson Sent: Monday, October 22, 2018 7:11 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Problem running zypper upgrade Thanks, it doesn’t look like I have much: # snapper list Type | # | Pre # | Date | User | Cleanup | Description | Userdata ---+---+---+--+--+-+---+- single | 0 | | | root | | current | single | 1 | | Tue Feb 2 12:01:30 2016 | root | | first root filesystem | # btrfs filesystem df / Data, single: total=50.02GiB, used=20.89GiB System, RAID1: total=32.00MiB, used=16.00KiB Metadata, RAID1: total=79.06MiB, used=73.30MiB Metadata, DUP: total=725.50MiB, used=638.70MiB GlobalReserve, single: total=69.91MiB, used=64.00KiB # btrfs filesystem usage / Overall: Device size: 51.66GiB Device allocated: 51.65GiB Device unallocated: 3.08MiB Device missing: 0.00B Used: 22.28GiB Free (estimated): 29.13GiB (min: 29.13GiB) Data ratio:1.00 Metadata ratio:2.00 Global reserve:69.91MiB (used: 64.00KiB) Data,single: Size:50.02GiB, Used:20.89GiB /dev/dasdb2 5.64GiB /dev/dasdd 21.99GiB /dev/dasde1 22.38GiB Metadata,RAID1: Size:79.06MiB, Used:73.30MiB /dev/dasdb2 79.06MiB /dev/dasde1 79.06MiB Metadata,DUP: Size:725.50MiB, Used:638.70MiB /dev/dasdb2 939.00MiB /dev/dasdd512.00MiB System,RAID1: Size:32.00MiB, Used:16.00KiB /dev/dasdb2 32.00MiB /dev/dasde1 32.00MiB Unallocated: /dev/dasdb2 1.00MiB /dev/dasdd 1.05MiB /dev/dasde1 1.03MiB # btrfs fi show Label: none uuid: d80841ed-2839-4dfc-b3be-4539adce5eb5 Total devices 3 FS bytes used 21.58GiB devid1 size 6.67GiB used 6.67GiB path /dev/dasdb2 devid2 size 22.49GiB used 22.49GiB path /dev/dasdd devid3 size 22.49GiB used 22.49GiB path /dev/dasde1 I’m not sure why it used /dev/dasdd rather than ./dev/dasdd1 On 10/22/18, 07:23, "Linux on 390 Port on behalf of Harley Linker" wrote: If the root is under btrfs, then the output of 'df' is misleading as the space could be tied up by snapshots. Below are commands that I used last week to find and free space in a root filesystem. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.marist.edu%2Fhtbin%2Fwlvindex%3FLINUX-390data=02%7C01%7Charley.linker%40ENSONO.COM%7C7cac7be10a564d95a08608d638184059%7Cd483ed84f7bf4078a58ffb250feccf8f%7C0%7C0%7C636758074153999796sdata=9jNlwkLZmsoZ13KuzL90%2Be0UeJJEQH0tmZe9qKqYqOs%3Dreserved=0 -- For more information on Linux on System z, visit https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwiki.linuxvm.org%2Fdata=02%7C01%7Charley.linker%40ENSONO.COM%7C7cac7be10a564d95a08608d638184059%7Cd483ed84f7bf4078a58ffb250feccf8f%7C0%7C0%7C636758074154009804sdata=%2BAP%2FquU9GhbfTUFZQ8UVOkkoj8C4JB3a%2BjA0fDOco7Q%3Dreserved=0 © 2018 Ensono, LP. All rights reserved. Ensono is a trademark of Ensono, LP. The information contained in this communication is confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please resend this communication to
Re: backup product
You may want to investigate IBM's Spectrum Protect. I don't know if it supports SLES 15 or not though. One of my clients uses the Base componenet to backup SLES 11 and SLES 12 zLinux hosts (non-database files) and also runs a component that is database aware to back up the Oracle databases. Harley Linker Jr. Sr. Systems Programmer Ensono e: harley.lin...@ensono.com o: 630.944.5111 www.ensono.com -Original Message- From: Linux on 390 Port On Behalf Of Levy, Alan Sent: Monday, November 4, 2019 12:01 PM To: LINUX-390@VM.MARIST.EDU Subject: backup product *** ATTENTION! This message originated from outside of Ensono. Treat hyperlinks and attachments in this email with caution. *** The divisions here are migrating away from Netbackup to CommVault. The only problem is that Netbackup currently does not work with SLES15 and CommVault is not certified for s390x SLES15 (only for x86). Does anyone have any recommendations for a product that will backup up our linux servers (dasd and san) ? We are also precluded from using VMTAPE and VMBACKUP (from CA). Thanks. This e-mail, including any attachments, may be confidential, privileged or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit https://nam03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww2.marist.edu%2Fhtbin%2Fwlvindex%3FLINUX-390data=02%7C01%7Charley.linker%40ENSONO.COM%7C8b3b7ab651f94770296f08d761511c56%7Cd483ed84f7bf4078a58ffb250feccf8f%7C0%7C1%7C637084873320314699sdata=EW4EUfZklAEhZSk5e7OF9WFUH6OXIsdTYDhGHgtIQ1U%3Dreserved=0 © 2019 Ensono, LP. All rights reserved. Ensono is a trademark of Ensono, LP. The information contained in this communication is confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please resend this communication to the sender and delete the original message or any copy of it from your computer system. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
