Highlighted
dlietz Absent Member.
Absent Member.
1528 views

TSM backups of OES11 SP2

Hello,

I'm configuring a backup of an OES11 sp2 VM using the TSM client for Linux and was hoping for some configuration tips, whether of NSS or the TSM client itself. We're running TSM 7.1 and I've installed the 7.1 client on the OES server.

My current dsm.sys file only contains the standard node information so I'm wondering about things like excludes/includes, nss modifications, etc.

Thanks for any assistance.

Dan
Labels (2)
Tags (2)
0 Likes
12 Replies
Anonymous_User Absent Member.
Absent Member.

Re: TSM backups of OES11 SP2

dlietz wrote:

> My current dsm.sys file only contains the standard node information so
> I'm wondering about things like excludes/includes, nss modifications,
> etc.


we use the following NSS options in order to backup and restore Novell
Trustee information successfully:
/ListXattrNWMetadata
/CtimeIsMetadataModTime
Check restores with care 😉

We have one TSM node defined for every NSS volumes. Nothing special in
the DSM configuration files. AFAIK it is not possible to use one node
for NSS and other POSIX file systems. So the partitions for the
operating system (xfs in our setup) use another TSM node.

Günther





0 Likes
dlietz Absent Member.
Absent Member.

Re: TSM backups of OES11 SP2

Thanks for the info. Could you possibly provide sample dsm.sys/dsm.opt with any sensitive information removed? I'm relatively new to TSM and I'm still learning syntax and the definition of many of the options.

I'm also finding IBM's website rather difficult to navigate due to it's size and finding information specifically related to OES/NSS has been like searching for a needle in a haystack.

Thanks for any assistance you're able to provide.

Dan

=?UTF-8?B?R8O8bnRoZXIgU2Nod2Fyeg==?=;2399860 wrote:
dlietz wrote:


we use the following NSS options in order to backup and restore Novell
Trustee information successfully:
/ListXattrNWMetadata
/CtimeIsMetadataModTime
Check restores with care 😉

We have one TSM node defined for every NSS volumes. Nothing special in
the DSM configuration files. AFAIK it is not possible to use one node
for NSS and other POSIX file systems. So the partitions for the
operating system (xfs in our setup) use another TSM node.

Günther

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: TSM backups of OES11 SP2

dlietz wrote:
>
> Thanks for the info. Could you possibly provide sample dsm.sys/dsm.opt
> with any sensitive information removed? I'm relatively new to TSM and
> I'm still learning syntax and the definition of many of the options.


Nothing special in the client configuration here:

dsm.sys:
SErvername MYSERVER
TCPServeraddress myserver.example.com
TCPPort 1500
COMMmethod TCPIP
Passwordaccess GENERATE
passworddir /media/nss/TEST/backup
managedservices schedule
Nodename TEST
TCPClientAddress oes11.example.com
Inclexcl /media/nss/TEST/backup/inclexcl
TCPBuffsize 32
TCPWindowsize 0
TCPNodelay Yes
TXNBytelimit 2G
ERRORLOGname /media/nss/TEST/backup/dsmerror.log
ERRORLOGretention 30 S
SCHEDLOGname /media/nss/TEST/backup/dsmsched.log
SCHEDLOGretention 30 S

TXNBytelimit is critical for performance. All log files as well the file
with the password hash are stored on the NSS volume.

dsm.opt:
SErvername MYSERVER
Subdir Yes
EDITOR NO
DOmain /media/nss/TEST

The EDITOR variable had to be set in order to make the CLI for TSM work.
This might be different in your environment.

> I'm also finding IBM's website rather difficult to navigate due to it's
> size and finding information specifically related to OES/NSS has been
> like searching for a needle in a haystack.


A totally agree. It is awkward. Get the pdf of the document and print it
out. The online version is most confusing. TSM just works for NSS, but
there is not much documentation available.

Günther

0 Likes
dbgallo1 Absent Member.
Absent Member.

Re: TSM backups of OES11 SP2

hardest part is dealing with it in a clustered environment. You need to manually kill the dsmcad for that session prior to moving the volume to another node, we're working on a cron script that would restart them all during the day to make sure there aren't any rogue ones running
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: TSM backups of OES11 SP2

dbgallo wrote:
>
> hardest part is dealing with it in a clustered environment. You need to
> manually kill the dsmcad for that session prior to moving the volume to
> another node, we're working on a cron script that would restart them all
> during the day to make sure there aren't any rogue ones running


This can be done quite easily withe the cluster scripts. Send me mail
for some examples on this as I do not want to share our cluster
configuration in public (and exposing my limited skills in bash also).

