Antwort: Re: [ADSM-L] Antwort: Re: [ADSM-L] syslog

Hi Remco, you're right, the severity inside TSM is not applied to the severity within SYSLOG. If IBM would do so I would have one problem less to tackle with ;-) Maybe time for an RFE ;-) best regards, Rainer Von:"Remco Post" An: ADSM-L@VM.MARIST.EDU Datum:

Re: windows server 2016

Actually, the false "nested directories" error/message was a bug introduced in 8.1.0.0 (hit many of our Linux boxes first and then popped up on a few Windows servers) and fixed in 8.1.0.2. On Wed, Sep 20, 2017 at 1:25 PM, Rick Adamson wrote: > Win2016 support started

Re: Antwort: Re: [ADSM-L] syslog

> On 20 Sep 2017, at 09:23, Rainer Holzinger > wrote: > > Hi Remco, > > I can confirm IBM's information. > SYSLOG records are coming in via syslog facility 'user' and severity > 'info’. Hi Rainer, I’m now guessing all are of sev. info, not reflecting the

Re: windows server 2016

As long as we are talking about Windows Server 2016, I thought I would take the opportunity to share this link, which is a wrapper for some recent developerWorks wiki articles on using IBM Spectrum Protect to back up and recover \Windows Server 2016 and Windows 10:

Re: windows server 2016

Win2016 support started with client level 8.1, however there were a couple of issues with it like problems installing from a network share and limits on nested directories that were addressed in 8.2 -Rick Adamson -Original Message- From: ADSM: Dist Stor Manager

windows server 2016

Just checking to see if I am reading correctly. Does windows server 2016 require the v8 client? It appears so from the web pages. Sometimes the screen reading software scrambles the tables. Thanks for the help.

Re: ANS1357S after upgrade to V8.1.2 Server

Hi Bill, This document describes client/server compatibility: http://www.ibm.com/support/docview.wss?uid=swg21053218 In your case, is it possible that the node or admin had, at some time, authenticated using an 8.1.2 client? For affected nodes, check the SESSIONSECURITY setting, see if it is

Re: ANS1357S after upgrade to V8.1.2 Server

Not it. It stopped working once I upgrade to V8.1.2. Worked fine at Server V8.1.1 and V7.1.7. I'm looking for a document that says what client versions are support at the V8.1.2 server level. Since 8.1.2 is forcing TLS12. -Original Message- From: ADSM: Dist Stor Manager

Re: rebinding objects for API client archives

Content preview: Yep that's correct. We actually create a separate management class for every archive because we know our clients will want to change it. Fortunately TSM supports an unlimited number of management classes... [...] Content analysis details: (0.7 points, 5.0 required)

Re: rebinding objects for API client archives

Hello, during execution of expiration process on TSM/SP server each backed up/archived object is processed, currently active backup/archive copy group retention (versions and/or days) is applied. Based on result if object is eligible for deletion, it is deleted; otherwise object is kept until

Re: rebinding objects for API client archives

I think I'm confused (not unusual!). Rebinding is CHANGING the MgtClass an object is bound to, NOT changing the policies within a MgtClass. If we just change the policies of the MgtClass to retain the archive for 12 years, that WILL work. What WON'T work is creating a NEW MgtClass with 12

rebinding objects for API client archives

We have a TSM instance that is dedicated to "applications". These are applications that use the API client to store some kind of object in TSM. An example is IBM Content Manager. Nodes are in domains with a default Mgt Class with 7 years retention, and store their data as Archives, although

Antwort: Re: [ADSM-L] syslog

Hi Remco, I can confirm IBM's information. SYSLOG records are coming in via syslog facility 'user' and severity 'info'. Best regards, Rainer Von:"Remco Post" An: ADSM-L@VM.MARIST.EDU Datum: 19.09.2017 22:47 Betreff:Re: [ADSM-L] syslog Gesendet von: