Re: syslog

2017-08-23 Thread Shawn Drew 

I think this syntax is specific to rsyslog (which you probably have)
When you put it in the conf, make sure it is above the line for the
messages file

if $programname == 'dsmserv' and not ($msg contains 'REPORTING_ADMIN')
and not ($msg contains 'ANR8592I') then /var/log/dsmserv.log
& @splunkserver.intranet
& ~

That is 3 lines, in case it wraps.
Line 1) I am filtering out messages that are created by a specific
data-collector service account (connects every 5 minutes) and a specific
informational message.  Make sure and setup logrotation for this log
Line 2) Duplicate the log msg previously described and also send it to
"splunkserver.intranet"
Line 3) Any log already filtered, do not include in any further logging.
This prevents TSM logs from also showing up in the messages file but
needs to be before the messages line in the conf for this to work.


This sends the message using the standard syslog protocol to
"splunkserver.intranet".  That server receives the message using the its
own standard rsyslog installation (needs to be configured to receive
syslog)  Then splunk will monitor the messages file and load it into the
index.  You can then use splunk filters if you want to move it to a
separate index or whatever. I have all the TSM/DataDomain stuff going
into an isolated index.  I think splunk can be configured to receive
syslog messages directly but we don't do it that way (I don't run the
splunk server)



On 8/23/2017 3:56 PM, Remco Post wrote:

Tell me more, please. I'm quite sure that there is Splunk in my future as well, 
can you share your syslog config?

Re: syslog

2017-08-23 Thread Remco Post 
Tell me more, please. I'm quite sure that there is Splunk in my future as well, 
can you share your syslog config?

-- 

Remco Post
re...@plcs.nl
06-248 21 622

> Op 23 aug. 2017 om 19:12 heeft Shawn Drew  het volgende 
> geschreven:
> 
> Yes, they ninja-added this is 7.1.4
> I enabled it and now I can collect all TSM actlogs and use syslog to forward 
> to splunk without a splunk agent and without the weird formatting of the 
> filetextexit. I wish they had this on all the architectures.
> You can use the syslog utilities to do filtering if you want also.
> 
>> On Aug 23, 2017, 11:08 AM -0400, Remco Post , wrote:
>> Hi all,
>> 
>> I read something nice in the TSM server manual: TSM now supports logging to 
>> syslog on Linux (and, it no longer supports SNMP). Now, my customer has a 
>> very specific policy: certain events must be logged to an off-host logging 
>> facility. The current solution is to write those events to a filetextexit 
>> and copy these events once a minute to a remote host. Brrr. So, I was 
>> wondering: has anyone done anything with TSM and syslog and forwarded the 
>> syslog events to another host for further processing?
>> 
>> --
>> 
>> 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: error retrieving archives

2017-08-23 Thread David Jelinek 
On 08/23/2017 03:00 PM, Skylar Thompson wrote:

> Is the original filesystem different from the destination filesystem? It
> looks like the destination filesystem is having issues with the extended
> attributes TSM has stored for the archived files.

Most likely, at least different versions.

--
Have a wonderful day,
David Jelinek

Re: error retrieving archives

2017-08-23 Thread Skylar Thompson 
 Content preview:  Is the original filesystem different from the destination
   filesystem? It looks like the destination filesystem is having issues with
the extended attributes TSM has stored for the archived files. On Wed, Aug
23, 2017 at 02:51:34PM -0400, David Jelinek wrote: > 08/23/2017 10:15:58
   ANS1587W Unable to read extended attributes for > object 
/mnt/tsm/linux/aux-jet/shared/data1/20161002/BMW
due to errno: > 34, reason: Numerical result out of range > 08/23/2017 
10:15:58
ANS0361I DIAG: TransErrno: Unexpected error from > psGetXattrNameList, errno
= 34 > > The linux machine I am attempting to retrieve on is not the same
> physical machine, but is the same node name. The retrieve is being done
> from root (the archive was also done from root on the former machine).
   > > Many files retrieve ok I am retrieving to a new location. The retrieve
> command is: > > dsmc retrieve "/shared/data1/*" > 
/mnt/tsm/linux/aux-jet/shared/data1/20161204/
-subdir=yes > -tod=12/31/2016 -fromdate=11/08/2016 > > The directories are
shared out from the original box to a number of system. > > Is there any
   way for me to retrieve these files? > > > -- > Have a wonderful day, > David
Jelinek [...]

 Content analysis details:   (0.7 points, 5.0 required)

  pts rule name  description
  -- --
  0.7 SPF_NEUTRALSPF: sender does not match SPF record (neutral)
 -0.0 RP_MATCHES_RCVDEnvelope sender domain matches handover relay 
domain
X-Barracuda-Connect: mx.gs.washington.edu[128.208.8.134]
X-Barracuda-Start-Time: 1503514803
X-Barracuda-Encrypted: ECDHE-RSA-AES256-GCM-SHA384
X-Barracuda-URL: https://148.100.49.28:443/cgi-mod/mark.cgi
X-Barracuda-Scan-Msg-Size: 1404
X-Virus-Scanned: by bsmtpd at marist.edu
X-Barracuda-BRTS-Status: 1
X-Barracuda-Spam-Score: 0.00
X-Barracuda-Spam-Status: No, SCORE=0.00 using global scores of TAG_LEVEL=3.5 
QUARANTINE_LEVEL=1000.0 KILL_LEVEL=5.5 tests=
X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.42237
Rule breakdown below
 pts rule name  description
 -- 
--

Is the original filesystem different from the destination filesystem? It
looks like the destination filesystem is having issues with the extended
attributes TSM has stored for the archived files.

On Wed, Aug 23, 2017 at 02:51:34PM -0400, David Jelinek wrote:
> 08/23/2017 10:15:58 ANS1587W Unable to read extended attributes for
> object /mnt/tsm/linux/aux-jet/shared/data1/20161002/BMW due to errno:
> 34, reason: Numerical result out of range
> 08/23/2017 10:15:58 ANS0361I DIAG: TransErrno: Unexpected error from
> psGetXattrNameList, errno = 34
>
> The linux machine I am attempting to retrieve on is not the same
> physical machine, but is the same node name. The retrieve is being done
> from root (the archive was also done from root on the former machine).
>
> Many files retrieve ok I am retrieving to a new location. The retrieve
> command is:
>
> dsmc retrieve "/shared/data1/*"
> /mnt/tsm/linux/aux-jet/shared/data1/20161204/ -subdir=yes
> -tod=12/31/2016 -fromdate=11/08/2016
>
> The directories are shared out from the original box to a number of system.
>
> Is there any way for me to retrieve these files?
>
>
> --
> Have a wonderful day,
> David Jelinek

--
-- Skylar Thompson (skyl...@u.washington.edu)
-- Genome Sciences Department, System Administrator
-- Foege Building S046, (206)-685-7354
-- University of Washington School of Medicine

error retrieving archives

2017-08-23 Thread David Jelinek 
08/23/2017 10:15:58 ANS1587W Unable to read extended attributes for
object /mnt/tsm/linux/aux-jet/shared/data1/20161002/BMW due to errno:
34, reason: Numerical result out of range
08/23/2017 10:15:58 ANS0361I DIAG: TransErrno: Unexpected error from
psGetXattrNameList, errno = 34

The linux machine I am attempting to retrieve on is not the same
physical machine, but is the same node name. The retrieve is being done
from root (the archive was also done from root on the former machine).

Many files retrieve ok I am retrieving to a new location. The retrieve
command is:

dsmc retrieve "/shared/data1/*"
/mnt/tsm/linux/aux-jet/shared/data1/20161204/ -subdir=yes
-tod=12/31/2016 -fromdate=11/08/2016

The directories are shared out from the original box to a number of system.

Is there any way for me to retrieve these files?


--
Have a wonderful day,
David Jelinek

Re: syslog

2017-08-23 Thread Shawn Drew 
Yes, they ninja-added this is 7.1.4
I enabled it and now I can collect all TSM actlogs and use syslog to forward to 
splunk without a splunk agent and without the weird formatting of the 
filetextexit. I wish they had this on all the architectures.
You can use the syslog utilities to do filtering if you want also.

On Aug 23, 2017, 11:08 AM -0400, Remco Post , wrote:
> Hi all,
>
> I read something nice in the TSM server manual: TSM now supports logging to 
> syslog on Linux (and, it no longer supports SNMP). Now, my customer has a 
> very specific policy: certain events must be logged to an off-host logging 
> facility. The current solution is to write those events to a filetextexit and 
> copy these events once a minute to a remote host. Brrr. So, I was wondering: 
> has anyone done anything with TSM and syslog and forwarded the syslog events 
> to another host for further processing?
>
> --
>
> Met vriendelijke groeten/Kind Regards,
>
> Remco Post
> r.p...@plcs.nl
> +31 6 248 21 622

syslog

2017-08-23 Thread Remco Post 
Hi all,

I read something nice in the TSM server manual: TSM now supports logging to 
syslog on Linux (and, it no longer supports SNMP). Now, my customer has a very 
specific policy: certain events must be logged to an off-host logging facility. 
The current solution is to write those events to a filetextexit and copy these 
events once a minute to a remote host. Brrr. So, I was wondering: has anyone 
done anything with TSM and syslog and forwarded the syslog events to another 
host for further processing?

-- 

 Met vriendelijke groeten/Kind Regards,

Remco Post
r.p...@plcs.nl
+31 6 248 21 622

Re: tracefile option

2017-08-23 Thread Lee, Gary 
That did it.

Dsm.opt.

Wish it were better documented, like in the manuals.



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Loon, 
Eric van (ITOPT3) - KLM
Sent: Wednesday, August 23, 2017 10:14 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] tracefile option

Hi Gary!
Shouldn't TRACEFILE and TRACEFLAGS be specified in the dsm.opt instead of the 
dsm.sys?
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 Lee, 
Gary
Sent: woensdag 23 augustus 2017 15:25
To: ADSM-L@VM.MARIST.EDU
Subject: Re: tracefile option

On executing dsmc, I receive the following.

root@bb-dm01 bin]# dsmc 
ANS1036S The option 'TRACEFILE' or the value supplied for it is not valid. It wa
s found in options file '/opt/tivoli/tsm/client/ba/bin/dsm.sys' 
 
  at line number: 18
  
  The complete entry: '  tracefile  /root/trace.out'
  

[ root@bb-dm01 bin]#
  


Any ideas?

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan 
Forray
Sent: Wednesday, August 23, 2017 9:18 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] tracefile option

Or perhaps this:

https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww-01.ibm.com%2Fsupport%2Fdocview.wss%3Fuid%3Dswg21696736=02%7C01%7Cglee%40BSU.EDU%7C4abd6c97fa984946a34308d4ea29e4fd%7C6fff909f07dc40da9e30fd7549c0f494%7C0%7C0%7C636390913033705401=esznddRKQmyA85LvvxGbVuQNWXblEY7SHn9UedHcNlI%3D=0

1. Enable VM client-side tracing. This is done in the datamovers options file 
TRACEFLAGS VM ENTER EXIT PID TID GENERAL TRACEFILE \VEtrace.txt

Note: The tracefile can be put in any location, the default path is the working 
directory. Ensure the path used has sufficient free disk space so it does not 
fill the disk. It is recommended to not place this on the system disk.

On Wed, Aug 23, 2017 at 9:00 AM, Lee, Gary  wrote:

> Can someone point me toward the syntax for the tracefile option?
>
> Linux Client 7.1.6.4,  used as a data mover. For tsm for VE.
> Directed by ibm support to turn on tracing, but tracefile appears to 
> be an error in the dsm.sys file.
>



--
*Zoltan Forray*
Spectrum Protect (p.k.a. TSM) Software & Hardware Administrator Xymon Monitor 
Administrator VMware Administrator Virginia Commonwealth University UCC/Office 
of Technology Services
https://na01.safelinks.protection.outlook.com/?url=www.ucc.vcu.edu=02%7C01%7Cglee%40BSU.EDU%7C4abd6c97fa984946a34308d4ea29e4fd%7C6fff909f07dc40da9e30fd7549c0f494%7C0%7C0%7C636390913033705401=L%2FCeV%2BktgrTUvk4UyEF%2FqVRKdHKrXZ300oC04nvx040%3D=0
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 
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Finfosecurity.vcu.edu%2Fphishing.html=02%7C01%7Cglee%40BSU.EDU%7C4abd6c97fa984946a34308d4ea29e4fd%7C6fff909f07dc40da9e30fd7549c0f494%7C0%7C0%7C636390913033705401=6buRu2wHQ94rbd29nonV3yRGNgkeWe3Nht%2FH7A45wB8%3D=0

For information, services and offers, please visit our web site: 
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.klm.com=02%7C01%7Cglee%40BSU.EDU%7Cd2441794347845dbee9208d4ea317f35%7C6fff909f07dc40da9e30fd7549c0f494%7C0%7C0%7C636390945692013069=juP%2BWdgXbyQXp6IU%2FmohPNk%2Fyp9%2BqpGfl4ms6hzZKuo%3D=0.
 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: tracefile option

2017-08-23 Thread Loon, Eric van (ITOPT3) - KLM 
Hi Gary!
Shouldn't TRACEFILE and TRACEFLAGS be specified in the dsm.opt instead of the 
dsm.sys?
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 Lee, 
Gary
Sent: woensdag 23 augustus 2017 15:25
To: ADSM-L@VM.MARIST.EDU
Subject: Re: tracefile option

On executing dsmc, I receive the following.

root@bb-dm01 bin]# dsmc 
ANS1036S The option 'TRACEFILE' or the value supplied for it is not valid. It wa
s found in options file '/opt/tivoli/tsm/client/ba/bin/dsm.sys' 
 
  at line number: 18
  
  The complete entry: '  tracefile  /root/trace.out'
  

[ root@bb-dm01 bin]#
  


Any ideas?

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan 
Forray
Sent: Wednesday, August 23, 2017 9:18 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] tracefile option

Or perhaps this:

https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww-01.ibm.com%2Fsupport%2Fdocview.wss%3Fuid%3Dswg21696736=02%7C01%7Cglee%40BSU.EDU%7C4abd6c97fa984946a34308d4ea29e4fd%7C6fff909f07dc40da9e30fd7549c0f494%7C0%7C0%7C636390913033705401=esznddRKQmyA85LvvxGbVuQNWXblEY7SHn9UedHcNlI%3D=0

1. Enable VM client-side tracing. This is done in the datamovers options file 
TRACEFLAGS VM ENTER EXIT PID TID GENERAL TRACEFILE \VEtrace.txt

Note: The tracefile can be put in any location, the default path is the working 
directory. Ensure the path used has sufficient free disk space so it does not 
fill the disk. It is recommended to not place this on the system disk.

On Wed, Aug 23, 2017 at 9:00 AM, Lee, Gary  wrote:

> Can someone point me toward the syntax for the tracefile option?
>
> Linux Client 7.1.6.4,  used as a data mover. For tsm for VE.
> Directed by ibm support to turn on tracing, but tracefile appears to 
> be an error in the dsm.sys file.
>



--
*Zoltan Forray*
Spectrum Protect (p.k.a. TSM) Software & Hardware Administrator Xymon Monitor 
Administrator VMware Administrator Virginia Commonwealth University UCC/Office 
of Technology Services
https://na01.safelinks.protection.outlook.com/?url=www.ucc.vcu.edu=02%7C01%7Cglee%40BSU.EDU%7C4abd6c97fa984946a34308d4ea29e4fd%7C6fff909f07dc40da9e30fd7549c0f494%7C0%7C0%7C636390913033705401=L%2FCeV%2BktgrTUvk4UyEF%2FqVRKdHKrXZ300oC04nvx040%3D=0
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 
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Finfosecurity.vcu.edu%2Fphishing.html=02%7C01%7Cglee%40BSU.EDU%7C4abd6c97fa984946a34308d4ea29e4fd%7C6fff909f07dc40da9e30fd7549c0f494%7C0%7C0%7C636390913033705401=6buRu2wHQ94rbd29nonV3yRGNgkeWe3Nht%2FH7A45wB8%3D=0

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: tracefile option

2017-08-23 Thread Zoltan Forray 
Did you try on the commandline, i.e.  dsmc -tracefile= /root/trace.out

Since I have no experience with the VM client, there is the comment in the
doc on tracing in VM "This is done in the *datamovers* options file"



On Wed, Aug 23, 2017 at 9:25 AM, Lee, Gary  wrote:

> On executing dsmc, I receive the following.
>
> root@bb-dm01 bin]# dsmc
> ANS1036S The option 'TRACEFILE' or the value supplied for it is not valid.
> It wa
> s found in options file '/opt/tivoli/tsm/client/ba/bin/dsm.sys'
>   at line number: 18
>   The complete entry: '  tracefile  /root/trace.out'
>
> [ root@bb-dm01 bin]#
>
>
> Any ideas?
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
> Zoltan Forray
> Sent: Wednesday, August 23, 2017 9:18 AM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] tracefile option
>
> Or perhaps this:
>
> https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fwww-01.ibm.com%2Fsupport%2Fdocview.wss%3Fuid%
> 3Dswg21696736=02%7C01%7Cglee%40BSU.EDU%7C4abd6c97fa984946a34308d4ea29
> e4fd%7C6fff909f07dc40da9e30fd7549c0f494%7C0%7C0%
> 7C636390913033705401=esznddRKQmyA85LvvxGbVuQNWXblEY
> 7SHn9UedHcNlI%3D=0
>
> 1. Enable VM client-side tracing. This is done in the datamovers options
> file
> TRACEFLAGS VM ENTER EXIT PID TID GENERAL
> TRACEFILE \VEtrace.txt
>
> Note: The tracefile can be put in any location, the default path is the
> working directory. Ensure the path used has sufficient free disk space so
> it does not fill the disk. It is recommended to not place this on the
> system disk.
>
> On Wed, Aug 23, 2017 at 9:00 AM, Lee, Gary  wrote:
>
> > Can someone point me toward the syntax for the tracefile option?
> >
> > Linux Client 7.1.6.4,  used as a data mover. For tsm for VE.
> > Directed by ibm support to turn on tracing, but tracefile appears to be
> an
> > error in the dsm.sys file.
> >
>
>
>
> --
> *Zoltan Forray*
> Spectrum Protect (p.k.a. TSM) Software & Hardware Administrator
> Xymon Monitor Administrator
> VMware Administrator
> Virginia Commonwealth University
> UCC/Office of Technology Services
> https://na01.safelinks.protection.outlook.com/?url=
> www.ucc.vcu.edu=02%7C01%7Cglee%40BSU.EDU%
> 7C4abd6c97fa984946a34308d4ea29e4fd%7C6fff909f07dc40da9e30fd7549c0
> f494%7C0%7C0%7C636390913033705401=L%2FCeV%2BktgrTUvk4UyEF%
> 2FqVRKdHKrXZ300oC04nvx040%3D=0
> 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 https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Finfosecurity.vcu.edu%2Fphishing.html=02%
> 7C01%7Cglee%40BSU.EDU%7C4abd6c97fa984946a34308d4ea29e4fd%
> 7C6fff909f07dc40da9e30fd7549c0f494%7C0%7C0%7C636390913033705401=
> 6buRu2wHQ94rbd29nonV3yRGNgkeWe3Nht%2FH7A45wB8%3D=0
>



--
*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: 8.1.2 client and 7.1.7 servers

2017-08-23 Thread Stefan Folkerts 
>From what I understand so far (pre 8.1) the only thing that totally stopped
working on basically prehistoric clients is the scheduling services on the
client so people that need to backup for instance, an old NT 4.0 server or
something need to use some other scheduler but other than that all basics
still work with version 3 clients from what I heard...no guarantees from
me! :-P


On Wed, Aug 23, 2017 at 2:46 PM, Zoltan Forray  wrote:

> My other concern is really old, unsupported clients.  So far my OS400/BRMS
> 5.5 client is still working with 7.1.7 and we have a smattering of 6.3 and
> older unsupported clients (old Solaris, RHEL x32, Windows 2003 and until
> recently an IRIX box) so 8.1.x is not on any current schedule.
>
> On Wed, Aug 23, 2017 at 8:14 AM, Stefan Folkerts <
> stefan.folke...@gmail.com>
> wrote:
>
> > I agree Zoltan, it's very specific and I too would like for IBM to
> explain
> > what the reasoning behind the warning is.
> > Personally, I suspect it's a cover your *** type of deal, with that many
> > releases of so many different kind of clients floating around I would
> kind
> > of understand the reasoning behind something like that.
> >
> > On Wed, Aug 23, 2017 at 2:04 PM, Zoltan Forray  wrote:
> >
> > > I agree with both of your responses that it should not be an issue and
> > the
> > > "compatibility" page says it should be good as far as server/client
> > levels
> > > go.  But since the docs have the very specific warning about upgrading
> > the
> > > servers to 8.1.2 before clients or *"If you do not upgrade your servers
> > > first, communication between servers and clients might be
> > interrupted."*, I
> > > felt I should ask for empirical evidence that it wont cause problems.
> The
> > > warning was not specific on what kinds of communications problems to
> > expect
> > > or if/how they can be addresses if someone decides to download and
> > upgrade
> > > their client simply based on the "yes, 7.1 servers are compatible with
> > 8.1
> > > clients" document and didn't see the warning I read.
> > >
> > > Perhaps it is due to TLS 1.2 now turned ON by default.  Either way,
> more
> > > details/specifics from IBM would be helpful.
> > >
> > > On Wed, Aug 23, 2017 at 4:21 AM, Stefan Folkerts <
> > > stefan.folke...@gmail.com>
> > > wrote:
> > >
> > > > I agree with Eric and I have 8.2 VE setups connected to 7.1 servers
> at
> > > > multiple sites, i've never seen any issues. I do find the
> documentation
> > > > strange if it say's you need to upgrade your clients before upgrading
> > the
> > > > server. The only thing that makes sense to me is client-side dedup
> with
> > > > compression, for that you want your clients on the latest level
> > otherwise
> > > > the compression isn't compatible with the server compression and you
> > > don't
> > > > get optimal results.
> > > >
> > > > On Wed, Aug 23, 2017 at 9:17 AM, Loon, Eric van (ITOPT3) - KLM <
> > > > eric-van.l...@klm.com> wrote:
> > > >
> > > > > Nor with up-leveled clients by the way, which is the case here.
> > > > > Kind regards,
> > > > > Eric van Loon
> > > > > Air France/KLM Storage Engineering
> > > > >
> > > > >
> > > > > -Original Message-
> > > > > From: Loon, Eric van (ITOPT3) - KLM
> > > > > Sent: woensdag 23 augustus 2017 9:15
> > > > > To: ADSM-L@VM.MARIST.EDU
> > > > > Subject: RE: 8.1.2 client and 7.1.7 servers
> > > > >
> > > > > Hi Zoltan!
> > > > > The page http://www-01.ibm.com/support/docview.wss?uid=swg21053218
> > > shows
> > > > > that the SP 8.1.2 client is supported with all 8.1 and 7.1
> servers. I
> > > > have
> > > > > never encountered issues with down-leveled clients in my 20+ years
> of
> > > TSM
> > > > > history.
> > > > > 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
> > > > > Zoltan Forray
> > > > > Sent: dinsdag 22 augustus 2017 15:03
> > > > > To: ADSM-L@VM.MARIST.EDU
> > > > > Subject: 8.1.2 client and 7.1.7 servers
> > > > >
> > > > > Has anyone tried using the latest 8.1.2 clients with 7.1.7 servers?
> > I
> > > > > haven't had the chance to test such a configuration (since my lone
> > test
> > > > > server is at 8.1.1) and with the dire-warnings in the readme docs,
> I
> > > made
> > > > > sure everyone on my staff knows to NOT install 8.1.2 clients.
> > > > >
> > > > > From the readme/docs:
> > > > >
> > > > > Upgrade your IBM Spectrum Protect™ servers to Version 8.1.2 before
> > you
> > > > > upgrade the backup-archive clients.
> > > > >
> > > > >
> > > > >
> > > > > If you do not upgrade your servers first, communication between
> > servers
> > > > > and clients might be interrupted.
> > > > >
> > > > >
> > > > > --
> > > > > *Zoltan Forray*
> > > > > Spectrum Protect (p.k.a. TSM) Software & Hardware Administrator
> Xymon
> > > > > Monitor Administrator VMware