Günther

0 Likes
dlietz Absent Member.
Absent Member.

Re: TSM backups of OES11 SP2

Thanks for the info. What about exclusions? Anything special, for example /opt/novell/nss/mnt?

Thanks again for the info. We're not using a cluster at this point so no worries there.

Dan

=?UTF-8?B?R8O8bnRoZXIgU2Nod2Fyeg==?=;2400216 wrote:
dlietz wrote:
>
> Thanks for the info. Could you possibly provide sample dsm.sys/dsm.opt
> with any sensitive information removed? I'm relatively new to TSM and
> I'm still learning syntax and the definition of many of the options.


Nothing special in the client configuration here:

dsm.sys:
SErvername MYSERVER
TCPServeraddress myserver.example.com
TCPPort 1500
COMMmethod TCPIP
Passwordaccess GENERATE
passworddir /media/nss/TEST/backup
managedservices schedule
Nodename TEST
TCPClientAddress oes11.example.com
Inclexcl /media/nss/TEST/backup/inclexcl
TCPBuffsize 32
TCPWindowsize 0
TCPNodelay Yes
TXNBytelimit 2G
ERRORLOGname /media/nss/TEST/backup/dsmerror.log
ERRORLOGretention 30 S
SCHEDLOGname /media/nss/TEST/backup/dsmsched.log
SCHEDLOGretention 30 S

TXNBytelimit is critical for performance. All log files as well the file
with the password hash are stored on the NSS volume.

dsm.opt:
SErvername MYSERVER
Subdir Yes
EDITOR NO
DOmain /media/nss/TEST

The EDITOR variable had to be set in order to make the CLI for TSM work.
This might be different in your environment.

> I'm also finding IBM's website rather difficult to navigate due to it's
> size and finding information specifically related to OES/NSS has been
> like searching for a needle in a haystack.


A totally agree. It is awkward. Get the pdf of the document and print it
out. The online version is most confusing. TSM just works for NSS, but
there is not much documentation available.

Günther
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: TSM backups of OES11 SP2

dlietz wrote:
>
> Thanks for the info. What about exclusions? Anything special, for
> example /opt/novell/nss/mnt?


This is part of the system partitions and will not be included by the
TSM Node that does the backup for my NSS volumes. But indeed I do have
an entry for it in the exclusion list for the Node that does the backup
for system partitions like /opt.
This should not be necessary as the TSM client will not go beyond
partitions with the default settings. Thus a backup job for /opt will
not include any file system that is mounted somewhere in the /opt
partition. Just test this on your system.

Günther
0 Likes
Knowledge Partner
Knowledge Partner

Re: TSM backups of OES11 SP2

Am 14.07.2015 um 16:56 schrieb dbgallo:
>
> hardest part is dealing with it in a clustered environment. You need to
> manually kill the dsmcad


That's what the cluster unload script is for. 😉

CU,
--
Massimo Rosen
Novell Knowledge Partner
No emails please!
http://www.cfc-it.de
CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
0 Likes
dbgallo1 Absent Member.
Absent Member.

Re: TSM backups of OES11 SP2

when they all are DSMCAD and you have multiple sessions on one server, it gets difficult
0 Likes
Knowledge Partner
Knowledge Partner

Re: TSM backups of OES11 SP2

Am 20.07.2015 um 20:46 schrieb dbgallo:
>
> when they all are DSMCAD and you have multiple sessions on one server,
> it gets difficult


I'm not at a TSM customer right now and I'm not fluent enough in TSM
myself to know the proper commands out of my head,, but I have several
TSM customers and can tell you it's possible.

CU,
--
Massimo Rosen
Novell Knowledge Partner
No emails please!
http://www.cfc-it.de
CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: TSM backups of OES11 SP2

dbgallo wrote:
>
> when they all are DSMCAD and you have multiple sessions on one server,
> it gets difficult


Not really. You just have to start the scheduler with the proper
environment:
# export DSM_CONFIG=/media/nss/TEST/backup/dsm.opt
# dsmcad schedule &
This way one can start a multitude of schedulers all with their own
options and TSM nodes.

Günther

0 Likes
dbgallo1 Absent Member.
Absent Member.

Re: TSM backups of OES11 SP2

read up on this, it gets a bit cumbersome, but effectively you copy the DSMCAD to dsmcad-node1, dsmcad-node2 etc... for each resource and copy the init scripts for each one to /etc/init.d/ .. then replicate that setup across your resource nodes. Finally, modify your cluster load and unload scripts to match the call the init scripts to start and stop the process. Our TSM guy is looking at this
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.