Linux cache tuning
Hi everybody, I'm trying to find the best way to tune Linux disk caching, but the Blueprints are not mentioning anything about these parameters. On the Internet, I find some mixed information about tuning disk cache in a SAN environment, so I'm wondering what everybody else is using. If you are using SP with SAN storage attached, can you please send me the output from the following commands: sysctl vm.dirty_ratio sysctl vm.dirty_background_ratio sysctl vm.dirty_expire_centisecs sysctl vm.dirty_writeback_centisecs Just for comparison reasons. Thanks in advance! Kind regards, Eric van Loon Air France/KLM Core Infra For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286
Re: 8.1.15 Linux client update causing failures
Good to hear. I opened a ticket as Andy recommended but have not heard anything about an available eFix. FWIW, I seemed to have caused these issues when I re-activated replication on one of my servers. This server was originally using virtual volumes to create offsite backups (trying to move away from tapes since we will be getting rid of magnetic tape/libraries by the time we move to a new datacenter by the end of 2023). However, we started having weekly cores/crashes on this server. At first IBM gave us an eFix (8.1.14.102) but we continued to have weekly crashes and when IBM analyzed our latest crash, they said they discovered a new problem caused by RECONCILE VOLUMES which we use daily on these virtual volumes/server. On Wed, Jul 20, 2022 at 4:58 AM Loon, Eric van (ITOP DI) - KLM < eric-van.l...@klm.com> wrote: > Hi everybody, > > I tested a fix I received from IBM this morning, which seems to be working > OK. So let's hope IBM will release a 8.1.15.100 soon. > > Kind regards, > Eric van Loon > Core Infra > > -Original Message- > From: ADSM: Dist Stor Manager On Behalf Of Andrew > Raibeck > Sent: dinsdag 19 juli 2022 22:46 > To: ADSM-L@VM.MARIST.EDU > Subject: Re: 8.1.15 Linux client update causing failures > > Hi, the following flash is published for this issue. > > https://www.ibm.com/support/pages/node/6605073 > > Best regards, > > Andy > > Andrew Raibeck > IBM Spectrum Protect Level 3 > IBM Systems, Storage > stor...@us.ibm.com > > IBM > > -Original Message- > From: ADSM: Dist Stor Manager On Behalf Of Andrew > Raibeck > Sent: Tuesday, 19 July, 2022 07:05 > To: ADSM-L@VM.MARIST.EDU > Subject: [EXTERNAL] Re: 8.1.15 Linux client update causing failures > > Hi Michael, > > The APAR is IT41452. It is not yet visible on the web, but it should be in > the next day or two. Then, until the APAR is closed, you need to log in > with your IBM ID to view it. > > Best regards, > > Andy > > Andrew Raibeck > IBM Spectrum Protect Level 3 > IBM Systems, Storage > stor...@us.ibm.com > > IBM > > -Original Message- > From: ADSM: Dist Stor Manager On Behalf Of Michael > Roesch > Sent: Tuesday, 19 July, 2022 05:30 > To: ADSM-L@VM.MARIST.EDU > Subject: [EXTERNAL] Re: 8.1.15 Linux client update causing failures > > Hi all, > > Did IBM already create an APAR for this issue? We're currently holding off > on the 8.1.15.0 client rollout and it would be great to know if IBM's > initial assumptions have proven true, which would mean we're not affected > b/c we don't use replication. > > Thank you > > Kind regards > Michael Roesch > > On Thu, Jul 14, 2022 at 2:29 PM Andrew Raibeck wrote: > > > Hi Zoltan, > > > > The problem I refer to occurs immediately while starting the client. > > Even by merely running "dsmc", it crashes. Is that the case for you? > > Or does the operation run for a period of time, and then crash? If the > > problem occurs on a particular client, does it always occur? Or is it > intermittent? > > > > If you have gdb installed on a representative system, then try getting > > a stack trace. > > > > 1. Start gdb: > > > > gdb /opt/tivoli/tsm/client/ba/bin/dsmc core_file_name > > > > where "core_file_name" is the name of the core. > > > > 2. In the "(gdb)" prompt, type these commands: > > > > bt > > q > > > > The first command shows the backtrace (which is the part of interest) > > and the second command quits the debugger. > > > > If you do not have a core file, then it is probably because the core > > file ulimit is too small or 0. Run "ulimit -c" to display the current > value. > > Then run "ulimit -c unlimited", reproduce the issue, and get the > > backtrace as I previously mentioned. After, you can set the ulimit > > back to its original value and delete the core file. > > > > The following article includes an alternative (and more comprehensive) > > doc > > collection: > > > > > > https://www.ibm.com/support/pages/collecting-data-spectrum-protect-cli > > ent-crash-linux > > > > The following is a representative backtrace of the problem I referred to. > > > > (gdb) bt > > #0 0x7f04e2c06387 in raise () from /lib64/libc.so.6 > > #1 0x7f04e2c07a78 in abort () from /lib64/libc.so.6 > > #2 0x00712a74 in psTrapHandler(int) () > > #3 > > #4 0x7f04e2c06387 in raise () from /lib64/libc.so.6 > > #5 0x7f04e2c07a78 in abort () from /lib64/libc.so.6 > &
Re: 8.1.15 Linux client update causing failures
Hi, the following flash is published for this issue. https://www.ibm.com/support/pages/node/6605073 Best regards, Andy Andrew Raibeck IBM Spectrum Protect Level 3 IBM Systems, Storage stor...@us.ibm.com IBM -Original Message- From: ADSM: Dist Stor Manager On Behalf Of Andrew Raibeck Sent: Tuesday, 19 July, 2022 07:05 To: ADSM-L@VM.MARIST.EDU Subject: [EXTERNAL] Re: 8.1.15 Linux client update causing failures Hi Michael, The APAR is IT41452. It is not yet visible on the web, but it should be in the next day or two. Then, until the APAR is closed, you need to log in with your IBM ID to view it. Best regards, Andy Andrew Raibeck IBM Spectrum Protect Level 3 IBM Systems, Storage stor...@us.ibm.com IBM -Original Message- From: ADSM: Dist Stor Manager On Behalf Of Michael Roesch Sent: Tuesday, 19 July, 2022 05:30 To: ADSM-L@VM.MARIST.EDU Subject: [EXTERNAL] Re: 8.1.15 Linux client update causing failures Hi all, Did IBM already create an APAR for this issue? We're currently holding off on the 8.1.15.0 client rollout and it would be great to know if IBM's initial assumptions have proven true, which would mean we're not affected b/c we don't use replication. Thank you Kind regards Michael Roesch On Thu, Jul 14, 2022 at 2:29 PM Andrew Raibeck wrote: > Hi Zoltan, > > The problem I refer to occurs immediately while starting the client. > Even by merely running "dsmc", it crashes. Is that the case for you? > Or does the operation run for a period of time, and then crash? If the > problem occurs on a particular client, does it always occur? Or is it > intermittent? > > If you have gdb installed on a representative system, then try getting > a stack trace. > > 1. Start gdb: > > gdb /opt/tivoli/tsm/client/ba/bin/dsmc core_file_name > > where "core_file_name" is the name of the core. > > 2. In the "(gdb)" prompt, type these commands: > > bt > q > > The first command shows the backtrace (which is the part of interest) > and the second command quits the debugger. > > If you do not have a core file, then it is probably because the core > file ulimit is too small or 0. Run "ulimit -c" to display the current value. > Then run "ulimit -c unlimited", reproduce the issue, and get the > backtrace as I previously mentioned. After, you can set the ulimit > back to its original value and delete the core file. > > The following article includes an alternative (and more comprehensive) > doc > collection: > > > https://www.ibm.com/support/pages/collecting-data-spectrum-protect-cli > ent-crash-linux > > The following is a representative backtrace of the problem I referred to. > > (gdb) bt > #0 0x7f04e2c06387 in raise () from /lib64/libc.so.6 > #1 0x7f04e2c07a78 in abort () from /lib64/libc.so.6 > #2 0x00712a74 in psTrapHandler(int) () > #3 > #4 0x7f04e2c06387 in raise () from /lib64/libc.so.6 > #5 0x7f04e2c07a78 in abort () from /lib64/libc.so.6 > #6 0x7f04e2c48ed7 in __libc_message () from /lib64/libc.so.6 > #7 0x7f04e2c51299 in _int_free () from /lib64/libc.so.6 > #8 0x7f04e2c3e1b7 in fclose@@GLIBC_2.2.5 () from /lib64/libc.so.6 > #9 0x006efe2f in clientOptions::optSaveReplConnInfo() () > #10 0x0068103f in cuSignOnEResp(Sess_o*) () > #11 0x00652b75 in scSignOnTheSession(Sess_o*) () > #12 0x00658ce3 in NegotiateSession(Sess_o*) () > #13 0x00653648 in OpenSess(Sess_o*, bool) () > #14 0x00654ad0 in Logon(Sess_o*) () > #15 0x00656c36 in CheckSession(Sess_o*, sessLoadPolicy_t) () > #16 0x0043e5fe in dscInit(int, char**, cliType_t) () > #17 0x0043eb5b in dscmain(int, char**) () > #18 0x0043b3fa in main () > > If your backtrace differs, or you want further assistance diagnosing > your particular instance of the crash, then please open a support case with > IBM. > If you want, you can privately email your case number to me, for my > awareness. > > If you open a case with IBM, it will help support "hit the ground running" > if you can provide some information up front. > > 1. Temporarily enable core file creation. > > 2. Add these options to configure the client for SERVICE tracing: > > TRACEFLAGS SERVICE > TRACEFILE /some_path/dsmc_trace.txt > > (I'm sure you have done this befoe.) > > 3. Reproduce the problem. > > 4. Collect the diagnostic data as described in this article: > > > https://www.ibm.com/support/pages/collecting-data-spectrum-protect-cli > ent-crash-linux > > 5. Put the core file ulimit setting back to its original value. > > 6. Open a case with IBM and provide the service trace, dsm
Re: 8.1.15 Linux client update causing failures
Thank you, Andy On Thu, Jul 14, 2022 at 12:39 PM Andrew Raibeck wrote: > Hi, > > Initial assessment is that clients that meet all of the following > conditions are affected: > > - The client is Linux (any architecture), including backup-archive client > and API applications > - The client is configured for automatic failover to a replication server > > Note that the preceding information is subject to change as we learn more. > > Kindest regards, > > Andy > > Andrew Raibeck > IBM Spectrum Protect Level 3 > IBM Systems, Storage > stor...@us.ibm.com > > IBM > > -Original Message- > From: ADSM: Dist Stor Manager On Behalf Of Michael > Roesch > Sent: Thursday, 14 July, 2022 06:23 > To: ADSM-L@VM.MARIST.EDU > Subject: [EXTERNAL] Re: 8.1.15 Linux client update causing failures > > Hi, > > Does the client for AIX show this problem as well? Did this happen on x64 > Linux or also on PPC? > > Kind regards > Michael Roesch > > On Wed, Jul 13, 2022 at 4:19 AM Saravanan Palanisamy < > evergreen.sa...@gmail.com> wrote: > > > So far We don’t see any issues in windows. All scheduled backups are > > successful. > > > > Regards > > Sarav > > +65 9857 8665 > > > > > > > On 13 Jul 2022, at 9:00 AM, Tom Alverson > wrote: > > > > > > Is the windows client safe for this version? > > > > > > > > >> On Tue, Jul 12, 2022, 7:06 PM Saravanan Palanisamy < > > >> evergreen.sa...@gmail.com> wrote: > > >> > > >> Hi Zoltan > > >> > > >> Yes we have also faced same issue and IBM support confirmed they > > >> will > > open > > >> new APAR. We have reverted all clients v8.1.14 to address the issue. > > >> > > >> Regards > > >> Sarav > > >> +65 9857 8665 > > >> > > >> > > >>>> On 13 Jul 2022, at 2:31 AM, Del Hoobler wrote: > > >>> > > >>> Hi Zoltan, > > >>> > > >>> IBM knows about this ... and it's being actively worked. > > >>> > > >>> I am sure it will be mitigated soon. > > >>> > > >>> Feel free to open a fresh IBM Support case so you can be quickly > > >> notified once it is fixed. > > >>> > > >>> > > >>> Del > > >>> > > >>> ____ > > >>> From: ADSM: Dist Stor Manager on behalf of > > >> Zoltan Forray > > >>> Sent: Tuesday, July 12, 2022 1:56 PM > > >>> To: ADSM-L@VM.MARIST.EDU > > >>> Subject: [EXTERNAL] 8.1.15 Linux client update causing failures > > >>> > > >>> We started rolling out the 8.1.15 Linux client via apogee and many > > >> clients > > >>> are failing with: > > >>> > > >>> *** Error in `dsmc': double free or corruption (!prev): > > >> 0x02baf970 > > >>> *** > > >>> > > >>> The only matching Google hit goes back to a V7 client issue - long > > fixed. > > >>> > > >>> At first I thought it might be related to a Linux flavor (we run > > Rocky8, > > >>> CentOS 7.1/8, RHEL 7/8) but I don't see a pattern. All of these > > servers > > >>> are upgrading from 8.1.14 and downleveling the client to 8.1.14 > > >>> fixes > > >> this. > > >>> > > >>> Anyone else seeing this? > > >>> > > >>> FWIW, I could swear that during one of my many Google searches I > > >>> saw a reference to 8.1.15.2 (eFix?) but now I can't find it again. > > >>> -- > > >>> *Zoltan Forray* > > >>> Enterprise Backup Administrator > > >>> VMware Systems Administrator > > >>> Enterprise Compute & Storage Platforms Team VCU Infrastructure > > >>> Services > > >>> www.ucc.vcu.edu > >>> __www.ucc.vcu.edu&d=DwIFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=Ij6DLy1l7wDp > > >>> CbTfcDkLC_KknvhyGdCy_RnAGnhV37I&m=lx_phvPLtz3INd_W8oJ4eGdfN5WYsItt > > >>> NeFE_AVOLSP0Mp2Rq34RX6Nb9ogoyHYd&s=e_k1hOLaA6N1PWcNH0bBFZaIJtG1FAb > > >>> mQyN9dy5iR6c&e= > zfor...@vcu.edu - 804-828-4807 Don't be a > > >>> phishing victim - VCU and other reputable organizations will never > > >>> use email to request that you reply with your password, social > > >>> security number or confidential personal information. For more > > >>> details visit > > >>> INVALID URI REMOVED > > >>> du_&d=DwIFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=Ij6DLy1l7wDpCbTfcDkLC_Kknv > > >>> hyGdCy_RnAGnhV37I&m=lx_phvPLtz3INd_W8oJ4eGdfN5WYsIttNeFE_AVOLSP0Mp > > >>> 2Rq34RX6Nb9ogoyHYd&s=VS499q-uVPEP-6-QrjIgicZ_oLB4kvyLNBmMlJeWBEI&e > > >>> = > > >>> > >>> questionpro.com&d=DwIFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=Ij6DLy1l7wDpCb > > >>> TfcDkLC_KknvhyGdCy_RnAGnhV37I&m=lx_phvPLtz3INd_W8oJ4eGdfN5WYsIttNe > > >>> FE_AVOLSP0Mp2Rq34RX6Nb9ogoyHYd&s=BqXWlinKYJb1mlgHqBJJz4HitGo2CCEEt > > >>> UAK46yC9F4&e= > > > >> > > >
Re: 8.1.15 Linux client update causing failures
Hi Michael, The APAR is IT41452. It is not yet visible on the web, but it should be in the next day or two. Then, until the APAR is closed, you need to log in with your IBM ID to view it. Best regards, Andy Andrew Raibeck IBM Spectrum Protect Level 3 IBM Systems, Storage stor...@us.ibm.com IBM -Original Message- From: ADSM: Dist Stor Manager On Behalf Of Michael Roesch Sent: Tuesday, 19 July, 2022 05:30 To: ADSM-L@VM.MARIST.EDU Subject: [EXTERNAL] Re: 8.1.15 Linux client update causing failures Hi all, Did IBM already create an APAR for this issue? We're currently holding off on the 8.1.15.0 client rollout and it would be great to know if IBM's initial assumptions have proven true, which would mean we're not affected b/c we don't use replication. Thank you Kind regards Michael Roesch On Thu, Jul 14, 2022 at 2:29 PM Andrew Raibeck wrote: > Hi Zoltan, > > The problem I refer to occurs immediately while starting the client. > Even by merely running "dsmc", it crashes. Is that the case for you? > Or does the operation run for a period of time, and then crash? If the > problem occurs on a particular client, does it always occur? Or is it > intermittent? > > If you have gdb installed on a representative system, then try getting > a stack trace. > > 1. Start gdb: > > gdb /opt/tivoli/tsm/client/ba/bin/dsmc core_file_name > > where "core_file_name" is the name of the core. > > 2. In the "(gdb)" prompt, type these commands: > > bt > q > > The first command shows the backtrace (which is the part of interest) > and the second command quits the debugger. > > If you do not have a core file, then it is probably because the core > file ulimit is too small or 0. Run "ulimit -c" to display the current value. > Then run "ulimit -c unlimited", reproduce the issue, and get the > backtrace as I previously mentioned. After, you can set the ulimit > back to its original value and delete the core file. > > The following article includes an alternative (and more comprehensive) > doc > collection: > > > https://www.ibm.com/support/pages/collecting-data-spectrum-protect-cli > ent-crash-linux > > The following is a representative backtrace of the problem I referred to. > > (gdb) bt > #0 0x7f04e2c06387 in raise () from /lib64/libc.so.6 > #1 0x7f04e2c07a78 in abort () from /lib64/libc.so.6 > #2 0x00712a74 in psTrapHandler(int) () > #3 > #4 0x7f04e2c06387 in raise () from /lib64/libc.so.6 > #5 0x7f04e2c07a78 in abort () from /lib64/libc.so.6 > #6 0x7f04e2c48ed7 in __libc_message () from /lib64/libc.so.6 > #7 0x7f04e2c51299 in _int_free () from /lib64/libc.so.6 > #8 0x7f04e2c3e1b7 in fclose@@GLIBC_2.2.5 () from /lib64/libc.so.6 > #9 0x006efe2f in clientOptions::optSaveReplConnInfo() () > #10 0x0068103f in cuSignOnEResp(Sess_o*) () > #11 0x00652b75 in scSignOnTheSession(Sess_o*) () > #12 0x00658ce3 in NegotiateSession(Sess_o*) () > #13 0x00653648 in OpenSess(Sess_o*, bool) () > #14 0x00654ad0 in Logon(Sess_o*) () > #15 0x00656c36 in CheckSession(Sess_o*, sessLoadPolicy_t) () > #16 0x0043e5fe in dscInit(int, char**, cliType_t) () > #17 0x0043eb5b in dscmain(int, char**) () > #18 0x0043b3fa in main () > > If your backtrace differs, or you want further assistance diagnosing > your particular instance of the crash, then please open a support case with > IBM. > If you want, you can privately email your case number to me, for my > awareness. > > If you open a case with IBM, it will help support "hit the ground running" > if you can provide some information up front. > > 1. Temporarily enable core file creation. > > 2. Add these options to configure the client for SERVICE tracing: > > TRACEFLAGS SERVICE > TRACEFILE /some_path/dsmc_trace.txt > > (I'm sure you have done this befoe.) > > 3. Reproduce the problem. > > 4. Collect the diagnostic data as described in this article: > > > https://www.ibm.com/support/pages/collecting-data-spectrum-protect-cli > ent-crash-linux > > 5. Put the core file ulimit setting back to its original value. > > 6. Open a case with IBM and provide the service trace, dsmc output (or > dsmsched.log if you schedule the operation), dsmerror.log, and the > files collected from the article of step 4. > > You can remove the core file after the data is sent to IBM. > > Regards, > > Andrew Raibeck > IBM Spectrum Protect Level 3 > IBM Systems, Storage > stor...@us.ibm.com > > IBM > > -Original Message- > From: ADSM: Dist Stor Manager On Behalf
Re: 8.1.15 Linux client update causing failures
Hi all, Did IBM already create an APAR for this issue? We're currently holding off on the 8.1.15.0 client rollout and it would be great to know if IBM's initial assumptions have proven true, which would mean we're not affected b/c we don't use replication. Thank you Kind regards Michael Roesch On Thu, Jul 14, 2022 at 2:29 PM Andrew Raibeck wrote: > Hi Zoltan, > > The problem I refer to occurs immediately while starting the client. Even > by merely running "dsmc", it crashes. Is that the case for you? Or does the > operation run for a period of time, and then crash? If the problem occurs > on a particular client, does it always occur? Or is it intermittent? > > If you have gdb installed on a representative system, then try getting a > stack trace. > > 1. Start gdb: > > gdb /opt/tivoli/tsm/client/ba/bin/dsmc core_file_name > > where "core_file_name" is the name of the core. > > 2. In the "(gdb)" prompt, type these commands: > > bt > q > > The first command shows the backtrace (which is the part of interest) and > the second command quits the debugger. > > If you do not have a core file, then it is probably because the core file > ulimit is too small or 0. Run "ulimit -c" to display the current value. > Then run "ulimit -c unlimited", reproduce the issue, and get the backtrace > as I previously mentioned. After, you can set the ulimit back to its > original value and delete the core file. > > The following article includes an alternative (and more comprehensive) doc > collection: > > > https://www.ibm.com/support/pages/collecting-data-spectrum-protect-client-crash-linux > > The following is a representative backtrace of the problem I referred to. > > (gdb) bt > #0 0x7f04e2c06387 in raise () from /lib64/libc.so.6 > #1 0x7f04e2c07a78 in abort () from /lib64/libc.so.6 > #2 0x00712a74 in psTrapHandler(int) () > #3 > #4 0x7f04e2c06387 in raise () from /lib64/libc.so.6 > #5 0x7f04e2c07a78 in abort () from /lib64/libc.so.6 > #6 0x7f04e2c48ed7 in __libc_message () from /lib64/libc.so.6 > #7 0x7f04e2c51299 in _int_free () from /lib64/libc.so.6 > #8 0x7f04e2c3e1b7 in fclose@@GLIBC_2.2.5 () from /lib64/libc.so.6 > #9 0x006efe2f in clientOptions::optSaveReplConnInfo() () > #10 0x0068103f in cuSignOnEResp(Sess_o*) () > #11 0x00652b75 in scSignOnTheSession(Sess_o*) () > #12 0x00658ce3 in NegotiateSession(Sess_o*) () > #13 0x00653648 in OpenSess(Sess_o*, bool) () > #14 0x00654ad0 in Logon(Sess_o*) () > #15 0x00656c36 in CheckSession(Sess_o*, sessLoadPolicy_t) () > #16 0x0043e5fe in dscInit(int, char**, cliType_t) () > #17 0x0043eb5b in dscmain(int, char**) () > #18 0x0043b3fa in main () > > If your backtrace differs, or you want further assistance diagnosing your > particular instance of the crash, then please open a support case with IBM. > If you want, you can privately email your case number to me, for my > awareness. > > If you open a case with IBM, it will help support "hit the ground running" > if you can provide some information up front. > > 1. Temporarily enable core file creation. > > 2. Add these options to configure the client for SERVICE tracing: > > TRACEFLAGS SERVICE > TRACEFILE /some_path/dsmc_trace.txt > > (I'm sure you have done this befoe.) > > 3. Reproduce the problem. > > 4. Collect the diagnostic data as described in this article: > > > https://www.ibm.com/support/pages/collecting-data-spectrum-protect-client-crash-linux > > 5. Put the core file ulimit setting back to its original value. > > 6. Open a case with IBM and provide the service trace, dsmc output (or > dsmsched.log if you schedule the operation), dsmerror.log, and the files > collected from the article of step 4. > > You can remove the core file after the data is sent to IBM. > > Regards, > > Andrew Raibeck > IBM Spectrum Protect Level 3 > IBM Systems, Storage > stor...@us.ibm.com > > IBM > > -Original Message- > From: ADSM: Dist Stor Manager On Behalf Of Zoltan > Forray > Sent: Thursday, 14 July, 2022 08:04 > To: ADSM-L@VM.MARIST.EDU > Subject: [EXTERNAL] Re: 8.1.15 Linux client update causing failures > > Andy, > > You said *"- The client is configured for automatic failover to a > replication server"* but that doesn't jive with our situation/environment. > Until recently, we have not run replication on any of our backups (offsite > copies are to tape or virtual volumes on another ISP server) and disk > backups are to non-container (FILE) storage. I
Re: 8.1.15 Linux client update causing failures
Hi Zoltan, The problem I refer to occurs immediately while starting the client. Even by merely running "dsmc", it crashes. Is that the case for you? Or does the operation run for a period of time, and then crash? If the problem occurs on a particular client, does it always occur? Or is it intermittent? If you have gdb installed on a representative system, then try getting a stack trace. 1. Start gdb: gdb /opt/tivoli/tsm/client/ba/bin/dsmc core_file_name where "core_file_name" is the name of the core. 2. In the "(gdb)" prompt, type these commands: bt q The first command shows the backtrace (which is the part of interest) and the second command quits the debugger. If you do not have a core file, then it is probably because the core file ulimit is too small or 0. Run "ulimit -c" to display the current value. Then run "ulimit -c unlimited", reproduce the issue, and get the backtrace as I previously mentioned. After, you can set the ulimit back to its original value and delete the core file. The following article includes an alternative (and more comprehensive) doc collection: https://www.ibm.com/support/pages/collecting-data-spectrum-protect-client-crash-linux The following is a representative backtrace of the problem I referred to. (gdb) bt #0 0x7f04e2c06387 in raise () from /lib64/libc.so.6 #1 0x7f04e2c07a78 in abort () from /lib64/libc.so.6 #2 0x00712a74 in psTrapHandler(int) () #3 #4 0x7f04e2c06387 in raise () from /lib64/libc.so.6 #5 0x7f04e2c07a78 in abort () from /lib64/libc.so.6 #6 0x7f04e2c48ed7 in __libc_message () from /lib64/libc.so.6 #7 0x7f04e2c51299 in _int_free () from /lib64/libc.so.6 #8 0x7f04e2c3e1b7 in fclose@@GLIBC_2.2.5 () from /lib64/libc.so.6 #9 0x006efe2f in clientOptions::optSaveReplConnInfo() () #10 0x0068103f in cuSignOnEResp(Sess_o*) () #11 0x00652b75 in scSignOnTheSession(Sess_o*) () #12 0x00658ce3 in NegotiateSession(Sess_o*) () #13 0x00653648 in OpenSess(Sess_o*, bool) () #14 0x00654ad0 in Logon(Sess_o*) () #15 0x00656c36 in CheckSession(Sess_o*, sessLoadPolicy_t) () #16 0x0043e5fe in dscInit(int, char**, cliType_t) () #17 0x0043eb5b in dscmain(int, char**) () #18 0x0043b3fa in main () If your backtrace differs, or you want further assistance diagnosing your particular instance of the crash, then please open a support case with IBM. If you want, you can privately email your case number to me, for my awareness. If you open a case with IBM, it will help support "hit the ground running" if you can provide some information up front. 1. Temporarily enable core file creation. 2. Add these options to configure the client for SERVICE tracing: TRACEFLAGS SERVICE TRACEFILE /some_path/dsmc_trace.txt (I'm sure you have done this befoe.) 3. Reproduce the problem. 4. Collect the diagnostic data as described in this article: https://www.ibm.com/support/pages/collecting-data-spectrum-protect-client-crash-linux 5. Put the core file ulimit setting back to its original value. 6. Open a case with IBM and provide the service trace, dsmc output (or dsmsched.log if you schedule the operation), dsmerror.log, and the files collected from the article of step 4. You can remove the core file after the data is sent to IBM. Regards, Andrew Raibeck IBM Spectrum Protect Level 3 IBM Systems, Storage stor...@us.ibm.com IBM -Original Message- From: ADSM: Dist Stor Manager On Behalf Of Zoltan Forray Sent: Thursday, 14 July, 2022 08:04 To: ADSM-L@VM.MARIST.EDU Subject: [EXTERNAL] Re: 8.1.15 Linux client update causing failures Andy, You said *"- The client is configured for automatic failover to a replication server"* but that doesn't jive with our situation/environment. Until recently, we have not run replication on any of our backups (offsite copies are to tape or virtual volumes on another ISP server) and disk backups are to non-container (FILE) storage. I queried our Linux admins and these failures are all over the place - not just for the few we recently started replicating. On Thu, Jul 14, 2022 at 6:39 AM Andrew Raibeck wrote: > Hi, > > Initial assessment is that clients that meet all of the following > conditions are affected: > > - The client is Linux (any architecture), including backup-archive > client and API applications > - The client is configured for automatic failover to a replication > server > > Note that the preceding information is subject to change as we learn more. > > Kindest regards, > > Andy > > Andrew Raibeck > IBM Spectrum Protect Level 3 > IBM Systems, Storage > stor...@us.ibm.com > > IBM > > -Original Message- > From: ADSM: Dist Stor Manager On Behalf Of > Michael Roesch > Sent: Thursday, 14 July, 2022 06:23 &g
Re: 8.1.15 Linux client update causing failures
Andy, You said *"- The client is configured for automatic failover to a replication server"* but that doesn't jive with our situation/environment. Until recently, we have not run replication on any of our backups (offsite copies are to tape or virtual volumes on another ISP server) and disk backups are to non-container (FILE) storage. I queried our Linux admins and these failures are all over the place - not just for the few we recently started replicating. On Thu, Jul 14, 2022 at 6:39 AM Andrew Raibeck wrote: > Hi, > > Initial assessment is that clients that meet all of the following > conditions are affected: > > - The client is Linux (any architecture), including backup-archive client > and API applications > - The client is configured for automatic failover to a replication server > > Note that the preceding information is subject to change as we learn more. > > Kindest regards, > > Andy > > Andrew Raibeck > IBM Spectrum Protect Level 3 > IBM Systems, Storage > stor...@us.ibm.com > > IBM > > -Original Message- > From: ADSM: Dist Stor Manager On Behalf Of Michael > Roesch > Sent: Thursday, 14 July, 2022 06:23 > To: ADSM-L@VM.MARIST.EDU > Subject: [EXTERNAL] Re: 8.1.15 Linux client update causing failures > > Hi, > > Does the client for AIX show this problem as well? Did this happen on x64 > Linux or also on PPC? > > Kind regards > Michael Roesch > > On Wed, Jul 13, 2022 at 4:19 AM Saravanan Palanisamy < > evergreen.sa...@gmail.com> wrote: > > > So far We don’t see any issues in windows. All scheduled backups are > > successful. > > > > Regards > > Sarav > > +65 9857 8665 > > > > > > > On 13 Jul 2022, at 9:00 AM, Tom Alverson > wrote: > > > > > > Is the windows client safe for this version? > > > > > > > > >> On Tue, Jul 12, 2022, 7:06 PM Saravanan Palanisamy < > > >> evergreen.sa...@gmail.com> wrote: > > >> > > >> Hi Zoltan > > >> > > >> Yes we have also faced same issue and IBM support confirmed they > > >> will > > open > > >> new APAR. We have reverted all clients v8.1.14 to address the issue. > > >> > > >> Regards > > >> Sarav > > >> +65 9857 8665 > > >> > > >> > > >>>> On 13 Jul 2022, at 2:31 AM, Del Hoobler wrote: > > >>> > > >>> Hi Zoltan, > > >>> > > >>> IBM knows about this ... and it's being actively worked. > > >>> > > >>> I am sure it will be mitigated soon. > > >>> > > >>> Feel free to open a fresh IBM Support case so you can be quickly > > >> notified once it is fixed. > > >>> > > >>> > > >>> Del > > >>> > > >>> > > >>> From: ADSM: Dist Stor Manager on behalf of > > >> Zoltan Forray > > >>> Sent: Tuesday, July 12, 2022 1:56 PM > > >>> To: ADSM-L@VM.MARIST.EDU > > >>> Subject: [EXTERNAL] 8.1.15 Linux client update causing failures > > >>> > > >>> We started rolling out the 8.1.15 Linux client via apogee and many > > >> clients > > >>> are failing with: > > >>> > > >>> *** Error in `dsmc': double free or corruption (!prev): > > >> 0x02baf970 > > >>> *** > > >>> > > >>> The only matching Google hit goes back to a V7 client issue - long > > fixed. > > >>> > > >>> At first I thought it might be related to a Linux flavor (we run > > Rocky8, > > >>> CentOS 7.1/8, RHEL 7/8) but I don't see a pattern. All of these > > servers > > >>> are upgrading from 8.1.14 and downleveling the client to 8.1.14 > > >>> fixes > > >> this. > > >>> > > >>> Anyone else seeing this? > > >>> > > >>> FWIW, I could swear that during one of my many Google searches I > > >>> saw a reference to 8.1.15.2 (eFix?) but now I can't find it again. > > >>> -- > > >>> *Zoltan Forray* > > >>> Enterprise Backup Administrator > > >>> VMware Systems Administrator > > >>> Enterprise Compute & Storage Platforms Team VCU Infrastructure > > >>> Services > > >>> www.ucc.vcu.edu > >>> __www.ucc.vcu.edu&d=DwIFaQ&a
Re: 8.1.15 Linux client update causing failures
Hi, Initial assessment is that clients that meet all of the following conditions are affected: - The client is Linux (any architecture), including backup-archive client and API applications - The client is configured for automatic failover to a replication server Note that the preceding information is subject to change as we learn more. Kindest regards, Andy Andrew Raibeck IBM Spectrum Protect Level 3 IBM Systems, Storage stor...@us.ibm.com IBM -Original Message- From: ADSM: Dist Stor Manager On Behalf Of Michael Roesch Sent: Thursday, 14 July, 2022 06:23 To: ADSM-L@VM.MARIST.EDU Subject: [EXTERNAL] Re: 8.1.15 Linux client update causing failures Hi, Does the client for AIX show this problem as well? Did this happen on x64 Linux or also on PPC? Kind regards Michael Roesch On Wed, Jul 13, 2022 at 4:19 AM Saravanan Palanisamy < evergreen.sa...@gmail.com> wrote: > So far We don’t see any issues in windows. All scheduled backups are > successful. > > Regards > Sarav > +65 9857 8665 > > > > On 13 Jul 2022, at 9:00 AM, Tom Alverson wrote: > > > > Is the windows client safe for this version? > > > > > >> On Tue, Jul 12, 2022, 7:06 PM Saravanan Palanisamy < > >> evergreen.sa...@gmail.com> wrote: > >> > >> Hi Zoltan > >> > >> Yes we have also faced same issue and IBM support confirmed they > >> will > open > >> new APAR. We have reverted all clients v8.1.14 to address the issue. > >> > >> Regards > >> Sarav > >> +65 9857 8665 > >> > >> > >>>> On 13 Jul 2022, at 2:31 AM, Del Hoobler wrote: > >>> > >>> Hi Zoltan, > >>> > >>> IBM knows about this ... and it's being actively worked. > >>> > >>> I am sure it will be mitigated soon. > >>> > >>> Feel free to open a fresh IBM Support case so you can be quickly > >> notified once it is fixed. > >>> > >>> > >>> Del > >>> > >>> > >>> From: ADSM: Dist Stor Manager on behalf of > >> Zoltan Forray > >>> Sent: Tuesday, July 12, 2022 1:56 PM > >>> To: ADSM-L@VM.MARIST.EDU > >>> Subject: [EXTERNAL] 8.1.15 Linux client update causing failures > >>> > >>> We started rolling out the 8.1.15 Linux client via apogee and many > >> clients > >>> are failing with: > >>> > >>> *** Error in `dsmc': double free or corruption (!prev): > >> 0x02baf970 > >>> *** > >>> > >>> The only matching Google hit goes back to a V7 client issue - long > fixed. > >>> > >>> At first I thought it might be related to a Linux flavor (we run > Rocky8, > >>> CentOS 7.1/8, RHEL 7/8) but I don't see a pattern. All of these > servers > >>> are upgrading from 8.1.14 and downleveling the client to 8.1.14 > >>> fixes > >> this. > >>> > >>> Anyone else seeing this? > >>> > >>> FWIW, I could swear that during one of my many Google searches I > >>> saw a reference to 8.1.15.2 (eFix?) but now I can't find it again. > >>> -- > >>> *Zoltan Forray* > >>> Enterprise Backup Administrator > >>> VMware Systems Administrator > >>> Enterprise Compute & Storage Platforms Team VCU Infrastructure > >>> Services > >>> www.ucc.vcu.edu >>> __www.ucc.vcu.edu&d=DwIFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=Ij6DLy1l7wDp > >>> CbTfcDkLC_KknvhyGdCy_RnAGnhV37I&m=lx_phvPLtz3INd_W8oJ4eGdfN5WYsItt > >>> NeFE_AVOLSP0Mp2Rq34RX6Nb9ogoyHYd&s=e_k1hOLaA6N1PWcNH0bBFZaIJtG1FAb > >>> mQyN9dy5iR6c&e= > zfor...@vcu.edu - 804-828-4807 Don't be a > >>> phishing victim - VCU and other reputable organizations will never > >>> use email to request that you reply with your password, social > >>> security number or confidential personal information. For more > >>> details visit > >>> INVALID URI REMOVED > >>> du_&d=DwIFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=Ij6DLy1l7wDpCbTfcDkLC_Kknv > >>> hyGdCy_RnAGnhV37I&m=lx_phvPLtz3INd_W8oJ4eGdfN5WYsIttNeFE_AVOLSP0Mp > >>> 2Rq34RX6Nb9ogoyHYd&s=VS499q-uVPEP-6-QrjIgicZ_oLB4kvyLNBmMlJeWBEI&e > >>> = > >>> >>> questionpro.com&d=DwIFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=Ij6DLy1l7wDpCb > >>> TfcDkLC_KknvhyGdCy_RnAGnhV37I&m=lx_phvPLtz3INd_W8oJ4eGdfN5WYsIttNe > >>> FE_AVOLSP0Mp2Rq34RX6Nb9ogoyHYd&s=BqXWlinKYJb1mlgHqBJJz4HitGo2CCEEt > >>> UAK46yC9F4&e= > > >> >
Re: 8.1.15 Linux client update causing failures
Hi, Does the client for AIX show this problem as well? Did this happen on x64 Linux or also on PPC? Kind regards Michael Roesch On Wed, Jul 13, 2022 at 4:19 AM Saravanan Palanisamy < evergreen.sa...@gmail.com> wrote: > So far We don’t see any issues in windows. All scheduled backups are > successful. > > Regards > Sarav > +65 9857 8665 > > > > On 13 Jul 2022, at 9:00 AM, Tom Alverson wrote: > > > > Is the windows client safe for this version? > > > > > >> On Tue, Jul 12, 2022, 7:06 PM Saravanan Palanisamy < > >> evergreen.sa...@gmail.com> wrote: > >> > >> Hi Zoltan > >> > >> Yes we have also faced same issue and IBM support confirmed they will > open > >> new APAR. We have reverted all clients v8.1.14 to address the issue. > >> > >> Regards > >> Sarav > >> +65 9857 8665 > >> > >> > >>>> On 13 Jul 2022, at 2:31 AM, Del Hoobler wrote: > >>> > >>> Hi Zoltan, > >>> > >>> IBM knows about this ... and it's being actively worked. > >>> > >>> I am sure it will be mitigated soon. > >>> > >>> Feel free to open a fresh IBM Support case so you can be quickly > >> notified once it is fixed. > >>> > >>> > >>> Del > >>> > >>> > >>> From: ADSM: Dist Stor Manager on behalf of > >> Zoltan Forray > >>> Sent: Tuesday, July 12, 2022 1:56 PM > >>> To: ADSM-L@VM.MARIST.EDU > >>> Subject: [EXTERNAL] 8.1.15 Linux client update causing failures > >>> > >>> We started rolling out the 8.1.15 Linux client via apogee and many > >> clients > >>> are failing with: > >>> > >>> *** Error in `dsmc': double free or corruption (!prev): > >> 0x02baf970 > >>> *** > >>> > >>> The only matching Google hit goes back to a V7 client issue - long > fixed. > >>> > >>> At first I thought it might be related to a Linux flavor (we run > Rocky8, > >>> CentOS 7.1/8, RHEL 7/8) but I don't see a pattern. All of these > servers > >>> are upgrading from 8.1.14 and downleveling the client to 8.1.14 fixes > >> this. > >>> > >>> Anyone else seeing this? > >>> > >>> FWIW, I could swear that during one of my many Google searches I saw a > >>> reference to 8.1.15.2 (eFix?) but now I can't find it again. > >>> -- > >>> *Zoltan Forray* > >>> Enterprise Backup Administrator > >>> VMware Systems Administrator > >>> Enterprise Compute & Storage Platforms Team > >>> VCU Infrastructure Services > >>> www.ucc.vcu.edu<http://www.ucc.vcu.edu> > >>> zfor...@vcu.edu - 804-828-4807 > >>> Don't be a phishing victim - VCU and other reputable organizations will > >>> never use email to request that you reply with your password, social > >>> security number or confidential personal information. For more details > >>> visit http://phishing.vcu.edu/ > >>> <https://adminmicro2.questionpro.com > > >> >
Re: 8.1.15 Linux client update causing failures
So far We don’t see any issues in windows. All scheduled backups are successful. Regards Sarav +65 9857 8665 > On 13 Jul 2022, at 9:00 AM, Tom Alverson wrote: > > Is the windows client safe for this version? > > >> On Tue, Jul 12, 2022, 7:06 PM Saravanan Palanisamy < >> evergreen.sa...@gmail.com> wrote: >> >> Hi Zoltan >> >> Yes we have also faced same issue and IBM support confirmed they will open >> new APAR. We have reverted all clients v8.1.14 to address the issue. >> >> Regards >> Sarav >> +65 9857 8665 >> >> >>>> On 13 Jul 2022, at 2:31 AM, Del Hoobler wrote: >>> >>> Hi Zoltan, >>> >>> IBM knows about this ... and it's being actively worked. >>> >>> I am sure it will be mitigated soon. >>> >>> Feel free to open a fresh IBM Support case so you can be quickly >> notified once it is fixed. >>> >>> >>> Del >>> >>> >>> From: ADSM: Dist Stor Manager on behalf of >> Zoltan Forray >>> Sent: Tuesday, July 12, 2022 1:56 PM >>> To: ADSM-L@VM.MARIST.EDU >>> Subject: [EXTERNAL] 8.1.15 Linux client update causing failures >>> >>> We started rolling out the 8.1.15 Linux client via apogee and many >> clients >>> are failing with: >>> >>> *** Error in `dsmc': double free or corruption (!prev): >> 0x02baf970 >>> *** >>> >>> The only matching Google hit goes back to a V7 client issue - long fixed. >>> >>> At first I thought it might be related to a Linux flavor (we run Rocky8, >>> CentOS 7.1/8, RHEL 7/8) but I don't see a pattern. All of these servers >>> are upgrading from 8.1.14 and downleveling the client to 8.1.14 fixes >> this. >>> >>> Anyone else seeing this? >>> >>> FWIW, I could swear that during one of my many Google searches I saw a >>> reference to 8.1.15.2 (eFix?) but now I can't find it again. >>> -- >>> *Zoltan Forray* >>> Enterprise Backup Administrator >>> VMware Systems Administrator >>> Enterprise Compute & Storage Platforms Team >>> VCU Infrastructure Services >>> www.ucc.vcu.edu<http://www.ucc.vcu.edu> >>> zfor...@vcu.edu - 804-828-4807 >>> Don't be a phishing victim - VCU and other reputable organizations will >>> never use email to request that you reply with your password, social >>> security number or confidential personal information. For more details >>> visit http://phishing.vcu.edu/ >>> <https://adminmicro2.questionpro.com > >>
Re: 8.1.15 Linux client update causing failures
Is the windows client safe for this version? On Tue, Jul 12, 2022, 7:06 PM Saravanan Palanisamy < evergreen.sa...@gmail.com> wrote: > Hi Zoltan > > Yes we have also faced same issue and IBM support confirmed they will open > new APAR. We have reverted all clients v8.1.14 to address the issue. > > Regards > Sarav > +65 9857 8665 > > > > On 13 Jul 2022, at 2:31 AM, Del Hoobler wrote: > > > > Hi Zoltan, > > > > IBM knows about this ... and it's being actively worked. > > > > I am sure it will be mitigated soon. > > > > Feel free to open a fresh IBM Support case so you can be quickly > notified once it is fixed. > > > > > > Del > > > > > > From: ADSM: Dist Stor Manager on behalf of > Zoltan Forray > > Sent: Tuesday, July 12, 2022 1:56 PM > > To: ADSM-L@VM.MARIST.EDU > > Subject: [EXTERNAL] 8.1.15 Linux client update causing failures > > > > We started rolling out the 8.1.15 Linux client via apogee and many > clients > > are failing with: > > > > *** Error in `dsmc': double free or corruption (!prev): > 0x02baf970 > > *** > > > > The only matching Google hit goes back to a V7 client issue - long fixed. > > > > At first I thought it might be related to a Linux flavor (we run Rocky8, > > CentOS 7.1/8, RHEL 7/8) but I don't see a pattern. All of these servers > > are upgrading from 8.1.14 and downleveling the client to 8.1.14 fixes > this. > > > > Anyone else seeing this? > > > > FWIW, I could swear that during one of my many Google searches I saw a > > reference to 8.1.15.2 (eFix?) but now I can't find it again. > > -- > > *Zoltan Forray* > > Enterprise Backup Administrator > > VMware Systems Administrator > > Enterprise Compute & Storage Platforms Team > > VCU Infrastructure Services > > www.ucc.vcu.edu<http://www.ucc.vcu.edu> > > zfor...@vcu.edu - 804-828-4807 > > Don't be a phishing victim - VCU and other reputable organizations will > > never use email to request that you reply with your password, social > > security number or confidential personal information. For more details > > visit http://phishing.vcu.edu/ > > <https://adminmicro2.questionpro.com > >
Re: 8.1.15 Linux client update causing failures
Hi Zoltan Yes we have also faced same issue and IBM support confirmed they will open new APAR. We have reverted all clients v8.1.14 to address the issue. Regards Sarav +65 9857 8665 > On 13 Jul 2022, at 2:31 AM, Del Hoobler wrote: > > Hi Zoltan, > > IBM knows about this ... and it's being actively worked. > > I am sure it will be mitigated soon. > > Feel free to open a fresh IBM Support case so you can be quickly notified > once it is fixed. > > > Del > > > From: ADSM: Dist Stor Manager on behalf of Zoltan > Forray > Sent: Tuesday, July 12, 2022 1:56 PM > To: ADSM-L@VM.MARIST.EDU > Subject: [EXTERNAL] 8.1.15 Linux client update causing failures > > We started rolling out the 8.1.15 Linux client via apogee and many clients > are failing with: > > *** Error in `dsmc': double free or corruption (!prev): 0x02baf970 > *** > > The only matching Google hit goes back to a V7 client issue - long fixed. > > At first I thought it might be related to a Linux flavor (we run Rocky8, > CentOS 7.1/8, RHEL 7/8) but I don't see a pattern. All of these servers > are upgrading from 8.1.14 and downleveling the client to 8.1.14 fixes this. > > Anyone else seeing this? > > FWIW, I could swear that during one of my many Google searches I saw a > reference to 8.1.15.2 (eFix?) but now I can't find it again. > -- > *Zoltan Forray* > Enterprise Backup Administrator > VMware Systems Administrator > Enterprise Compute & Storage Platforms Team > VCU Infrastructure Services > www.ucc.vcu.edu<http://www.ucc.vcu.edu> > zfor...@vcu.edu - 804-828-4807 > Don't be a phishing victim - VCU and other reputable organizations will > never use email to request that you reply with your password, social > security number or confidential personal information. For more details > visit http://phishing.vcu.edu/ > <https://adminmicro2.questionpro.com >
Re: 8.1.15 Linux client update causing failures
Hi Zoltan, IBM knows about this ... and it's being actively worked. I am sure it will be mitigated soon. Feel free to open a fresh IBM Support case so you can be quickly notified once it is fixed. Del From: ADSM: Dist Stor Manager on behalf of Zoltan Forray Sent: Tuesday, July 12, 2022 1:56 PM To: ADSM-L@VM.MARIST.EDU Subject: [EXTERNAL] 8.1.15 Linux client update causing failures We started rolling out the 8.1.15 Linux client via apogee and many clients are failing with: *** Error in `dsmc': double free or corruption (!prev): 0x02baf970 *** The only matching Google hit goes back to a V7 client issue - long fixed. At first I thought it might be related to a Linux flavor (we run Rocky8, CentOS 7.1/8, RHEL 7/8) but I don't see a pattern. All of these servers are upgrading from 8.1.14 and downleveling the client to 8.1.14 fixes this. Anyone else seeing this? FWIW, I could swear that during one of my many Google searches I saw a reference to 8.1.15.2 (eFix?) but now I can't find it again. -- *Zoltan Forray* Enterprise Backup Administrator VMware Systems Administrator Enterprise Compute & Storage Platforms Team VCU Infrastructure Services www.ucc.vcu.edu<http://www.ucc.vcu.edu> zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://phishing.vcu.edu/ <https://adminmicro2.questionpro.com >
8.1.15 Linux client update causing failures
We started rolling out the 8.1.15 Linux client via apogee and many clients are failing with: *** Error in `dsmc': double free or corruption (!prev): 0x02baf970 *** The only matching Google hit goes back to a V7 client issue - long fixed. At first I thought it might be related to a Linux flavor (we run Rocky8, CentOS 7.1/8, RHEL 7/8) but I don't see a pattern. All of these servers are upgrading from 8.1.14 and downleveling the client to 8.1.14 fixes this. Anyone else seeing this? FWIW, I could swear that during one of my many Google searches I saw a reference to 8.1.15.2 (eFix?) but now I can't find it again. -- *Zoltan Forray* Enterprise Backup Administrator VMware Systems Administrator Enterprise Compute & Storage Platforms Team VCU Infrastructure Services www.ucc.vcu.edu zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://phishing.vcu.edu/ <https://adminmicro2.questionpro.com>
Re: Node Hypervisor info missing for CentOS Linux
Hi Zoltan, you have to install the CIT (Common Inventory Technology) packages which are included within the client .tar file TIVsm-APIcit.x86_64.rpm TIVsm-BAcit.x86_64.rpm Regards, Uwe -Original Message- From: ADSM: Dist Stor Manager On Behalf Of Zoltan Forray Sent: Donnerstag, 14. Oktober 2021 14:17 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Node Hypervisor info missing for CentOS Linux A while ago we started converting RHEL servers to CentOS due to price hikes/cost. Yesterday I was trying to determine how many of our servers on VMware are still backing up via ISP client vs SP+ and discovered that the NODE Hypervisor field is blank for CentOS VM's on VMware. Does anyone know if this is a bug/fixed in later releases? Right now the 8.1.10 client is automatically deployed to all Linux servers via Puppet. Or am I simply out-of-luck since CentOS isn't on the "officially supported" OS list? -- *Zoltan Forray* IBM Spectrum Protect Administrator VMware Administrator Virginia Commonwealth University UCC/Office of Technology Services www.ucc.vcu.edu zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://phishing.vcu.edu/ <https://adminmicro2.questionpro.com>
Node Hypervisor info missing for CentOS Linux
A while ago we started converting RHEL servers to CentOS due to price hikes/cost. Yesterday I was trying to determine how many of our servers on VMware are still backing up via ISP client vs SP+ and discovered that the NODE Hypervisor field is blank for CentOS VM's on VMware. Does anyone know if this is a bug/fixed in later releases? Right now the 8.1.10 client is automatically deployed to all Linux servers via Puppet. Or am I simply out-of-luck since CentOS isn't on the "officially supported" OS list? -- *Zoltan Forray* IBM Spectrum Protect Administrator VMware Administrator Virginia Commonwealth University UCC/Office of Technology Services www.ucc.vcu.edu zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://phishing.vcu.edu/ <https://adminmicro2.questionpro.com>
Re: MS SQL for Linux
Thank You Del. I have voted for the request. Regards Sarav +65 9857 8665 > On 24 Apr 2020, at 6:19 AM, Del Hoobler wrote: > > Hi Sarav, > > We have not seen a lot of demand for this yet. If you are interested, > please vote for this RFE: > > http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=108504 > > > Del > > > > "ADSM: Dist Stor Manager" wrote on 04/23/2020 > 03:28:25 PM: > >> From: Saravanan Palanisamy >> To: ADSM-L@VM.MARIST.EDU >> Date: 04/23/2020 03:29 PM >> Subject: [EXTERNAL] MS SQL for Linux >> Sent by: "ADSM: Dist Stor Manager" >> >> Team >> >> Done anyone know whether IBM will support Linux MS SQL in near future ? >> >> >> Regards >> Sarav >> +65 9857 8665 >>
Re: MS SQL for Linux
Hi Sarav, We have not seen a lot of demand for this yet. If you are interested, please vote for this RFE: http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=108504 Del "ADSM: Dist Stor Manager" wrote on 04/23/2020 03:28:25 PM: > From: Saravanan Palanisamy > To: ADSM-L@VM.MARIST.EDU > Date: 04/23/2020 03:29 PM > Subject: [EXTERNAL] MS SQL for Linux > Sent by: "ADSM: Dist Stor Manager" > > Team > > Done anyone know whether IBM will support Linux MS SQL in near future ? > > > Regards > Sarav > +65 9857 8665 >
MS SQL for Linux
Team Done anyone know whether IBM will support Linux MS SQL in near future ? Regards Sarav +65 9857 8665
Set password unix/linux
Probably simple. But how do I set the TSM node password on a linux client without contacting the TSM server? In windows it is easy but I have found no way on linux/unix. Hans Chr.
7.1.9.100 Server for Linux patch
Anyone from IBM have the details on this recently released patch level? All attempts to access the "Fix History" or "Updates, limitations" pages return errors/missing. -- *Zoltan Forray* Spectrum Protect (p.k.a. TSM) Software & Hardware Administrator Xymon Monitor Administrator VMware Administrator Virginia Commonwealth University UCC/Office of Technology Services www.ucc.vcu.edu zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://phishing.vcu.edu/
R: [ADSM-L] R: [ADSM-L] Netapp snapdiff issues having TSM client on a Linux machine, making use of NFS mounts
The BA Spectrum clients get the list of files to backup from the NetApp; you can read it from the IBM page: The second snapshot is called the diffsnapshot, or differences snapshot. The client then incrementally backs up the files that are reported as changed, by NetApp, to the IBM Spectrum Protect server. You can find the same concept also at https://www.lascon.co.uk/tsm-backups.php#bsnetapp, where you'll find: The second snapshot is called the diffsnapshot. TSM then incrementally backs up the files reported as changed by NetApp to the TSM server. I am pretty sure it's not necessary to create exclusion rule of .snapshot (NFS) or ~ snapshot (CIFS) it is the "entry point" from which the BA Spectrum agent get the access of the files who needs backups. I say that because web documentation never require the adoption of this rule. These are NetApp construct that is automatically recognized by the BA Spectrum agents. Cheers. -Messaggio originale- Da: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] Per conto di Efim Inviato: giovedì 20 settembre 2018 10:52 A: ADSM-L@VM.MARIST.EDU Oggetto: Re: [ADSM-L] R: [ADSM-L] Netapp snapdiff issues having TSM client on a Linux machine, making use of NFS mounts SP client use NetApp API to detect file changes between 2(two) snapshots. After that client have the list of changed files and backup it from mounted volume. I believe that it is unnecessary to copy the snapshot itself because it's pointless. Efim > 20 сент. 2018 г., в 11:29, Tommaso Bollini написал(а): > > @Efim > the .snapshot (or ~snapshot) folders are NetApp construct recognized by the > BA Spectrum agent api: > https://www.ibm.com/support/knowledgecenter/en/SSEQVQ_8.1.2/client/r_o > pt_snapdiff.html The BA Spectrum agent will copy all files listed in > the NetApp snapshot image. > The log error simply reports the point at which this backup job has in > exception echoing the full path of what BA API read from the snapshot image. > > I hope I was helpful. > Greetings. > > -Messaggio originale- > Da: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] Per conto di > Efim > Inviato: mercoledì 19 settembre 2018 18:39 > A: ADSM-L@VM.MARIST.EDU > Oggetto: Re: [ADSM-L] Netapp snapdiff issues having TSM client on a > Linux machine, making use of NFS mounts > > Arnaud, > > Can you explain why you are copying the .snapshot folder during incremental > filesystem backup with snapdiff? > It contains snapshots created by netapp and SP for this FS. > I believe that it should be excluded from copying in your backup job. > > Efim > > >> 19 сент. 2018 г., в 18:28, PAC Brion Arnaud >> написал(а): >> >> Hi Robert, >> >> Thanks a lot for appreciated feedback, unfortunately even when using TSM own >> snapshots the problem still exists : >> >> root@xx:~ # dsmc i /Airwarder -snapdiff -diffsnapshot=create >> -snapdiffhttps -optfile=$OPTPATH >/tmp/snapshot_Airwarder.log >> >> root@ xx:~ # more /tmp/snapshot_Airwarder.log IBM Spectrum >> Protect Command Line Backup-Archive Client Interface Client Version >> 8, Release 1, Level 4.0 Client date/time: 09/19/2018 17:17:41 >> (c) Copyright by IBM Corporation and other(s) 1990, 2017. All Rights >> Reserved. >> >> Node Name: NETAPP_CH1_NFS >> Session established with server xx: Linux/ppc64le Server Version >> 8, Release 1, Level 4.000 Server date/time: 09/19/2018 17:17:42 >> Last >> access: 09/18/2018 12:12:17 >> >> >> Incremental by snapshot difference of volume '/Airwarder' >> >> Connected to NetApp Storage Virtual Machine >> Management Filer Host/IP Address : xx >> Filer Version Information: NetApp Release 9.3P3: Wed Apr 04 >> 13:07:06 >> UTC 2018 >> Storage VM Name : ch1ns100 >> Storage VM Host/IP Address : xx >> Storage VM Volume Style : Flex >> Login User : tsm-backup-user >> Transport: HTTPS >> >> Performing a Full Incremental Backup of volume '/Airwarder' >> Creating Base Snapshot. >> Using Base Snapshot 'TSM_CH135BA2689781857_AIRWARDER' with timestamp >> 09/19/2018 >> 17:17:43 >> ANS4007E Error processing >> '/Airwarder/.snapshot/TSM_CH135BA2689781857_AIRWARDER/ >> acrimport_ref/ch': access to the object is denied ANS4007E Error >> processing '/Airwarder/.snapshot/TSM_CH135BA2689781857_AIRWARDER/ >> acrimport_test/ch': access to the object is denied >> ANS1898I * Processed 500 files * >> ANS4007E Err
Re: R: [ADSM-L] Netapp snapdiff issues having TSM client on a Linux machine, making use of NFS mounts
SP client use NetApp API to detect file changes between 2(two) snapshots. After that client have the list of changed files and backup it from mounted volume. I believe that it is unnecessary to copy the snapshot itself because it's pointless. Efim > 20 сент. 2018 г., в 11:29, Tommaso Bollini написал(а): > > @Efim > the .snapshot (or ~snapshot) folders are NetApp construct recognized by the > BA Spectrum agent api: > https://www.ibm.com/support/knowledgecenter/en/SSEQVQ_8.1.2/client/r_opt_snapdiff.html > The BA Spectrum agent will copy all files listed in the NetApp snapshot image. > The log error simply reports the point at which this backup job has in > exception echoing the full path of what BA API read from the snapshot image. > > I hope I was helpful. > Greetings. > > -Messaggio originale- > Da: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] Per conto di Efim > Inviato: mercoledì 19 settembre 2018 18:39 > A: ADSM-L@VM.MARIST.EDU > Oggetto: Re: [ADSM-L] Netapp snapdiff issues having TSM client on a Linux > machine, making use of NFS mounts > > Arnaud, > > Can you explain why you are copying the .snapshot folder during incremental > filesystem backup with snapdiff? > It contains snapshots created by netapp and SP for this FS. > I believe that it should be excluded from copying in your backup job. > > Efim > > >> 19 сент. 2018 г., в 18:28, PAC Brion Arnaud >> написал(а): >> >> Hi Robert, >> >> Thanks a lot for appreciated feedback, unfortunately even when using TSM own >> snapshots the problem still exists : >> >> root@xx:~ # dsmc i /Airwarder -snapdiff -diffsnapshot=create >> -snapdiffhttps -optfile=$OPTPATH >/tmp/snapshot_Airwarder.log >> >> root@ xx:~ # more /tmp/snapshot_Airwarder.log IBM Spectrum Protect >> Command Line Backup-Archive Client Interface Client Version 8, >> Release 1, Level 4.0 Client date/time: 09/19/2018 17:17:41 >> (c) Copyright by IBM Corporation and other(s) 1990, 2017. All Rights >> Reserved. >> >> Node Name: NETAPP_CH1_NFS >> Session established with server xx: Linux/ppc64le Server Version >> 8, Release 1, Level 4.000 Server date/time: 09/19/2018 17:17:42 Last >> access: 09/18/2018 12:12:17 >> >> >> Incremental by snapshot difference of volume '/Airwarder' >> >> Connected to NetApp Storage Virtual Machine >> Management Filer Host/IP Address : xx >> Filer Version Information: NetApp Release 9.3P3: Wed Apr 04 >> 13:07:06 >> UTC 2018 >> Storage VM Name : ch1ns100 >> Storage VM Host/IP Address : xx >> Storage VM Volume Style : Flex >> Login User : tsm-backup-user >> Transport: HTTPS >> >> Performing a Full Incremental Backup of volume '/Airwarder' >> Creating Base Snapshot. >> Using Base Snapshot 'TSM_CH135BA2689781857_AIRWARDER' with timestamp >> 09/19/2018 >> 17:17:43 >> ANS4007E Error processing >> '/Airwarder/.snapshot/TSM_CH135BA2689781857_AIRWARDER/ >> acrimport_ref/ch': access to the object is denied ANS4007E Error >> processing '/Airwarder/.snapshot/TSM_CH135BA2689781857_AIRWARDER/ >> acrimport_test/ch': access to the object is denied >> ANS1898I * Processed 500 files * >> ANS4007E Error processing >> '/Airwarder/.snapshot/TSM_CH135BA2689781857_AIRWARDER/ >> >> I'm lost here ... >> >> Cheers. >> >> Arnaud >> >> ** >> ** >> Backup and Recovery Systems Administrator Panalpina Management Ltd., >> Basle, Switzerland, CIT Department Viadukstrasse 42, P.O. Box 4002 >> Basel/CH >> Phone: +41 (61) 226 11 11, FAX: +41 (61) 226 17 01 >> Direct: +41 (61) 226 19 78 >> e-mail: arnaud.br...@panalpina.com >> This electronic message transmission contains information from Panalpina and >> is confidential or privileged. >> This information is intended only for the person (s) named above. If >> you are not the intended recipient, any disclosure, copying, distribution or >> use or any other action based on the contents of this information is >> strictly prohibited. >> >> If you receive this electronic transmission in error, please notify the >> sender by e-mail, telephone or fax at the numbers listed above. Thank you. >> **
R: [ADSM-L] Netapp snapdiff issues having TSM client on a Linux machine, making use of NFS mounts
@Efim the .snapshot (or ~snapshot) folders are NetApp construct recognized by the BA Spectrum agent api: https://www.ibm.com/support/knowledgecenter/en/SSEQVQ_8.1.2/client/r_opt_snapdiff.html The BA Spectrum agent will copy all files listed in the NetApp snapshot image. The log error simply reports the point at which this backup job has in exception echoing the full path of what BA API read from the snapshot image. I hope I was helpful. Greetings. -Messaggio originale- Da: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] Per conto di Efim Inviato: mercoledì 19 settembre 2018 18:39 A: ADSM-L@VM.MARIST.EDU Oggetto: Re: [ADSM-L] Netapp snapdiff issues having TSM client on a Linux machine, making use of NFS mounts Arnaud, Can you explain why you are copying the .snapshot folder during incremental filesystem backup with snapdiff? It contains snapshots created by netapp and SP for this FS. I believe that it should be excluded from copying in your backup job. Efim > 19 сент. 2018 г., в 18:28, PAC Brion Arnaud > написал(а): > > Hi Robert, > > Thanks a lot for appreciated feedback, unfortunately even when using TSM own > snapshots the problem still exists : > > root@xx:~ # dsmc i /Airwarder -snapdiff -diffsnapshot=create > -snapdiffhttps -optfile=$OPTPATH >/tmp/snapshot_Airwarder.log > > root@ xx:~ # more /tmp/snapshot_Airwarder.log IBM Spectrum Protect > Command Line Backup-Archive Client Interface Client Version 8, > Release 1, Level 4.0 Client date/time: 09/19/2018 17:17:41 > (c) Copyright by IBM Corporation and other(s) 1990, 2017. All Rights > Reserved. > > Node Name: NETAPP_CH1_NFS > Session established with server xx: Linux/ppc64le Server Version > 8, Release 1, Level 4.000 Server date/time: 09/19/2018 17:17:42 Last > access: 09/18/2018 12:12:17 > > > Incremental by snapshot difference of volume '/Airwarder' > > Connected to NetApp Storage Virtual Machine >Management Filer Host/IP Address : xx >Filer Version Information: NetApp Release 9.3P3: Wed Apr 04 > 13:07:06 > UTC 2018 >Storage VM Name : ch1ns100 >Storage VM Host/IP Address : xx >Storage VM Volume Style : Flex >Login User : tsm-backup-user >Transport: HTTPS > > Performing a Full Incremental Backup of volume '/Airwarder' > Creating Base Snapshot. > Using Base Snapshot 'TSM_CH135BA2689781857_AIRWARDER' with timestamp > 09/19/2018 > 17:17:43 > ANS4007E Error processing > '/Airwarder/.snapshot/TSM_CH135BA2689781857_AIRWARDER/ > acrimport_ref/ch': access to the object is denied ANS4007E Error > processing '/Airwarder/.snapshot/TSM_CH135BA2689781857_AIRWARDER/ > acrimport_test/ch': access to the object is denied > ANS1898I * Processed 500 files * > ANS4007E Error processing > '/Airwarder/.snapshot/TSM_CH135BA2689781857_AIRWARDER/ > > I'm lost here ... > > Cheers. > > Arnaud > > ** > ** > Backup and Recovery Systems Administrator Panalpina Management Ltd., > Basle, Switzerland, CIT Department Viadukstrasse 42, P.O. Box 4002 > Basel/CH > Phone: +41 (61) 226 11 11, FAX: +41 (61) 226 17 01 > Direct: +41 (61) 226 19 78 > e-mail: arnaud.br...@panalpina.com > This electronic message transmission contains information from Panalpina and > is confidential or privileged. > This information is intended only for the person (s) named above. If > you are not the intended recipient, any disclosure, copying, distribution or > use or any other action based on the contents of this information is strictly > prohibited. > > If you receive this electronic transmission in error, please notify the > sender by e-mail, telephone or fax at the numbers listed above. Thank you. > ** > ** > www.panalpina.com > > > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf > Of Robert Talda > Sent: Tuesday, September 18, 2018 10:48 PM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: Netapp snapdiff issues having TSM client on a Linux > machine, making use of NFS mounts > > Brion: > Here at Cornell, we have a TSM client on a Linux system backing up NFS > shares via NFS mounts and snapdiff differentials - and have been doing so for > years. > > First, the gory details: > - For TSM > TSM Client Version 7, Release 1, Level 6.0 (*red faced, thoug
Re: Netapp snapdiff issues having TSM client on a Linux machine, making use of NFS mounts
Hi Efim and All who helped Quick update on this : it appeared that some export policy rule (i.e." -superuser sys" ) had not been properly set on our Netapp, thus refraining TSM client to reach some files. Once this corrected, I was able to get successful snapshot backups done. @Efim : thanks for your advice, I'll take it in consideration ! Just have to discuss with our storage team what exactly they are expecting from me ;-) Cheers. Arnaud -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Efim Sent: Wednesday, September 19, 2018 6:39 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Netapp snapdiff issues having TSM client on a Linux machine, making use of NFS mounts Arnaud, Can you explain why you are copying the .snapshot folder during incremental filesystem backup with snapdiff? It contains snapshots created by netapp and SP for this FS. I believe that it should be excluded from copying in your backup job. Efim > 19 сент. 2018 г., в 18:28, PAC Brion Arnaud > написал(а): > > Hi Robert, > > Thanks a lot for appreciated feedback, unfortunately even when using TSM own > snapshots the problem still exists : > > root@xx:~ # dsmc i /Airwarder -snapdiff -diffsnapshot=create > -snapdiffhttps -optfile=$OPTPATH >/tmp/snapshot_Airwarder.log > > root@ xx:~ # more /tmp/snapshot_Airwarder.log > IBM Spectrum Protect > Command Line Backup-Archive Client Interface > Client Version 8, Release 1, Level 4.0 > Client date/time: 09/19/2018 17:17:41 > (c) Copyright by IBM Corporation and other(s) 1990, 2017. All Rights > Reserved. > > Node Name: NETAPP_CH1_NFS > Session established with server xx: Linux/ppc64le > Server Version 8, Release 1, Level 4.000 > Server date/time: 09/19/2018 17:17:42 Last access: 09/18/2018 12:12:17 > > > Incremental by snapshot difference of volume '/Airwarder' > > Connected to NetApp Storage Virtual Machine >Management Filer Host/IP Address : xx >Filer Version Information: NetApp Release 9.3P3: Wed Apr 04 > 13:07:06 > UTC 2018 >Storage VM Name : ch1ns100 >Storage VM Host/IP Address : xx >Storage VM Volume Style : Flex >Login User : tsm-backup-user >Transport: HTTPS > > Performing a Full Incremental Backup of volume '/Airwarder' > Creating Base Snapshot. > Using Base Snapshot 'TSM_CH135BA2689781857_AIRWARDER' with timestamp > 09/19/2018 > 17:17:43 > ANS4007E Error processing > '/Airwarder/.snapshot/TSM_CH135BA2689781857_AIRWARDER/ > acrimport_ref/ch': access to the object is denied > ANS4007E Error processing > '/Airwarder/.snapshot/TSM_CH135BA2689781857_AIRWARDER/ > acrimport_test/ch': access to the object is denied > ANS1898I * Processed 500 files * > ANS4007E Error processing > '/Airwarder/.snapshot/TSM_CH135BA2689781857_AIRWARDER/ > > I'm lost here ... > > Cheers. > > Arnaud > > > Backup and Recovery Systems Administrator > Panalpina Management Ltd., Basle, Switzerland, > CIT Department Viadukstrasse 42, P.O. Box 4002 Basel/CH > Phone: +41 (61) 226 11 11, FAX: +41 (61) 226 17 01 > Direct: +41 (61) 226 19 78 > e-mail: arnaud.br...@panalpina.com > This electronic message transmission contains information from Panalpina and > is confidential or privileged. > This information is intended only for the person (s) named above. If you are > not the intended recipient, any disclosure, copying, distribution or use or > any other action based on the contents of this > information is strictly prohibited. > > If you receive this electronic transmission in error, please notify the > sender by e-mail, telephone or fax at the numbers listed above. Thank you. > **** > www.panalpina.com > > > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of > Robert Talda > Sent: Tuesday, September 18, 2018 10:48 PM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: Netapp snapdiff issues having TSM client on a Linux machine, > making use of NFS mounts > > Brion: > Here at Cornell, we have a TSM client on a Linux system backing up NFS > shares via NFS mounts and snapdiff differentials - and have been doing so for > years. > > First, the gory details: > - For TSM > TSM Client Version 7, Release 1, Level 6.0 (*red faced, th
Re: Netapp snapdiff issues having TSM client on a Linux machine, making use of NFS mounts
Arnaud, Can you explain why you are copying the .snapshot folder during incremental filesystem backup with snapdiff? It contains snapshots created by netapp and SP for this FS. I believe that it should be excluded from copying in your backup job. Efim > 19 сент. 2018 г., в 18:28, PAC Brion Arnaud > написал(а): > > Hi Robert, > > Thanks a lot for appreciated feedback, unfortunately even when using TSM own > snapshots the problem still exists : > > root@xx:~ # dsmc i /Airwarder -snapdiff -diffsnapshot=create > -snapdiffhttps -optfile=$OPTPATH >/tmp/snapshot_Airwarder.log > > root@ xx:~ # more /tmp/snapshot_Airwarder.log > IBM Spectrum Protect > Command Line Backup-Archive Client Interface > Client Version 8, Release 1, Level 4.0 > Client date/time: 09/19/2018 17:17:41 > (c) Copyright by IBM Corporation and other(s) 1990, 2017. All Rights > Reserved. > > Node Name: NETAPP_CH1_NFS > Session established with server xx: Linux/ppc64le > Server Version 8, Release 1, Level 4.000 > Server date/time: 09/19/2018 17:17:42 Last access: 09/18/2018 12:12:17 > > > Incremental by snapshot difference of volume '/Airwarder' > > Connected to NetApp Storage Virtual Machine >Management Filer Host/IP Address : xx >Filer Version Information: NetApp Release 9.3P3: Wed Apr 04 > 13:07:06 > UTC 2018 >Storage VM Name : ch1ns100 >Storage VM Host/IP Address : xx >Storage VM Volume Style : Flex >Login User : tsm-backup-user >Transport: HTTPS > > Performing a Full Incremental Backup of volume '/Airwarder' > Creating Base Snapshot. > Using Base Snapshot 'TSM_CH135BA2689781857_AIRWARDER' with timestamp > 09/19/2018 > 17:17:43 > ANS4007E Error processing > '/Airwarder/.snapshot/TSM_CH135BA2689781857_AIRWARDER/ > acrimport_ref/ch': access to the object is denied > ANS4007E Error processing > '/Airwarder/.snapshot/TSM_CH135BA2689781857_AIRWARDER/ > acrimport_test/ch': access to the object is denied > ANS1898I * Processed 500 files * > ANS4007E Error processing > '/Airwarder/.snapshot/TSM_CH135BA2689781857_AIRWARDER/ > > I'm lost here ... > > Cheers. > > Arnaud > > > Backup and Recovery Systems Administrator > Panalpina Management Ltd., Basle, Switzerland, > CIT Department Viadukstrasse 42, P.O. Box 4002 Basel/CH > Phone: +41 (61) 226 11 11, FAX: +41 (61) 226 17 01 > Direct: +41 (61) 226 19 78 > e-mail: arnaud.br...@panalpina.com > This electronic message transmission contains information from Panalpina and > is confidential or privileged. > This information is intended only for the person (s) named above. If you are > not the intended recipient, any disclosure, copying, distribution or use or > any other action based on the contents of this > information is strictly prohibited. > > If you receive this electronic transmission in error, please notify the > sender by e-mail, telephone or fax at the numbers listed above. Thank you. > **** > www.panalpina.com > > > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of > Robert Talda > Sent: Tuesday, September 18, 2018 10:48 PM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: Netapp snapdiff issues having TSM client on a Linux machine, > making use of NFS mounts > > Brion: > Here at Cornell, we have a TSM client on a Linux system backing up NFS > shares via NFS mounts and snapdiff differentials - and have been doing so for > years. > > First, the gory details: > - For TSM > TSM Client Version 7, Release 1, Level 6.0 (*red faced, thought I had > upgraded to SP 8.1.2.0 months ago*) > Running on CentOS Linux release 7.5.1804 (kernel 3.10.0-862.2.3.el7.x86_64) > Accessing TSM Server for Linux Version 7, Release 1, Level 7.200 > - For NetApp > Filer Version Information: NetApp Release 9.3P6 > > We aren’t seeing your issue, and I suspect I know why. We are telling the > TSM client to create its own snapshots - and not use the snapshots being > created hourly (or daily or weekly even) by the team managing the Netapp - > said snapshots being equivalent to the ones you are trying to take advantage > of in your backups. > > That is, the relevant part of the daily backup schedule looks like: > S
Re: Netapp snapdiff issues having TSM client on a Linux machine, making use of NFS mounts
Hi Robert, Thanks a lot for appreciated feedback, unfortunately even when using TSM own snapshots the problem still exists : root@xx:~ # dsmc i /Airwarder -snapdiff -diffsnapshot=create -snapdiffhttps -optfile=$OPTPATH >/tmp/snapshot_Airwarder.log root@ xx:~ # more /tmp/snapshot_Airwarder.log IBM Spectrum Protect Command Line Backup-Archive Client Interface Client Version 8, Release 1, Level 4.0 Client date/time: 09/19/2018 17:17:41 (c) Copyright by IBM Corporation and other(s) 1990, 2017. All Rights Reserved. Node Name: NETAPP_CH1_NFS Session established with server xx: Linux/ppc64le Server Version 8, Release 1, Level 4.000 Server date/time: 09/19/2018 17:17:42 Last access: 09/18/2018 12:12:17 Incremental by snapshot difference of volume '/Airwarder' Connected to NetApp Storage Virtual Machine Management Filer Host/IP Address : xx Filer Version Information: NetApp Release 9.3P3: Wed Apr 04 13:07:06 UTC 2018 Storage VM Name : ch1ns100 Storage VM Host/IP Address : xx Storage VM Volume Style : Flex Login User : tsm-backup-user Transport: HTTPS Performing a Full Incremental Backup of volume '/Airwarder' Creating Base Snapshot. Using Base Snapshot 'TSM_CH135BA2689781857_AIRWARDER' with timestamp 09/19/2018 17:17:43 ANS4007E Error processing '/Airwarder/.snapshot/TSM_CH135BA2689781857_AIRWARDER/ acrimport_ref/ch': access to the object is denied ANS4007E Error processing '/Airwarder/.snapshot/TSM_CH135BA2689781857_AIRWARDER/ acrimport_test/ch': access to the object is denied ANS1898I * Processed 500 files * ANS4007E Error processing '/Airwarder/.snapshot/TSM_CH135BA2689781857_AIRWARDER/ I'm lost here ... Cheers. Arnaud Backup and Recovery Systems Administrator Panalpina Management Ltd., Basle, Switzerland, CIT Department Viadukstrasse 42, P.O. Box 4002 Basel/CH Phone: +41 (61) 226 11 11, FAX: +41 (61) 226 17 01 Direct: +41 (61) 226 19 78 e-mail: arnaud.br...@panalpina.com This electronic message transmission contains information from Panalpina and is confidential or privileged. This information is intended only for the person (s) named above. If you are not the intended recipient, any disclosure, copying, distribution or use or any other action based on the contents of this information is strictly prohibited. If you receive this electronic transmission in error, please notify the sender by e-mail, telephone or fax at the numbers listed above. Thank you. www.panalpina.com -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Robert Talda Sent: Tuesday, September 18, 2018 10:48 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Netapp snapdiff issues having TSM client on a Linux machine, making use of NFS mounts Brion: Here at Cornell, we have a TSM client on a Linux system backing up NFS shares via NFS mounts and snapdiff differentials - and have been doing so for years. First, the gory details: - For TSM TSM Client Version 7, Release 1, Level 6.0 (*red faced, thought I had upgraded to SP 8.1.2.0 months ago*) Running on CentOS Linux release 7.5.1804 (kernel 3.10.0-862.2.3.el7.x86_64) Accessing TSM Server for Linux Version 7, Release 1, Level 7.200 - For NetApp Filer Version Information: NetApp Release 9.3P6 We aren’t seeing your issue, and I suspect I know why. We are telling the TSM client to create its own snapshots - and not use the snapshots being created hourly (or daily or weekly even) by the team managing the Netapp - said snapshots being equivalent to the ones you are trying to take advantage of in your backups. That is, the relevant part of the daily backup schedule looks like: Schedule Name: DAILY.INCR.NFS.SNAPDIFF Description: Daily SnapDiff Incremental Action: Incremental Subaction: Options: -snapdiff -diffsnapshot=create -snapdiffhttps During a backup, then, the following type of information is written to the dsmsched.log: 09/13/2018 00:38:08 Incremental by snapshot difference of volume '/nas-backup/vol/cit-pea1-test' 09/13/2018 00:38:10 ANS2328I Using Snapshot Differential Change Log. 09/13/2018 00:38:10 Connected to NetApp Storage Virtual Machine Management Filer Host/IP Address : ccc-cdot01.cit.cornell.edu Filer Version Information: NetApp Release 9.3P6: Thu Jun 14 20:21:25 UTC 2018 Storage VM Name : cit-sfshared05 Storage VM Host/IP Address : cit-sfshared05-backup.fil
Re: Netapp snapdiff issues having TSM client on a Linux machine, making use of NFS mounts
Del, Thanks for your clarifications which are perfectly making sense. The way we operate our shop (users are always using the machine's node name as user ID) just made me forget that any admin might be granted authority on some other node, in our case the datamover ... Cheers. Arnaud -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Del Hoobler Sent: Tuesday, September 18, 2018 10:16 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Netapp snapdiff issues having TSM client on a Linux machine, making use of NFS mounts Hi Arnaud, >> ... there's still the limitation that this GUI will be usable only once logged on the machine hosting the Spectrum Protect client What do you mean by "that machine"? The Backup-Archive client is not in the data path for an NDMP backup or restore. The data path is between the NetApp filer and the server's tape library (or more generally speaking the storage pools). The Backup-Archive client is reading metadata from the server to present information to the end user. This means that the user can log in to any machine (Windows/AIX/Solaris x86) that has a Backup-Archive client. When the user logs into the Spectrum Protect server (at launch of the Backup-Archive client) they are providing an admin id that is not tied to a specific machine. Del "ADSM: Dist Stor Manager" wrote on 09/18/2018 07:57:56 AM: > From: PAC Brion Arnaud > To: ADSM-L@VM.MARIST.EDU > Date: 09/18/2018 07:58 AM > Subject: Re: Netapp snapdiff issues having TSM client on a Linux > machine, making use of NFS mounts > Sent by: "ADSM: Dist Stor Manager" > > Hi Del, > > Thanks for the information, which I got as well thru other channels > (IBM support), but there's still the limitation that this GUI will > be usable only once logged on the machine hosting the Spectrum Protect client. > This means that I will be forced to grant some of my colleagues > (which were previously doing the restores on their own) specific > logging rights on that machine. Was not the case before ... > > Cheers. > > Arnaud > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On > Behalf Of Del Hoobler > Sent: Tuesday, September 18, 2018 12:57 PM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: Netapp snapdiff issues having TSM client on a Linux > machine, making use of NFS mounts > > Hi Arnaud, > > Not related to SnapDiff ... but just some info on NDMP and B/A Client... > > In Spectrum Protect BA client 8.1.6 that GAs this coming Friday (21 > September) you will be able to use the native Java GUI to handle NDMP > backups/restores. > > > Del > > > > > > > "ADSM: Dist Stor Manager" wrote on 09/18/2018 > 06:20:52 AM: > > > From: PAC Brion Arnaud > > To: ADSM-L@VM.MARIST.EDU > > Date: 09/18/2018 06:21 AM > > Subject: Netapp snapdiff issues having TSM client on a Linux > > machine, making use of NFS mounts > > Sent by: "ADSM: Dist Stor Manager" > > > > Hi All, > > > > Following to IBM's decision to withdraw the web GUI in the latest > > versions of their clients (thus making NDMP hardly usable), as well > > as to the renewal of our NAS infrastructure (now using Netapp), I'm > > trying to implement netapp snapdiffs in our shop. > > > > So far we succeeded in defining necessary user and roles on the > > Netapp, as well as to setup the TSM client in order to interact with > > our filer, but I'm now facing an issue where some files cannot be > > backed up, apparently due to access rights. > > > > Here an extract of our backup log : > > > > IBM Spectrum Protect > > Command Line Backup-Archive Client Interface > > Client Version 8, Release 1, Level 4.0 > > Client date/time: 09/18/2018 10:26:28 > > (c) Copyright by IBM Corporation and other(s) 1990, 2017. All > RightsReserved. > > > > Node Name: NETAPP_CH1_NFS > > Session established with server XXX: Linux/ppc64le > > Server Version 8, Release 1, Level 4.000 > > Server date/time: 09/18/2018 10:26:28 Last access: 09/18/2018 > 10:00:37 > > > > > > Incremental by snapshot difference of volume '/Airwarder' > > > > Connected to NetApp Storage Virtual Machine > > Management Filer Host/IP Address : > > Filer Version Information: NetApp Release 9.3P3: Wed Apr > > 04 13:07:06 UTC 2018 > > Storage VM Name : xxx >
Re: Netapp snapdiff issues having TSM client on a Linux machine, making use of NFS mounts
Brion: Here at Cornell, we have a TSM client on a Linux system backing up NFS shares via NFS mounts and snapdiff differentials - and have been doing so for years. First, the gory details: - For TSM TSM Client Version 7, Release 1, Level 6.0 (*red faced, thought I had upgraded to SP 8.1.2.0 months ago*) Running on CentOS Linux release 7.5.1804 (kernel 3.10.0-862.2.3.el7.x86_64) Accessing TSM Server for Linux Version 7, Release 1, Level 7.200 - For NetApp Filer Version Information: NetApp Release 9.3P6 We aren’t seeing your issue, and I suspect I know why. We are telling the TSM client to create its own snapshots - and not use the snapshots being created hourly (or daily or weekly even) by the team managing the Netapp - said snapshots being equivalent to the ones you are trying to take advantage of in your backups. That is, the relevant part of the daily backup schedule looks like: Schedule Name: DAILY.INCR.NFS.SNAPDIFF Description: Daily SnapDiff Incremental Action: Incremental Subaction: Options: -snapdiff -diffsnapshot=create -snapdiffhttps During a backup, then, the following type of information is written to the dsmsched.log: 09/13/2018 00:38:08 Incremental by snapshot difference of volume '/nas-backup/vol/cit-pea1-test' 09/13/2018 00:38:10 ANS2328I Using Snapshot Differential Change Log. 09/13/2018 00:38:10 Connected to NetApp Storage Virtual Machine Management Filer Host/IP Address : ccc-cdot01.cit.cornell.edu Filer Version Information: NetApp Release 9.3P6: Thu Jun 14 20:21:25 UTC 2018 Storage VM Name : cit-sfshared05 Storage VM Host/IP Address : cit-sfshared05-backup.files.cornell.edu Storage VM Volume Style : Flex Login User : tsmbackup Transport: HTTPS 09/13/2018 00:38:10 Performing a Snapshot Differential Backup of volume '/nas-backup/vol/cit-pea1-test' 09/13/2018 00:38:10 Creating Diff Snapshot. 09/13/2018 00:38:10 Using Base Snapshot 'TSM_SANT5B9759FC1AB6_CIT_PEA1_TEST_VOL' with timestamp 09/11/2018 06:00:28 09/13/2018 00:38:10 Using Diff Snapshot 'TSM_SANT5B99E9B24F814_CIT_PEA1_TEST_VOL' with timestamp 09/13/2018 04:38:10 Then, on the next backup (48 hours later thanks to a large amount of data to backup on 9/13), the Diff Snapshot becomes the base: 09/15/2018 01:29:22 ANS2328I Using Snapshot Differential Change Log. 09/15/2018 01:29:22 Connected to NetApp Storage Virtual Machine Management Filer Host/IP Address : ccc-cdot01.cit.cornell.edu Filer Version Information: NetApp Release 9.3P6: Thu Jun 14 20:21:25 UTC 2018 Storage VM Name : cit-sfshared05 Storage VM Host/IP Address : cit-sfshared05-backup.files.cornell.edu Storage VM Volume Style : Flex Login User : tsmbackup Transport: HTTPS 09/15/2018 01:29:22 Performing a Snapshot Differential Backup of volume '/nas-backup/vol/cit-pea1-test' 09/15/2018 01:29:22 Creating Diff Snapshot. 09/15/2018 01:29:22 Using Base Snapshot 'TSM_SANT5B99E9B24F814_CIT_PEA1_TEST_VOL' with timestamp 09/13/2018 04:38:10 09/15/2018 01:29:22 Using Diff Snapshot 'TSM_SANT5B9C98B1A15B2_CIT_PEA1_TEST_VOL' with timestamp 09/15/2018 05:29:21 I think that consistency is what is missing in your approach - I suspect that there are intervening snapshots with information about files that have been deleted or changed that are not part of what the TSM client is seeing. I will add that our NetApp team is very happy with this approach. The TSM client has been very efficient in its management of the snapshots, and in those rare cases when it doesn’t, the snapshots are easy to identify and clean up. FWIW, Bob Robert Talda EZ-Backup Systems Engineer Cornell University +1 607-255-8280 r...@cornell.edu > On Sep 18, 2018, at 8:35 AM, PAC Brion Arnaud > wrote: > > Hi Tommaso, > > The backup command I'm using (dsmc i /Airwarder -snapdiff -snapdiffhttps > -diffsnapshotname="daily.*" -diffsnapshot=latest -useexistingbase > -optfile=dsm_netapp.opt) includes the "useexistingbase" statement. > Based on my understanding of the documentation, this means that the S.P. > client will not trigger the creation of a new snapshot on the Netapp device, > but instead, make use of a snapshot that had been created previously by some > internal mechanism of the Netapp. > Therefore, it seems very unlikely that any process still has a grip on any of > the files being part of this snapshot ... > My humble opinion only of course, I'm waiting on others fellow members of > this list feedback ! > > In addition to this, I would like to avoid the use of any exclud
Re: Netapp snapdiff issues having TSM client on a Linux machine, making use of NFS mounts
Hi Arnaud, >> ... there's still the limitation that this GUI will be usable only once logged on the machine hosting the Spectrum Protect client What do you mean by "that machine"? The Backup-Archive client is not in the data path for an NDMP backup or restore. The data path is between the NetApp filer and the server's tape library (or more generally speaking the storage pools). The Backup-Archive client is reading metadata from the server to present information to the end user. This means that the user can log in to any machine (Windows/AIX/Solaris x86) that has a Backup-Archive client. When the user logs into the Spectrum Protect server (at launch of the Backup-Archive client) they are providing an admin id that is not tied to a specific machine. Del "ADSM: Dist Stor Manager" wrote on 09/18/2018 07:57:56 AM: > From: PAC Brion Arnaud > To: ADSM-L@VM.MARIST.EDU > Date: 09/18/2018 07:58 AM > Subject: Re: Netapp snapdiff issues having TSM client on a Linux > machine, making use of NFS mounts > Sent by: "ADSM: Dist Stor Manager" > > Hi Del, > > Thanks for the information, which I got as well thru other channels > (IBM support), but there's still the limitation that this GUI will > be usable only once logged on the machine hosting the Spectrum Protect client. > This means that I will be forced to grant some of my colleagues > (which were previously doing the restores on their own) specific > logging rights on that machine. Was not the case before ... > > Cheers. > > Arnaud > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On > Behalf Of Del Hoobler > Sent: Tuesday, September 18, 2018 12:57 PM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: Netapp snapdiff issues having TSM client on a Linux > machine, making use of NFS mounts > > Hi Arnaud, > > Not related to SnapDiff ... but just some info on NDMP and B/A Client... > > In Spectrum Protect BA client 8.1.6 that GAs this coming Friday (21 > September) you will be able to use the native Java GUI to handle NDMP > backups/restores. > > > Del > > > > > > > "ADSM: Dist Stor Manager" wrote on 09/18/2018 > 06:20:52 AM: > > > From: PAC Brion Arnaud > > To: ADSM-L@VM.MARIST.EDU > > Date: 09/18/2018 06:21 AM > > Subject: Netapp snapdiff issues having TSM client on a Linux > > machine, making use of NFS mounts > > Sent by: "ADSM: Dist Stor Manager" > > > > Hi All, > > > > Following to IBM's decision to withdraw the web GUI in the latest > > versions of their clients (thus making NDMP hardly usable), as well > > as to the renewal of our NAS infrastructure (now using Netapp), I'm > > trying to implement netapp snapdiffs in our shop. > > > > So far we succeeded in defining necessary user and roles on the > > Netapp, as well as to setup the TSM client in order to interact with > > our filer, but I'm now facing an issue where some files cannot be > > backed up, apparently due to access rights. > > > > Here an extract of our backup log : > > > > IBM Spectrum Protect > > Command Line Backup-Archive Client Interface > > Client Version 8, Release 1, Level 4.0 > > Client date/time: 09/18/2018 10:26:28 > > (c) Copyright by IBM Corporation and other(s) 1990, 2017. All > RightsReserved. > > > > Node Name: NETAPP_CH1_NFS > > Session established with server XXX: Linux/ppc64le > > Server Version 8, Release 1, Level 4.000 > > Server date/time: 09/18/2018 10:26:28 Last access: 09/18/2018 > 10:00:37 > > > > > > Incremental by snapshot difference of volume '/Airwarder' > > > > Connected to NetApp Storage Virtual Machine > > Management Filer Host/IP Address : > > Filer Version Information: NetApp Release 9.3P3: Wed Apr > > 04 13:07:06 UTC 2018 > > Storage VM Name : xxx > > Storage VM Host/IP Address : XX > > Storage VM Volume Style : Flex > > Login User : tsm-backup-user > > Transport: HTTPS > > > > Performing a Full Incremental Backup of volume '/Airwarder' > > Using Base Snapshot 'vserverdr.0.7b5a59c4-656c-11e8- > > bb80-00a098d614c2.2018-09-18_102500' with timestamp 09/18/2018 10:25:02 > > ANS4007E Error processing '/Airwarder/.snapshot/vserverdr.0. > > 7b5a59c4-65
Re: Netapp snapdiff issues having TSM client on a Linux machine, making use of NFS mounts
Hi Tommaso, The backup command I'm using (dsmc i /Airwarder -snapdiff -snapdiffhttps -diffsnapshotname="daily.*" -diffsnapshot=latest -useexistingbase -optfile=dsm_netapp.opt) includes the "useexistingbase" statement. Based on my understanding of the documentation, this means that the S.P. client will not trigger the creation of a new snapshot on the Netapp device, but instead, make use of a snapshot that had been created previously by some internal mechanism of the Netapp. Therefore, it seems very unlikely that any process still has a grip on any of the files being part of this snapshot ... My humble opinion only of course, I'm waiting on others fellow members of this list feedback ! In addition to this, I would like to avoid the use of any exclude statement during the backup : I doubt that any of my customers would be very happy to hear that I'm not able to restore some of his precious files because the Spectrum Protect client had limitations ... Such issues never aroused with NDMP-based backups ! Cheers. Arnaud -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Tommaso Bollini Sent: Tuesday, September 18, 2018 12:29 PM To: ADSM-L@VM.MARIST.EDU Subject: R: [ADSM-L] Netapp snapdiff issues having TSM client on a Linux machine, making use of NFS mounts Hello Arnaud, maybe it would be: The NetApp snapshot indicates which files are modified on the LUN (for which their backup is triggered); but the Backup-Archive client cannot "take" them because they are locked by the application. Perhaps you can solve by inserting the appropiate rules in incl.excl file to skip them. -Messaggio originale- Da: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] Per conto di PAC Brion Arnaud Inviato: martedì 18 settembre 2018 12:21 A: ADSM-L@VM.MARIST.EDU Oggetto: [ADSM-L] Netapp snapdiff issues having TSM client on a Linux machine, making use of NFS mounts Hi All, Following to IBM's decision to withdraw the web GUI in the latest versions of their clients (thus making NDMP hardly usable), as well as to the renewal of our NAS infrastructure (now using Netapp), I'm trying to implement netapp snapdiffs in our shop. So far we succeeded in defining necessary user and roles on the Netapp, as well as to setup the TSM client in order to interact with our filer, but I'm now facing an issue where some files cannot be backed up, apparently due to access rights. Here an extract of our backup log : IBM Spectrum Protect Command Line Backup-Archive Client Interface Client Version 8, Release 1, Level 4.0 Client date/time: 09/18/2018 10:26:28 (c) Copyright by IBM Corporation and other(s) 1990, 2017. All Rights Reserved. Node Name: NETAPP_CH1_NFS Session established with server XXX: Linux/ppc64le Server Version 8, Release 1, Level 4.000 Server date/time: 09/18/2018 10:26:28 Last access: 09/18/2018 10:00:37 Incremental by snapshot difference of volume '/Airwarder' Connected to NetApp Storage Virtual Machine Management Filer Host/IP Address : Filer Version Information: NetApp Release 9.3P3: Wed Apr 04 13:07:06 UTC 2018 Storage VM Name : xxx Storage VM Host/IP Address : XX Storage VM Volume Style : Flex Login User : tsm-backup-user Transport: HTTPS Performing a Full Incremental Backup of volume '/Airwarder' Using Base Snapshot 'vserverdr.0.7b5a59c4-656c-11e8-bb80-00a098d614c2.2018-09-18_102500' with timestamp 09/18/2018 10:25:02 ANS4007E Error processing '/Airwarder/.snapshot/vserverdr.0.7b5a59c4-656c-11e8-bb80-00a098d614c2.2018-09-18_102500/acrimport_ref/ch': access to the object is denied ANS4007E Error processing '/Airwarder/.snapshot/vserverdr.0.7b5a59c4-656c-11e8-bb80-00a098d614c2.2018-09-18_102500/acrimport_test/ch': access to the object is denied ANS1898I * Processed 500 files * Directory--> 4,096 /Airwarder/ [Sent] Directory--> 4,096 /Airwarder/.etc [Sent] (skipped some lines) ANS1228E Sending of object '/Airwarder/acrimport_ref/config/log4j.conf' failed. ANS4007E Error processing '/Airwarder/acrimport_ref/config/log4j.conf': access to the object is denied Normal File--> 309 /Airwarder/acrimport_ref/config/sapConnector.cfg ** Unsuccessful ** ANS1228E Sending of object '/Airwarder/acrimport_ref/config/sapConnector.cfg' failed. ANS4007E Error processing '/Airwarder/acrimport_ref/config/sapConnector.cfg': access to the object is denied Normal File--> 330 /Airwarder/acrimport_ref/config/sapConnector.cfg.bak ** Unsuccessful ** ANS1228E Sending of object '/Airwarder/acrimport_ref/config/sapConnector.cfg.bak' failed. ANS4007E Error processing
Re: Netapp snapdiff issues having TSM client on a Linux machine, making use of NFS mounts
Hi Del, Thanks for the information, which I got as well thru other channels (IBM support), but there's still the limitation that this GUI will be usable only once logged on the machine hosting the Spectrum Protect client. This means that I will be forced to grant some of my colleagues (which were previously doing the restores on their own) specific logging rights on that machine. Was not the case before ... Cheers. Arnaud -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Del Hoobler Sent: Tuesday, September 18, 2018 12:57 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Netapp snapdiff issues having TSM client on a Linux machine, making use of NFS mounts Hi Arnaud, Not related to SnapDiff ... but just some info on NDMP and B/A Client... In Spectrum Protect BA client 8.1.6 that GAs this coming Friday (21 September) you will be able to use the native Java GUI to handle NDMP backups/restores. Del "ADSM: Dist Stor Manager" wrote on 09/18/2018 06:20:52 AM: > From: PAC Brion Arnaud > To: ADSM-L@VM.MARIST.EDU > Date: 09/18/2018 06:21 AM > Subject: Netapp snapdiff issues having TSM client on a Linux > machine, making use of NFS mounts > Sent by: "ADSM: Dist Stor Manager" > > Hi All, > > Following to IBM's decision to withdraw the web GUI in the latest > versions of their clients (thus making NDMP hardly usable), as well > as to the renewal of our NAS infrastructure (now using Netapp), I'm > trying to implement netapp snapdiffs in our shop. > > So far we succeeded in defining necessary user and roles on the > Netapp, as well as to setup the TSM client in order to interact with > our filer, but I'm now facing an issue where some files cannot be > backed up, apparently due to access rights. > > Here an extract of our backup log : > > IBM Spectrum Protect > Command Line Backup-Archive Client Interface > Client Version 8, Release 1, Level 4.0 > Client date/time: 09/18/2018 10:26:28 > (c) Copyright by IBM Corporation and other(s) 1990, 2017. All RightsReserved. > > Node Name: NETAPP_CH1_NFS > Session established with server XXX: Linux/ppc64le > Server Version 8, Release 1, Level 4.000 > Server date/time: 09/18/2018 10:26:28 Last access: 09/18/2018 10:00:37 > > > Incremental by snapshot difference of volume '/Airwarder' > > Connected to NetApp Storage Virtual Machine > Management Filer Host/IP Address : > Filer Version Information: NetApp Release 9.3P3: Wed Apr > 04 13:07:06 UTC 2018 > Storage VM Name : xxx > Storage VM Host/IP Address : XX > Storage VM Volume Style : Flex > Login User : tsm-backup-user > Transport: HTTPS > > Performing a Full Incremental Backup of volume '/Airwarder' > Using Base Snapshot 'vserverdr.0.7b5a59c4-656c-11e8- > bb80-00a098d614c2.2018-09-18_102500' with timestamp 09/18/2018 10:25:02 > ANS4007E Error processing '/Airwarder/.snapshot/vserverdr.0. > 7b5a59c4-656c-11e8-bb80-00a098d614c2.2018-09-18_102500/ > acrimport_ref/ch': access to the object is denied > ANS4007E Error processing '/Airwarder/.snapshot/vserverdr.0. > 7b5a59c4-656c-11e8-bb80-00a098d614c2.2018-09-18_102500/ > acrimport_test/ch': access to the object is denied > ANS1898I * Processed 500 files * > Directory--> 4,096 /Airwarder/ [Sent] > Directory--> 4,096 /Airwarder/.etc [Sent] > > (skipped some lines) > > ANS1228E Sending of object '/Airwarder/acrimport_ref/config/ > log4j.conf' failed. > ANS4007E Error processing '/Airwarder/acrimport_ref/config/ > log4j.conf': access to the object is denied > Normal File--> 309 /Airwarder/acrimport_ref/config/ > sapConnector.cfg ** Unsuccessful ** > ANS1228E Sending of object '/Airwarder/acrimport_ref/config/ > sapConnector.cfg' failed. > ANS4007E Error processing '/Airwarder/acrimport_ref/config/ > sapConnector.cfg': access to the object is denied > Normal File--> 330 /Airwarder/acrimport_ref/config/ > sapConnector.cfg.bak ** Unsuccessful ** > ANS1228E Sending of object '/Airwarder/acrimport_ref/config/ > sapConnector.cfg.bak' failed. > ANS4007E Error processing '/Airwarder/acrimport_ref/config/ > sapConnector.cfg.bak': access to the object is denied > > (skipped some lines) > > ANS1802E Incremental backup of '/Airwarder' finished with 90 failure(s) > > > Total number of objects inspected:5,881 >
Re: Netapp snapdiff issues having TSM client on a Linux machine, making use of NFS mounts
Hi Arnaud, Not related to SnapDiff ... but just some info on NDMP and B/A Client... In Spectrum Protect BA client 8.1.6 that GAs this coming Friday (21 September) you will be able to use the native Java GUI to handle NDMP backups/restores. Del "ADSM: Dist Stor Manager" wrote on 09/18/2018 06:20:52 AM: > From: PAC Brion Arnaud > To: ADSM-L@VM.MARIST.EDU > Date: 09/18/2018 06:21 AM > Subject: Netapp snapdiff issues having TSM client on a Linux > machine, making use of NFS mounts > Sent by: "ADSM: Dist Stor Manager" > > Hi All, > > Following to IBM's decision to withdraw the web GUI in the latest > versions of their clients (thus making NDMP hardly usable), as well > as to the renewal of our NAS infrastructure (now using Netapp), I'm > trying to implement netapp snapdiffs in our shop. > > So far we succeeded in defining necessary user and roles on the > Netapp, as well as to setup the TSM client in order to interact with > our filer, but I'm now facing an issue where some files cannot be > backed up, apparently due to access rights. > > Here an extract of our backup log : > > IBM Spectrum Protect > Command Line Backup-Archive Client Interface > Client Version 8, Release 1, Level 4.0 > Client date/time: 09/18/2018 10:26:28 > (c) Copyright by IBM Corporation and other(s) 1990, 2017. All RightsReserved. > > Node Name: NETAPP_CH1_NFS > Session established with server XXX: Linux/ppc64le > Server Version 8, Release 1, Level 4.000 > Server date/time: 09/18/2018 10:26:28 Last access: 09/18/2018 10:00:37 > > > Incremental by snapshot difference of volume '/Airwarder' > > Connected to NetApp Storage Virtual Machine > Management Filer Host/IP Address : > Filer Version Information: NetApp Release 9.3P3: Wed Apr > 04 13:07:06 UTC 2018 > Storage VM Name : xxx > Storage VM Host/IP Address : XX > Storage VM Volume Style : Flex > Login User : tsm-backup-user > Transport: HTTPS > > Performing a Full Incremental Backup of volume '/Airwarder' > Using Base Snapshot 'vserverdr.0.7b5a59c4-656c-11e8- > bb80-00a098d614c2.2018-09-18_102500' with timestamp 09/18/2018 10:25:02 > ANS4007E Error processing '/Airwarder/.snapshot/vserverdr.0. > 7b5a59c4-656c-11e8-bb80-00a098d614c2.2018-09-18_102500/ > acrimport_ref/ch': access to the object is denied > ANS4007E Error processing '/Airwarder/.snapshot/vserverdr.0. > 7b5a59c4-656c-11e8-bb80-00a098d614c2.2018-09-18_102500/ > acrimport_test/ch': access to the object is denied > ANS1898I * Processed 500 files * > Directory--> 4,096 /Airwarder/ [Sent] > Directory--> 4,096 /Airwarder/.etc [Sent] > > (skipped some lines) > > ANS1228E Sending of object '/Airwarder/acrimport_ref/config/ > log4j.conf' failed. > ANS4007E Error processing '/Airwarder/acrimport_ref/config/ > log4j.conf': access to the object is denied > Normal File--> 309 /Airwarder/acrimport_ref/config/ > sapConnector.cfg ** Unsuccessful ** > ANS1228E Sending of object '/Airwarder/acrimport_ref/config/ > sapConnector.cfg' failed. > ANS4007E Error processing '/Airwarder/acrimport_ref/config/ > sapConnector.cfg': access to the object is denied > Normal File--> 330 /Airwarder/acrimport_ref/config/ > sapConnector.cfg.bak ** Unsuccessful ** > ANS1228E Sending of object '/Airwarder/acrimport_ref/config/ > sapConnector.cfg.bak' failed. > ANS4007E Error processing '/Airwarder/acrimport_ref/config/ > sapConnector.cfg.bak': access to the object is denied > > (skipped some lines) > > ANS1802E Incremental backup of '/Airwarder' finished with 90 failure(s) > > > Total number of objects inspected:5,881 > Total number of objects backed up:5,791 > Total number of objects updated: 0 > Total number of objects rebound: 0 > Total number of objects deleted: 0 > Total number of objects expired: 0 > Total number of objects failed: 90 > Total number of objects encrypted:0 > Total number of objects grew: 0 > Total number of retries: 15 > Total number of bytes inspected: 1.27 GB > Total number of bytes transferred: 1.37 GB > Data transfer time: 18.61 sec > Network data transfer rate: 77,367.92 KB/sec > Aggregate data transfer rat
R: [ADSM-L] Netapp snapdiff issues having TSM client on a Linux machine, making use of NFS mounts
Hello Arnaud, maybe it would be: The NetApp snapshot indicates which files are modified on the LUN (for which their backup is triggered); but the Backup-Archive client cannot "take" them because they are locked by the application. Perhaps you can solve by inserting the appropiate rules in incl.excl file to skip them. -Messaggio originale- Da: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] Per conto di PAC Brion Arnaud Inviato: martedì 18 settembre 2018 12:21 A: ADSM-L@VM.MARIST.EDU Oggetto: [ADSM-L] Netapp snapdiff issues having TSM client on a Linux machine, making use of NFS mounts Hi All, Following to IBM's decision to withdraw the web GUI in the latest versions of their clients (thus making NDMP hardly usable), as well as to the renewal of our NAS infrastructure (now using Netapp), I'm trying to implement netapp snapdiffs in our shop. So far we succeeded in defining necessary user and roles on the Netapp, as well as to setup the TSM client in order to interact with our filer, but I'm now facing an issue where some files cannot be backed up, apparently due to access rights. Here an extract of our backup log : IBM Spectrum Protect Command Line Backup-Archive Client Interface Client Version 8, Release 1, Level 4.0 Client date/time: 09/18/2018 10:26:28 (c) Copyright by IBM Corporation and other(s) 1990, 2017. All Rights Reserved. Node Name: NETAPP_CH1_NFS Session established with server XXX: Linux/ppc64le Server Version 8, Release 1, Level 4.000 Server date/time: 09/18/2018 10:26:28 Last access: 09/18/2018 10:00:37 Incremental by snapshot difference of volume '/Airwarder' Connected to NetApp Storage Virtual Machine Management Filer Host/IP Address : Filer Version Information: NetApp Release 9.3P3: Wed Apr 04 13:07:06 UTC 2018 Storage VM Name : xxx Storage VM Host/IP Address : XX Storage VM Volume Style : Flex Login User : tsm-backup-user Transport: HTTPS Performing a Full Incremental Backup of volume '/Airwarder' Using Base Snapshot 'vserverdr.0.7b5a59c4-656c-11e8-bb80-00a098d614c2.2018-09-18_102500' with timestamp 09/18/2018 10:25:02 ANS4007E Error processing '/Airwarder/.snapshot/vserverdr.0.7b5a59c4-656c-11e8-bb80-00a098d614c2.2018-09-18_102500/acrimport_ref/ch': access to the object is denied ANS4007E Error processing '/Airwarder/.snapshot/vserverdr.0.7b5a59c4-656c-11e8-bb80-00a098d614c2.2018-09-18_102500/acrimport_test/ch': access to the object is denied ANS1898I * Processed 500 files * Directory--> 4,096 /Airwarder/ [Sent] Directory--> 4,096 /Airwarder/.etc [Sent] (skipped some lines) ANS1228E Sending of object '/Airwarder/acrimport_ref/config/log4j.conf' failed. ANS4007E Error processing '/Airwarder/acrimport_ref/config/log4j.conf': access to the object is denied Normal File--> 309 /Airwarder/acrimport_ref/config/sapConnector.cfg ** Unsuccessful ** ANS1228E Sending of object '/Airwarder/acrimport_ref/config/sapConnector.cfg' failed. ANS4007E Error processing '/Airwarder/acrimport_ref/config/sapConnector.cfg': access to the object is denied Normal File--> 330 /Airwarder/acrimport_ref/config/sapConnector.cfg.bak ** Unsuccessful ** ANS1228E Sending of object '/Airwarder/acrimport_ref/config/sapConnector.cfg.bak' failed. ANS4007E Error processing '/Airwarder/acrimport_ref/config/sapConnector.cfg.bak': access to the object is denied (skipped some lines) ANS1802E Incremental backup of '/Airwarder' finished with 90 failure(s) Total number of objects inspected:5,881 Total number of objects backed up:5,791 Total number of objects updated: 0 Total number of objects rebound: 0 Total number of objects deleted: 0 Total number of objects expired: 0 Total number of objects failed: 90 Total number of objects encrypted:0 Total number of objects grew: 0 Total number of retries: 15 Total number of bytes inspected: 1.27 GB Total number of bytes transferred: 1.37 GB Data transfer time: 18.61 sec Network data transfer rate: 77,367.92 KB/sec Aggregate data transfer rate: 36,807.03 KB/sec Objects compressed by:0% Total data reduction ratio:0.00% Elapsed processing time: 00:00:39 Here, a closer look at some of the files making problems : root@xx:~ # ls -al /Airwarder/acrimport_ref/config/sapConnector.cfg.bak -rw-r- 1 root root 330 May 6 2009 /Airwarder/acrimport_ref/config/sapConnector.cfg.bak root@xx:~ # ls -la /Airwarder/.snapshot/vserv
Netapp snapdiff issues having TSM client on a Linux machine, making use of NFS mounts
Hi All, Following to IBM's decision to withdraw the web GUI in the latest versions of their clients (thus making NDMP hardly usable), as well as to the renewal of our NAS infrastructure (now using Netapp), I'm trying to implement netapp snapdiffs in our shop. So far we succeeded in defining necessary user and roles on the Netapp, as well as to setup the TSM client in order to interact with our filer, but I'm now facing an issue where some files cannot be backed up, apparently due to access rights. Here an extract of our backup log : IBM Spectrum Protect Command Line Backup-Archive Client Interface Client Version 8, Release 1, Level 4.0 Client date/time: 09/18/2018 10:26:28 (c) Copyright by IBM Corporation and other(s) 1990, 2017. All Rights Reserved. Node Name: NETAPP_CH1_NFS Session established with server XXX: Linux/ppc64le Server Version 8, Release 1, Level 4.000 Server date/time: 09/18/2018 10:26:28 Last access: 09/18/2018 10:00:37 Incremental by snapshot difference of volume '/Airwarder' Connected to NetApp Storage Virtual Machine Management Filer Host/IP Address : Filer Version Information: NetApp Release 9.3P3: Wed Apr 04 13:07:06 UTC 2018 Storage VM Name : xxx Storage VM Host/IP Address : XX Storage VM Volume Style : Flex Login User : tsm-backup-user Transport: HTTPS Performing a Full Incremental Backup of volume '/Airwarder' Using Base Snapshot 'vserverdr.0.7b5a59c4-656c-11e8-bb80-00a098d614c2.2018-09-18_102500' with timestamp 09/18/2018 10:25:02 ANS4007E Error processing '/Airwarder/.snapshot/vserverdr.0.7b5a59c4-656c-11e8-bb80-00a098d614c2.2018-09-18_102500/acrimport_ref/ch': access to the object is denied ANS4007E Error processing '/Airwarder/.snapshot/vserverdr.0.7b5a59c4-656c-11e8-bb80-00a098d614c2.2018-09-18_102500/acrimport_test/ch': access to the object is denied ANS1898I * Processed 500 files * Directory--> 4,096 /Airwarder/ [Sent] Directory--> 4,096 /Airwarder/.etc [Sent] (skipped some lines) ANS1228E Sending of object '/Airwarder/acrimport_ref/config/log4j.conf' failed. ANS4007E Error processing '/Airwarder/acrimport_ref/config/log4j.conf': access to the object is denied Normal File--> 309 /Airwarder/acrimport_ref/config/sapConnector.cfg ** Unsuccessful ** ANS1228E Sending of object '/Airwarder/acrimport_ref/config/sapConnector.cfg' failed. ANS4007E Error processing '/Airwarder/acrimport_ref/config/sapConnector.cfg': access to the object is denied Normal File--> 330 /Airwarder/acrimport_ref/config/sapConnector.cfg.bak ** Unsuccessful ** ANS1228E Sending of object '/Airwarder/acrimport_ref/config/sapConnector.cfg.bak' failed. ANS4007E Error processing '/Airwarder/acrimport_ref/config/sapConnector.cfg.bak': access to the object is denied (skipped some lines) ANS1802E Incremental backup of '/Airwarder' finished with 90 failure(s) Total number of objects inspected:5,881 Total number of objects backed up:5,791 Total number of objects updated: 0 Total number of objects rebound: 0 Total number of objects deleted: 0 Total number of objects expired: 0 Total number of objects failed: 90 Total number of objects encrypted:0 Total number of objects grew: 0 Total number of retries: 15 Total number of bytes inspected: 1.27 GB Total number of bytes transferred: 1.37 GB Data transfer time: 18.61 sec Network data transfer rate: 77,367.92 KB/sec Aggregate data transfer rate: 36,807.03 KB/sec Objects compressed by:0% Total data reduction ratio:0.00% Elapsed processing time: 00:00:39 Here, a closer look at some of the files making problems : root@xx:~ # ls -al /Airwarder/acrimport_ref/config/sapConnector.cfg.bak -rw-r- 1 root root 330 May 6 2009 /Airwarder/acrimport_ref/config/sapConnector.cfg.bak root@xx:~ # ls -la /Airwarder/.snapshot/vserverdr.0.7b5a59c4-656c-11e8-bb80-00a098d614c2.2018-09-18_121000/acrimport_ref/ch ls: cannot open directory /Airwarder/.snapshot/vserverdr.0.7b5a59c4-656c-11e8-bb80-00a098d614c2.2018-09-18_121000/acrimport_ref/ch: Permission denied And who I am: root@xx:~ # id uid=0(root) gid=0(root) groups=0(root) Any idea on how to solve such issues ? Cheers. Arnaud Backup and Recovery Systems Administrator Panalpina Management Ltd., Basle, Switzerland, CIT Department Viadukstrasse 42, P.O.
Re: 8.1.2+ Linux client and file rights in /etc/adsm
Andy, Thanks for the confirmation that we can remove global write. On Wed, Aug 15, 2018 at 7:27 AM Andrew Raibeck wrote: > @Zoltan, set the files with chmod 664 (-rw-rw-r--). > > @Tandon, if that is not working for Netezza, you should contact Netezza > support about that. Full permissions does not sound right to me. > > Regards, > > Andy > > > > > Andrew Raibeck | IBM Spectrum Protect Level 3 | stor...@us.ibm.com > > IBM Tivoli Storage Manager links: > Product support: > > https://www.ibm.com/support/entry/portal/product/tivoli/tivoli_storage_manager > > Online documentation: > > http://www.ibm.com/support/knowledgecenter/SSGSG7/landing/welcome_ssgsg7.html > > Product Wiki: > > https://www.ibm.com/developerworks/community/wikis/home/wiki/Tivoli%20Storage%20Manager > > "ADSM: Dist Stor Manager" wrote on 2018-08-14 > 20:13:56: > > > From: Tandon Kadambala > > To: ADSM-L@VM.MARIST.EDU > > Date: 2018-08-14 20:16 > > Subject: Re: 8.1.2+ Linux client and file rights in /etc/adsm > > Sent by: "ADSM: Dist Stor Manager" > > > > Hi, > > > > We have give chmod 777 TSM* and spcli* > > > > We checked netzza db backups all working fine. > > > > Without full permissions it won't work > > > > Thanks and regards, > > Tandon K > > TSM Administrator, > > IBM India Pvt LTD., > > > > > > On Wed, Aug 15, 2018, 12:58 AM Zoltan Forray wrote: > > > > > Can someone point me to a document that lists the minimum file rights > > > required for files in /etc/adsm? > > > > > > Our security/scanning process is barking about file in /etc/adsm having > > > world/global rights and we need to either justify or remove those > rights: > > > > > > /etc/adsm] > > > -rw-rw-rw-. 1 root root80 Sep 13 2017 spclicert.crl > > > -rw-rw-rw-. 1 root root 10080 Sep 18 2017 spclicert.kdb > > > -rw-rw-rw-. 1 root root80 Sep 13 2017 spclicert.rdb > > > -rw---. 1 root root 193 Sep 13 2017 spclicert.sth > > > -rw-rw-rw-. 1 root root 1290 Jun 15 19:05 TSM.IDX > > > -rw-rw-rw-. 1 root root 6319 Jun 15 19:05 TSM.KDB > > > -rw---. 1 root root 193 Sep 13 2017 TSM.sth > > > > > > -- > > > *Zoltan Forray* > > > Spectrum Protect (p.k.a. TSM) Software & Hardware Administrator > > > Xymon Monitor Administrator > > > VMware Administrator > > > Virginia Commonwealth University > > > UCC/Office of Technology Services > > > www.ucc.vcu.edu > > > zfor...@vcu.edu - 804-828-4807 > > > Don't be a phishing victim - VCU and other reputable organizations will > > > never use email to request that you reply with your password, social > > > security number or confidential personal information. For more details > > > visit INVALID URI REMOVED > > u=http-3A__phishing.vcu.edu_&d=DwIBaQ&c=jf_iaSHvJObTbx- > > > > siA1ZOg&r=Ij6DLy1l7wDpCbTfcDkLC_KknvhyGdCy_RnAGnhV37I&m=4lGIl0DL_WDWrNOSA_GwiuHuTHt9GekFlm6mfMiH- > > > pg&s=bVn4fQViO6UoLJnZlE9OkAshwADIEfzXMHvlOclYXy8&e= > > > > > > -- *Zoltan Forray* Spectrum Protect (p.k.a. TSM) Software & Hardware Administrator Xymon Monitor Administrator VMware Administrator Virginia Commonwealth University UCC/Office of Technology Services www.ucc.vcu.edu zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://phishing.vcu.edu/
Re: 8.1.2+ Linux client and file rights in /etc/adsm
@Zoltan, set the files with chmod 664 (-rw-rw-r--). @Tandon, if that is not working for Netezza, you should contact Netezza support about that. Full permissions does not sound right to me. Regards, Andy Andrew Raibeck | IBM Spectrum Protect Level 3 | stor...@us.ibm.com IBM Tivoli Storage Manager links: Product support: https://www.ibm.com/support/entry/portal/product/tivoli/tivoli_storage_manager Online documentation: http://www.ibm.com/support/knowledgecenter/SSGSG7/landing/welcome_ssgsg7.html Product Wiki: https://www.ibm.com/developerworks/community/wikis/home/wiki/Tivoli%20Storage%20Manager "ADSM: Dist Stor Manager" wrote on 2018-08-14 20:13:56: > From: Tandon Kadambala > To: ADSM-L@VM.MARIST.EDU > Date: 2018-08-14 20:16 > Subject: Re: 8.1.2+ Linux client and file rights in /etc/adsm > Sent by: "ADSM: Dist Stor Manager" > > Hi, > > We have give chmod 777 TSM* and spcli* > > We checked netzza db backups all working fine. > > Without full permissions it won't work > > Thanks and regards, > Tandon K > TSM Administrator, > IBM India Pvt LTD., > > > On Wed, Aug 15, 2018, 12:58 AM Zoltan Forray wrote: > > > Can someone point me to a document that lists the minimum file rights > > required for files in /etc/adsm? > > > > Our security/scanning process is barking about file in /etc/adsm having > > world/global rights and we need to either justify or remove those rights: > > > > /etc/adsm] > > -rw-rw-rw-. 1 root root80 Sep 13 2017 spclicert.crl > > -rw-rw-rw-. 1 root root 10080 Sep 18 2017 spclicert.kdb > > -rw-rw-rw-. 1 root root80 Sep 13 2017 spclicert.rdb > > -rw---. 1 root root 193 Sep 13 2017 spclicert.sth > > -rw-rw-rw-. 1 root root 1290 Jun 15 19:05 TSM.IDX > > -rw-rw-rw-. 1 root root 6319 Jun 15 19:05 TSM.KDB > > -rw---. 1 root root 193 Sep 13 2017 TSM.sth > > > > -- > > *Zoltan Forray* > > Spectrum Protect (p.k.a. TSM) Software & Hardware Administrator > > Xymon Monitor Administrator > > VMware Administrator > > Virginia Commonwealth University > > UCC/Office of Technology Services > > www.ucc.vcu.edu > > zfor...@vcu.edu - 804-828-4807 > > Don't be a phishing victim - VCU and other reputable organizations will > > never use email to request that you reply with your password, social > > security number or confidential personal information. For more details > > visit INVALID URI REMOVED > u=http-3A__phishing.vcu.edu_&d=DwIBaQ&c=jf_iaSHvJObTbx- > siA1ZOg&r=Ij6DLy1l7wDpCbTfcDkLC_KknvhyGdCy_RnAGnhV37I&m=4lGIl0DL_WDWrNOSA_GwiuHuTHt9GekFlm6mfMiH- > pg&s=bVn4fQViO6UoLJnZlE9OkAshwADIEfzXMHvlOclYXy8&e= > > >
Re: 8.1.2+ Linux client and file rights in /etc/adsm
Hi, We have give chmod 777 TSM* and spcli* We checked netzza db backups all working fine. Without full permissions it won't work Thanks and regards, Tandon K TSM Administrator, IBM India Pvt LTD., On Wed, Aug 15, 2018, 5:43 AM Tandon Kadambala wrote: > Hi, > > We have give chmod 777 TSM* and spcli* > > We checked netzza db backups all working fine. > > Without full permissions it won't work > > Thanks and regards, > Tandon K > TSM Administrator, > IBM India Pvt LTD., > > > On Wed, Aug 15, 2018, 12:58 AM Zoltan Forray wrote: > >> Can someone point me to a document that lists the minimum file rights >> required for files in /etc/adsm? >> >> Our security/scanning process is barking about file in /etc/adsm having >> world/global rights and we need to either justify or remove those rights: >> >> /etc/adsm] >> -rw-rw-rw-. 1 root root80 Sep 13 2017 spclicert.crl >> -rw-rw-rw-. 1 root root 10080 Sep 18 2017 spclicert.kdb >> -rw-rw-rw-. 1 root root80 Sep 13 2017 spclicert.rdb >> -rw---. 1 root root 193 Sep 13 2017 spclicert.sth >> -rw-rw-rw-. 1 root root 1290 Jun 15 19:05 TSM.IDX >> -rw-rw-rw-. 1 root root 6319 Jun 15 19:05 TSM.KDB >> -rw---. 1 root root 193 Sep 13 2017 TSM.sth >> >> -- >> *Zoltan Forray* >> Spectrum Protect (p.k.a. TSM) Software & Hardware Administrator >> Xymon Monitor Administrator >> VMware Administrator >> Virginia Commonwealth University >> UCC/Office of Technology Services >> www.ucc.vcu.edu >> zfor...@vcu.edu - 804-828-4807 >> Don't be a phishing victim - VCU and other reputable organizations will >> never use email to request that you reply with your password, social >> security number or confidential personal information. For more details >> visit http://phishing.vcu.edu/ >> >
Re: 8.1.2+ Linux client and file rights in /etc/adsm
Hi, We have give chmod 777 TSM* and spcli* We checked netzza db backups all working fine. Without full permissions it won't work Thanks and regards, Tandon K TSM Administrator, IBM India Pvt LTD., On Wed, Aug 15, 2018, 12:58 AM Zoltan Forray wrote: > Can someone point me to a document that lists the minimum file rights > required for files in /etc/adsm? > > Our security/scanning process is barking about file in /etc/adsm having > world/global rights and we need to either justify or remove those rights: > > /etc/adsm] > -rw-rw-rw-. 1 root root80 Sep 13 2017 spclicert.crl > -rw-rw-rw-. 1 root root 10080 Sep 18 2017 spclicert.kdb > -rw-rw-rw-. 1 root root80 Sep 13 2017 spclicert.rdb > -rw---. 1 root root 193 Sep 13 2017 spclicert.sth > -rw-rw-rw-. 1 root root 1290 Jun 15 19:05 TSM.IDX > -rw-rw-rw-. 1 root root 6319 Jun 15 19:05 TSM.KDB > -rw---. 1 root root 193 Sep 13 2017 TSM.sth > > -- > *Zoltan Forray* > Spectrum Protect (p.k.a. TSM) Software & Hardware Administrator > Xymon Monitor Administrator > VMware Administrator > Virginia Commonwealth University > UCC/Office of Technology Services > www.ucc.vcu.edu > zfor...@vcu.edu - 804-828-4807 > Don't be a phishing victim - VCU and other reputable organizations will > never use email to request that you reply with your password, social > security number or confidential personal information. For more details > visit http://phishing.vcu.edu/ >
8.1.2+ Linux client and file rights in /etc/adsm
Can someone point me to a document that lists the minimum file rights required for files in /etc/adsm? Our security/scanning process is barking about file in /etc/adsm having world/global rights and we need to either justify or remove those rights: /etc/adsm] -rw-rw-rw-. 1 root root80 Sep 13 2017 spclicert.crl -rw-rw-rw-. 1 root root 10080 Sep 18 2017 spclicert.kdb -rw-rw-rw-. 1 root root80 Sep 13 2017 spclicert.rdb -rw---. 1 root root 193 Sep 13 2017 spclicert.sth -rw-rw-rw-. 1 root root 1290 Jun 15 19:05 TSM.IDX -rw-rw-rw-. 1 root root 6319 Jun 15 19:05 TSM.KDB -rw---. 1 root root 193 Sep 13 2017 TSM.sth -- *Zoltan Forray* Spectrum Protect (p.k.a. TSM) Software & Hardware Administrator Xymon Monitor Administrator VMware Administrator Virginia Commonwealth University UCC/Office of Technology Services www.ucc.vcu.edu zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://phishing.vcu.edu/
Re: TSM 8.1.1 on Linux crash
Hi, how nice of them. Now if only they would fix the bug that crashes the kernel if you remove/reboot/access a tape drive at the wrong time… > On 2 Feb 2018, at 19:33, Zoltan Forray wrote: > > Remco, > > I don't know if you noticed that IBM updated the lin_tape.fixlist file to > include RHEL 7.4. I got a notice about an update but didn't see anything > changing, version-wise. This was the file from November, 2017 > > Fixlist for Linux IBM Tape Device Driver (lin_tape) > > (C) Copyright IBM Corporation 2007-2017 > > Level Date Description > --- > 3.0.23 11/03/2017 - Initial support for RHEL 6.9 (min. kernel version > 2.6.32-696) >- Support for LTO8 >- Fix for reservation conflict when reserve_6 used >- Fix for failover after device rediscovery (introduced > at 3.0.20) >- Fix for device name after removal (introduced at > 3.0.20) >- Fix for read with resid through join interface > > This is the file, today. > > Fixlist for Linux IBM Tape Device Driver (lin_tape) > > (C) Copyright IBM Corporation 2007-2017 > > Level Date Description > --- > 3.0.23 11/03/2017 - Initial support for RHEL 7.4 (min. kernel > version 3.10.0-693) >- Initial support for RHEL 6.9 (min. kernel > version 2.6.32-696) >- Support for LTO8 >- Fix for reservation conflict when reserve_6 used >- Fix for failover after device rediscovery > (introduced at 3.0.20) >- Fix for device name after removal (introduced at 3.0.20) >- Fix for read with resid through join interface > > > and they thought we wouldn't notice 🤔 > > > On Fri, Jan 12, 2018 at 11:29 AM, Remco Post wrote: > >> Today we checked the lin_tape driver versions. Well, in 3.0.23 are a >> number of fixes for issues introduced in our current level 3.0.20… Found >> out another nice issue: we’re at redhat 7.4, while lin_tape doesn’t seem to >> support RHEL 7.4. >> >> >>> On 10 Jan 2018, at 10:32, Remco Post wrote: >>> >>>> On 10 Jan 2018, at 02:05, Harris, Steven > BTFINANCIALGROUP.COM <mailto:steven.har...@btfinancialgroup.com>> wrote: >>>> >>>> Remco >>>> >>>> Can you please explain what the fall-out is? >>> >>> The fall-out is TSM locking up a CPU in an uninterruptible routine, with >> only one solution: reboot the entire Linux box. >>> >>>> >>>> I'm using TSM 7.1.0 on AIX and have issues with LTO6 drives emulating >> LTOs. Sometimes I just power cycle the drive and that clears the problem, >> but that does not always work. >>>> >>>> Whilst I don't have any linux servers or storage agents in that >> particular mix, I'd like to understand what you are seeing for future >> reference. >>>> >>>> Thanks >>>> >>>> Steve >>>> >>>> Steven Harris >>>> TSM Admin/Consultant >>>> >>>> Canberra Australia >>>> >>>> >>>> >>>> This message and any attachment is confidential and may be privileged >> or otherwise protected from disclosure. You should immediately delete the >> message if you are not the intended recipient. If you have received this >> email by mistake please delete it from your system; you should not copy the >> message or disclose its content to anyone. >>>> >>>> This electronic communication may contain general financial product >> advice but should not be relied upon or construed as a recommendation of >> any financial product. The information has been prepared without taking >> into account your objectives, financial situation or needs. You should >> consider the Product Disclosure Statement relating to the financial product >> and consult your financial adviser before making a decision about whether >> to acquire, hold or dispose of a financial product. >>>> >>>> For further details on the financial product please go to >> http://www.bt.com.au >>>> >>>> Past performance is not a reliable indicator of future performance. >>> >>> -- >>> >>> Met vriendelijke groeten/Kind Regards, >>> >>> Remco Post >>&g
Re: TSM 8.1.1 on Linux crash
Remco, I don't know if you noticed that IBM updated the lin_tape.fixlist file to include RHEL 7.4. I got a notice about an update but didn't see anything changing, version-wise. This was the file from November, 2017 Fixlist for Linux IBM Tape Device Driver (lin_tape) (C) Copyright IBM Corporation 2007-2017 Level Date Description --- 3.0.23 11/03/2017 - Initial support for RHEL 6.9 (min. kernel version 2.6.32-696) - Support for LTO8 - Fix for reservation conflict when reserve_6 used - Fix for failover after device rediscovery (introduced at 3.0.20) - Fix for device name after removal (introduced at 3.0.20) - Fix for read with resid through join interface This is the file, today. Fixlist for Linux IBM Tape Device Driver (lin_tape) (C) Copyright IBM Corporation 2007-2017 Level Date Description --- 3.0.23 11/03/2017 - Initial support for RHEL 7.4 (min. kernel version 3.10.0-693) - Initial support for RHEL 6.9 (min. kernel version 2.6.32-696) - Support for LTO8 - Fix for reservation conflict when reserve_6 used - Fix for failover after device rediscovery (introduced at 3.0.20) - Fix for device name after removal (introduced at 3.0.20) - Fix for read with resid through join interface and they thought we wouldn't notice 🤔 On Fri, Jan 12, 2018 at 11:29 AM, Remco Post wrote: > Today we checked the lin_tape driver versions. Well, in 3.0.23 are a > number of fixes for issues introduced in our current level 3.0.20… Found > out another nice issue: we’re at redhat 7.4, while lin_tape doesn’t seem to > support RHEL 7.4. > > > > On 10 Jan 2018, at 10:32, Remco Post wrote: > > > >> On 10 Jan 2018, at 02:05, Harris, Steven BTFINANCIALGROUP.COM <mailto:steven.har...@btfinancialgroup.com>> wrote: > >> > >> Remco > >> > >> Can you please explain what the fall-out is? > > > > The fall-out is TSM locking up a CPU in an uninterruptible routine, with > only one solution: reboot the entire Linux box. > > > >> > >> I'm using TSM 7.1.0 on AIX and have issues with LTO6 drives emulating > LTOs. Sometimes I just power cycle the drive and that clears the problem, > but that does not always work. > >> > >> Whilst I don't have any linux servers or storage agents in that > particular mix, I'd like to understand what you are seeing for future > reference. > >> > >> Thanks > >> > >> Steve > >> > >> Steven Harris > >> TSM Admin/Consultant > >> > >> Canberra Australia > >> > >> > >> > >> This message and any attachment is confidential and may be privileged > or otherwise protected from disclosure. You should immediately delete the > message if you are not the intended recipient. If you have received this > email by mistake please delete it from your system; you should not copy the > message or disclose its content to anyone. > >> > >> This electronic communication may contain general financial product > advice but should not be relied upon or construed as a recommendation of > any financial product. The information has been prepared without taking > into account your objectives, financial situation or needs. You should > consider the Product Disclosure Statement relating to the financial product > and consult your financial adviser before making a decision about whether > to acquire, hold or dispose of a financial product. > >> > >> For further details on the financial product please go to > http://www.bt.com.au > >> > >> Past performance is not a reliable indicator of future performance. > > > > -- > > > > Met vriendelijke groeten/Kind Regards, > > > > Remco Post > > r.p...@plcs.nl <mailto:r.p...@plcs.nl> > > +31 6 248 21 622 > > -- > > Met vriendelijke groeten/Kind Regards, > > Remco Post > r.p...@plcs.nl > +31 6 248 21 622 > -- *Zoltan Forray* Spectrum Protect (p.k.a. TSM) Software & Hardware Administrator Xymon Monitor Administrator VMware Administrator Virginia Commonwealth University UCC/Office of Technology Services www.ucc.vcu.edu zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://phishing.vcu.edu/
Re: TSM 8.1.1 on Linux crash
>we’re at redhat 7.4, while lin_tape doesn’t seem to support RHEL 7.4 I wouldn't be too concerned about this. We have installed the "latest" lin_tape drivers on our RHEL Linux systems waaay before the readme said it supported the OS level we were installing it on. I wouldn't suspect a world of difference between 7.3 and 7.4. On Fri, Jan 12, 2018 at 11:29 AM, Remco Post wrote: > Today we checked the lin_tape driver versions. Well, in 3.0.23 are a > number of fixes for issues introduced in our current level 3.0.20… Found > out another nice issue: we’re at redhat 7.4, while lin_tape doesn’t seem to > support RHEL 7.4. > > > > On 10 Jan 2018, at 10:32, Remco Post wrote: > > > >> On 10 Jan 2018, at 02:05, Harris, Steven BTFINANCIALGROUP.COM <mailto:steven.har...@btfinancialgroup.com>> wrote: > >> > >> Remco > >> > >> Can you please explain what the fall-out is? > > > > The fall-out is TSM locking up a CPU in an uninterruptible routine, with > only one solution: reboot the entire Linux box. > > > >> > >> I'm using TSM 7.1.0 on AIX and have issues with LTO6 drives emulating > LTOs. Sometimes I just power cycle the drive and that clears the problem, > but that does not always work. > >> > >> Whilst I don't have any linux servers or storage agents in that > particular mix, I'd like to understand what you are seeing for future > reference. > >> > >> Thanks > >> > >> Steve > >> > >> Steven Harris > >> TSM Admin/Consultant > >> > >> Canberra Australia > >> > >> > >> > >> This message and any attachment is confidential and may be privileged > or otherwise protected from disclosure. You should immediately delete the > message if you are not the intended recipient. If you have received this > email by mistake please delete it from your system; you should not copy the > message or disclose its content to anyone. > >> > >> This electronic communication may contain general financial product > advice but should not be relied upon or construed as a recommendation of > any financial product. The information has been prepared without taking > into account your objectives, financial situation or needs. You should > consider the Product Disclosure Statement relating to the financial product > and consult your financial adviser before making a decision about whether > to acquire, hold or dispose of a financial product. > >> > >> For further details on the financial product please go to > http://www.bt.com.au > >> > >> Past performance is not a reliable indicator of future performance. > > > > -- > > > > Met vriendelijke groeten/Kind Regards, > > > > Remco Post > > r.p...@plcs.nl <mailto:r.p...@plcs.nl> > > +31 6 248 21 622 > > -- > > Met vriendelijke groeten/Kind Regards, > > Remco Post > r.p...@plcs.nl > +31 6 248 21 622 > -- *Zoltan Forray* Spectrum Protect (p.k.a. TSM) Software & Hardware Administrator Xymon Monitor Administrator VMware Administrator Virginia Commonwealth University UCC/Office of Technology Services www.ucc.vcu.edu zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://phishing.vcu.edu/
Re: TSM 8.1.1 on Linux crash
Today we checked the lin_tape driver versions. Well, in 3.0.23 are a number of fixes for issues introduced in our current level 3.0.20… Found out another nice issue: we’re at redhat 7.4, while lin_tape doesn’t seem to support RHEL 7.4. > On 10 Jan 2018, at 10:32, Remco Post wrote: > >> On 10 Jan 2018, at 02:05, Harris, Steven > <mailto:steven.har...@btfinancialgroup.com>> wrote: >> >> Remco >> >> Can you please explain what the fall-out is? > > The fall-out is TSM locking up a CPU in an uninterruptible routine, with only > one solution: reboot the entire Linux box. > >> >> I'm using TSM 7.1.0 on AIX and have issues with LTO6 drives emulating LTOs. >> Sometimes I just power cycle the drive and that clears the problem, but that >> does not always work. >> >> Whilst I don't have any linux servers or storage agents in that particular >> mix, I'd like to understand what you are seeing for future reference. >> >> Thanks >> >> Steve >> >> Steven Harris >> TSM Admin/Consultant >> >> Canberra Australia >> >> >> >> This message and any attachment is confidential and may be privileged or >> otherwise protected from disclosure. You should immediately delete the >> message if you are not the intended recipient. If you have received this >> email by mistake please delete it from your system; you should not copy the >> message or disclose its content to anyone. >> >> This electronic communication may contain general financial product advice >> but should not be relied upon or construed as a recommendation of any >> financial product. The information has been prepared without taking into >> account your objectives, financial situation or needs. You should consider >> the Product Disclosure Statement relating to the financial product and >> consult your financial adviser before making a decision about whether to >> acquire, hold or dispose of a financial product. >> >> For further details on the financial product please go to >> http://www.bt.com.au >> >> Past performance is not a reliable indicator of future performance. > > -- > > Met vriendelijke groeten/Kind Regards, > > Remco Post > r.p...@plcs.nl <mailto:r.p...@plcs.nl> > +31 6 248 21 622 -- Met vriendelijke groeten/Kind Regards, Remco Post r.p...@plcs.nl +31 6 248 21 622
Re: TSM 8.1.1 on Linux crash
> On 10 Jan 2018, at 02:05, Harris, Steven > wrote: > > Remco > > Can you please explain what the fall-out is? The fall-out is TSM locking up a CPU in an uninterruptible routine, with only one solution: reboot the entire Linux box. > > I'm using TSM 7.1.0 on AIX and have issues with LTO6 drives emulating LTOs. > Sometimes I just power cycle the drive and that clears the problem, but that > does not always work. > > Whilst I don't have any linux servers or storage agents in that particular > mix, I'd like to understand what you are seeing for future reference. > > Thanks > > Steve > > Steven Harris > TSM Admin/Consultant > > Canberra Australia > > > > This message and any attachment is confidential and may be privileged or > otherwise protected from disclosure. You should immediately delete the > message if you are not the intended recipient. If you have received this > email by mistake please delete it from your system; you should not copy the > message or disclose its content to anyone. > > This electronic communication may contain general financial product advice > but should not be relied upon or construed as a recommendation of any > financial product. The information has been prepared without taking into > account your objectives, financial situation or needs. You should consider > the Product Disclosure Statement relating to the financial product and > consult your financial adviser before making a decision about whether to > acquire, hold or dispose of a financial product. > > For further details on the financial product please go to > http://www.bt.com.au > > Past performance is not a reliable indicator of future performance. -- Met vriendelijke groeten/Kind Regards, Remco Post r.p...@plcs.nl +31 6 248 21 622
Re: TSM 8.1.1 on Linux crash
Remco Can you please explain what the fall-out is? I'm using TSM 7.1.0 on AIX and have issues with LTO6 drives emulating LTOs. Sometimes I just power cycle the drive and that clears the problem, but that does not always work. Whilst I don't have any linux servers or storage agents in that particular mix, I'd like to understand what you are seeing for future reference. Thanks Steve Steven Harris TSM Admin/Consultant Canberra Australia This message and any attachment is confidential and may be privileged or otherwise protected from disclosure. You should immediately delete the message if you are not the intended recipient. If you have received this email by mistake please delete it from your system; you should not copy the message or disclose its content to anyone. This electronic communication may contain general financial product advice but should not be relied upon or construed as a recommendation of any financial product. The information has been prepared without taking into account your objectives, financial situation or needs. You should consider the Product Disclosure Statement relating to the financial product and consult your financial adviser before making a decision about whether to acquire, hold or dispose of a financial product. For further details on the financial product please go to http://www.bt.com.au Past performance is not a reliable indicator of future performance.
Re: TSM 8.1.1 on Linux crash
> Op 9 jan. 2018, om 18:14 heeft Martin Janosik het > volgende geschreven: > > Hello there, > > errno 16 usually corresponds to 'device busy'. I have observed this error > mostly on systems with shared library (shared=yes) and with storage agents > that had some problems to communicate with TSM server. > Are you facing the issue only on a single tape drive, or all? Are they > zoned by any chance also to other systems, i.e. 2nd cluster node? > Can you send few lines from actlog related to the drive with error before > failure occured? > Hi Martin, you are absolutely right, the drives are shared to multiple systems. The issue arises when the TSM instance using the drive crashes. To then free up the drive it has to be rebooted. But apparently, rebooting a tape drive is not a safe operation, given the fall-out is sometimes has. > M. Janosik > > "ADSM: Dist Stor Manager" wrote on 2018-01-09 > 17:58:09: > >> From: Remco Post >> To: ADSM-L@VM.MARIST.EDU >> Date: 2018-01-09 17:59 >> Subject: [ADSM-L] TSM 8.1.1 on Linux crash >> Sent by: "ADSM: Dist Stor Manager" >> >> Hi All, >> >> over here we have a few TSM servers on Linux (RHEL 7.4) TSM 8.1.1. >> 021 (to be upgraded to .100 soon) and we see something new that we >> never saw on AIX. If for some reason a tape gets left in a drive >> (IBM 3592) the only way to get the drive working again in to reboot >> the drive. Until then TSM is unable to open the drive (error 16). >> Unfortunately we seem to be able to reliably cause severe issues in >> TSM by rebooting a tapedrive: >> >> kernel: NMI watchdog: BUG: soft lockup - CPU#6 stuck for 22s! > [dsmserv:6021] >> >> The only way out is to reboot the entire server. >> >> We never had such issues with TSM on AIX… is this something Linux- >> specific that we can hang TSM in non-interuptable routines (kernel >> space) by simply rebooting a tape drive? >> >> -- >> >> Met vriendelijke groeten/Kind Regards, >> >> Remco Post >> r.p...@plcs.nl >> +31 6 248 21 622 >> -- Met vriendelijke groeten/Kind Regards, Remco Post r.p...@plcs.nl +31 6 248 21 622
Re: TSM 8.1.1 on Linux crash
Hello there, errno 16 usually corresponds to 'device busy'. I have observed this error mostly on systems with shared library (shared=yes) and with storage agents that had some problems to communicate with TSM server. Are you facing the issue only on a single tape drive, or all? Are they zoned by any chance also to other systems, i.e. 2nd cluster node? Can you send few lines from actlog related to the drive with error before failure occured? M. Janosik "ADSM: Dist Stor Manager" wrote on 2018-01-09 17:58:09: > From: Remco Post > To: ADSM-L@VM.MARIST.EDU > Date: 2018-01-09 17:59 > Subject: [ADSM-L] TSM 8.1.1 on Linux crash > Sent by: "ADSM: Dist Stor Manager" > > Hi All, > > over here we have a few TSM servers on Linux (RHEL 7.4) TSM 8.1.1. > 021 (to be upgraded to .100 soon) and we see something new that we > never saw on AIX. If for some reason a tape gets left in a drive > (IBM 3592) the only way to get the drive working again in to reboot > the drive. Until then TSM is unable to open the drive (error 16). > Unfortunately we seem to be able to reliably cause severe issues in > TSM by rebooting a tapedrive: > > kernel: NMI watchdog: BUG: soft lockup - CPU#6 stuck for 22s! [dsmserv:6021] > > The only way out is to reboot the entire server. > > We never had such issues with TSM on AIX… is this something Linux- > specific that we can hang TSM in non-interuptable routines (kernel > space) by simply rebooting a tape drive? > > -- > > Met vriendelijke groeten/Kind Regards, > > Remco Post > r.p...@plcs.nl > +31 6 248 21 622 >
TSM 8.1.1 on Linux crash
Hi All, over here we have a few TSM servers on Linux (RHEL 7.4) TSM 8.1.1.021 (to be upgraded to .100 soon) and we see something new that we never saw on AIX. If for some reason a tape gets left in a drive (IBM 3592) the only way to get the drive working again in to reboot the drive. Until then TSM is unable to open the drive (error 16). Unfortunately we seem to be able to reliably cause severe issues in TSM by rebooting a tapedrive: kernel: NMI watchdog: BUG: soft lockup - CPU#6 stuck for 22s! [dsmserv:6021] The only way out is to reboot the entire server. We never had such issues with TSM on AIX… is this something Linux-specific that we can hang TSM in non-interuptable routines (kernel space) by simply rebooting a tape drive? -- Met vriendelijke groeten/Kind Regards, Remco Post r.p...@plcs.nl +31 6 248 21 622
Re: Has anyone any info on Linux on Power - Big Endian clients
Hi, I think that this post from Del Hoobler should answer your questions: https://www.mail-archive.com/adsm-l@vm.marist.edu/msg100743.html "IBM did not drop the API support for LoP BE specifically so that Data Protection for SAP HANA on Power BE continues to be supported." I think that there won't be any new Full Client Big Endian distributions in the future. Giacomo Testa -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of King, Harold Clyde (Hal) Sent: Friday, November 10, 2017 17:20 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Has anyone any info on Linux on Power - Big Endian clients Due to the recent CVEs (CVE-2017-1301) we have been upgrading our Spectrum Protect clients to 8.1.2. I have found all but the clients for Linux on Power (PPC) Big Endian. All that seems to be released for it is a new API no actual client. I called the first level support and they sent me to sales, who have not yet gotten back to me. Has anyone any idea as to why the API would be released without a client? Has anyone heard from sales or support as to when they might release a full client distribution? Thanks in advance -- Hal King - h...@utk.edu Systems Administrator Office of Information Technology Shared Systems Services The University of Tennessee 103C5 Kingston Pike Building 2309 Kingston Pk. Knoxville, TN 37996 Phone : 974-1599 Helpdesk 24/7 : 974-9900
Has anyone any info on Linux on Power - Big Endian clients
Due to the recent CVEs (CVE-2017-1301) we have been upgrading our Spectrum Protect clients to 8.1.2. I have found all but the clients for Linux on Power (PPC) Big Endian. All that seems to be released for it is a new API no actual client. I called the first level support and they sent me to sales, who have not yet gotten back to me. Has anyone any idea as to why the API would be released without a client? Has anyone heard from sales or support as to when they might release a full client distribution? Thanks in advance -- Hal King - h...@utk.edu Systems Administrator Office of Information Technology Shared Systems Services The University of Tennessee 103C5 Kingston Pike Building 2309 Kingston Pk. Knoxville, TN 37996 Phone : 974-1599 Helpdesk 24/7 : 974-9900
Re: Migrate from TSM Server 5.5.7 on Windows to TSM Server 7.1.7 on Linux - the unsupported way because exportdb --> insertdb did not work
Hi Dennis, I suggest if possible upgrading your old server to a minimum of version 6.3 then retry the migration, then both databases are full DB2. Many people had issues going from 5.x straight to version 7 and had much more success by first upgrading the old server. Also, if possible I would use the "new server network method". It eliminates the complexities that a tape library adds to the process. Hope this helps -Rick Adamson -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Schneck, Dennis Sent: Wednesday, August 02, 2017 3:24 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Migrate from TSM Server 5.5.7 on Windows to TSM Server 7.1.7 on Linux - the unsupported way because exportdb --> insertdb did not work Hello, how to migrate from TSM Server 5.5.x on Windows to TSM Server 7.1.7 on Linux ( only one tape library ) ? because my way ( see 2nd ) is not supported 1st I tryed: ( exportdb --> insertdb ) VM1: TSM 5.5.7 on Windows and VM2: TSM 7.1.7 on Windows VM1: restore backup from productive System. install UpgradeTool VM2: migrate on VM2 with dsmupgdx from VM1 then I had TSM 7.1.7 running. Did a exportdb on TSM 7.1.7 on Windows If "insertdb" on Linux TSM Server 7.1.7 got this error: /opt/tivoli/tsm/server/bin/dsmserv insertdb manifest=/import/manifest.txt IBM Tivoli Storage Manager for Linux/x86_64 Version 7, Release 1, Level 7.100 ... "ANR1953E INSERTDB: Linux/x86_64 cannot be the target of a database upgrade from Windows." 2nd I tryed: ( local migrate ) Install TSM Server 5.5.7 on Linux ( SLES 12 SP2 ) + TSM Client 5.5.4.0 restore backup from productive System. Install UpgradeTool Upgrade to TSM 7.1.3 an run "dsmupgdx" for migrate local Server (Network Method). Then TSM Server 7.1.3 is running with Data from TSM Server 5.5.x Windows Then Update to 7.1.7.300 this works... but IBM support say by phonecall - " .. this is not supported " :-( Any proposals for a supported way ? Thanks Dennis
Re: Migrate from TSM Server 5.5.7 on Windows to TSM Server 7.1.7 on Linux - the unsupported way because exportdb --> insertdb did not work
You may also want to make use of the documents found in this link. https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli%20Storage%20Manager/page/Migrating%20Tivoli%20Storage%20Manager%20Servers%20from%20one%20Operating%20System%20to%20another __ Andrew Galloway Operational Systems Continuity Analyst SSC RCMP Technology Directorate CIO Building C1035 R.C.M.P. Headquarters 1200 Vanier Parkway Ottawa ON K1A 0R2 613.998.7707 andrew.gallo...@ssc-spc.gc.ca__ >>> "Schneck, Dennis" 2017-08-02 3:24 AM >>> Hello, how to migrate from TSM Server 5.5.x on Windows to TSM Server 7.1.7 on Linux ( only one tape library ) ? because my way ( see 2nd ) is not supported 1st I tryed: ( exportdb --> insertdb ) VM1: TSM 5.5.7 on Windows and VM2: TSM 7.1.7 on Windows VM1: restore backup from productive System. install UpgradeTool VM2: migrate on VM2 with dsmupgdx from VM1 then I had TSM 7.1.7 running. Did a exportdb on TSM 7.1.7 on Windows If "insertdb" on Linux TSM Server 7.1.7 got this error: /opt/tivoli/tsm/server/bin/dsmserv insertdb manifest=/import/manifest.txt IBM Tivoli Storage Manager for Linux/x86_64 Version 7, Release 1, Level 7.100 ... "ANR1953E INSERTDB: Linux/x86_64 cannot be the target of a database upgrade from Windows." 2nd I tryed: ( local migrate ) Install TSM Server 5.5.7 on Linux ( SLES 12 SP2 ) + TSM Client 5.5.4.0 restore backup from productive System. Install UpgradeTool Upgrade to TSM 7.1.3 an run "dsmupgdx" for migrate local Server (Network Method). Then TSM Server 7.1.3 is running with Data from TSM Server 5.5.x Windows Then Update to 7.1.7.300 this works... but IBM support say by phonecall - " .. this is not supported " :-( Any proposals for a supported way ? Thanks Dennis
Re: Migrate from TSM Server 5.5.7 on Windows to TSM Server 7.1.7 on Linux - the unsupported way because exportdb --> insertdb did not work
Hi I am nou sre if it is supported. But create server to server connection between old and new server and export node by node... We did it last year and it works, bur depend on amount of data HTH Chavdar On Wednesday, 2 August 2017, Loon, Eric van (ITOPT3) - KLM < eric-van.l...@klm.com> wrote: > Hi Dennis! > Can you partition your library? In that case you can connect it to both > your old Windows server and your new Linux server and use export node > toserver= to move your existing backups to the new TSM server. > Kind regards, > Eric van Loon > Air France/KLM Storage Engineering > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU ] > On Behalf Of Schneck, Dennis > Sent: woensdag 2 augustus 2017 9:24 > To: ADSM-L@VM.MARIST.EDU > Subject: Migrate from TSM Server 5.5.7 on Windows to TSM Server 7.1.7 on > Linux - the unsupported way because exportdb --> insertdb did not work > > Hello, > how to migrate from TSM Server 5.5.x on Windows to TSM Server 7.1.7 on > Linux ( only one tape library ) ? > because my way ( see 2nd ) is not supported > > > 1st I tryed: ( exportdb --> insertdb ) > > VM1: TSM 5.5.7 on Windows and VM2: TSM 7.1.7 on Windows > > VM1: > restore backup from productive System. > install UpgradeTool > > VM2: > migrate on VM2 with dsmupgdx from VM1 > then I had TSM 7.1.7 running. > Did a exportdb on TSM 7.1.7 on Windows > > If "insertdb" on Linux TSM Server 7.1.7 got this error: > > /opt/tivoli/tsm/server/bin/dsmserv insertdb manifest=/import/manifest.txt > > IBM Tivoli Storage Manager for Linux/x86_64 Version 7, Release 1, Level > 7.100 ... > "ANR1953E INSERTDB: Linux/x86_64 cannot be the target of a database > upgrade from Windows." > > > > 2nd I tryed: ( local migrate ) > > Install TSM Server 5.5.7 on Linux ( SLES 12 SP2 ) + TSM Client 5.5.4.0 > restore backup from productive System. > Install UpgradeTool > > Upgrade to TSM 7.1.3 an run "dsmupgdx" > for migrate local Server (Network Method). > Then TSM Server 7.1.3 is running with Data from TSM Server 5.5.x Windows > Then Update to 7.1.7.300 > > this works... but IBM support say by phonecall - " .. this is not > supported " :-( > > > > Any proposals for a supported way ? > > > > Thanks > Dennis > > For information, services and offers, please visit our web site: > http://www.klm.com. This e-mail and any attachment may contain > confidential and privileged material intended for the addressee only. If > you are not the addressee, you are notified that no part of the e-mail or > any attachment may be disclosed, copied or distributed, and that any other > action related to this e-mail or attachment is strictly prohibited, and may > be unlawful. If you have received this e-mail by error, please notify the > sender immediately by return e-mail, and delete this message. > > Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its > employees shall not be liable for the incorrect or incomplete transmission > of this e-mail or any attachments, nor responsible for any delay in receipt. > Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch > Airlines) is registered in Amstelveen, The Netherlands, with registered > number 33014286 > >
Re: Migrate from TSM Server 5.5.7 on Windows to TSM Server 7.1.7 on Linux - the unsupported way because exportdb --> insertdb did not work
Hi Dennis! Can you partition your library? In that case you can connect it to both your old Windows server and your new Linux server and use export node toserver= to move your existing backups to the new TSM server. Kind regards, Eric van Loon Air France/KLM Storage Engineering -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Schneck, Dennis Sent: woensdag 2 augustus 2017 9:24 To: ADSM-L@VM.MARIST.EDU Subject: Migrate from TSM Server 5.5.7 on Windows to TSM Server 7.1.7 on Linux - the unsupported way because exportdb --> insertdb did not work Hello, how to migrate from TSM Server 5.5.x on Windows to TSM Server 7.1.7 on Linux ( only one tape library ) ? because my way ( see 2nd ) is not supported 1st I tryed: ( exportdb --> insertdb ) VM1: TSM 5.5.7 on Windows and VM2: TSM 7.1.7 on Windows VM1: restore backup from productive System. install UpgradeTool VM2: migrate on VM2 with dsmupgdx from VM1 then I had TSM 7.1.7 running. Did a exportdb on TSM 7.1.7 on Windows If "insertdb" on Linux TSM Server 7.1.7 got this error: /opt/tivoli/tsm/server/bin/dsmserv insertdb manifest=/import/manifest.txt IBM Tivoli Storage Manager for Linux/x86_64 Version 7, Release 1, Level 7.100 ... "ANR1953E INSERTDB: Linux/x86_64 cannot be the target of a database upgrade from Windows." 2nd I tryed: ( local migrate ) Install TSM Server 5.5.7 on Linux ( SLES 12 SP2 ) + TSM Client 5.5.4.0 restore backup from productive System. Install UpgradeTool Upgrade to TSM 7.1.3 an run "dsmupgdx" for migrate local Server (Network Method). Then TSM Server 7.1.3 is running with Data from TSM Server 5.5.x Windows Then Update to 7.1.7.300 this works... but IBM support say by phonecall - " .. this is not supported " :-( Any proposals for a supported way ? Thanks Dennis For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286
Migrate from TSM Server 5.5.7 on Windows to TSM Server 7.1.7 on Linux - the unsupported way because exportdb --> insertdb did not work
Hello, how to migrate from TSM Server 5.5.x on Windows to TSM Server 7.1.7 on Linux ( only one tape library ) ? because my way ( see 2nd ) is not supported 1st I tryed: ( exportdb --> insertdb ) VM1: TSM 5.5.7 on Windows and VM2: TSM 7.1.7 on Windows VM1: restore backup from productive System. install UpgradeTool VM2: migrate on VM2 with dsmupgdx from VM1 then I had TSM 7.1.7 running. Did a exportdb on TSM 7.1.7 on Windows If "insertdb" on Linux TSM Server 7.1.7 got this error: /opt/tivoli/tsm/server/bin/dsmserv insertdb manifest=/import/manifest.txt IBM Tivoli Storage Manager for Linux/x86_64 Version 7, Release 1, Level 7.100 ... "ANR1953E INSERTDB: Linux/x86_64 cannot be the target of a database upgrade from Windows." 2nd I tryed: ( local migrate ) Install TSM Server 5.5.7 on Linux ( SLES 12 SP2 ) + TSM Client 5.5.4.0 restore backup from productive System. Install UpgradeTool Upgrade to TSM 7.1.3 an run "dsmupgdx" for migrate local Server (Network Method). Then TSM Server 7.1.3 is running with Data from TSM Server 5.5.x Windows Then Update to 7.1.7.300 this works... but IBM support say by phonecall - " .. this is not supported " :-( Any proposals for a supported way ? Thanks Dennis
Re: Upgrading Linux server from 7.1.7.300 to 8.1.1 - fail
I have gone the uninstall/reinstall route. I was concerned it would mess up the installation even more than it already has. I will wait for 8.1.2 before upgrading any additional server. At this point, 7.1.7.300 should resolve most of the issues I am seeing at 7.1.6.300. Thanks for the help. On Wed, Jul 26, 2017 at 8:23 AM, Giacomo Testa wrote: > Hi, > > > > Also this document says that the Release Date of Spectrum Protect > 8.1.1.000 was 24 Mar 2017: > > http://www-01.ibm.com/support/docview.wss?uid=swg24043483 > > > > Could it maybe be that the date 06/30/2017 on the > SP_8.1.1_LIN86_SER-STG_ML.bin file that you have, is the date on which it > was packaged or downloaded? > > > > This is the release order, based on the wiki page: > > https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/ > Tivoli+Storage+Manager/page/TSM+Schedule+for+Fix-Packs > > > > 8.1.0 December 9, 2016 > > 7.1.7.100 February 9, 2017 > > 8.1.1 March 24, 2017 > > 7.1.7.200 May 5, 2017 > > 7.1.7.300 June 20, 2017 > > > > 7.1.7.100 was released before 8.1.1, so that's why this particular upgrade > should work. > > > > Giacomo Testa > > > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of > Zoltan Forray > Sent: Wednesday, July 26, 2017 13:53 > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] Upgrading Linux server from 7.1.7.300 to 8.1.1 - fail > > > > Thank you for the response and links. The symptoms sound exactly like > what I am seeing but the dates don't correlate . The 7.1.7.300 package I > upgraded the server to (from 7.1.7.000) is dated 06/20/2017 while the > SP_8.1.1_LIN86_SER-STG_ML.bin file I am using to install 8.1.1 is dated > > 06/30/2017 - unless the dates have to be much later than 06/30/2017 (*For > example, the following upgrade procedures can fail: - 3: Upgrade from > patch release 7.1.7.200 to V8.1.1*). > > > > I am re-downloading the 8.1.1 install package to see if it makes a > difference, since the docs say "*If 7.1.7.100 is installed, you can obtain > a V8.1.1 installation package from Passport Advantage and directly upgrade > the server to V8.1.1 without uninstalling 7.1.7.100"* > > > > If not, I will go the uninstall route. Again, thanks. > > > > On Wed, Jul 26, 2017 at 6:00 AM, Giacomo Testa < giacomo.te...@gmail.com> giacomo.te...@gmail.com> > > wrote: > > > > > Hi, > > > > > > There seems to be a problem upgrading a Spectrum Protect server from > > > 7.1.7.x to 8.1.x, if 8.1.x was released earlier than 7.1.7.x. > > > > > > <http://www-01.ibm.com/support/docview.wss?uid=swg1IT20210> > http://www-01.ibm.com/support/docview.wss?uid=swg1IT20210 > > > <http://www-01.ibm.com/support/docview.wss?uid=swg22002297> > http://www-01.ibm.com/support/docview.wss?uid=swg22002297 > > > > > > Delivery (Release) Dates: > > > <https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki> > https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki > > > / > > > Tivoli+Storage+Manager/page/TSM+Schedule+for+Fix-Packs > > > > > > > > > Giacomo Testa > > > > > > -Original Message- > > > From: ADSM: Dist Stor Manager [ <mailto:ADSM-L@VM.MARIST.EDU> mailto: > ADSM-L@VM.MARIST.EDU] On Behalf > > > Of Zoltan Forray > > > Sent: Tuesday, July 25, 2017 20:11 > > > To: <mailto:ADSM-L@VM.MARIST.EDU> ADSM-L@VM.MARIST.EDU > > > Subject: [ADSM-L] Upgrading Linux server from 7.1.7.300 to 8.1.1 - > > > fail > > > > > > Is there any reason I can't upgrade from 7.1.7.x to 8.1.1 using the > > > Passport download package? Do I have to go to 8.1.0 first? > > > > > > I am working on a test server - RHEL7. It was 7.1.7.000 - installed > > > 7.1.7.300 - no problem. > > > > > > Extracted the 8.1.1 package from Passport so it includes the license > > > file but installing it as an "Update" fails trying to uninstall DB2, I > think. > > > Been Googling anything on install/upgrade and there isn't anything > > > special for me to do as far as I know/can find, other than *./install.sh > -c*. > > > Don't have any issues with disk space or ulimits. The ever popular "if > > > you have a failure - check these logs and fix the problem" is pretty > useless. > > > This is all I can find: > > > > > > ERROR: The deinstallation process cannot continue while
Re: Upgrading Linux server from 7.1.7.300 to 8.1.1 - fail
It is the download date. When I check Passport, it says the release date is "07 April 2017". If this still won't work, I will go the uninstall route, especially since at this point TSM wont run since it says TSM isn't installed. That means that the doc saying I can just go to Passport and redownload a more-current version (until 8.1.2 comes out), is pretty useless. On Wed, Jul 26, 2017 at 8:23 AM, Giacomo Testa wrote: > Hi, > > > > Also this document says that the Release Date of Spectrum Protect > 8.1.1.000 was 24 Mar 2017: > > http://www-01.ibm.com/support/docview.wss?uid=swg24043483 > > > > Could it maybe be that the date 06/30/2017 on the > SP_8.1.1_LIN86_SER-STG_ML.bin file that you have, is the date on which it > was packaged or downloaded? > > > > This is the release order, based on the wiki page: > > https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/ > Tivoli+Storage+Manager/page/TSM+Schedule+for+Fix-Packs > > > > 8.1.0 December 9, 2016 > > 7.1.7.100 February 9, 2017 > > 8.1.1 March 24, 2017 > > 7.1.7.200 May 5, 2017 > > 7.1.7.300 June 20, 2017 > > > > 7.1.7.100 was released before 8.1.1, so that's why this particular upgrade > should work. > > > > Giacomo Testa > > > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of > Zoltan Forray > Sent: Wednesday, July 26, 2017 13:53 > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] Upgrading Linux server from 7.1.7.300 to 8.1.1 - fail > > > > Thank you for the response and links. The symptoms sound exactly like > what I am seeing but the dates don't correlate . The 7.1.7.300 package I > upgraded the server to (from 7.1.7.000) is dated 06/20/2017 while the > SP_8.1.1_LIN86_SER-STG_ML.bin file I am using to install 8.1.1 is dated > > 06/30/2017 - unless the dates have to be much later than 06/30/2017 (*For > example, the following upgrade procedures can fail: - 3: Upgrade from > patch release 7.1.7.200 to V8.1.1*). > > > > I am re-downloading the 8.1.1 install package to see if it makes a > difference, since the docs say "*If 7.1.7.100 is installed, you can obtain > a V8.1.1 installation package from Passport Advantage and directly upgrade > the server to V8.1.1 without uninstalling 7.1.7.100"* > > > > If not, I will go the uninstall route. Again, thanks. > > > > On Wed, Jul 26, 2017 at 6:00 AM, Giacomo Testa < giacomo.te...@gmail.com> giacomo.te...@gmail.com> > > wrote: > > > > > Hi, > > > > > > There seems to be a problem upgrading a Spectrum Protect server from > > > 7.1.7.x to 8.1.x, if 8.1.x was released earlier than 7.1.7.x. > > > > > > <http://www-01.ibm.com/support/docview.wss?uid=swg1IT20210> > http://www-01.ibm.com/support/docview.wss?uid=swg1IT20210 > > > <http://www-01.ibm.com/support/docview.wss?uid=swg22002297> > http://www-01.ibm.com/support/docview.wss?uid=swg22002297 > > > > > > Delivery (Release) Dates: > > > <https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki> > https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki > > > / > > > Tivoli+Storage+Manager/page/TSM+Schedule+for+Fix-Packs > > > > > > > > > Giacomo Testa > > > > > > -Original Message- > > > From: ADSM: Dist Stor Manager [ <mailto:ADSM-L@VM.MARIST.EDU> mailto: > ADSM-L@VM.MARIST.EDU] On Behalf > > > Of Zoltan Forray > > > Sent: Tuesday, July 25, 2017 20:11 > > > To: <mailto:ADSM-L@VM.MARIST.EDU> ADSM-L@VM.MARIST.EDU > > > Subject: [ADSM-L] Upgrading Linux server from 7.1.7.300 to 8.1.1 - > > > fail > > > > > > Is there any reason I can't upgrade from 7.1.7.x to 8.1.1 using the > > > Passport download package? Do I have to go to 8.1.0 first? > > > > > > I am working on a test server - RHEL7. It was 7.1.7.000 - installed > > > 7.1.7.300 - no problem. > > > > > > Extracted the 8.1.1 package from Passport so it includes the license > > > file but installing it as an "Update" fails trying to uninstall DB2, I > think. > > > Been Googling anything on install/upgrade and there isn't anything > > > special for me to do as far as I know/can find, other than *./install.sh > -c*. > > > Don't have any issues with disk space or ulimits. The ever popular "if > > > you have a failure - check these logs and fix the problem" is pretty > useless. > > > This is all I c
Re: Upgrading Linux server from 7.1.7.300 to 8.1.1 - fail
Hi, Also this document says that the Release Date of Spectrum Protect 8.1.1.000 was 24 Mar 2017: http://www-01.ibm.com/support/docview.wss?uid=swg24043483 Could it maybe be that the date 06/30/2017 on the SP_8.1.1_LIN86_SER-STG_ML.bin file that you have, is the date on which it was packaged or downloaded? This is the release order, based on the wiki page: https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli+Storage+Manager/page/TSM+Schedule+for+Fix-Packs 8.1.0 December 9, 2016 7.1.7.100 February 9, 2017 8.1.1 March 24, 2017 7.1.7.200 May 5, 2017 7.1.7.300 June 20, 2017 7.1.7.100 was released before 8.1.1, so that's why this particular upgrade should work. Giacomo Testa -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan Forray Sent: Wednesday, July 26, 2017 13:53 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Upgrading Linux server from 7.1.7.300 to 8.1.1 - fail Thank you for the response and links. The symptoms sound exactly like what I am seeing but the dates don't correlate . The 7.1.7.300 package I upgraded the server to (from 7.1.7.000) is dated 06/20/2017 while the SP_8.1.1_LIN86_SER-STG_ML.bin file I am using to install 8.1.1 is dated 06/30/2017 - unless the dates have to be much later than 06/30/2017 (*For example, the following upgrade procedures can fail: - 3: Upgrade from patch release 7.1.7.200 to V8.1.1*). I am re-downloading the 8.1.1 install package to see if it makes a difference, since the docs say "*If 7.1.7.100 is installed, you can obtain a V8.1.1 installation package from Passport Advantage and directly upgrade the server to V8.1.1 without uninstalling 7.1.7.100"* If not, I will go the uninstall route. Again, thanks. On Wed, Jul 26, 2017 at 6:00 AM, Giacomo Testa < <mailto:giacomo.te...@gmail.com> giacomo.te...@gmail.com> wrote: > Hi, > > There seems to be a problem upgrading a Spectrum Protect server from > 7.1.7.x to 8.1.x, if 8.1.x was released earlier than 7.1.7.x. > > <http://www-01.ibm.com/support/docview.wss?uid=swg1IT20210> > http://www-01.ibm.com/support/docview.wss?uid=swg1IT20210 > <http://www-01.ibm.com/support/docview.wss?uid=swg22002297> > http://www-01.ibm.com/support/docview.wss?uid=swg22002297 > > Delivery (Release) Dates: > <https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki> > https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki > / > Tivoli+Storage+Manager/page/TSM+Schedule+for+Fix-Packs > > > Giacomo Testa > > -Original Message- > From: ADSM: Dist Stor Manager [ <mailto:ADSM-L@VM.MARIST.EDU> > mailto:ADSM-L@VM.MARIST.EDU] On Behalf > Of Zoltan Forray > Sent: Tuesday, July 25, 2017 20:11 > To: <mailto:ADSM-L@VM.MARIST.EDU> ADSM-L@VM.MARIST.EDU > Subject: [ADSM-L] Upgrading Linux server from 7.1.7.300 to 8.1.1 - > fail > > Is there any reason I can't upgrade from 7.1.7.x to 8.1.1 using the > Passport download package? Do I have to go to 8.1.0 first? > > I am working on a test server - RHEL7. It was 7.1.7.000 - installed > 7.1.7.300 - no problem. > > Extracted the 8.1.1 package from Passport so it includes the license > file but installing it as an "Update" fails trying to uninstall DB2, I think. > Been Googling anything on install/upgrade and there isn't anything > special for me to do as far as I know/can find, other than *./install.sh -c*. > Don't have any issues with disk space or ulimits. The ever popular "if > you have a failure - check these logs and fix the problem" is pretty useless. > This is all I can find: > > ERROR: The deinstallation process cannot continue while there are DB2 > instances related to the current DB2 copy. If you need to move up or > down a level from this DB2 level, use the installFixPack command from > the DB2 image for the level you desire to move to, which will update > this copy. If you are only trying to uninstall this DB2 copy, you must > either drop the related instance(s) "tsminst1" first, or you can > update the instances to another DB2 copy which is at the same version > as this DB2 copy, then restart the db2_deinstall command. > > Preparing the system :...Failure > > > -- > *Zoltan Forray* > Spectrum Protect (p.k.a. TSM) Software & Hardware Administrator Xymon > Monitor Administrator VMware Administrator Virginia Commonwealth > University UCC/Office of Technology Services <http://www.ucc.vcu.edu> > www.ucc.vcu.edu > <mailto:zfor...@vcu.edu> zfor...@vcu.edu - > 804-828-4807 Don't be a phishing victim - VCU and other reputa
Re: Upgrading Linux server from 7.1.7.300 to 8.1.1 - fail
Thank you for the response and links. The symptoms sound exactly like what I am seeing but the dates don't correlate . The 7.1.7.300 package I upgraded the server to (from 7.1.7.000) is dated 06/20/2017 while the SP_8.1.1_LIN86_SER-STG_ML.bin file I am using to install 8.1.1 is dated 06/30/2017 - unless the dates have to be much later than 06/30/2017 (*For example, the following upgrade procedures can fail: - 3: Upgrade from patch release 7.1.7.200 to V8.1.1*). I am re-downloading the 8.1.1 install package to see if it makes a difference, since the docs say "*If 7.1.7.100 is installed, you can obtain a V8.1.1 installation package from Passport Advantage and directly upgrade the server to V8.1.1 without uninstalling 7.1.7.100"* If not, I will go the uninstall route. Again, thanks. On Wed, Jul 26, 2017 at 6:00 AM, Giacomo Testa wrote: > Hi, > > There seems to be a problem upgrading a Spectrum Protect server from > 7.1.7.x to 8.1.x, if 8.1.x was released earlier than 7.1.7.x. > > http://www-01.ibm.com/support/docview.wss?uid=swg1IT20210 > http://www-01.ibm.com/support/docview.wss?uid=swg22002297 > > Delivery (Release) Dates: > https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/ > Tivoli+Storage+Manager/page/TSM+Schedule+for+Fix-Packs > > > Giacomo Testa > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of > Zoltan Forray > Sent: Tuesday, July 25, 2017 20:11 > To: ADSM-L@VM.MARIST.EDU > Subject: [ADSM-L] Upgrading Linux server from 7.1.7.300 to 8.1.1 - fail > > Is there any reason I can't upgrade from 7.1.7.x to 8.1.1 using the > Passport download package? Do I have to go to 8.1.0 first? > > I am working on a test server - RHEL7. It was 7.1.7.000 - installed > 7.1.7.300 - no problem. > > Extracted the 8.1.1 package from Passport so it includes the license file > but installing it as an "Update" fails trying to uninstall DB2, I think. > Been Googling anything on install/upgrade and there isn't anything special > for me to do as far as I know/can find, other than *./install.sh -c*. > Don't have any issues with disk space or ulimits. The ever popular "if you > have a failure - check these logs and fix the problem" is pretty useless. > This is all I can find: > > ERROR: The deinstallation process cannot continue while there are DB2 > instances related to the current DB2 copy. If you need to move up or down a > level from this DB2 level, use the installFixPack command from the DB2 > image for the level you desire to move to, which will update this copy. If > you are only trying to uninstall this DB2 copy, you must either drop the > related instance(s) "tsminst1" first, or you can update the instances to > another DB2 copy which is at the same version as this DB2 copy, then > restart the db2_deinstall command. > > Preparing the system :...Failure > > > -- > *Zoltan Forray* > Spectrum Protect (p.k.a. TSM) Software & Hardware Administrator Xymon > Monitor Administrator VMware Administrator Virginia Commonwealth University > UCC/Office of Technology Services www.ucc.vcu.edu zfor...@vcu.edu - > 804-828-4807 Don't be a phishing victim - VCU and other reputable > organizations will never use email to request that you reply with your > password, social security number or confidential personal information. For > more details visit http://infosecurity.vcu.edu/phishing.html > -- *Zoltan Forray* Spectrum Protect (p.k.a. TSM) Software & Hardware Administrator Xymon Monitor Administrator VMware Administrator Virginia Commonwealth University UCC/Office of Technology Services www.ucc.vcu.edu zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html
Re: Upgrading Linux server from 7.1.7.300 to 8.1.1 - fail
Hi, There seems to be a problem upgrading a Spectrum Protect server from 7.1.7.x to 8.1.x, if 8.1.x was released earlier than 7.1.7.x. http://www-01.ibm.com/support/docview.wss?uid=swg1IT20210 http://www-01.ibm.com/support/docview.wss?uid=swg22002297 Delivery (Release) Dates: https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli+Storage+Manager/page/TSM+Schedule+for+Fix-Packs Giacomo Testa -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan Forray Sent: Tuesday, July 25, 2017 20:11 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Upgrading Linux server from 7.1.7.300 to 8.1.1 - fail Is there any reason I can't upgrade from 7.1.7.x to 8.1.1 using the Passport download package? Do I have to go to 8.1.0 first? I am working on a test server - RHEL7. It was 7.1.7.000 - installed 7.1.7.300 - no problem. Extracted the 8.1.1 package from Passport so it includes the license file but installing it as an "Update" fails trying to uninstall DB2, I think. Been Googling anything on install/upgrade and there isn't anything special for me to do as far as I know/can find, other than *./install.sh -c*. Don't have any issues with disk space or ulimits. The ever popular "if you have a failure - check these logs and fix the problem" is pretty useless. This is all I can find: ERROR: The deinstallation process cannot continue while there are DB2 instances related to the current DB2 copy. If you need to move up or down a level from this DB2 level, use the installFixPack command from the DB2 image for the level you desire to move to, which will update this copy. If you are only trying to uninstall this DB2 copy, you must either drop the related instance(s) "tsminst1" first, or you can update the instances to another DB2 copy which is at the same version as this DB2 copy, then restart the db2_deinstall command. Preparing the system :...Failure -- *Zoltan Forray* Spectrum Protect (p.k.a. TSM) Software & Hardware Administrator Xymon Monitor Administrator VMware Administrator Virginia Commonwealth University UCC/Office of Technology Services www.ucc.vcu.edu zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html
Upgrading Linux server from 7.1.7.300 to 8.1.1 - fail
Is there any reason I can't upgrade from 7.1.7.x to 8.1.1 using the Passport download package? Do I have to go to 8.1.0 first? I am working on a test server - RHEL7. It was 7.1.7.000 - installed 7.1.7.300 - no problem. Extracted the 8.1.1 package from Passport so it includes the license file but installing it as an "Update" fails trying to uninstall DB2, I think. Been Googling anything on install/upgrade and there isn't anything special for me to do as far as I know/can find, other than *./install.sh -c*. Don't have any issues with disk space or ulimits. The ever popular "if you have a failure - check these logs and fix the problem" is pretty useless. This is all I can find: ERROR: The deinstallation process cannot continue while there are DB2 instances related to the current DB2 copy. If you need to move up or down a level from this DB2 level, use the installFixPack command from the DB2 image for the level you desire to move to, which will update this copy. If you are only trying to uninstall this DB2 copy, you must either drop the related instance(s) "tsminst1" first, or you can update the instances to another DB2 copy which is at the same version as this DB2 copy, then restart the db2_deinstall command. Preparing the system :...Failure -- *Zoltan Forray* Spectrum Protect (p.k.a. TSM) Software & Hardware Administrator Xymon Monitor Administrator VMware Administrator Virginia Commonwealth University UCC/Office of Technology Services www.ucc.vcu.edu zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html
Re: Linux on Power Support - Available now
Hi Steve, I ***think*** you are asking me if a future version of the Spectrum Protect pLinux LE server will support tape, VTLs and LANfree... then yes, that's the plan. I am not entirely sure what you mean when you mention vBS, TDP/VE, and Intel. The statements above are about a Spectrum Protect server, not about any of the client components. Del "ADSM: Dist Stor Manager" wrote on 06/01/2017 07:38:41 PM: > From: "Harris, Steven" > To: ADSM-L@VM.MARIST.EDU > Date: 06/01/2017 07:40 PM > Subject: Re: Linux on Power Support - Available now > Sent by: "ADSM: Dist Stor Manager" > > Thanks for that Del. > > I realize you can't pre-announce anything here, but a Power-linux LE > vBS server to handle TDP for VE would be awesome and avoid many of > the architectural limitations of Intel boxes. In my case that would > imply TS3500 driver support and Lan free as well. > > Can we assume that's in the pipeline? > > Cheers > > Steve. > > Steven Harris > TSM Admin/Consultant > Canberra Australia. > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On > Behalf Of Del Hoobler > Sent: Friday, 2 June 2017 3:31 AM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] Linux on Power Support - Available now > > IBM Spectrum Protect 8.1 now supports the Linux on Power -Llittle Endian > > Details here: > > https://www.ibm.com/developerworks/community/blogs/ > 869bac74-5fc2-4b94-81a2-6153890e029a/entry/ > Feel_the_power_IBM_Spectrum_Protect_now_supports_the_Linux_on_Power_Systems_little_endian_operating_system? > lang=en > > > > Del > > > > - Forwarded by Del Hoobler/Endicott/IBM on 06/01/2017 01:27 PM - > > Del Hoobler/Endicott/IBM wrote on 04/24/2017 02:47:21 PM: > > > From: Del Hoobler/Endicott/IBM > > To: "ADSM: Dist Stor Manager" > > Date: 04/24/2017 02:47 PM > > Subject: Re: Linux on Power Support > > > > Hi Jonathan, > > > > Spectrum Protect 8.1 server dropped Linux on Power - Big Endian (you > > can still get it for Spectrum Protect 7.1 server). > > > > Spectrum Protect 8.1 is adding support for Linux on Power - Little > > Endian. It is targeted to be released for RHEL within the next few > months. > > > > > > Del > > > > > > > "ADSM: Dist Stor Manager" wrote on 04/24/2017 > > 02:38:28 PM: > > > > > From: Jonathan Dresang > > > To: ADSM-L@VM.MARIST.EDU > > > Date: 04/24/2017 02:39 PM > > > Subject: Linux on Power Support > > > Sent by: "ADSM: Dist Stor Manager" > > > > > > Hello all, > > > > > > Does IBM no longer support running TSM/Spectrum Protect on Linux > systems > > > running on Power with 8.1? I went to Passport Advantage and > > > couldn't > find > > > it there, but found 7.1.7 downloads for the server code for Linux on > > > Power? > > > > > > Thanks, > > > > > > > > > Jonathan Dresang > > > Madison Gas & Electric > > > 608-252-7296 > > > > > This message and any attachment is confidential and may be > privileged or otherwise protected from disclosure. You should > immediately delete the message if you are not the intended > recipient. If you have received this email by mistake please delete > it from your system; you should not copy the message or disclose its > content to anyone. > > This electronic communication may contain general financial product > advice but should not be relied upon or construed as a > recommendation of any financial product. The information has been > prepared without taking into account your objectives, financial > situation or needs. You should consider the Product Disclosure > Statement relating to the financial product and consult your > financial adviser before making a decision about whether to acquire, > hold or dispose of a financial product. > > For further details on the financial product please go to http://www.bt.com.au > > Past performance is not a reliable indicator of future performance. >
Re: Linux on Power Support - Available now
Thanks for that Del. I realize you can't pre-announce anything here, but a Power-linux LE vBS server to handle TDP for VE would be awesome and avoid many of the architectural limitations of Intel boxes. In my case that would imply TS3500 driver support and Lan free as well. Can we assume that's in the pipeline? Cheers Steve. Steven Harris TSM Admin/Consultant Canberra Australia. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Del Hoobler Sent: Friday, 2 June 2017 3:31 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Linux on Power Support - Available now IBM Spectrum Protect 8.1 now supports the Linux on Power -Llittle Endian Details here: https://www.ibm.com/developerworks/community/blogs/869bac74-5fc2-4b94-81a2-6153890e029a/entry/Feel_the_power_IBM_Spectrum_Protect_now_supports_the_Linux_on_Power_Systems_little_endian_operating_system?lang=en Del - Forwarded by Del Hoobler/Endicott/IBM on 06/01/2017 01:27 PM - Del Hoobler/Endicott/IBM wrote on 04/24/2017 02:47:21 PM: > From: Del Hoobler/Endicott/IBM > To: "ADSM: Dist Stor Manager" > Date: 04/24/2017 02:47 PM > Subject: Re: Linux on Power Support > > Hi Jonathan, > > Spectrum Protect 8.1 server dropped Linux on Power - Big Endian (you > can still get it for Spectrum Protect 7.1 server). > > Spectrum Protect 8.1 is adding support for Linux on Power - Little > Endian. It is targeted to be released for RHEL within the next few months. > > > Del > > > "ADSM: Dist Stor Manager" wrote on 04/24/2017 > 02:38:28 PM: > > > From: Jonathan Dresang > > To: ADSM-L@VM.MARIST.EDU > > Date: 04/24/2017 02:39 PM > > Subject: Linux on Power Support > > Sent by: "ADSM: Dist Stor Manager" > > > > Hello all, > > > > Does IBM no longer support running TSM/Spectrum Protect on Linux systems > > running on Power with 8.1? I went to Passport Advantage and > > couldn't find > > it there, but found 7.1.7 downloads for the server code for Linux on > > Power? > > > > Thanks, > > > > > > Jonathan Dresang > > Madison Gas & Electric > > 608-252-7296 > > This message and any attachment is confidential and may be privileged or otherwise protected from disclosure. You should immediately delete the message if you are not the intended recipient. If you have received this email by mistake please delete it from your system; you should not copy the message or disclose its content to anyone. This electronic communication may contain general financial product advice but should not be relied upon or construed as a recommendation of any financial product. The information has been prepared without taking into account your objectives, financial situation or needs. You should consider the Product Disclosure Statement relating to the financial product and consult your financial adviser before making a decision about whether to acquire, hold or dispose of a financial product. For further details on the financial product please go to http://www.bt.com.au Past performance is not a reliable indicator of future performance.
Re: Linux on Power Support - Available now
IBM Spectrum Protect 8.1 now supports the Linux on Power -Llittle Endian Details here: https://www.ibm.com/developerworks/community/blogs/869bac74-5fc2-4b94-81a2-6153890e029a/entry/Feel_the_power_IBM_Spectrum_Protect_now_supports_the_Linux_on_Power_Systems_little_endian_operating_system?lang=en Del - Forwarded by Del Hoobler/Endicott/IBM on 06/01/2017 01:27 PM - Del Hoobler/Endicott/IBM wrote on 04/24/2017 02:47:21 PM: > From: Del Hoobler/Endicott/IBM > To: "ADSM: Dist Stor Manager" > Date: 04/24/2017 02:47 PM > Subject: Re: Linux on Power Support > > Hi Jonathan, > > Spectrum Protect 8.1 server dropped Linux on Power - Big Endian (you > can still get it for Spectrum Protect 7.1 server). > > Spectrum Protect 8.1 is adding support for Linux on Power - Little > Endian. It is targeted to be released for RHEL within the next few months. > > > Del > > > "ADSM: Dist Stor Manager" wrote on 04/24/2017 > 02:38:28 PM: > > > From: Jonathan Dresang > > To: ADSM-L@VM.MARIST.EDU > > Date: 04/24/2017 02:39 PM > > Subject: Linux on Power Support > > Sent by: "ADSM: Dist Stor Manager" > > > > Hello all, > > > > Does IBM no longer support running TSM/Spectrum Protect on Linux systems > > running on Power with 8.1? I went to Passport Advantage and couldn't find > > it there, but found 7.1.7 downloads for the server code for Linux on > > Power? > > > > Thanks, > > > > > > Jonathan Dresang > > Madison Gas & Electric > > 608-252-7296 > >
Re: Linux on Power Support
Hi Jonathan, Spectrum Protect 8.1 server dropped Linux on Power - Big Endian (you can still get it for Spectrum Protect 7.1 server). Spectrum Protect 8.1 is adding support for Linux on Power - Little Endian. It is targeted to be released for RHEL within the next few months. Del "ADSM: Dist Stor Manager" wrote on 04/24/2017 02:38:28 PM: > From: Jonathan Dresang > To: ADSM-L@VM.MARIST.EDU > Date: 04/24/2017 02:39 PM > Subject: Linux on Power Support > Sent by: "ADSM: Dist Stor Manager" > > Hello all, > > Does IBM no longer support running TSM/Spectrum Protect on Linux systems > running on Power with 8.1? I went to Passport Advantage and couldn't find > it there, but found 7.1.7 downloads for the server code for Linux on > Power? > > Thanks, > > > Jonathan Dresang > Madison Gas & Electric > 608-252-7296 >
Linux on Power Support
Hello all, Does IBM no longer support running TSM/Spectrum Protect on Linux systems running on Power with 8.1? I went to Passport Advantage and couldn't find it there, but found 7.1.7 downloads for the server code for Linux on Power? Thanks, Jonathan Dresang Madison Gas & Electric 608-252-7296
Protectier Tuning/ Linux tape Tuning
Hi all My customer is running a TSM for VE backup solution involving Linux x86_64 as the vBS with storage agent installed, writing direct to Protectier VTL. Throughput to the VTL is needs improvement both at a whole of VTL level and at the individual tape session level, to handle the workload. I've trawled through searches but can find nothing on either Protectier tuning or on Linux tape (e.g changing SCSI block size, number of buffers, size of buffers) If anyone aware of such resources could you please post a link to them? Thanks Steve Steven Harris TSM Admin/Consultant Canberra Australia This message and any attachment is confidential and may be privileged or otherwise protected from disclosure. You should immediately delete the message if you are not the intended recipient. If you have received this email by mistake please delete it from your system; you should not copy the message or disclose its content to anyone. This electronic communication may contain general financial product advice but should not be relied upon or construed as a recommendation of any financial product. The information has been prepared without taking into account your objectives, financial situation or needs. You should consider the Product Disclosure Statement relating to the financial product and consult your financial adviser before making a decision about whether to acquire, hold or dispose of a financial product. For further details on the financial product please go to http://www.bt.com.au Past performance is not a reliable indicator of future performance.
Re: TSM Server on CentOS Linux
Hello "both" :) It was the compat lib the problem. tks to send me the log location. Now the server is UP and importing some production data form v6 (en old V5) TSM Servers. Thanks and good weekend. Grazie Maurizio Il 15.02.2017 09:30, Sasa Drnjevic ha scritto: On 14.2.2017. 16:52, .Maurizio TERUZZI wrote: Hello Sasa, I still have the same error. I put the Kernal parameters in sysctl.conf file directly. Hi Maurizio. It wasn't me sending you the quick and dirty howto :-) It was from dennis.schn...@schulergroup.com I have only sent you a hint for the /etc/hosts file OK, some other hints follow...Did you disable SELinux? Hints: - To determine if SELinux is installed and in enforcing mode, perform one of the following tasks: Check the /etc/sysconfig/selinux file. Run the "sestatus" operating system command. Check the /var/log/messages file for SELinux notices. To disable SELinux, complete one of the following tasks: Set permissive mode by issuing the "setenforce 0" command as a superuser. Modify the /etc/sysconfig/selinux file and reboot the machine. - And also examine the cfg wizard logs here... # ls -la /var/tivoli/tsm/ drwxrwxr-x 2 root root4096 Dec 21 2015 . drwxrwxr-x 3 root root4096 Dec 21 2015 .. -rw-rw-r-- 1 root root 69564 Dec 21 2015 dsmicfgx.trc -rw-rw-r-- 1 root root 578 Dec 21 2015 rxa_message.log -rw-rw-r-- 1 root root 1704037 Dec 21 2015 rxa_trace.log Regards, -- Sasa Drnjevic www.srce.unizg.hr All required packages are installed, I re-run you commands to be sure. Here the host content: cat /etc/hosts 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 10.16.23.101 tsmtest tsmtest1.bluewin.lan User&Grp grep -i tsm /etc/group tsmsrv:x:1001: id tsminst1 uid=1001(tsminst1) gid=1001(tsmsrv) groups=1001(tsmsrv) TSM Directory structure: ls -lRa /tsm /tsm: total 0 drwxr-xr-x. 1 tsminst1 tsmsrv 36 Jan 31 14:26 . dr-xr-xr-x. 1 root root 200 Feb 14 11:42 .. drwxr-xr-x. 1 tsminst1 tsmsrv 0 Jan 28 19:50 archlog drwxr-xr-x. 1 tsminst1 tsmsrv 184 Feb 3 14:51 bin drwxr-xr-x. 1 tsminst1 tsmsrv 0 Jan 28 19:50 db drwxr-xr-x. 1 tsminst1 tsmsrv 0 Jan 28 19:50 log drwxr-xr-x. 1 tsminst1 tsmsrv 0 Jan 28 19:50 stg /tsm/archlog: total 0 drwxr-xr-x. 1 tsminst1 tsmsrv 0 Jan 28 19:50 . drwxr-xr-x. 1 tsminst1 tsmsrv 36 Jan 31 14:26 .. /tsm/bin: total 5239532 drwxr-xr-x. 1 tsminst1 tsmsrv184 Feb 3 14:51 . drwxr-xr-x. 1 tsminst1 tsmsrv 36 Jan 31 14:26 .. drwxr-xr-x. 1 tsminst1 tsmsrv104 Feb 3 14:37 .input -rwxrwxr-x. 1 tsminst1 tsmsrv 2664623713 Jan 31 01:16 SP_8.1_LIN86_SER_STG_ML.bin /tsm/bin/.input: total 16 drwxr-xr-x. 1 tsminst1 tsmsrv 104 Feb 3 14:37 . drwxr-xr-x. 1 tsminst1 tsmsrv 184 Feb 3 14:51 .. -rw-r--r-- 1 root root 2115 Nov 21 21:34 installnew32.xml -rw-r--r-- 1 root root 2115 Nov 21 21:34 installnew64.xml -rw-r--r-- 1 root root 5646 Nov 21 21:34 install_response.xml /tsm/db: total 0 drwxr-xr-x. 1 tsminst1 tsmsrv 0 Jan 28 19:50 . drwxr-xr-x. 1 tsminst1 tsmsrv 36 Jan 31 14:26 .. /tsm/log: total 0 drwxr-xr-x. 1 tsminst1 tsmsrv 0 Jan 28 19:50 . drwxr-xr-x. 1 tsminst1 tsmsrv 36 Jan 31 14:26 .. /tsm/stg: total 0 drwxr-xr-x. 1 tsminst1 tsmsrv 0 Jan 28 19:50 . drwxr-xr-x. 1 tsminst1 tsmsrv 36 Jan 31 14:26 .. (I don't have too much place on disks, I will look for partitions on future production server. I miss the compat library... I didn't see on the documentation but it's the same problem that in V6 (yes, I still in V6.x). Since 1h at preparing the new instance... lets wait. Thank for your the help. Maurizio -- Cordiali saluti / Meilleures salutations Maurizio Teruzzi https://www.linkedin.com/in/teruzzi Join my computation group for social aid. https://join.worldcommunitygrid.org?recruiterId=184105&teamId=K85XNJBR9N1 I- Pensate al impatto ambientale prima di stampare questa email F- Pensez à l'environnement avant d'imprimer cet email E- Please consider your environmental concern before printing this email
Re: TSM Server on CentOS Linux
On 14.2.2017. 16:52, .Maurizio TERUZZI wrote: > Hello Sasa, > > I still have the same error. > > I put the Kernal parameters in sysctl.conf file directly. Hi Maurizio. It wasn't me sending you the quick and dirty howto :-) It was from dennis.schn...@schulergroup.com I have only sent you a hint for the /etc/hosts file OK, some other hints follow...Did you disable SELinux? Hints: - To determine if SELinux is installed and in enforcing mode, perform one of the following tasks: Check the /etc/sysconfig/selinux file. Run the "sestatus" operating system command. Check the /var/log/messages file for SELinux notices. To disable SELinux, complete one of the following tasks: Set permissive mode by issuing the "setenforce 0" command as a superuser. Modify the /etc/sysconfig/selinux file and reboot the machine. - And also examine the cfg wizard logs here... # ls -la /var/tivoli/tsm/ drwxrwxr-x 2 root root4096 Dec 21 2015 . drwxrwxr-x 3 root root4096 Dec 21 2015 .. -rw-rw-r-- 1 root root 69564 Dec 21 2015 dsmicfgx.trc -rw-rw-r-- 1 root root 578 Dec 21 2015 rxa_message.log -rw-rw-r-- 1 root root 1704037 Dec 21 2015 rxa_trace.log Regards, -- Sasa Drnjevic www.srce.unizg.hr > All required packages are installed, I re-run you commands to be sure. > > Here the host content: > cat /etc/hosts > 127.0.0.1 localhost localhost.localdomain localhost4 > localhost4.localdomain4 > ::1 localhost localhost.localdomain localhost6 > localhost6.localdomain6 > 10.16.23.101 tsmtest tsmtest1.bluewin.lan > > User&Grp > grep -i tsm /etc/group > tsmsrv:x:1001: > id tsminst1 > uid=1001(tsminst1) gid=1001(tsmsrv) groups=1001(tsmsrv) > > TSM Directory structure: > ls -lRa /tsm > /tsm: > total 0 > drwxr-xr-x. 1 tsminst1 tsmsrv 36 Jan 31 14:26 . > dr-xr-xr-x. 1 root root 200 Feb 14 11:42 .. > drwxr-xr-x. 1 tsminst1 tsmsrv 0 Jan 28 19:50 archlog > drwxr-xr-x. 1 tsminst1 tsmsrv 184 Feb 3 14:51 bin > drwxr-xr-x. 1 tsminst1 tsmsrv 0 Jan 28 19:50 db > drwxr-xr-x. 1 tsminst1 tsmsrv 0 Jan 28 19:50 log > drwxr-xr-x. 1 tsminst1 tsmsrv 0 Jan 28 19:50 stg > > /tsm/archlog: > total 0 > drwxr-xr-x. 1 tsminst1 tsmsrv 0 Jan 28 19:50 . > drwxr-xr-x. 1 tsminst1 tsmsrv 36 Jan 31 14:26 .. > > /tsm/bin: > total 5239532 > drwxr-xr-x. 1 tsminst1 tsmsrv184 Feb 3 14:51 . > drwxr-xr-x. 1 tsminst1 tsmsrv 36 Jan 31 14:26 .. > drwxr-xr-x. 1 tsminst1 tsmsrv104 Feb 3 14:37 .input > -rwxrwxr-x. 1 tsminst1 tsmsrv 2664623713 Jan 31 01:16 > SP_8.1_LIN86_SER_STG_ML.bin > > /tsm/bin/.input: > total 16 > drwxr-xr-x. 1 tsminst1 tsmsrv 104 Feb 3 14:37 . > drwxr-xr-x. 1 tsminst1 tsmsrv 184 Feb 3 14:51 .. > -rw-r--r-- 1 root root 2115 Nov 21 21:34 installnew32.xml > -rw-r--r-- 1 root root 2115 Nov 21 21:34 installnew64.xml > -rw-r--r-- 1 root root 5646 Nov 21 21:34 install_response.xml > > /tsm/db: > total 0 > drwxr-xr-x. 1 tsminst1 tsmsrv 0 Jan 28 19:50 . > drwxr-xr-x. 1 tsminst1 tsmsrv 36 Jan 31 14:26 .. > > /tsm/log: > total 0 > drwxr-xr-x. 1 tsminst1 tsmsrv 0 Jan 28 19:50 . > drwxr-xr-x. 1 tsminst1 tsmsrv 36 Jan 31 14:26 .. > > /tsm/stg: > total 0 > drwxr-xr-x. 1 tsminst1 tsmsrv 0 Jan 28 19:50 . > drwxr-xr-x. 1 tsminst1 tsmsrv 36 Jan 31 14:26 .. > > > (I don't have too much place on disks, I will look for partitions on > future production server. > > > I miss the compat library... I didn't see on the documentation but it's > the same problem that in V6 (yes, I still in V6.x). > Since 1h at preparing the new instance... lets wait. > > > Thank for your the help. > > Maurizio
Re: TSM Server on CentOS Linux
Hello Sasa, I still have the same error. I put the Kernal parameters in sysctl.conf file directly. All required packages are installed, I re-run you commands to be sure. Here the host content: cat /etc/hosts 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 10.16.23.101 tsmtest tsmtest1.bluewin.lan User&Grp grep -i tsm /etc/group tsmsrv:x:1001: id tsminst1 uid=1001(tsminst1) gid=1001(tsmsrv) groups=1001(tsmsrv) TSM Directory structure: ls -lRa /tsm /tsm: total 0 drwxr-xr-x. 1 tsminst1 tsmsrv 36 Jan 31 14:26 . dr-xr-xr-x. 1 root root 200 Feb 14 11:42 .. drwxr-xr-x. 1 tsminst1 tsmsrv 0 Jan 28 19:50 archlog drwxr-xr-x. 1 tsminst1 tsmsrv 184 Feb 3 14:51 bin drwxr-xr-x. 1 tsminst1 tsmsrv 0 Jan 28 19:50 db drwxr-xr-x. 1 tsminst1 tsmsrv 0 Jan 28 19:50 log drwxr-xr-x. 1 tsminst1 tsmsrv 0 Jan 28 19:50 stg /tsm/archlog: total 0 drwxr-xr-x. 1 tsminst1 tsmsrv 0 Jan 28 19:50 . drwxr-xr-x. 1 tsminst1 tsmsrv 36 Jan 31 14:26 .. /tsm/bin: total 5239532 drwxr-xr-x. 1 tsminst1 tsmsrv184 Feb 3 14:51 . drwxr-xr-x. 1 tsminst1 tsmsrv 36 Jan 31 14:26 .. drwxr-xr-x. 1 tsminst1 tsmsrv104 Feb 3 14:37 .input -rwxrwxr-x. 1 tsminst1 tsmsrv 2664623713 Jan 31 01:16 SP_8.1_LIN86_SER_STG_ML.bin /tsm/bin/.input: total 16 drwxr-xr-x. 1 tsminst1 tsmsrv 104 Feb 3 14:37 . drwxr-xr-x. 1 tsminst1 tsmsrv 184 Feb 3 14:51 .. -rw-r--r-- 1 root root 2115 Nov 21 21:34 installnew32.xml -rw-r--r-- 1 root root 2115 Nov 21 21:34 installnew64.xml -rw-r--r-- 1 root root 5646 Nov 21 21:34 install_response.xml /tsm/db: total 0 drwxr-xr-x. 1 tsminst1 tsmsrv 0 Jan 28 19:50 . drwxr-xr-x. 1 tsminst1 tsmsrv 36 Jan 31 14:26 .. /tsm/log: total 0 drwxr-xr-x. 1 tsminst1 tsmsrv 0 Jan 28 19:50 . drwxr-xr-x. 1 tsminst1 tsmsrv 36 Jan 31 14:26 .. /tsm/stg: total 0 drwxr-xr-x. 1 tsminst1 tsmsrv 0 Jan 28 19:50 . drwxr-xr-x. 1 tsminst1 tsmsrv 36 Jan 31 14:26 .. (I don't have too much place on disks, I will look for partitions on future production server. I miss the compat library... I didn't see on the documentation but it's the same problem that in V6 (yes, I still in V6.x). Since 1h at preparing the new instance... lets wait. Thank for your the help. Maurizio
Re: Availability for Spectrum Protect 8.1 server software for Linux on power system
Hi Rick, The setup will look like following : 2 datacenters, each equipped with one TSM server (Power S824l) and one Isilon cluster made of 5 x NL410 nodes. Connectivity to TSM server will be made thru 2 X 10 gbs connections/node, so altogether 100 gbs. Each TSM server will also be attached to an IBM Flash System 900 array, allowing for around 4 TB database storage. Our goal is to be able to ingest around 35 TB/day/site, against deduplicated directory container pools, in around 8 hours, and to have that data replicated cross-site for each TSM server, to allow for Disaster Recovery purposes. Cheers. Arnaud -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Rick Adamson Sent: Tuesday, February 14, 2017 1:51 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Availability for Spectrum Protect 8.1 server software for Linux on power system Arnaud, Thanks for the feedback, I just received delivery of two Isilons yesterday, one for our production DC and another for DR, hopefully I won't regret it. All of my TSM/ISP servers run on MS Windows 2012 R2 so NFS won't be an issue. For several years we have used Data Domain but it was reaching its end of service. One of my biggest concerns is if it will be able to handle the workload or become a performance bottleneck. I'll post back more info as I get them deployed and up to speed Can you expand on your model, number of nodes and network connectivity ? Thanks again -Rick Adamson -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of PAC Brion Arnaud Sent: Tuesday, February 14, 2017 5:57 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Availability for Spectrum Protect 8.1 server software for Linux on power system Hi Zoltan, Many reasons for it, which I'll try to shortly summarize : 1) Isilon makes use of NFS, whose performance is not that good on AIX systems. We are an AIX shop, and are forced to move to Power Linux machines to get sufficient performance to cover our backup needs. Our first experience with Power Linux machines revealed serious lacks in the functionalities we are accustomed to : no easy HMC setup, thus lack of call home capabilities so far. In addition to this we needed to setup a RedHat satellite server to allow for installation on remote servers, and so far are unable to boot our machines from it ... This will probably work sooner or later, but requires lots of involvement and time from our sys-admins. 2) Isilon is not perfectly fitting in a big TSM environment. In order to get decent performance, a third party tool will be needed, whose name is dsmISI. See following : https://urldefense.proofpoint.com/v2/url?u=http-3A__stefanradtke.blogspot.ch_2015_06_how-2Dto-2Doptimize-2Dtsm-2Doperations-2Dwith.html&d=DwIGaQ&c=AzgFQeXLLKhxSQaoFCm29A&r=uJG3UnPaeoz9naeIzbwWFddVED8ETOYHxjoACoofi2Y&m=IvL1NDqYjCA6eIK2-Dzb4BB_fBbpaVFQ5qhxSny2G4I&s=kpqDyDb694uLBMIK6iSla9-xv73XJeNfOXU4XAwfyCI&e= This means another layer of complexity in the setup, and another vendor to talk to, if facing performance issues. I had more than my lot of "ping-pong" games during my career as TSM administrator, between IBM and other vendors, to reject the responsibility on each other in case of issues. Having 3 parties involved in our setup will make such games even more frequent ... 3) User base for such a combination in Switzerland is inexistent, at least in the same order of size than ours. EMC has not been able to provide any customer reference in this country, with whom we could talk to about their setup. There must be a good reason for it ... 4) Compatibility issues : this was more kind of a guts feeling I had, but as usually, it revealed to be true : see the problems I will now be facing with Little/Big endian versions of TSM/Spectrum Protect (without to mention that Spectrum Protect 8.1 is not even available for Power Linux so far). I'm currently facing another one : the Isilon we got is running OneFS 8, and there's so far no official statement that it is supported, whether by TSM or by dsmISI. A downgrade to OneFS 7.x revealed to be impossible, due to the fact that the 8 TB disks installed in the machine are not supporting it ... 5) Support by EMC : revealed to be less efficient than the one offered by IBM. Since EMC merged with Dell, it became even worse (for a non-native English speaking person, having a call with support based in India is a nightmare). Also our storage administrator informed me that from his experience, upgrade procedures on EMC devices where much more complicated than the ones for IBM hardware, and almost always required intervention of the vendor to be conducted properly (lots of dependencies in microcodes, switch versions and so on ...) 6) Costs ... Of course, your mileage may vary, but in our case I&#x
Re: TSM Server on CentOS Linux
Hello, here a quick and dirty howto. Hope it helps. Dennis Am 14.02.2017 um 10:40 schrieb .Maurizio TERUZZI: > Ciao, > > thanks for you reply Sasa. > Yes, alla are goog and "pingeable" in form IP, hostname, FQDN on local and > also from remote host. > > Creers > Maurizio > > > > > Il 14.02.2017 09:52, Sasa Drnjevic ha scritto: >> Hi, >> check if your /etc/hosts file contains all of the IP addresses of the >> host and hostnames (including localhost). >> >> Regards, >> >> -- >> Sasa Drnjevic >> www.srce.unizg.hr >> >> >> >> >> >> On 13.2.2017. 23:38, .Maurizio TERUZZI wrote: >>> hello, >>> >>> I'm trying to configure the TSM instance but I have trouble on the first >>> step of the wizard, after press the first NEXT I receive the Error: >>> Cannot start The Wizard, error establishing local connection for wizard >>> validation. >>> >>> What I checked (1- 127.0.0.1; 2- hostname, 3- FQDN) >>> - SSH connection (all 3 possibility works); >>> - PING connection (all 3 possibility works); >>> - instance folder right ok; >>> - I'm logger with instance user. >>> >>> I was looking for the logfile without success. >>> >>> PrintScreen available on demand. >>> >>> >>> Thansk >>> Maurizio > > IBM Spectrum Protect Server V7.1 on CentOS 7-1611 (x86_64) CentOS: https://www.centos.org/download/ TSM Server: http://www-01.ibm.com/support/docview.wss?uid=swg21239415 Client: ftp://public.dhe.ibm.com/storage/tivoli-storage-management/maintenance/client/v7r1/Linux/LinuxX86/BA/ Files in /install ISP_7141_LINUX_X86_64_SSA_ML.bin ( or another 7er Version with License include ) 7.1.7.100-TIV-TSMSRV-Linuxx86_64.bin 7.1.6.2-TIV-TSMBAC-LinuxX86.tar Install Centos: choose minimal Internet Access needed - via Proxy https://www.centos.org/docs/5/html/yum/sn-yum-proxy-server.html yum update ( reboot if needed ) yum install net-tools compat-libstdc++-33.i686 yum groupinstall "X Window system" Example: /dev/sda for OS /dev/sdb for TSM-Instance (/tsminst1) /etc/sysctl.d/99-tsm.conf #TSM Parameter kernel.randomize_va_space=0 vm.swappiness=0 vm.overcommit_memory=0 http://www-01.ibm.com/support/docview.wss?uid=swg21459502 https://www.ibm.com/support/knowledgecenter/en/SSGSG7_7.1.1/com.ibm.itsm.perf.doc/t_perf_linux_server.html http://www-01.ibm.com/support/docview.wss?uid=swg21459502 sysctl -p or reboot User, Group, Filesystem: groupadd tsmsrvrs -g useradd -m -u -g -s /bin/bash tsminst1 passwd tsminst1 mkdir /tsminst1 mount /dev/sdb1 /tsminst1 mkdir /tsminst1/db01 mkdir /tsminst1/db02 mkdir /tsminst1/db03 mkdir /tsminst1/db04 mkdir /tsminst1/tsmaclog mkdir /tsminst1/tsmarchlog chown -R tsminst1 /tsminst1/ chgrp -R tsmsrvrs /tsminst1/ vi /etc/hosts 192.168.1.240 testtsmsrv01 Install TSM SRV 7.1.7.100 cd /install/ ./7.1.7.100-TIV-TSMSRV-Linuxx86_64.bin ./install.sh -c -acceptLicense If not enough Memory ./install.sh -vmargs "-DBYPASS_TSM_REQ_CHECKS=true" X-Server needed ( ssh -CY root@testtsmsrv01 | putty with SSH -> X11 -> Enable X11 forwarding ) run: /opt/tivoli/tsm/server/bin/dsmicfgx Install TSM Server License files (for alter Import) delete Files/directories from 7.1.7.x ./ISP_7141_LINUX_X86_64_SSA_ML.bin ./install.sh Install TSM Client: tar xvf 7.1.6.2-TIV-TSMBAC-LinuxX86.tar rpm -ivh TIVsm-API64.x86_64.rpm TIVsm-BA.x86_64.rpm Import/acitvate License login with dsmadmc /opt/tivoli/tsm/server/bin/tsmdiag/dsmadmc register license file=tsmee.lic dsmadmc > q lic dsmadmc > PREPARE dsmadmc > q db vi /opt/tivoli/tsm/client/ba/bin/dsm.sys SERVERNAME TSMDBMGR_tsminst1 * --- * * This stanza was added by the TSM Instance Configuration Utility * * --- * COMMMETHOD TCPIP TCPPORT 1500 TCPSERVERADDRESS 127.0.0.1 NODENAME $$_TSMDBMGR_$$ ERRORLOGNAME /tsminst1/tsmdbmgr.log PASSWORDDIR /tsminst1 Session established with server TESTTSMSRV01: Linux/x86_64 Server Version 7, Release 1, Level 7.100 Server date/time: 02/14/2017 13:37:50 Last access: 02/14/2017 13:23:56 tsm: TESTTSMSRV01> tsm: TESTTSMSRV01>register license file=tsmee.lic tsm: TESTTSMSRV01>q lic vi /opt/tivoli/tsm/server/bin/dsm.opt SERVERNAME TSMDBMGR_tsm * --- * * This stanza was added by the TSM Instance Configuration Utility * * ---
Re: Availability for Spectrum Protect 8.1 server software for Linux on power system
Arnaud, Thanks for the feedback, I just received delivery of two Isilons yesterday, one for our production DC and another for DR, hopefully I won't regret it. All of my TSM/ISP servers run on MS Windows 2012 R2 so NFS won't be an issue. For several years we have used Data Domain but it was reaching its end of service. One of my biggest concerns is if it will be able to handle the workload or become a performance bottleneck. I'll post back more info as I get them deployed and up to speed Can you expand on your model, number of nodes and network connectivity ? Thanks again -Rick Adamson -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of PAC Brion Arnaud Sent: Tuesday, February 14, 2017 5:57 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Availability for Spectrum Protect 8.1 server software for Linux on power system Hi Zoltan, Many reasons for it, which I'll try to shortly summarize : 1) Isilon makes use of NFS, whose performance is not that good on AIX systems. We are an AIX shop, and are forced to move to Power Linux machines to get sufficient performance to cover our backup needs. Our first experience with Power Linux machines revealed serious lacks in the functionalities we are accustomed to : no easy HMC setup, thus lack of call home capabilities so far. In addition to this we needed to setup a RedHat satellite server to allow for installation on remote servers, and so far are unable to boot our machines from it ... This will probably work sooner or later, but requires lots of involvement and time from our sys-admins. 2) Isilon is not perfectly fitting in a big TSM environment. In order to get decent performance, a third party tool will be needed, whose name is dsmISI. See following : https://urldefense.proofpoint.com/v2/url?u=http-3A__stefanradtke.blogspot.ch_2015_06_how-2Dto-2Doptimize-2Dtsm-2Doperations-2Dwith.html&d=DwIGaQ&c=AzgFQeXLLKhxSQaoFCm29A&r=uJG3UnPaeoz9naeIzbwWFddVED8ETOYHxjoACoofi2Y&m=IvL1NDqYjCA6eIK2-Dzb4BB_fBbpaVFQ5qhxSny2G4I&s=kpqDyDb694uLBMIK6iSla9-xv73XJeNfOXU4XAwfyCI&e= This means another layer of complexity in the setup, and another vendor to talk to, if facing performance issues. I had more than my lot of "ping-pong" games during my career as TSM administrator, between IBM and other vendors, to reject the responsibility on each other in case of issues. Having 3 parties involved in our setup will make such games even more frequent ... 3) User base for such a combination in Switzerland is inexistent, at least in the same order of size than ours. EMC has not been able to provide any customer reference in this country, with whom we could talk to about their setup. There must be a good reason for it ... 4) Compatibility issues : this was more kind of a guts feeling I had, but as usually, it revealed to be true : see the problems I will now be facing with Little/Big endian versions of TSM/Spectrum Protect (without to mention that Spectrum Protect 8.1 is not even available for Power Linux so far). I'm currently facing another one : the Isilon we got is running OneFS 8, and there's so far no official statement that it is supported, whether by TSM or by dsmISI. A downgrade to OneFS 7.x revealed to be impossible, due to the fact that the 8 TB disks installed in the machine are not supporting it ... 5) Support by EMC : revealed to be less efficient than the one offered by IBM. Since EMC merged with Dell, it became even worse (for a non-native English speaking person, having a call with support based in India is a nightmare). Also our storage administrator informed me that from his experience, upgrade procedures on EMC devices where much more complicated than the ones for IBM hardware, and almost always required intervention of the vendor to be conducted properly (lots of dependencies in microcodes, switch versions and so on ...) 6) Costs ... Of course, your mileage may vary, but in our case I'm pretty sure that management made the wrong choice (I would have gone IBM Spectrum Scale in conjunction with an AIX based server : one vendor, blueprints provided, and guaranteed performance). Cheers. Arnaud -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan Forray Sent: Monday, February 13, 2017 4:38 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Availability for Spectrum Protect 8.1 server software for Linux on power system Arnaud, On Fri, Feb 10, 2017 at 9:21 AM, PAC Brion Arnaud < arnaud.br...@panalpina.com> wrote: > because our management (despite my warnings not to do so) decided that > the target storage for backups would be an EMC Isilon, that connects > to the TSM server using NFS mounts. A little off topic for this thread but why do you feel it is a "bad idea" to use EMC Isilon for TSM target storage for backups? We are leanin
Re: Availability for Spectrum Protect 8.1 server software for Linux on power system
Hi Zoltan, Many reasons for it, which I'll try to shortly summarize : 1) Isilon makes use of NFS, whose performance is not that good on AIX systems. We are an AIX shop, and are forced to move to Power Linux machines to get sufficient performance to cover our backup needs. Our first experience with Power Linux machines revealed serious lacks in the functionalities we are accustomed to : no easy HMC setup, thus lack of call home capabilities so far. In addition to this we needed to setup a RedHat satellite server to allow for installation on remote servers, and so far are unable to boot our machines from it ... This will probably work sooner or later, but requires lots of involvement and time from our sys-admins. 2) Isilon is not perfectly fitting in a big TSM environment. In order to get decent performance, a third party tool will be needed, whose name is dsmISI. See following : http://stefanradtke.blogspot.ch/2015/06/how-to-optimize-tsm-operations-with.html This means another layer of complexity in the setup, and another vendor to talk to, if facing performance issues. I had more than my lot of "ping-pong" games during my career as TSM administrator, between IBM and other vendors, to reject the responsibility on each other in case of issues. Having 3 parties involved in our setup will make such games even more frequent ... 3) User base for such a combination in Switzerland is inexistent, at least in the same order of size than ours. EMC has not been able to provide any customer reference in this country, with whom we could talk to about their setup. There must be a good reason for it ... 4) Compatibility issues : this was more kind of a guts feeling I had, but as usually, it revealed to be true : see the problems I will now be facing with Little/Big endian versions of TSM/Spectrum Protect (without to mention that Spectrum Protect 8.1 is not even available for Power Linux so far). I'm currently facing another one : the Isilon we got is running OneFS 8, and there's so far no official statement that it is supported, whether by TSM or by dsmISI. A downgrade to OneFS 7.x revealed to be impossible, due to the fact that the 8 TB disks installed in the machine are not supporting it ... 5) Support by EMC : revealed to be less efficient than the one offered by IBM. Since EMC merged with Dell, it became even worse (for a non-native English speaking person, having a call with support based in India is a nightmare). Also our storage administrator informed me that from his experience, upgrade procedures on EMC devices where much more complicated than the ones for IBM hardware, and almost always required intervention of the vendor to be conducted properly (lots of dependencies in microcodes, switch versions and so on ...) 6) Costs ... Of course, your mileage may vary, but in our case I'm pretty sure that management made the wrong choice (I would have gone IBM Spectrum Scale in conjunction with an AIX based server : one vendor, blueprints provided, and guaranteed performance). Cheers. Arnaud -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan Forray Sent: Monday, February 13, 2017 4:38 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Availability for Spectrum Protect 8.1 server software for Linux on power system Arnaud, On Fri, Feb 10, 2017 at 9:21 AM, PAC Brion Arnaud < arnaud.br...@panalpina.com> wrote: > because our management (despite my warnings not to do so) decided that the > target storage for backups would be an EMC Isilon, that connects to the TSM > server using NFS mounts. A little off topic for this thread but why do you feel it is a "bad idea" to use EMC Isilon for TSM target storage for backups? We are leaning in this direction and in fact have such a configuration for our offsite replication target server. We are aggressively moving away from expensive VNX storage to Isilon. So I am curious why you feel the way you do? -- *Zoltan Forray* Spectrum Protect (p.k.a. TSM) Software & Hardware Administrator Xymon Monitor Administrator VMware Administrator (in training) Virginia Commonwealth University UCC/Office of Technology Services www.ucc.vcu.edu zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html
Re: TSM Server on CentOS Linux
Ciao, thanks for you reply Sasa. Yes, alla are goog and "pingeable" in form IP, hostname, FQDN on local and also from remote host. Creers Maurizio Il 14.02.2017 09:52, Sasa Drnjevic ha scritto: Hi, check if your /etc/hosts file contains all of the IP addresses of the host and hostnames (including localhost). Regards, -- Sasa Drnjevic www.srce.unizg.hr On 13.2.2017. 23:38, .Maurizio TERUZZI wrote: hello, I'm trying to configure the TSM instance but I have trouble on the first step of the wizard, after press the first NEXT I receive the Error: Cannot start The Wizard, error establishing local connection for wizard validation. What I checked (1- 127.0.0.1; 2- hostname, 3- FQDN) - SSH connection (all 3 possibility works); - PING connection (all 3 possibility works); - instance folder right ok; - I'm logger with instance user. I was looking for the logfile without success. PrintScreen available on demand. Thansk Maurizio -- Cordiali saluti / Meilleures salutations Maurizio Teruzzi https://www.linkedin.com/in/teruzzi Join my computation group for social aid. https://join.worldcommunitygrid.org?recruiterId=184105&teamId=K85XNJBR9N1 I- Pensate al impatto ambientale prima di stampare questa email F- Pensez à l'environnement avant d'imprimer cet email E- Please consider your environmental concern before printing this email
Re: TSM Server on CentOS Linux
Hi, check if your /etc/hosts file contains all of the IP addresses of the host and hostnames (including localhost). Regards, -- Sasa Drnjevic www.srce.unizg.hr On 13.2.2017. 23:38, .Maurizio TERUZZI wrote: > hello, > > I'm trying to configure the TSM instance but I have trouble on the first > step of the wizard, after press the first NEXT I receive the Error: > Cannot start The Wizard, error establishing local connection for wizard > validation. > > What I checked (1- 127.0.0.1; 2- hostname, 3- FQDN) > - SSH connection (all 3 possibility works); > - PING connection (all 3 possibility works); > - instance folder right ok; > - I'm logger with instance user. > > I was looking for the logfile without success. > > PrintScreen available on demand. > > > Thansk > Maurizio
TSM Server on CentOS Linux
hello, I'm trying to configure the TSM instance but I have trouble on the first step of the wizard, after press the first NEXT I receive the Error: Cannot start The Wizard, error establishing local connection for wizard validation. What I checked (1- 127.0.0.1; 2- hostname, 3- FQDN) - SSH connection (all 3 possibility works); - PING connection (all 3 possibility works); - instance folder right ok; - I'm logger with instance user. I was looking for the logfile without success. PrintScreen available on demand. Thansk Maurizio
TSM Server on CentOS Linux
TSM server 8.1 installed on CentOS7, tks mike Messaggio Inoltrato Oggetto:Re: [ADSM-L] TSM Server on CentOS Linux Data: Fri, 3 Feb 2017 14:43:06 +0100 Mittente: .Maurizio TERUZZI A: michael_s.ry...@roche.com Ciao Michael, thanks for you help. YOUR solution passed the pre-req test for V7.1.7 but I installed the wrong one :) I will try with the V8.1.0 if possible YE, it's works on CENTOS 7! Below the output GRAZIE Maurizio P.S.: I will make a resume for the group => IBM Installation Manager> Install Select packages to install: 1. [X] IBM® Installation Manager 1.8.5 2. [X] IBM Spectrum Protect server 8.1.0.20161121_2118 3. [ ] IBM Spectrum Protect languages 8.1.0.20161121_2112 4. [X] IBM Spectrum Protect license 8.1.0.20161121_2112 5. [ ] IBM Spectrum Protect storage agent 8.1.0.20161121_2110 6. [X] IBM Spectrum Protect device driver 8.1.0.20161121_2115 7. [ ] IBM Spectrum Protect Operations Center 8.1.0.20161121_1638 O. Check for Other Versions, Fixes, and Extensions N. Next, C. Cancel -> [N] Validating package prerequisites... . => IBM Installation Manager> Install> Prerequisites Validation results: * [WARNING] IBM Spectrum Protect server 8.1.0.20161121_2118 contains validation warning. 1. WARNING: The operating system where you are installing the product is not supported. For more information, see http://www.ibm.com/software/tivoli/products/storage-mgr/platforms.html. 2. WARNING: The system does not meet the recommended memory requirement of 16 GB. * [WARNING] IBM Spectrum Protect license 8.1.0.20161121_2112 contains validation warning. 3. WARNING: The operating system where you are installing the product is not supported. For more information, see http://www.ibm.com/software/tivoli/products/storage-mgr/platforms.html. * [WARNING] IBM Spectrum Protect device driver 8.1.0.20161121_2115 contains validation warning. 4. WARNING: The operating system where you are installing the product is not supported. For more information, see http://www.ibm.com/software/tivoli/products/storage-mgr/platforms.html. Enter the number of the error or warning message above to view more details. Options: R. Recheck status. B. Back, N. Next, C. Cancel -> [N] Il 31.01.2017 22:56, Ryder, Michael S ha scritto: I believe you add a parameter to your call of install.sh like this install.sh -g -vmargs "-DBYPASS_TSM_REQ_CHECKS=true" I haven't tried this in some time... Good luck. Best regards, Mike, x7942 RMD IT Client Services On Tue, Jan 31, 2017 at 4:50 PM, .Maurizio TERUZZI < maurizio.teru...@bluewin.ch> wrote: Hello, I agreed with previuos opinions but my management insist at least for the test TSM server on CentOS (or other free distr). I tryed TSM server version 7.1.x and 8.1.x and I'm facing on the same problem because of non-support on both relase verification (Install Manager). Anyone can help to go further with this? * [ERROR] IBM Tivoli Storage Manager server 7.1.7.20160907_1803 contains validation errors. 1. ERROR: The operating system where you are installing the product is not supported. For more information, see http://www.ibm.com/software/tivoli/products/storage-mgr/platforms.html. Same kind of message for v8.1.x. Some years ago I changed a parameter to installa a Oracle DB on a unsopported distr but I don't remember how I procedes, this works years without problems. Current system: lsb_release -a LSB Version::core-4.1-ia32:core-4.1-noarch Distributor ID: CentOS Description:CentOS Linux release 7.3.1611 (Core) Release:7.3.1611 Codename: Core Thanks Maurizio -- Cordiali saluti / Meilleures salutations Maurizio Teruzzi https://www.linkedin.com/in/teruzzi Join my computation group for social aid. https://join.worldcommunitygrid.org?recruiterId=184105&teamId=K85XNJBR9N1 I- Pensate al impatto ambientale prima di stampare questa email F- Pensez à l'environnement avant d'imprimer cet email E- Please consider your environmental concern before printing this email
Re: Availability for Spectrum Protect 8.1 server software for Linux on power system
Arnaud, On Fri, Feb 10, 2017 at 9:21 AM, PAC Brion Arnaud < arnaud.br...@panalpina.com> wrote: > because our management (despite my warnings not to do so) decided that the > target storage for backups would be an EMC Isilon, that connects to the TSM > server using NFS mounts. A little off topic for this thread but why do you feel it is a "bad idea" to use EMC Isilon for TSM target storage for backups? We are leaning in this direction and in fact have such a configuration for our offsite replication target server. We are aggressively moving away from expensive VNX storage to Isilon. So I am curious why you feel the way you do? -- *Zoltan Forray* Spectrum Protect (p.k.a. TSM) Software & Hardware Administrator Xymon Monitor Administrator VMware Administrator (in training) Virginia Commonwealth University UCC/Office of Technology Services www.ucc.vcu.edu zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html
Re: Availability for Spectrum Protect 8.1 server software for Linux on power system
Hi Arnaud, IBM plans to provide a migration path for customer to transition from BE--->LE. Will this help? Del --- "ADSM: Dist Stor Manager" wrote on 02/10/2017 09:21:55 AM: > From: PAC Brion Arnaud > To: ADSM-L@VM.MARIST.EDU > Date: 02/10/2017 09:22 AM > Subject: Re: Availability for Spectrum Protect 8.1 server software > for Linux on power system > Sent by: "ADSM: Dist Stor Manager" > > Del, > > Again, thanks for your feedback ! > > Unfortunately this is a nightmare scenario for us : we have almost > no other platform choice than a Power Linux machine for our upcoming > Spectrum Protect project, because our management (despite my > warnings not to do so) decided that the target storage for backups > would be an EMC Isilon, that connects to the TSM server using NFS mounts. > AIX is not an option, as its implementation of NFS protocol is not > efficient enough, and Linux on X86 platform neither is, due to its > much lower I/O capabilities (we are speaking of an environment > supposed to ingest 35 TB /day/server, making use only of > deduplicated directory-container storage pools ...) > For now, the Isilon storage has already been delivered, and we end > with a setup able to run TSM 7.1.X properly, but with no options > anymore to upgrade to Spectrum protect 8.1 and higher. > Of course, at the time were the decision had been taken to make use > of Isilon storage (end of December 2016), none of our consultants at > IBM had been able to pinpoint such an issue ... > > This is really, really bad :-( > > Cheers. > > Arnaud > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On > Behalf Of Del Hoobler > Sent: Friday, February 10, 2017 1:24 PM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: Availability for Spectrum Protect 8.1 server software > for Linux on power system > > Hi Arnaud, > > As a general IBM statement, Linux on Power is transitioning from Big > Endian to Little Endian. This has been underway for a few years. Here are > a few blogs from IBM when this started a few years ago: > > https://www.ibm.com/developerworks/community/blogs/ > fe313521-2e95-46f2-817d-44a4f27eba32/entry/ > just_the_faqs_about_little_endian?lang=en > https://www.ibm.com/developerworks/community/blogs/ > fe313521-2e95-46f2-817d-44a4f27eba32/entry/ > More_FAQs_about_Little_Endian_An_Update?lang=en > > This means that applications for Linux on Power are also transitioning > from Big Endian to Little Endian, including Spectrum Protect. > > Spectrum Protect 7.1 supports Linux on Power Big Endian, but Spectrum > Protect 8.1 does not. Spectrum Protect 8.1 is targeted to add support for > Linux on Power Little Endian in the 1H of this year. > > > Del > > > > > "ADSM: Dist Stor Manager" wrote on 02/09/2017 > 03:24:30 AM: > > > From: PAC Brion Arnaud > > To: ADSM-L@VM.MARIST.EDU > > Date: 02/09/2017 03:26 AM > > Subject: Re: Availability for Spectrum Protect 8.1 server software > > for Linux on power system > > Sent by: "ADSM: Dist Stor Manager" > > > > Hi Del, > > > > Thanks a lot too, for what I would call "conflictual" information ... > > Do you have any link available that would confirm your saying ? > > For us it is paramount to have a guaranteed information, as we are > > about to buy a machine, which MUST be the right one ! > > > > And, if I may ask : from this page http://www-01.ibm.com/support/ > > docview.wss?uid=swg21108042 it seems that the 7.1.1 version of TSM > > server for Linux on Power is built for Big Endian. In that case why > > would IBM be willing to deliver the next version only for Little > > Endian ? This looks totally inconsistent to my eyes > > > > Cheers. > > > > Arnaud > > > > > ** > > Backup and Recovery Systems Administrator > > Panalpina Management Ltd., Basle, Switzerland, > > CIT Department Viadukstrasse 42, P.O. Box 4002 Basel/CH > > Phone: +41 (61) 226 11 11, FAX: +41 (61) 226 17 01 > > Direct: +41 (61) 226 19 78 > > e-mail: arnaud.br...@panalpina.com > > This electronic message transmission contains information from > > Panalpina and is confidential or privileged. This information is > > intended only for the person (s) named above. If you are not the > > intended recipient, any disclosure, copying, distribu
Re: Availability for Spectrum Protect 8.1 server software for Linux on power system
Del, Again, thanks for your feedback ! Unfortunately this is a nightmare scenario for us : we have almost no other platform choice than a Power Linux machine for our upcoming Spectrum Protect project, because our management (despite my warnings not to do so) decided that the target storage for backups would be an EMC Isilon, that connects to the TSM server using NFS mounts. AIX is not an option, as its implementation of NFS protocol is not efficient enough, and Linux on X86 platform neither is, due to its much lower I/O capabilities (we are speaking of an environment supposed to ingest 35 TB /day/server, making use only of deduplicated directory-container storage pools ...) For now, the Isilon storage has already been delivered, and we end with a setup able to run TSM 7.1.X properly, but with no options anymore to upgrade to Spectrum protect 8.1 and higher. Of course, at the time were the decision had been taken to make use of Isilon storage (end of December 2016), none of our consultants at IBM had been able to pinpoint such an issue ... This is really, really bad :-( Cheers. Arnaud -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Del Hoobler Sent: Friday, February 10, 2017 1:24 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Availability for Spectrum Protect 8.1 server software for Linux on power system Hi Arnaud, As a general IBM statement, Linux on Power is transitioning from Big Endian to Little Endian. This has been underway for a few years. Here are a few blogs from IBM when this started a few years ago: https://www.ibm.com/developerworks/community/blogs/fe313521-2e95-46f2-817d-44a4f27eba32/entry/just_the_faqs_about_little_endian?lang=en https://www.ibm.com/developerworks/community/blogs/fe313521-2e95-46f2-817d-44a4f27eba32/entry/More_FAQs_about_Little_Endian_An_Update?lang=en This means that applications for Linux on Power are also transitioning from Big Endian to Little Endian, including Spectrum Protect. Spectrum Protect 7.1 supports Linux on Power Big Endian, but Spectrum Protect 8.1 does not. Spectrum Protect 8.1 is targeted to add support for Linux on Power Little Endian in the 1H of this year. Del "ADSM: Dist Stor Manager" wrote on 02/09/2017 03:24:30 AM: > From: PAC Brion Arnaud > To: ADSM-L@VM.MARIST.EDU > Date: 02/09/2017 03:26 AM > Subject: Re: Availability for Spectrum Protect 8.1 server software > for Linux on power system > Sent by: "ADSM: Dist Stor Manager" > > Hi Del, > > Thanks a lot too, for what I would call "conflictual" information ... > Do you have any link available that would confirm your saying ? > For us it is paramount to have a guaranteed information, as we are > about to buy a machine, which MUST be the right one ! > > And, if I may ask : from this page http://www-01.ibm.com/support/ > docview.wss?uid=swg21108042 it seems that the 7.1.1 version of TSM > server for Linux on Power is built for Big Endian. In that case why > would IBM be willing to deliver the next version only for Little > Endian ? This looks totally inconsistent to my eyes > > Cheers. > > Arnaud > > ** > Backup and Recovery Systems Administrator > Panalpina Management Ltd., Basle, Switzerland, > CIT Department Viadukstrasse 42, P.O. Box 4002 Basel/CH > Phone: +41 (61) 226 11 11, FAX: +41 (61) 226 17 01 > Direct: +41 (61) 226 19 78 > e-mail: arnaud.br...@panalpina.com > This electronic message transmission contains information from > Panalpina and is confidential or privileged. This information is > intended only for the person (s) named above. If you are not the > intended recipient, any disclosure, copying, distribution or use or > any other action based on the contents of this information is > strictly prohibited. > > If you receive this electronic transmission in error, please notify > the sender by e-mail, telephone or fax at the numbers listed above. Thank you. > ** > > > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On > Behalf Of Del Hoobler > Sent: Wednesday, February 08, 2017 3:03 PM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: Availability for Spectrum Protect 8.1 server software > for Linux on power system > > IBM is a planning a pLinux (Little Endian) Spectrum Protect server in the > 1H of this year. > > > Del > > > > > "ADSM: Dist Stor Manager" wrote on 02/0
Re: Availability for Spectrum Protect 8.1 server software for Linux on power system
Hi Arnaud, As a general IBM statement, Linux on Power is transitioning from Big Endian to Little Endian. This has been underway for a few years. Here are a few blogs from IBM when this started a few years ago: https://www.ibm.com/developerworks/community/blogs/fe313521-2e95-46f2-817d-44a4f27eba32/entry/just_the_faqs_about_little_endian?lang=en https://www.ibm.com/developerworks/community/blogs/fe313521-2e95-46f2-817d-44a4f27eba32/entry/More_FAQs_about_Little_Endian_An_Update?lang=en This means that applications for Linux on Power are also transitioning from Big Endian to Little Endian, including Spectrum Protect. Spectrum Protect 7.1 supports Linux on Power Big Endian, but Spectrum Protect 8.1 does not. Spectrum Protect 8.1 is targeted to add support for Linux on Power Little Endian in the 1H of this year. Del "ADSM: Dist Stor Manager" wrote on 02/09/2017 03:24:30 AM: > From: PAC Brion Arnaud > To: ADSM-L@VM.MARIST.EDU > Date: 02/09/2017 03:26 AM > Subject: Re: Availability for Spectrum Protect 8.1 server software > for Linux on power system > Sent by: "ADSM: Dist Stor Manager" > > Hi Del, > > Thanks a lot too, for what I would call "conflictual" information ... > Do you have any link available that would confirm your saying ? > For us it is paramount to have a guaranteed information, as we are > about to buy a machine, which MUST be the right one ! > > And, if I may ask : from this page http://www-01.ibm.com/support/ > docview.wss?uid=swg21108042 it seems that the 7.1.1 version of TSM > server for Linux on Power is built for Big Endian. In that case why > would IBM be willing to deliver the next version only for Little > Endian ? This looks totally inconsistent to my eyes > > Cheers. > > Arnaud > > ** > Backup and Recovery Systems Administrator > Panalpina Management Ltd., Basle, Switzerland, > CIT Department Viadukstrasse 42, P.O. Box 4002 Basel/CH > Phone: +41 (61) 226 11 11, FAX: +41 (61) 226 17 01 > Direct: +41 (61) 226 19 78 > e-mail: arnaud.br...@panalpina.com > This electronic message transmission contains information from > Panalpina and is confidential or privileged. This information is > intended only for the person (s) named above. If you are not the > intended recipient, any disclosure, copying, distribution or use or > any other action based on the contents of this information is > strictly prohibited. > > If you receive this electronic transmission in error, please notify > the sender by e-mail, telephone or fax at the numbers listed above. Thank you. > ** > > > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On > Behalf Of Del Hoobler > Sent: Wednesday, February 08, 2017 3:03 PM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: Availability for Spectrum Protect 8.1 server software > for Linux on power system > > IBM is a planning a pLinux (Little Endian) Spectrum Protect server in the > 1H of this year. > > > Del > > > > > "ADSM: Dist Stor Manager" wrote on 02/08/2017 > 08:56:39 AM: > > > From: PAC Brion Arnaud > > To: ADSM-L@VM.MARIST.EDU > > Date: 02/08/2017 08:58 AM > > Subject: Re: Availability for Spectrum Protect 8.1 server software > > for Linux on power system > > Sent by: "ADSM: Dist Stor Manager" > > > > Hi Anders, > > > > Thanks a lot for fast feedback ! > > This will for sure ruin our plans for a cheaper environment :-( > > > > Best regards. > > > > Arnaud > > > > > > -Original Message- > > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On > > Behalf Of Anders Räntilä > > Sent: Wednesday, February 08, 2017 2:26 PM > > To: ADSM-L@VM.MARIST.EDU > > Subject: Re: Availability for Spectrum Protect 8.1 server software > > for Linux on power system > > > > http://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.0/srv.common/ > > r_techchg_srv_opsys_810.html > > > > Support for the following operating systems is discontinued: > > > > HP-UX > > Linux on Power SystemsT (big endian) > > Oracle Solaris > > > > /Anders Räntilä > > > > > > -Original Message- > > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On >
Re: Availability for Spectrum Protect 8.1 server software for Linux on power system
Hi Del, Thanks a lot too, for what I would call "conflictual" information ... Do you have any link available that would confirm your saying ? For us it is paramount to have a guaranteed information, as we are about to buy a machine, which MUST be the right one ! And, if I may ask : from this page http://www-01.ibm.com/support/docview.wss?uid=swg21108042 it seems that the 7.1.1 version of TSM server for Linux on Power is built for Big Endian. In that case why would IBM be willing to deliver the next version only for Little Endian ? This looks totally inconsistent to my eyes Cheers. Arnaud ** Backup and Recovery Systems Administrator Panalpina Management Ltd., Basle, Switzerland, CIT Department Viadukstrasse 42, P.O. Box 4002 Basel/CH Phone: +41 (61) 226 11 11, FAX: +41 (61) 226 17 01 Direct: +41 (61) 226 19 78 e-mail: arnaud.br...@panalpina.com This electronic message transmission contains information from Panalpina and is confidential or privileged. This information is intended only for the person (s) named above. If you are not the intended recipient, any disclosure, copying, distribution or use or any other action based on the contents of this information is strictly prohibited. If you receive this electronic transmission in error, please notify the sender by e-mail, telephone or fax at the numbers listed above. Thank you. ** -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Del Hoobler Sent: Wednesday, February 08, 2017 3:03 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Availability for Spectrum Protect 8.1 server software for Linux on power system IBM is a planning a pLinux (Little Endian) Spectrum Protect server in the 1H of this year. Del "ADSM: Dist Stor Manager" wrote on 02/08/2017 08:56:39 AM: > From: PAC Brion Arnaud > To: ADSM-L@VM.MARIST.EDU > Date: 02/08/2017 08:58 AM > Subject: Re: Availability for Spectrum Protect 8.1 server software > for Linux on power system > Sent by: "ADSM: Dist Stor Manager" > > Hi Anders, > > Thanks a lot for fast feedback ! > This will for sure ruin our plans for a cheaper environment :-( > > Best regards. > > Arnaud > > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On > Behalf Of Anders Räntilä > Sent: Wednesday, February 08, 2017 2:26 PM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: Availability for Spectrum Protect 8.1 server software > for Linux on power system > > http://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.0/srv.common/ > r_techchg_srv_opsys_810.html > > Support for the following operating systems is discontinued: > > HP-UX > Linux on Power SystemsT (big endian) > Oracle Solaris > > /Anders Räntilä > > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On > Behalf Of PAC Brion Arnaud > Sent: den 8 februari 2017 14:18 > To: ADSM-L@VM.MARIST.EDU > Subject: [ADSM-L] Availability for Spectrum Protect 8.1 server > software for Linux on power system > > Hi All, > > We are planning for a migration of our current TSM environment to > Spectrum Protect 8.1 instances, which are deemed to be running on a > Power Linux machine (Power S824L). > I'm however unable to find the corresponding server software on IBM > passport advantage site ... The latest version available for > download for such a platform is TSM 7.1.1, as well as a maintenance > level 7.1.7. > Does anyone have knowledge on if SP 8.1 for Power Linux is available > somewhere, or on its release date if still not existing ? > > Thanks a lot for any feedback ! > > Cheers. > > Arnaud > > ** > Backup and Recovery Systems Administrator > Panalpina Management Ltd., Basle, Switzerland, > CIT Department Viadukstrasse 42, P.O. Box 4002 Basel/CH > Phone: +41 (61) 226 11 11, FAX: +41 (61) 226 17 01 > Direct: +41 (61) 226 19 78 > e-mail: arnaud.br...@panalpina.com<mailto:arnaud.br...@panalpina.com> > This electronic message transmission contains information from > Panalpina and is confidential or privileged. This information is > intended only for the person (s) named above. If you are not the > intended recipient, any disclosure, copying, distribution or use or > any other action based on the contents of this information is > strictly prohibited. > > If you receive this electronic transmission in error, please notify > the sender by e-mail, telephone or fax at the numbers listed above. Thank you. > ** >
Re: Availability for Spectrum Protect 8.1 server software for Linux on power system
IBM is a planning a pLinux (Little Endian) Spectrum Protect server in the 1H of this year. Del "ADSM: Dist Stor Manager" wrote on 02/08/2017 08:56:39 AM: > From: PAC Brion Arnaud > To: ADSM-L@VM.MARIST.EDU > Date: 02/08/2017 08:58 AM > Subject: Re: Availability for Spectrum Protect 8.1 server software > for Linux on power system > Sent by: "ADSM: Dist Stor Manager" > > Hi Anders, > > Thanks a lot for fast feedback ! > This will for sure ruin our plans for a cheaper environment :-( > > Best regards. > > Arnaud > > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On > Behalf Of Anders Räntilä > Sent: Wednesday, February 08, 2017 2:26 PM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: Availability for Spectrum Protect 8.1 server software > for Linux on power system > > http://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.0/srv.common/ > r_techchg_srv_opsys_810.html > > Support for the following operating systems is discontinued: > > HP-UX > Linux on Power SystemsT (big endian) > Oracle Solaris > > /Anders Räntilä > > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On > Behalf Of PAC Brion Arnaud > Sent: den 8 februari 2017 14:18 > To: ADSM-L@VM.MARIST.EDU > Subject: [ADSM-L] Availability for Spectrum Protect 8.1 server > software for Linux on power system > > Hi All, > > We are planning for a migration of our current TSM environment to > Spectrum Protect 8.1 instances, which are deemed to be running on a > Power Linux machine (Power S824L). > I'm however unable to find the corresponding server software on IBM > passport advantage site ... The latest version available for > download for such a platform is TSM 7.1.1, as well as a maintenance > level 7.1.7. > Does anyone have knowledge on if SP 8.1 for Power Linux is available > somewhere, or on its release date if still not existing ? > > Thanks a lot for any feedback ! > > Cheers. > > Arnaud > > ** > Backup and Recovery Systems Administrator > Panalpina Management Ltd., Basle, Switzerland, > CIT Department Viadukstrasse 42, P.O. Box 4002 Basel/CH > Phone: +41 (61) 226 11 11, FAX: +41 (61) 226 17 01 > Direct: +41 (61) 226 19 78 > e-mail: arnaud.br...@panalpina.com<mailto:arnaud.br...@panalpina.com> > This electronic message transmission contains information from > Panalpina and is confidential or privileged. This information is > intended only for the person (s) named above. If you are not the > intended recipient, any disclosure, copying, distribution or use or > any other action based on the contents of this information is > strictly prohibited. > > If you receive this electronic transmission in error, please notify > the sender by e-mail, telephone or fax at the numbers listed above. Thank you. > ** >
Re: Re: How to exclude bad Linux mountpoint
Maybe you can identify characteristics of the bogus disks and create udev rules so they won't be mounted at all? Or for another TSM-only idea, since you can unmount them, maybe put the umount commands in a script and add a PRESChedulecmd to run the script before each backup? (Not sure if that precedes the client's enumeration of the filesystems, but I would hope so.) =Dave On 02/08/2017 07:52 AM, Zoltan Forray wrote: > We have unmounted it but It keeps coming back and will until Dell fixes it. > > On Wed, Feb 8, 2017 at 8:36 AM, Rick Adamson > wrote: > >> Zoltan, >> >> Would it be acceptable to just force an unmount of the ghost FS ? >> >> I had a similar situation where a vendor was hired to perform some >> analytics on our 150 Linux servers, his removal process failed, leaving the >> mount points. >> >> For me that was easier.. >> >> >> >> -Rick Adamson >> >> >> -Original Message- >> >> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of >> Zoltan Forray >> >> Sent: Tuesday, February 07, 2017 4:07 PM >> >> To: ADSM-L@VM.MARIST.EDU >> >> Subject: Re: [ADSM-L] How to exclude bad Linux mountpoint >> >> Thanks for the suggestions. I forgot about the EXCLUDE.FS which seems to >> have done the trick since it is a filesystem (see df below). Now to roll >> this out to all of my Linux servers. >> >> [zforray@processor ~]$ df -m >> Filesystem 1M-blocksUsed Available Use% Mounted on >> /dev/mapper/vg_processr_sys-lv_root >> 200317123 11885 38% / >> tmpfs48339 1 48339 1% /dev/shm >> /dev/sdb2 477 108 344 24% /boot >> /dev/sdb1 100 1 100 1% /boot/efi >> /dev/mapper/vg_processr_sys-lv_home >> 50269 10818 36891 23% /home >> /dev/mapper/vg_processr_sys-lv_tsmarchlog >> 302380 480301901 1% /tsmdb2 >> /dev/mapper/vg_processr_sys-lv_tsmarchlog2 >> 151190 348150843 1% /tsmarchlog2 >> /dev/mapper/vg_processr_sys-lv_tsmdb >> 403174 364843 38331 91% /tsmdb >> /dev/mapper/vg_processr_sys-lv_tsmlog >> 129016 120165 2298 99% /tsmlog >> /dev/mapper/vg_processr_pool-lv_tsmpool >> 10133861 9618741 344 100% /tsmpool >> /dev/mapper/vg_processr_sys-lv_var >> 14991 878 13346 7% /var >> /dev/sdd 2 0 2 0% /tmp/SECUPD >> /dev/sde 2 0 2 0% /tmp/SECUPD >> >> >> >> On Tue, Feb 7, 2017 at 3:05 PM, Andrew Raibeck wrote: >> >>> Hi Zoltan, >>> >>> It could be the simple act of enumerating file systems or mount points >>> that causes a problem. What kinds of problems, specifically, are you seeing? >>> >>> A couple of thoughts (not sure these will help): >>> >>> - Does this show up as a separate file system, such as when you do df -m? >>> If yes, you could try exclude.fs /tmp/SECUPD >>> >>> - Another possibility is to define it as a virtual mount point using >>> the VIRTUALMOUNTPOINT option, then using exclude.fs. >>> >>> Finally, a total "shot in the dark", but try searching the internet >>> for this directory name. One discussion I found indicates that >>> /tmp/SECUPD is causing other issues, too: >>> >>> https://urldefense.proofpoint.com/v2/url?u=http-3A__en. >> community.dell.com_support-2Dforums_servers_f_956_t_19996605&d=DwIGaQ&c= >> AzgFQeXLLKhxSQaoFCm29A&r=uJG3UnPaeoz9naeIzbwWFddVED8ETOYHxjoACoofi2Y&m= >> dpyZFjUm5jdJEy7vIroIPKAZVkonlHvpInjN-PV6Njo&s= >> emQBeN08TImOrf5CKuScl7Pu2yElvurRtxPTdEAeZps&e= >>> >>> Regards, >>> >>> Andy >>> >>> >>> >>> >>> Andrew Raibeck | IBM Spectrum Protect Level 3 | stor...@us.ibm.com >>> >>> "ADSM: Dist Stor Manager" wrote on 2017-02-07 >>> 14:45:50: >>> >>>> From: Zoltan Forray >>>> To: ADSM-L@VM.MARIST.EDU >>>> Date: 2017-02-07 14:46 >>>> Subject: How to exclude bad Linux mountpoint Sent by: "ADSM: Dist >>>> Stor Manager" >>>> >>>> Ever since a certain Dell update, a ghost mountpoint of /tmp/SECUPD >>>> is left hanging after iDRAC/OpenManage updates. This is now causing >>>> heartburn for TSM backups. >>>> >>>> I have tried pushing down via CLOPTSET to >>>> >>>> exclude.dir /tmp/SECUPD >>>> exclude /tmp/SECUPD >>>> >>>> but neither work - TSM still tries to access/back it up. >>>> >>>> Any suggestions on how to get TSM to stop trying to access this mount? >> > -- Hello World.David Bronder - Systems Architect Segmentation Fault ITS-EI, Univ. of Iowa Core dumped, disk trashed, quota filled, soda warm. david-bron...@uiowa.edu
Re: Availability for Spectrum Protect 8.1 server software for Linux on power system
Hi Anders, Thanks a lot for fast feedback ! This will for sure ruin our plans for a cheaper environment :-( Best regards. Arnaud -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Anders Räntilä Sent: Wednesday, February 08, 2017 2:26 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Availability for Spectrum Protect 8.1 server software for Linux on power system http://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.0/srv.common/r_techchg_srv_opsys_810.html Support for the following operating systems is discontinued: HP-UX Linux on Power SystemsT (big endian) Oracle Solaris /Anders Räntilä -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of PAC Brion Arnaud Sent: den 8 februari 2017 14:18 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Availability for Spectrum Protect 8.1 server software for Linux on power system Hi All, We are planning for a migration of our current TSM environment to Spectrum Protect 8.1 instances, which are deemed to be running on a Power Linux machine (Power S824L). I'm however unable to find the corresponding server software on IBM passport advantage site ... The latest version available for download for such a platform is TSM 7.1.1, as well as a maintenance level 7.1.7. Does anyone have knowledge on if SP 8.1 for Power Linux is available somewhere, or on its release date if still not existing ? Thanks a lot for any feedback ! Cheers. Arnaud ** Backup and Recovery Systems Administrator Panalpina Management Ltd., Basle, Switzerland, CIT Department Viadukstrasse 42, P.O. Box 4002 Basel/CH Phone: +41 (61) 226 11 11, FAX: +41 (61) 226 17 01 Direct: +41 (61) 226 19 78 e-mail: arnaud.br...@panalpina.com<mailto:arnaud.br...@panalpina.com> This electronic message transmission contains information from Panalpina and is confidential or privileged. This information is intended only for the person (s) named above. If you are not the intended recipient, any disclosure, copying, distribution or use or any other action based on the contents of this information is strictly prohibited. If you receive this electronic transmission in error, please notify the sender by e-mail, telephone or fax at the numbers listed above. Thank you. **
Re: How to exclude bad Linux mountpoint
We have unmounted it but It keeps coming back and will until Dell fixes it. On Wed, Feb 8, 2017 at 8:36 AM, Rick Adamson wrote: > Zoltan, > > Would it be acceptable to just force an unmount of the ghost FS ? > > I had a similar situation where a vendor was hired to perform some > analytics on our 150 Linux servers, his removal process failed, leaving the > mount points. > > For me that was easier.. > > > > -Rick Adamson > > > > > > -Original Message- > > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of > Zoltan Forray > > Sent: Tuesday, February 07, 2017 4:07 PM > > To: ADSM-L@VM.MARIST.EDU > > Subject: Re: [ADSM-L] How to exclude bad Linux mountpoint > > > > Thanks for the suggestions. I forgot about the EXCLUDE.FS which seems to > have done the trick since it is a filesystem (see df below). Now to roll > this out to all of my Linux servers. > > > > [zforray@processor ~]$ df -m > > Filesystem 1M-blocksUsed Available Use% Mounted on > > /dev/mapper/vg_processr_sys-lv_root > > 200317123 11885 38% / > > tmpfs48339 1 48339 1% /dev/shm > > /dev/sdb2 477 108 344 24% /boot > > /dev/sdb1 100 1 100 1% /boot/efi > > /dev/mapper/vg_processr_sys-lv_home > > 50269 10818 36891 23% /home > > /dev/mapper/vg_processr_sys-lv_tsmarchlog > > 302380 480301901 1% /tsmdb2 > > /dev/mapper/vg_processr_sys-lv_tsmarchlog2 > > 151190 348150843 1% /tsmarchlog2 > > /dev/mapper/vg_processr_sys-lv_tsmdb > > 403174 364843 38331 91% /tsmdb > > /dev/mapper/vg_processr_sys-lv_tsmlog > > 129016 120165 2298 99% /tsmlog > > /dev/mapper/vg_processr_pool-lv_tsmpool > > 10133861 9618741 344 100% /tsmpool > > /dev/mapper/vg_processr_sys-lv_var > > 14991 878 13346 7% /var > > /dev/sdd 2 0 2 0% /tmp/SECUPD > > /dev/sde 2 0 2 0% /tmp/SECUPD > > > > > > On Tue, Feb 7, 2017 at 3:05 PM, Andrew Raibeck wrote: > > > > > Hi Zoltan, > > > > > > It could be the simple act of enumerating file systems or mount points > > > that causes a problem. What kinds of problems, specifically, are you > seeing? > > > > > > A couple of thoughts (not sure these will help): > > > > > > - Does this show up as a separate file system, such as when you do df -m? > > > If yes, you could try exclude.fs /tmp/SECUPD > > > > > > - Another possibility is to define it as a virtual mount point using > > > the VIRTUALMOUNTPOINT option, then using exclude.fs. > > > > > > Finally, a total "shot in the dark", but try searching the internet > > > for this directory name. One discussion I found indicates that > > > /tmp/SECUPD is causing other issues, too: > > > > > > https://urldefense.proofpoint.com/v2/url?u=http-3A__en. > community.dell.com_support-2Dforums_servers_f_956_t_19996605&d=DwIGaQ&c= > AzgFQeXLLKhxSQaoFCm29A&r=uJG3UnPaeoz9naeIzbwWFddVED8ETOYHxjoACoofi2Y&m= > dpyZFjUm5jdJEy7vIroIPKAZVkonlHvpInjN-PV6Njo&s= > emQBeN08TImOrf5CKuScl7Pu2yElvurRtxPTdEAeZps&e= > > > > > > Regards, > > > > > > Andy > > > > > > > > > > > > > > > Andrew Raibeck | IBM Spectrum Protect Level 3 | stor...@us.ibm.com > > > > > > IBM Tivoli Storage Manager links: > > > Product support: > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__www. > ibm.com_support_entry_portal_product_tivoli_&d=DwIGaQ&c= > AzgFQeXLLKhxSQaoFCm29A&r=uJG3UnPaeoz9naeIzbwWFddVED8ETOYHxjoACoofi2Y&m= > dpyZFjUm5jdJEy7vIroIPKAZVkonlHvpInjN-PV6Njo&s= > ECVSfVXW6qbUJh9K4NzdycKHtgKidb30DOkhhN3vnSg&e= > > > tivoli_storage_manager > > > > > > Online documentation: > > > https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ibm. > com_support_knowledgecenter_SSGSG7_&d=DwIGaQ&c=AzgFQeXLLKhxSQaoFCm29A&r= > uJG3UnPaeoz9naeIzbwWFddVED8ETOYHxjoACoofi2Y&m= > dpyZFjUm5jdJEy7vIroIPKAZVkonlHvpInjN-PV6Njo&s=YvaXmgbA- > vSR09gHC1JzvaVMgvi9HcpCk8dhEP9YuxA&e= > > > landing/welcome_ssgsg7.html > > &
Re: How to exclude bad Linux mountpoint
Zoltan, Would it be acceptable to just force an unmount of the ghost FS ? I had a similar situation where a vendor was hired to perform some analytics on our 150 Linux servers, his removal process failed, leaving the mount points. For me that was easier.. -Rick Adamson -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan Forray Sent: Tuesday, February 07, 2017 4:07 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] How to exclude bad Linux mountpoint Thanks for the suggestions. I forgot about the EXCLUDE.FS which seems to have done the trick since it is a filesystem (see df below). Now to roll this out to all of my Linux servers. [zforray@processor ~]$ df -m Filesystem 1M-blocksUsed Available Use% Mounted on /dev/mapper/vg_processr_sys-lv_root 200317123 11885 38% / tmpfs48339 1 48339 1% /dev/shm /dev/sdb2 477 108 344 24% /boot /dev/sdb1 100 1 100 1% /boot/efi /dev/mapper/vg_processr_sys-lv_home 50269 10818 36891 23% /home /dev/mapper/vg_processr_sys-lv_tsmarchlog 302380 480301901 1% /tsmdb2 /dev/mapper/vg_processr_sys-lv_tsmarchlog2 151190 348150843 1% /tsmarchlog2 /dev/mapper/vg_processr_sys-lv_tsmdb 403174 364843 38331 91% /tsmdb /dev/mapper/vg_processr_sys-lv_tsmlog 129016 120165 2298 99% /tsmlog /dev/mapper/vg_processr_pool-lv_tsmpool 10133861 9618741 344 100% /tsmpool /dev/mapper/vg_processr_sys-lv_var 14991 878 13346 7% /var /dev/sdd 2 0 2 0% /tmp/SECUPD /dev/sde 2 0 2 0% /tmp/SECUPD On Tue, Feb 7, 2017 at 3:05 PM, Andrew Raibeck wrote: > Hi Zoltan, > > It could be the simple act of enumerating file systems or mount points > that causes a problem. What kinds of problems, specifically, are you seeing? > > A couple of thoughts (not sure these will help): > > - Does this show up as a separate file system, such as when you do df -m? > If yes, you could try exclude.fs /tmp/SECUPD > > - Another possibility is to define it as a virtual mount point using > the VIRTUALMOUNTPOINT option, then using exclude.fs. > > Finally, a total "shot in the dark", but try searching the internet > for this directory name. One discussion I found indicates that > /tmp/SECUPD is causing other issues, too: > > https://urldefense.proofpoint.com/v2/url?u=http-3A__en.community.dell.com_support-2Dforums_servers_f_956_t_19996605&d=DwIGaQ&c=AzgFQeXLLKhxSQaoFCm29A&r=uJG3UnPaeoz9naeIzbwWFddVED8ETOYHxjoACoofi2Y&m=dpyZFjUm5jdJEy7vIroIPKAZVkonlHvpInjN-PV6Njo&s=emQBeN08TImOrf5CKuScl7Pu2yElvurRtxPTdEAeZps&e= > > > Regards, > > Andy > > > > > Andrew Raibeck | IBM Spectrum Protect Level 3 | stor...@us.ibm.com > > IBM Tivoli Storage Manager links: > Product support: > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ibm.com_support_entry_portal_product_tivoli_&d=DwIGaQ&c=AzgFQeXLLKhxSQaoFCm29A&r=uJG3UnPaeoz9naeIzbwWFddVED8ETOYHxjoACoofi2Y&m=dpyZFjUm5jdJEy7vIroIPKAZVkonlHvpInjN-PV6Njo&s=ECVSfVXW6qbUJh9K4NzdycKHtgKidb30DOkhhN3vnSg&e= > > tivoli_storage_manager > > Online documentation: > https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ibm.com_support_knowledgecenter_SSGSG7_&d=DwIGaQ&c=AzgFQeXLLKhxSQaoFCm29A&r=uJG3UnPaeoz9naeIzbwWFddVED8ETOYHxjoACoofi2Y&m=dpyZFjUm5jdJEy7vIroIPKAZVkonlHvpInjN-PV6Njo&s=YvaXmgbA-vSR09gHC1JzvaVMgvi9HcpCk8dhEP9YuxA&e= > > landing/welcome_ssgsg7.html > > Product Wiki: > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ibm.com_developerworks_community_wikis_home_wiki_Tivoli-25&d=DwIGaQ&c=AzgFQeXLLKhxSQaoFCm29A&r=uJG3UnPaeoz9naeIzbwWFddVED8ETOYHxjoACoofi2Y&m=dpyZFjUm5jdJEy7vIroIPKAZVkonlHvpInjN-PV6Njo&s=i2qIxt6CveEAE0hGbd2V-kpyTFpNQgBj7tu6ei3GDZY&e= > > 20Storage%20Manager > > "ADSM: Dist Stor Manager" wrote on 2017-02-07 > 14:45:50: > > > From: Zoltan Forray > > To: ADSM-L@VM.MARIST.EDU > > Date: 2017-02-07 14:46 > > Subject: How to exclude bad Linux mountpoint Sent by: "ADSM: Dist > > Stor Manager" > > > > Ever since a certain Dell update, a ghost mountpoint of /tmp/SECUPD > > is > left > > hanging after iDRAC/OpenManage updates. This is now causing > > heartburn > for > > TSM backups. > > > > I have tried pushing down via CLOPTSET to > > > >
Re: Availability for Spectrum Protect 8.1 server software for Linux on power system
http://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.0/srv.common/r_techchg_srv_opsys_810.html Support for the following operating systems is discontinued: HP-UX Linux on Power SystemsT (big endian) Oracle Solaris /Anders Räntilä -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of PAC Brion Arnaud Sent: den 8 februari 2017 14:18 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Availability for Spectrum Protect 8.1 server software for Linux on power system Hi All, We are planning for a migration of our current TSM environment to Spectrum Protect 8.1 instances, which are deemed to be running on a Power Linux machine (Power S824L). I'm however unable to find the corresponding server software on IBM passport advantage site ... The latest version available for download for such a platform is TSM 7.1.1, as well as a maintenance level 7.1.7. Does anyone have knowledge on if SP 8.1 for Power Linux is available somewhere, or on its release date if still not existing ? Thanks a lot for any feedback ! Cheers. Arnaud ** Backup and Recovery Systems Administrator Panalpina Management Ltd., Basle, Switzerland, CIT Department Viadukstrasse 42, P.O. Box 4002 Basel/CH Phone: +41 (61) 226 11 11, FAX: +41 (61) 226 17 01 Direct: +41 (61) 226 19 78 e-mail: arnaud.br...@panalpina.com<mailto:arnaud.br...@panalpina.com> This electronic message transmission contains information from Panalpina and is confidential or privileged. This information is intended only for the person (s) named above. If you are not the intended recipient, any disclosure, copying, distribution or use or any other action based on the contents of this information is strictly prohibited. If you receive this electronic transmission in error, please notify the sender by e-mail, telephone or fax at the numbers listed above. Thank you. **
Availability for Spectrum Protect 8.1 server software for Linux on power system
Hi All, We are planning for a migration of our current TSM environment to Spectrum Protect 8.1 instances, which are deemed to be running on a Power Linux machine (Power S824L). I'm however unable to find the corresponding server software on IBM passport advantage site ... The latest version available for download for such a platform is TSM 7.1.1, as well as a maintenance level 7.1.7. Does anyone have knowledge on if SP 8.1 for Power Linux is available somewhere, or on its release date if still not existing ? Thanks a lot for any feedback ! Cheers. Arnaud ** Backup and Recovery Systems Administrator Panalpina Management Ltd., Basle, Switzerland, CIT Department Viadukstrasse 42, P.O. Box 4002 Basel/CH Phone: +41 (61) 226 11 11, FAX: +41 (61) 226 17 01 Direct: +41 (61) 226 19 78 e-mail: arnaud.br...@panalpina.com<mailto:arnaud.br...@panalpina.com> This electronic message transmission contains information from Panalpina and is confidential or privileged. This information is intended only for the person (s) named above. If you are not the intended recipient, any disclosure, copying, distribution or use or any other action based on the contents of this information is strictly prohibited. If you receive this electronic transmission in error, please notify the sender by e-mail, telephone or fax at the numbers listed above. Thank you. **
Re: How to exclude bad Linux mountpoint
Another thought: if you are seeing the client hang, try using the NFSTIMEOUT option to set a number of seconds the client will wait while trying to stat the file system, e.g., NFSTIMEOUT 10 to wait up to 10 seconds. Regards, Andy Andrew Raibeck | IBM Spectrum Protect Level 3 | stor...@us.ibm.com IBM Tivoli Storage Manager links: Product support: https://www.ibm.com/support/entry/portal/product/tivoli/tivoli_storage_manager Online documentation: http://www.ibm.com/support/knowledgecenter/SSGSG7/landing/welcome_ssgsg7.html Product Wiki: https://www.ibm.com/developerworks/community/wikis/home/wiki/Tivoli%20Storage%20Manager "ADSM: Dist Stor Manager" wrote on 2017-02-07 15:05:24: > From: Andrew Raibeck/Hartford/IBM@IBMUS > To: ADSM-L@VM.MARIST.EDU > Date: 2017-02-07 15:45 > Subject: Re: How to exclude bad Linux mountpoint > Sent by: "ADSM: Dist Stor Manager" > > Hi Zoltan, > > It could be the simple act of enumerating file systems or mount points that > causes a problem. What kinds of problems, specifically, are you seeing? > > A couple of thoughts (not sure these will help): > > - Does this show up as a separate file system, such as when you do df -m? > If yes, you could try exclude.fs /tmp/SECUPD > > - Another possibility is to define it as a virtual mount point using the > VIRTUALMOUNTPOINT option, then using exclude.fs. > > Finally, a total "shot in the dark", but try searching the internet for > this directory name. One discussion I found indicates that /tmp/SECUPD is > causing other issues, too: > > http://en.community.dell.com/support-forums/servers/f/956/t/19996605 > > Regards, > > Andy > > > > Andrew Raibeck | IBM Spectrum Protect Level 3 | stor...@us.ibm.com > > IBM Tivoli Storage Manager links: > Product support: > https://www.ibm.com/support/entry/portal/product/tivoli/tivoli_storage_manager > > Online documentation: > http://www.ibm.com/support/knowledgecenter/SSGSG7/landing/welcome_ssgsg7.html > > Product Wiki: > https://www.ibm.com/developerworks/community/wikis/home/wiki/Tivoli% > 20Storage%20Manager > > "ADSM: Dist Stor Manager" wrote on 2017-02-07 > 14:45:50: > > > From: Zoltan Forray > > To: ADSM-L@VM.MARIST.EDU > > Date: 2017-02-07 14:46 > > Subject: How to exclude bad Linux mountpoint > > Sent by: "ADSM: Dist Stor Manager" > > > > Ever since a certain Dell update, a ghost mountpoint of /tmp/SECUPD is > left > > hanging after iDRAC/OpenManage updates. This is now causing heartburn > for > > TSM backups. > > > > I have tried pushing down via CLOPTSET to > > > > exclude.dir /tmp/SECUPD > > exclude /tmp/SECUPD > > > > but neither work - TSM still tries to access/back it up. > > > > Any suggestions on how to get TSM to stop trying to access this mount? > > > > > > > > > > > > -- > > *Zoltan Forray* > > Spectrum Protect (p.k.a. TSM) Software & Hardware Administrator > > Xymon Monitor Administrator > > VMware Administrator (in training) > > Virginia Commonwealth University > > UCC/Office of Technology Services > > www.ucc.vcu.edu > > zfor...@vcu.edu - 804-828-4807 > > Don't be a phishing victim - VCU and other reputable organizations will > > never use email to request that you reply with your password, social > > security number or confidential personal information. For more details > > visit http://infosecurity.vcu.edu/phishing.html > > >
Re: How to exclude bad Linux mountpoint
Thanks for the suggestions. I forgot about the EXCLUDE.FS which seems to have done the trick since it is a filesystem (see df below). Now to roll this out to all of my Linux servers. [zforray@processor ~]$ df -m Filesystem 1M-blocksUsed Available Use% Mounted on /dev/mapper/vg_processr_sys-lv_root 200317123 11885 38% / tmpfs48339 1 48339 1% /dev/shm /dev/sdb2 477 108 344 24% /boot /dev/sdb1 100 1 100 1% /boot/efi /dev/mapper/vg_processr_sys-lv_home 50269 10818 36891 23% /home /dev/mapper/vg_processr_sys-lv_tsmarchlog 302380 480301901 1% /tsmdb2 /dev/mapper/vg_processr_sys-lv_tsmarchlog2 151190 348150843 1% /tsmarchlog2 /dev/mapper/vg_processr_sys-lv_tsmdb 403174 364843 38331 91% /tsmdb /dev/mapper/vg_processr_sys-lv_tsmlog 129016 120165 2298 99% /tsmlog /dev/mapper/vg_processr_pool-lv_tsmpool 10133861 9618741 344 100% /tsmpool /dev/mapper/vg_processr_sys-lv_var 14991 878 13346 7% /var /dev/sdd 2 0 2 0% /tmp/SECUPD /dev/sde 2 0 2 0% /tmp/SECUPD On Tue, Feb 7, 2017 at 3:05 PM, Andrew Raibeck wrote: > Hi Zoltan, > > It could be the simple act of enumerating file systems or mount points that > causes a problem. What kinds of problems, specifically, are you seeing? > > A couple of thoughts (not sure these will help): > > - Does this show up as a separate file system, such as when you do df -m? > If yes, you could try exclude.fs /tmp/SECUPD > > - Another possibility is to define it as a virtual mount point using the > VIRTUALMOUNTPOINT option, then using exclude.fs. > > Finally, a total "shot in the dark", but try searching the internet for > this directory name. One discussion I found indicates that /tmp/SECUPD is > causing other issues, too: > > http://en.community.dell.com/support-forums/servers/f/956/t/19996605 > > Regards, > > Andy > > > > > Andrew Raibeck | IBM Spectrum Protect Level 3 | stor...@us.ibm.com > > IBM Tivoli Storage Manager links: > Product support: > https://www.ibm.com/support/entry/portal/product/tivoli/ > tivoli_storage_manager > > Online documentation: > http://www.ibm.com/support/knowledgecenter/SSGSG7/ > landing/welcome_ssgsg7.html > > Product Wiki: > https://www.ibm.com/developerworks/community/wikis/home/wiki/Tivoli% > 20Storage%20Manager > > "ADSM: Dist Stor Manager" wrote on 2017-02-07 > 14:45:50: > > > From: Zoltan Forray > > To: ADSM-L@VM.MARIST.EDU > > Date: 2017-02-07 14:46 > > Subject: How to exclude bad Linux mountpoint > > Sent by: "ADSM: Dist Stor Manager" > > > > Ever since a certain Dell update, a ghost mountpoint of /tmp/SECUPD is > left > > hanging after iDRAC/OpenManage updates. This is now causing heartburn > for > > TSM backups. > > > > I have tried pushing down via CLOPTSET to > > > > exclude.dir /tmp/SECUPD > > exclude /tmp/SECUPD > > > > but neither work - TSM still tries to access/back it up. > > > > Any suggestions on how to get TSM to stop trying to access this mount? > > > > > > > > > > > > -- > > *Zoltan Forray* > > Spectrum Protect (p.k.a. TSM) Software & Hardware Administrator > > Xymon Monitor Administrator > > VMware Administrator (in training) > > Virginia Commonwealth University > > UCC/Office of Technology Services > > www.ucc.vcu.edu > > zfor...@vcu.edu - 804-828-4807 > > Don't be a phishing victim - VCU and other reputable organizations will > > never use email to request that you reply with your password, social > > security number or confidential personal information. For more details > > visit http://infosecurity.vcu.edu/phishing.html > > > -- *Zoltan Forray* Spectrum Protect (p.k.a. TSM) Software & Hardware Administrator Xymon Monitor Administrator VMware Administrator (in training) Virginia Commonwealth University UCC/Office of Technology Services www.ucc.vcu.edu zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html
Re: How to exclude bad Linux mountpoint
Hi Zoltan, It could be the simple act of enumerating file systems or mount points that causes a problem. What kinds of problems, specifically, are you seeing? A couple of thoughts (not sure these will help): - Does this show up as a separate file system, such as when you do df -m? If yes, you could try exclude.fs /tmp/SECUPD - Another possibility is to define it as a virtual mount point using the VIRTUALMOUNTPOINT option, then using exclude.fs. Finally, a total "shot in the dark", but try searching the internet for this directory name. One discussion I found indicates that /tmp/SECUPD is causing other issues, too: http://en.community.dell.com/support-forums/servers/f/956/t/19996605 Regards, Andy Andrew Raibeck | IBM Spectrum Protect Level 3 | stor...@us.ibm.com IBM Tivoli Storage Manager links: Product support: https://www.ibm.com/support/entry/portal/product/tivoli/tivoli_storage_manager Online documentation: http://www.ibm.com/support/knowledgecenter/SSGSG7/landing/welcome_ssgsg7.html Product Wiki: https://www.ibm.com/developerworks/community/wikis/home/wiki/Tivoli%20Storage%20Manager "ADSM: Dist Stor Manager" wrote on 2017-02-07 14:45:50: > From: Zoltan Forray > To: ADSM-L@VM.MARIST.EDU > Date: 2017-02-07 14:46 > Subject: How to exclude bad Linux mountpoint > Sent by: "ADSM: Dist Stor Manager" > > Ever since a certain Dell update, a ghost mountpoint of /tmp/SECUPD is left > hanging after iDRAC/OpenManage updates. This is now causing heartburn for > TSM backups. > > I have tried pushing down via CLOPTSET to > > exclude.dir /tmp/SECUPD > exclude /tmp/SECUPD > > but neither work - TSM still tries to access/back it up. > > Any suggestions on how to get TSM to stop trying to access this mount? > > > > > > -- > *Zoltan Forray* > Spectrum Protect (p.k.a. TSM) Software & Hardware Administrator > Xymon Monitor Administrator > VMware Administrator (in training) > Virginia Commonwealth University > UCC/Office of Technology Services > www.ucc.vcu.edu > zfor...@vcu.edu - 804-828-4807 > Don't be a phishing victim - VCU and other reputable organizations will > never use email to request that you reply with your password, social > security number or confidential personal information. For more details > visit http://infosecurity.vcu.edu/phishing.html >
Re: How to exclude bad Linux mountpoint
On 02/07/2017 01:45 PM, Zoltan Forray wrote: > Ever since a certain Dell update, a ghost mountpoint of /tmp/SECUPD is left > hanging after iDRAC/OpenManage updates. This is now causing heartburn for > TSM backups. > > I have tried pushing down via CLOPTSET to > > exclude.dir /tmp/SECUPD > exclude /tmp/SECUPD > > but neither work - TSM still tries to access/back it up. > > Any suggestions on how to get TSM to stop trying to access this mount? > You might try "exclude.fs /tmp/SECUPD" or "domain ALL-LOCAL -/tmp/SECUPD", but even with either/both of those, you may still get a hung client. If so, moving into the realm of kludges, maybe you could also mount some other filesystem (real, loop-mount an ISO or something, or bind-mount some other directory) at that same mount point. That might get the TSM client past the hang. (Or it could cause more problems. Best option would still be to try to resolve the ghost/stale mount itself.) -- Hello World.David Bronder - Systems Architect Segmentation Fault ITS-EI, Univ. of Iowa Core dumped, disk trashed, quota filled, soda warm. david-bron...@uiowa.edu
How to exclude bad Linux mountpoint
Ever since a certain Dell update, a ghost mountpoint of /tmp/SECUPD is left hanging after iDRAC/OpenManage updates. This is now causing heartburn for TSM backups. I have tried pushing down via CLOPTSET to exclude.dir /tmp/SECUPD exclude /tmp/SECUPD but neither work - TSM still tries to access/back it up. Any suggestions on how to get TSM to stop trying to access this mount? -- *Zoltan Forray* Spectrum Protect (p.k.a. TSM) Software & Hardware Administrator Xymon Monitor Administrator VMware Administrator (in training) Virginia Commonwealth University UCC/Office of Technology Services www.ucc.vcu.edu zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html
Re: TSM Server on CentOS Linux
Hi,
If the TSM installation script haven't change since in installed 7.1.3
on CentOS 6, the attached script 'rpm.bash' should do the trick. To
use the script you have to rename the program '/bin/rpm' to
'/bin/rpmbin' and make the script you new '/bin/rpm' and make it
executable.
Let us know if it works,
Paul-André
__
*Paul-André Chassé*, B. Sc.
Analyste de l'informatique - Centre de calcul scientifique (John-S.-Bourque)
Service des technologies de l'information
Université de Sherbrooke
Tél. : 819 821-8000, poste 62582
Courriel : paul-andre.cha...@usherbrooke.ca
Le 2017-02-01 à 03:56, Sasa Drnjevic a écrit :
On 31.1.2017. 23:25, .Maurizio TERUZZI wrote:
Hello Mike,
thanks for you quick reply.
I'll try it tomorrow, it's time to go bed.
Thanks Maurizio
FYI.
If...
# install.sh -g -vmargs "-DBYPASS_TSM_REQ_CHECKS=true"
...doesn't help on CentOS 6/7 (and I think it won't for the
TSM versions after 7.1.3 or higher), here is why:
https://www-01.ibm.com/support/docview.wss?uid=swg21990168&myns=swgtiv&mynp=OCSSSQWC&mync=E&cm_sp=swgtiv-_-OCSSSQWC-_-E
My solution was to make dummy packages (for CentOS 6 and 7) with the
exact following names:
redhat-release-server-6Server-6.8.0.5.el6.x86_64.rpm
redhat-release-server-7.2-7.2.9.el7.x86_64.rpm
So after installation of the dummy rpm on CentOS 6 or 7, the TSM check
returns the correct output:
centos6# rpm -qa --queryformat '%{RELEASE}\n' redhat-release* |grep \\.
6.8.0.5.el6
or
centos67# rpm -qa --queryformat '%{RELEASE}\n' redhat-release* |grep \\.
7.2.9.el7
Here are the spec files for creating the dummy rpms.
CentOS 7 "redhat-release-server.spec"
===
Summary: Empty RedHat Linux release file
Name: redhat-release-server
Version: 7.2
Release: 7.2.9.el7
License: GPLv2
Group: System Environment/Base
Source: ftp://localhost
URL: http://localhost
Packager: Santa Claus
%description
Empty (dummy) IBM Tivoli Storage Manager dependency RPM package
%files
/usr/local/etc/redhat-release
===
CentOS 6 "redhat-release-server.spec"
===
Summary: Empty RedHat Linux release file
Name: redhat-release-server
Version: 6Server
Release: 6.8.0.5.el6
License: Public
Group: System Environment/Base
Source: ftp://localhost
URL: http://localhost
Packager: Santa Claus
%description
Empty (dummy) IBM Tivoli Storage Manager dependency RPM package
%files
/usr/local/etc/redhat-release
===
You can put anything in /usr/local/etc/redhat-release cause it's there
just to make the rpm non-empty, and the TSM only checks if the correct
rpm is installed.
Regards,
--
Sasa Drnjevic
www.srce.unizg.hr
#!/bin/bash
ALLARGS=$@
if [ "$ALLARGS" == "-qa --queryformat %{RELEASE}\n redhat-release*" ]
then
rpm -qa --queryformat '%{RELEASE}\n' centos-release*
else
/bin/rpmbin $@
fi
Re: TSM Server on CentOS Linux
Hi,
On my homelab, I personnaly install IIM first and then put the vmargs in the
imcl.ini file (/opt/IBM/InstallationManager/eclipse/tools/imcl.ini).
The dash in -DBYPASS_TSM_REQ_CHECKS=true is required and the flag must be added
on a new line after the -vmargs flag.
--
Best regards / Cordialement / مع تحياتي
Erwann SIMON
- Mail original -
De: "Sasa Drnjevic"
À: ADSM-L@VM.MARIST.EDU
Envoyé: Mercredi 1 Février 2017 09:56:51
Objet: Re: [ADSM-L] TSM Server on CentOS Linux
On 31.1.2017. 23:25, .Maurizio TERUZZI wrote:
> Hello Mike,
>
> thanks for you quick reply.
>
> I'll try it tomorrow, it's time to go bed.
>
>
> Thanks Maurizio
FYI.
If...
# install.sh -g -vmargs "-DBYPASS_TSM_REQ_CHECKS=true"
...doesn't help on CentOS 6/7 (and I think it won't for the
TSM versions after 7.1.3 or higher), here is why:
https://www-01.ibm.com/support/docview.wss?uid=swg21990168&myns=swgtiv&mynp=OCSSSQWC&mync=E&cm_sp=swgtiv-_-OCSSSQWC-_-E
My solution was to make dummy packages (for CentOS 6 and 7) with the
exact following names:
redhat-release-server-6Server-6.8.0.5.el6.x86_64.rpm
redhat-release-server-7.2-7.2.9.el7.x86_64.rpm
So after installation of the dummy rpm on CentOS 6 or 7, the TSM check
returns the correct output:
centos6# rpm -qa --queryformat '%{RELEASE}\n' redhat-release* |grep \\.
6.8.0.5.el6
or
centos67# rpm -qa --queryformat '%{RELEASE}\n' redhat-release* |grep \\.
7.2.9.el7
Here are the spec files for creating the dummy rpms.
CentOS 7 "redhat-release-server.spec"
===
Summary: Empty RedHat Linux release file
Name: redhat-release-server
Version: 7.2
Release: 7.2.9.el7
License: GPLv2
Group: System Environment/Base
Source: ftp://localhost
URL: http://localhost
Packager: Santa Claus
%description
Empty (dummy) IBM Tivoli Storage Manager dependency RPM package
%files
/usr/local/etc/redhat-release
===
CentOS 6 "redhat-release-server.spec"
===
Summary: Empty RedHat Linux release file
Name: redhat-release-server
Version: 6Server
Release: 6.8.0.5.el6
License: Public
Group: System Environment/Base
Source: ftp://localhost
URL: http://localhost
Packager: Santa Claus
%description
Empty (dummy) IBM Tivoli Storage Manager dependency RPM package
%files
/usr/local/etc/redhat-release
===
You can put anything in /usr/local/etc/redhat-release cause it's there
just to make the rpm non-empty, and the TSM only checks if the correct
rpm is installed.
Regards,
--
Sasa Drnjevic
www.srce.unizg.hr
Re: TSM Server on CentOS Linux
On 31.1.2017. 23:25, .Maurizio TERUZZI wrote:
> Hello Mike,
>
> thanks for you quick reply.
>
> I'll try it tomorrow, it's time to go bed.
>
>
> Thanks Maurizio
FYI.
If...
# install.sh -g -vmargs "-DBYPASS_TSM_REQ_CHECKS=true"
...doesn't help on CentOS 6/7 (and I think it won't for the
TSM versions after 7.1.3 or higher), here is why:
https://www-01.ibm.com/support/docview.wss?uid=swg21990168&myns=swgtiv&mynp=OCSSSQWC&mync=E&cm_sp=swgtiv-_-OCSSSQWC-_-E
My solution was to make dummy packages (for CentOS 6 and 7) with the
exact following names:
redhat-release-server-6Server-6.8.0.5.el6.x86_64.rpm
redhat-release-server-7.2-7.2.9.el7.x86_64.rpm
So after installation of the dummy rpm on CentOS 6 or 7, the TSM check
returns the correct output:
centos6# rpm -qa --queryformat '%{RELEASE}\n' redhat-release* |grep \\.
6.8.0.5.el6
or
centos67# rpm -qa --queryformat '%{RELEASE}\n' redhat-release* |grep \\.
7.2.9.el7
Here are the spec files for creating the dummy rpms.
CentOS 7 "redhat-release-server.spec"
===
Summary: Empty RedHat Linux release file
Name: redhat-release-server
Version: 7.2
Release: 7.2.9.el7
License: GPLv2
Group: System Environment/Base
Source: ftp://localhost
URL: http://localhost
Packager: Santa Claus
%description
Empty (dummy) IBM Tivoli Storage Manager dependency RPM package
%files
/usr/local/etc/redhat-release
===
CentOS 6 "redhat-release-server.spec"
===
Summary: Empty RedHat Linux release file
Name: redhat-release-server
Version: 6Server
Release: 6.8.0.5.el6
License: Public
Group: System Environment/Base
Source: ftp://localhost
URL: http://localhost
Packager: Santa Claus
%description
Empty (dummy) IBM Tivoli Storage Manager dependency RPM package
%files
/usr/local/etc/redhat-release
===
You can put anything in /usr/local/etc/redhat-release cause it's there
just to make the rpm non-empty, and the TSM only checks if the correct
rpm is installed.
Regards,
--
Sasa Drnjevic
www.srce.unizg.hr