Re: tracefile option

2017-08-23 Thread Lee, Gary 
On executing dsmc, I receive the following.

root@bb-dm01 bin]# dsmc 
ANS1036S The option 'TRACEFILE' or the value supplied for it is not valid. It wa
s found in options file '/opt/tivoli/tsm/client/ba/bin/dsm.sys' 
 
  at line number: 18
  
  The complete entry: '  tracefile  /root/trace.out'
  

[ root@bb-dm01 bin]#
  


Any ideas?

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan 
Forray
Sent: Wednesday, August 23, 2017 9:18 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] tracefile option

Or perhaps this:

https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww-01.ibm.com%2Fsupport%2Fdocview.wss%3Fuid%3Dswg21696736=02%7C01%7Cglee%40BSU.EDU%7C4abd6c97fa984946a34308d4ea29e4fd%7C6fff909f07dc40da9e30fd7549c0f494%7C0%7C0%7C636390913033705401=esznddRKQmyA85LvvxGbVuQNWXblEY7SHn9UedHcNlI%3D=0

1. Enable VM client-side tracing. This is done in the datamovers options
file
TRACEFLAGS VM ENTER EXIT PID TID GENERAL
TRACEFILE \VEtrace.txt

Note: The tracefile can be put in any location, the default path is the
working directory. Ensure the path used has sufficient free disk space so
it does not fill the disk. It is recommended to not place this on the
system disk.

On Wed, Aug 23, 2017 at 9:00 AM, Lee, Gary  wrote:

> Can someone point me toward the syntax for the tracefile option?
>
> Linux Client 7.1.6.4,  used as a data mover. For tsm for VE.
> Directed by ibm support to turn on tracing, but tracefile appears to be an
> error in the dsm.sys file.
>



--
*Zoltan Forray*
Spectrum Protect (p.k.a. TSM) Software & Hardware Administrator
Xymon Monitor Administrator
VMware Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
https://na01.safelinks.protection.outlook.com/?url=www.ucc.vcu.edu=02%7C01%7Cglee%40BSU.EDU%7C4abd6c97fa984946a34308d4ea29e4fd%7C6fff909f07dc40da9e30fd7549c0f494%7C0%7C0%7C636390913033705401=L%2FCeV%2BktgrTUvk4UyEF%2FqVRKdHKrXZ300oC04nvx040%3D=0
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 
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Finfosecurity.vcu.edu%2Fphishing.html=02%7C01%7Cglee%40BSU.EDU%7C4abd6c97fa984946a34308d4ea29e4fd%7C6fff909f07dc40da9e30fd7549c0f494%7C0%7C0%7C636390913033705401=6buRu2wHQ94rbd29nonV3yRGNgkeWe3Nht%2FH7A45wB8%3D=0

Re: tracefile option

2017-08-23 Thread Zoltan Forray 
Or perhaps this:

http://www-01.ibm.com/support/docview.wss?uid=swg21696736

1. Enable VM client-side tracing. This is done in the datamovers options
file
TRACEFLAGS VM ENTER EXIT PID TID GENERAL
TRACEFILE \VEtrace.txt

Note: The tracefile can be put in any location, the default path is the
working directory. Ensure the path used has sufficient free disk space so
it does not fill the disk. It is recommended to not place this on the
system disk.

On Wed, Aug 23, 2017 at 9:00 AM, Lee, Gary  wrote:

> Can someone point me toward the syntax for the tracefile option?
>
> Linux Client 7.1.6.4,  used as a data mover. For tsm for VE.
> Directed by ibm support to turn on tracing, but tracefile appears to be an
> error in the dsm.sys file.
>



--
*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: tracefile option

