Hi all,
I'm wondering why the dedup cache file (TSMDEDUPDB_servernamenodename.DB,
located in the dedupcachepath directory) is not excluded by default ?
I generally exclude it because it causes somes retries and do think that
there's no need to back it up. But I may be wrong.
So, must we really
So what we need is a server option
SESSIONSECFORCE TRANSITIONAL
Only able to be set by editing dsmserv.opt and defaulting to NO. If its set
then the automatic update to SESSIONSECURITY strict is not permitted.
Update everything you need to then turn the option off.
I understand why
There is a known and somewhat documented restriction where an administrative ID
which connects to a New (7.1.8 or 8.1.2+) server from a New dsmadmc client,
cannot connect from an Old administrative client anymore, because
SESSIONSECURITY has been switched to STRICT.
I have now discovered that
Well, I was just thinking along... I won't bother you again.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Remco
Post
Sent: woensdag 21 februari 2018 17:53
To: ADSM-L@VM.MARIST.EDU
Subject: Re: empty containers?
I don’t know, nor do I care
