Updating tivoli backup client

The Bucky Backup Support Team recommends using POLLING.

updating tivoli backup client-81updating tivoli backup client-57

I've tried uninstalling the client, following the technote as closely as I could, and using the provided with the client to try and reset the DB backup node, but nothing has worked so far to correct this issue. __________________________ Matthew Mc Geary Senior Technical Specialist Information Technology T: (306) 933-8921 more information on Nutrien's email policy or to unsubscribe, click here: https:// Pour plus de renseignements sur la politique de courrier ? sabonnez, cliquez ici : https:// For more information on Nutrien's email policy or to unsubscribe, click here: https:// Pour plus de renseignements sur la politique de courrier électronique d’Nutrien ou pour vous désabonnez, cliquez ici : https:// This message was imported via the External Phorum Mail Module Looks like there is some nasty bug with BAC 8.1.4.1 itself: DB backup doesn't work on a clean installation of TSM server V8.1.4.0 with BAC 8.1.4.1 and rollback to BAC 8.1.4.0 didn't help.

-----Original Message----- From: ADSM: Dist Stor Manager On Behalf Of Anders Rantila Sent: Monday, April 2, 2018 PM To: [email protected] EDU Subject: Re: [ADSM-L] Unable to backup SP database after 8.1.5 server/8.1.4 client update Hi I had the same problem.

I've tried uninstalling the client, following the technote as closely as I could, and using the provided with the client to try and reset the DB backup node, but nothing has worked so far to correct this issue. __________________________ Matthew Mc Geary Senior Technical Specialist Information Technology T: (306) 933-8921 more information on Nutrien's email policy or to unsubscribe, click here: https:// Pour plus de renseignements sur la politique de courrier ?

There are 2 methods of communication for the TSM client scheduler: PROMPTED and POLLING.

The solution is to use client 8.1.4.1 ftp://ftp.com/storage/tivoli-storage-management/patches/client/v8r1/Windows/x64/v814/8.1.4.1-TIV-TSMBAC-Win X64Best Regards Anders Räntilä =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= RÄNKAB - Räntilä Konsult AB Klippingvägen 23 SE-196 32 Kungsängen Sweden Email: [email protected]: 46 701 489 431 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= -----Original Message----- From: ADSM: Dist Stor Manager [mailto: [email protected] EDU] On Behalf Of Matthew Mc Geary Sent: den 2 april 2018 To: [email protected] EDU Subject: [ADSM-L] Unable to backup SP database after 8.1.5 server/8.1.4 client update Hey folks, I'm in a bit of bind, did a update to 8.1.5 on a pair of remote servers as a way of easing into this new security stuff and working out the kinks before it rolls out to the larger servers.

I've tried uninstalling the client, following the technote as closely as I could, and using the provided with the client to try and reset the DB backup node, but nothing has worked so far to correct this issue. __________________________ Matthew Mc Geary Senior Technical Specialist Information Technology T: (306) 933-8921 more information on Nutrien's email policy or to unsubscribe, click here: https:// Pour plus de renseignements sur la politique de courrier ? sabonnez, cliquez ici : https:// This message was imported via the External Phorum Mail Module Anders, Thanks for the tip.

If your firewall does not permit outbound connections you may wish to permit connections to the server's IP address, and at least to the port(s) that the TSM server is using.

You may also need to permit "related" connections through the firewall also.

Support has pointed me to this technote: https://urldefense.proofpoint.com/v2/url?

u=http-3A__www-2D01com_support_docview.wss-3Fuid-3Dswg22009265&d=Dw IFAw&c=zg Hs Tq BQk GAd Nuo PRx Uz SQ&r=8bo J5U4b Jexv Rn8n Mj F_e Hn4i8OKnx LC20H4-Njk Lr0&m=FMLa Aqm3l UBmv XPEPMLGk VK3i VZ4w MEjp5o Xl S6l2bw&s=F7574e8KQwpc Esy H4DAcoe5Ztwh3Gbraw Obe5gf8Lss&e= but the referenced in the note DOES NOT EXIST, so I'm not able to run the update command to re-set the node password for the DB backup node.

To change the client scheduler mode, look in or for the SCHEDMODE directive and change it from PROMPTED to POLLING. You will need to save your changes & restart the TSM client scheduler for it to take effect.