2017-08-23 Thread Zoltan Forray 
I doubt if it has changed.  From this doc:
https://www.ibm.com/support/knowledgecenter/en/SSGSG7_7.1.1/com.ibm.itsm.tshoot.doc/t_pdg_enblclitraceoncli.html

Choose the location of the trace messages output by adding the following
text to the client options file: tracefile .
The tracefile name must be fully qualified, for example:

   - [image: Windows operating systems]tracefile c:\service\trace.out
   - [image: AIX operating systems][image: HP-UX operating systems][image:
   Linux operating systems][image: Oracle Solaris operating systems]tracefile
   /home/spike/trace.out
   - [image: Mac OS X operating systems]tracefile trace.txt


On Wed, Aug 23, 2017 at 9:00 AM, Lee, Gary  wrote:

> Can someone point me toward the syntax for the tracefile option?
>
> Linux Client 7.1.6.4,  used as a data mover. For tsm for VE.
> Directed by ibm support to turn on tracing, but tracefile appears to be an
> error in the dsm.sys file.
>



--
*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

tracefile option

2017-08-23 Thread Lee, Gary 
Can someone point me toward the syntax for the tracefile option?

Linux Client 7.1.6.4,  used as a data mover. For tsm for VE.
Directed by ibm support to turn on tracing, but tracefile appears to be an 
error in the dsm.sys file.

Re: 8.1.2 client and 7.1.7 servers

2017-08-23 Thread Zoltan Forray 
My other concern is really old, unsupported clients.  So far my OS400/BRMS
5.5 client is still working with 7.1.7 and we have a smattering of 6.3 and
older unsupported clients (old Solaris, RHEL x32, Windows 2003 and until
recently an IRIX box) so 8.1.x is not on any current schedule.

On Wed, Aug 23, 2017 at 8:14 AM, Stefan Folkerts 
wrote:

> I agree Zoltan, it's very specific and I too would like for IBM to explain
> what the reasoning behind the warning is.
> Personally, I suspect it's a cover your *** type of deal, with that many
> releases of so many different kind of clients floating around I would kind
> of understand the reasoning behind something like that.
>
> On Wed, Aug 23, 2017 at 2:04 PM, Zoltan Forray  wrote:
>
> > I agree with both of your responses that it should not be an issue and
> the
> > "compatibility" page says it should be good as far as server/client
> levels
> > go.  But since the docs have the very specific warning about upgrading
> the
> > servers to 8.1.2 before clients or *"If you do not upgrade your servers
> > first, communication between servers and clients might be
> interrupted."*, I
> > felt I should ask for empirical evidence that it wont cause problems. The
> > warning was not specific on what kinds of communications problems to
> expect
> > or if/how they can be addresses if someone decides to download and
> upgrade
> > their client simply based on the "yes, 7.1 servers are compatible with
> 8.1
> > clients" document and didn't see the warning I read.
> >
> > Perhaps it is due to TLS 1.2 now turned ON by default.  Either way, more
> > details/specifics from IBM would be helpful.
> >
> > On Wed, Aug 23, 2017 at 4:21 AM, Stefan Folkerts <
> > stefan.folke...@gmail.com>
> > wrote:
> >
> > > I agree with Eric and I have 8.2 VE setups connected to 7.1 servers at
> > > multiple sites, i've never seen any issues. I do find the documentation
> > > strange if it say's you need to upgrade your clients before upgrading
> the
> > > server. The only thing that makes sense to me is client-side dedup with
> > > compression, for that you want your clients on the latest level
> otherwise
> > > the compression isn't compatible with the server compression and you
> > don't
> > > get optimal results.
> > >
> > > On Wed, Aug 23, 2017 at 9:17 AM, Loon, Eric van (ITOPT3) - KLM <
> > > eric-van.l...@klm.com> wrote:
> > >
> > > > Nor with up-leveled clients by the way, which is the case here.
> > > > Kind regards,
> > > > Eric van Loon
> > > > Air France/KLM Storage Engineering
> > > >
> > > >
> > > > -Original Message-
> > > > From: Loon, Eric van (ITOPT3) - KLM
> > > > Sent: woensdag 23 augustus 2017 9:15
> > > > To: ADSM-L@VM.MARIST.EDU
> > > > Subject: RE: 8.1.2 client and 7.1.7 servers
> > > >
> > > > Hi Zoltan!
> > > > The page http://www-01.ibm.com/support/docview.wss?uid=swg21053218
> > shows
> > > > that the SP 8.1.2 client is supported with all 8.1 and 7.1 servers. I
> > > have
> > > > never encountered issues with down-leveled clients in my 20+ years of
> > TSM
> > > > history.
> > > > 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
> > > > Zoltan Forray
> > > > Sent: dinsdag 22 augustus 2017 15:03
> > > > To: ADSM-L@VM.MARIST.EDU
> > > > Subject: 8.1.2 client and 7.1.7 servers
> > > >
> > > > Has anyone tried using the latest 8.1.2 clients with 7.1.7 servers?
> I
> > > > haven't had the chance to test such a configuration (since my lone
> test
> > > > server is at 8.1.1) and with the dire-warnings in the readme docs, I
> > made
> > > > sure everyone on my staff knows to NOT install 8.1.2 clients.
> > > >
> > > > From the readme/docs:
> > > >
> > > > Upgrade your IBM Spectrum Protect™ servers to Version 8.1.2 before
> you
> > > > upgrade the backup-archive clients.
> > > >
> > > >
> > > >
> > > > If you do not upgrade your servers first, communication between
> servers
> > > > and clients might be interrupted.
> > > >
> > > >
> > > > --
> > > > *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
> > > > 
> > > > 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

Re: 8.1.2 client and 7.1.7 servers

2017-08-23 Thread Stefan Folkerts 
I agree Zoltan, it's very specific and I too would like for IBM to explain
what the reasoning behind the warning is.
Personally, I suspect it's a cover your *** type of deal, with that many
releases of so many different kind of clients floating around I would kind
of understand the reasoning behind something like that.

On Wed, Aug 23, 2017 at 2:04 PM, Zoltan Forray  wrote:

> I agree with both of your responses that it should not be an issue and the
> "compatibility" page says it should be good as far as server/client levels
> go.  But since the docs have the very specific warning about upgrading the
> servers to 8.1.2 before clients or *"If you do not upgrade your servers
> first, communication between servers and clients might be interrupted."*, I
> felt I should ask for empirical evidence that it wont cause problems. The
> warning was not specific on what kinds of communications problems to expect
> or if/how they can be addresses if someone decides to download and upgrade
> their client simply based on the "yes, 7.1 servers are compatible with 8.1
> clients" document and didn't see the warning I read.
>
> Perhaps it is due to TLS 1.2 now turned ON by default.  Either way, more
> details/specifics from IBM would be helpful.
>
> On Wed, Aug 23, 2017 at 4:21 AM, Stefan Folkerts <
> stefan.folke...@gmail.com>
> wrote:
>
> > I agree with Eric and I have 8.2 VE setups connected to 7.1 servers at
> > multiple sites, i've never seen any issues. I do find the documentation
> > strange if it say's you need to upgrade your clients before upgrading the
> > server. The only thing that makes sense to me is client-side dedup with
> > compression, for that you want your clients on the latest level otherwise
> > the compression isn't compatible with the server compression and you
> don't
> > get optimal results.
> >
> > On Wed, Aug 23, 2017 at 9:17 AM, Loon, Eric van (ITOPT3) - KLM <
> > eric-van.l...@klm.com> wrote:
> >
> > > Nor with up-leveled clients by the way, which is the case here.
> > > Kind regards,
> > > Eric van Loon
> > > Air France/KLM Storage Engineering
> > >
> > >
> > > -Original Message-
> > > From: Loon, Eric van (ITOPT3) - KLM
> > > Sent: woensdag 23 augustus 2017 9:15
> > > To: ADSM-L@VM.MARIST.EDU
> > > Subject: RE: 8.1.2 client and 7.1.7 servers
> > >
> > > Hi Zoltan!
> > > The page http://www-01.ibm.com/support/docview.wss?uid=swg21053218
> shows
> > > that the SP 8.1.2 client is supported with all 8.1 and 7.1 servers. I
> > have
> > > never encountered issues with down-leveled clients in my 20+ years of
> TSM
> > > history.
> > > 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
> > > Zoltan Forray
> > > Sent: dinsdag 22 augustus 2017 15:03
> > > To: ADSM-L@VM.MARIST.EDU
> > > Subject: 8.1.2 client and 7.1.7 servers
> > >
> > > Has anyone tried using the latest 8.1.2 clients with 7.1.7 servers?  I
> > > haven't had the chance to test such a configuration (since my lone test
> > > server is at 8.1.1) and with the dire-warnings in the readme docs, I
> made
> > > sure everyone on my staff knows to NOT install 8.1.2 clients.
> > >
> > > From the readme/docs:
> > >
> > > Upgrade your IBM Spectrum Protect™ servers to Version 8.1.2 before you
> > > upgrade the backup-archive clients.
> > >
> > >
> > >
> > > If you do not upgrade your servers first, communication between servers
> > > and clients might be interrupted.
> > >
> > >
> > > --
> > > *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
> > > 
> > > 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
> >

Re: 8.1.2 client and 7.1.7 servers

2017-08-23 Thread Zoltan Forray 
I agree with both of your responses that it should not be an issue and the
"compatibility" page says it should be good as far as server/client levels
go.  But since the docs have the very specific warning about upgrading the
servers to 8.1.2 before clients or *"If you do not upgrade your servers
first, communication between servers and clients might be interrupted."*, I
felt I should ask for empirical evidence that it wont cause problems. The
warning was not specific on what kinds of communications problems to expect
or if/how they can be addresses if someone decides to download and upgrade
their client simply based on the "yes, 7.1 servers are compatible with 8.1
clients" document and didn't see the warning I read.

Perhaps it is due to TLS 1.2 now turned ON by default.  Either way, more
details/specifics from IBM would be helpful.

On Wed, Aug 23, 2017 at 4:21 AM, Stefan Folkerts 
wrote:

> I agree with Eric and I have 8.2 VE setups connected to 7.1 servers at
> multiple sites, i've never seen any issues. I do find the documentation
> strange if it say's you need to upgrade your clients before upgrading the
> server. The only thing that makes sense to me is client-side dedup with
> compression, for that you want your clients on the latest level otherwise
> the compression isn't compatible with the server compression and you don't
> get optimal results.
>
> On Wed, Aug 23, 2017 at 9:17 AM, Loon, Eric van (ITOPT3) - KLM <
> eric-van.l...@klm.com> wrote:
>
> > Nor with up-leveled clients by the way, which is the case here.
> > Kind regards,
> > Eric van Loon
> > Air France/KLM Storage Engineering
> >
> >
> > -Original Message-
> > From: Loon, Eric van (ITOPT3) - KLM
> > Sent: woensdag 23 augustus 2017 9:15
> > To: ADSM-L@VM.MARIST.EDU
> > Subject: RE: 8.1.2 client and 7.1.7 servers
> >
> > Hi Zoltan!
> > The page http://www-01.ibm.com/support/docview.wss?uid=swg21053218 shows
> > that the SP 8.1.2 client is supported with all 8.1 and 7.1 servers. I
> have
> > never encountered issues with down-leveled clients in my 20+ years of TSM
> > history.
> > 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
> > Zoltan Forray
> > Sent: dinsdag 22 augustus 2017 15:03
> > To: ADSM-L@VM.MARIST.EDU
> > Subject: 8.1.2 client and 7.1.7 servers
> >
> > Has anyone tried using the latest 8.1.2 clients with 7.1.7 servers?  I
> > haven't had the chance to test such a configuration (since my lone test
> > server is at 8.1.1) and with the dire-warnings in the readme docs, I made
> > sure everyone on my staff knows to NOT install 8.1.2 clients.
> >
> > From the readme/docs:
> >
> > Upgrade your IBM Spectrum Protect™ servers to Version 8.1.2 before you
> > upgrade the backup-archive clients.
> >
> >
> >
> > If you do not upgrade your servers first, communication between servers
> > and clients might be interrupted.
> >
> >
> > --
> > *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
> > 
> > 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
> > 
> >
>



-- 
*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

Re: 8.1.2 client and 7.1.7 servers

2017-08-23 Thread Stefan Folkerts 
I agree with Eric and I have 8.2 VE setups connected to 7.1 servers at
multiple sites, i've never seen any issues. I do find the documentation
strange if it say's you need to upgrade your clients before upgrading the
server. The only thing that makes sense to me is client-side dedup with
compression, for that you want your clients on the latest level otherwise
the compression isn't compatible with the server compression and you don't
get optimal results.

On Wed, Aug 23, 2017 at 9:17 AM, Loon, Eric van (ITOPT3) - KLM <
eric-van.l...@klm.com> wrote:

> Nor with up-leveled clients by the way, which is the case here.
> Kind regards,
> Eric van Loon
> Air France/KLM Storage Engineering
>
>
> -Original Message-
> From: Loon, Eric van (ITOPT3) - KLM
> Sent: woensdag 23 augustus 2017 9:15
> To: ADSM-L@VM.MARIST.EDU
> Subject: RE: 8.1.2 client and 7.1.7 servers
>
> Hi Zoltan!
> The page http://www-01.ibm.com/support/docview.wss?uid=swg21053218 shows
> that the SP 8.1.2 client is supported with all 8.1 and 7.1 servers. I have
> never encountered issues with down-leveled clients in my 20+ years of TSM
> history.
> 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
> Zoltan Forray
> Sent: dinsdag 22 augustus 2017 15:03
> To: ADSM-L@VM.MARIST.EDU
> Subject: 8.1.2 client and 7.1.7 servers
>
> Has anyone tried using the latest 8.1.2 clients with 7.1.7 servers?  I
> haven't had the chance to test such a configuration (since my lone test
> server is at 8.1.1) and with the dire-warnings in the readme docs, I made
> sure everyone on my staff knows to NOT install 8.1.2 clients.
>
> From the readme/docs:
>
> Upgrade your IBM Spectrum Protect™ servers to Version 8.1.2 before you
> upgrade the backup-archive clients.
>
>
>
> If you do not upgrade your servers first, communication between servers
> and clients might be interrupted.
>
>
> --
> *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
> 
> 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.2 client and 7.1.7 servers

2017-08-23 Thread Loon, Eric van (ITOPT3) - KLM 
Nor with up-leveled clients by the way, which is the case here. 
Kind regards,
Eric van Loon
Air France/KLM Storage Engineering


-Original Message-
From: Loon, Eric van (ITOPT3) - KLM 
Sent: woensdag 23 augustus 2017 9:15
To: ADSM-L@VM.MARIST.EDU
Subject: RE: 8.1.2 client and 7.1.7 servers

Hi Zoltan!
The page http://www-01.ibm.com/support/docview.wss?uid=swg21053218 shows that 
the SP 8.1.2 client is supported with all 8.1 and 7.1 servers. I have never 
encountered issues with down-leveled clients in my 20+ years of TSM history.
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 Zoltan 
Forray
Sent: dinsdag 22 augustus 2017 15:03
To: ADSM-L@VM.MARIST.EDU
Subject: 8.1.2 client and 7.1.7 servers

Has anyone tried using the latest 8.1.2 clients with 7.1.7 servers?  I haven't 
had the chance to test such a configuration (since my lone test server is at 
8.1.1) and with the dire-warnings in the readme docs, I made sure everyone on 
my staff knows to NOT install 8.1.2 clients.

From the readme/docs:

Upgrade your IBM Spectrum Protect™ servers to Version 8.1.2 before you upgrade 
the backup-archive clients.



If you do not upgrade your servers first, communication between servers and 
clients might be interrupted.


--
*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

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.2 client and 7.1.7 servers

2017-08-23 Thread Loon, Eric van (ITOPT3) - KLM 
Hi Zoltan!
The page http://www-01.ibm.com/support/docview.wss?uid=swg21053218 shows that 
the SP 8.1.2 client is supported with all 8.1 and 7.1 servers. I have never 
encountered issues with down-leveled clients in my 20+ years of TSM history.
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 Zoltan 
Forray
Sent: dinsdag 22 augustus 2017 15:03
To: ADSM-L@VM.MARIST.EDU
Subject: 8.1.2 client and 7.1.7 servers

Has anyone tried using the latest 8.1.2 clients with 7.1.7 servers?  I haven't 
had the chance to test such a configuration (since my lone test server is at 
8.1.1) and with the dire-warnings in the readme docs, I made sure everyone on 
my staff knows to NOT install 8.1.2 clients.

From the readme/docs:

Upgrade your IBM Spectrum Protect™ servers to Version 8.1.2 before you upgrade 
the backup-archive clients.



If you do not upgrade your servers first, communication between servers and 
clients might be interrupted.


--
*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

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