xaminmo: (Josh 2004 Happy)
[personal profile] xaminmo
This is to prime search engines with something I couldn't find last time I looked.

The new TSM 7.1 operation center, also TSM, also called TSM Operations Center, or internally even TSM Control Center...

The default URL is https://xxx.xxx.xxx.xxx:11090/oc/

The port wasn't in the docs, and the path wasn't in some of the docs. None of it came up Googling.

So frustrating. I had a screen scrape of my install, but somehow missed this, or maybe it's only under advanced?

I couldn't find it in other docs, but Will was able to help me out.
xaminmo: (Josh 2004 Happy)
[personal profile] xaminmo
In the past, I set up TSM.PWD as root, but this seems to not be what I needed.

I'm posting because the error messages and IBM docs don't cover this.

tsmdbmgr.log shows:
ANS2119I An invalid replication server address return code rc value = 2 was received from the server.

TSM Activity log shows:
ANR2983E Database backup terminated due to environment or setup issue related to DSMI_DIR - DB2 sqlcode -2033 sqlerrmc 168. (SESSION: 1, PROCESS: 9)

db2diag.log shows:

2014-02-26- E415619A371 LEVEL: Error
PID : 15138852 TID : 1 PROC : db2vend
INSTANCE: tsminst1 NODE : 000
HOSTNAME: tsmserver
FUNCTION: DB2 UDB, database utilities, sqluvint, probe:321
DATA #1 : TSM RC, PD_DB2_TYPE_TSM_RC, 4 bytes
TSM RC=0x000000A8=168 -- see TSM API Reference for meaning.

EDUID : 38753 EDUNAME: db2med.35926.0 (TSMDB1) 0
FUNCTION: DB2 UDB, database utilities, sqluMapVend2MediaRCWithLog, probe:656
DATA #1 : String, 134 bytes
Vendor error: rc = 11 returned from function sqluvint.
Return_code structure from vendor library /tsm/tsminst1/sqllib/adsm/libtsm.a:

DATA #2 : Hexdump, 48 bytes
0x0A00030462F0C4D0 : 0000 00A8 3332 3120 3136 3800 0000 0000 ....321 168.....
0x0A00030462F0C4E0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x0A00030462F0C4F0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

EDUID : 38753 EDUNAME: db2med.35926.0 (TSMDB1) 0
FUNCTION: DB2 UDB, database utilities, sqluMapVend2MediaRCWithLog, probe:696
MESSAGE : Error in vendor support code at line: 321 rc: 168

RC 168 per dsmrc.h means:
#define DSM_RC_NO_PASS_FILE 168 /* password file needed and user is
not root */

Verified everything required for this:
• passworddir points to the right directory
• DSMI_DIR points to the right directory
• dsmtca runs okay
• dsmapipw runs okay

Verified hostname info was correct

dsmffdc.log shows:
[ FFDC_GENERAL_SERVER_ERROR ]: (rdbdb.c:4200) GetOtherLogsUsageInfo failed, rc=2813, archLogDir = /tsm/arch.

Checked, and the log directory inside dsmserv.opt was typoed as /tsm/arch instead of /tsm/arc as was used to create the instance and as exists on the filesystems.

Updated dsmserv.opt and restarted tsm server. No change other than fixing Q LOG

The TSM.PWD file must be owned by the instance user, not by root.
Make sure to run the dsmapipw as the instance user, or chown the file after.

Simple, and fairly obvious, but maybe not always so obvious.
xaminmo: Josh 2016 (Default)
[personal profile] xaminmo
Because I couldn't find references to this yet...
xaminmo: Josh 2016 (Default)
[personal profile] xaminmo
This is a new, clean install of the OS, and a new, clean download of the 6.3.1 reporting tool.

daltsmrpt: /install/2012/TSM/631rpt# cat /stdout
rootRA: com.ibm.tivoli.remoteaccess.LocalUNIXProtocol@298a298a
rootRA.isProtocolAvailable(): true
Exception: Userid is not privileged. java.net.ConnectException: CTGRI0002E Session not established.
(X) commiting registry
(X) shutting down service manager
(X) cleaning up temporary directories

daltsmrpt: /install/2012/TSM/631rpt# whoami

daltsmrpt: /install/2012/TSM/631ac# oslevel -s

If I get this sorted out, I'll post about it.
Read more... )
xaminmo: Josh 2016 (Default)
[personal profile] xaminmo
TSM Storage Agent on HP-UX 11.11 PA-RISC.
This is a legacy platform, so there are no updates.
When connecting to TSM 6.3, any restores need to be done without no-query.
If you do a no-query restore, the storage agent crashes with this:
Read more... )

You'll have to CANCEL RESTORE, then rm adsmserv.lock in the StorageAgent directory, then restart dsmsta.

No-query restore is via dsmj -> restore -> options -> disable no query restore
OR, from command line, make sure you have a question mark somewhere in your file path (an asterisk won't do it).

Then, consider upgrading your legacy applications to a supported platform.
xaminmo: Josh 2016 (Default)
[personal profile] xaminmo
Because I've not seen any full logs of TSM 6.2 or TSM 6.3 install anywhere, I'm posting a happy working install.

Note that this is from the download package, not base. We already have tivoli.tsm.license installed from the base CD manually (installp).

installing )
xaminmo: Josh 2016 (Default)
[personal profile] xaminmo
Because the AvePoint docs are somewhat Engrish and overall not so great, IBM has released a nice whitepaper at:

I've annotated below with asterisk notes.

Perms for Granular Backup :
1. Farm Admin within SharePoint
2. Web application policy within SharePoint
3. Local administrator where the particular DocAve Agent is installed
4. DBO permissions to the Content Databases and Central admin databases

Perms for Granular Backup including MySites :
1. Farm Admin within SharePoint
2. Web application policy within SharePoint
3. Full Control to Personalization Services within SharePoint
4. Local administrator where the particular DocAve Agent is installed.
5. Dbo permissions to the Content Databases and Central admin databases

Perms for Platform Backup :
1. Farm Admin within SharePoint
2. Web application policy within SharePoint
3. Local administrator where the particular DocAve Agent is installed
4. DBO permissions to the Content Databases and Central admin databases with SQL
5. Security Admin within SQL
* NOTE: You need a member agent installed on each active SQL server.
* NOTE: You need a member agent on each cluster node to get the cluster configs
* NOTE: Install a member agent on each WFE to spread the small-request load around since the agents are single threaded.

Perms How to grant SQL Sysadmin
1. Please open SQL Server Management Studio and connect to the SharePoint SQL instance.
2. Please go to Security -> Server Roles -> sysadmin.
3. Please click on Add button and add DocAve Agent account into this group.

How to give Local Admin permissions
1. Please log in to XXX server and go to Server Manager.
2. Please go to Configuration -> Local Users and Groups -> Groups -> Administrators.
3. Please click on Add button and add DocAve Agent account into this group.

Granting the Agent Farm Admin permissions
1. Please log in to SharePoint Central Admin.
2. Please go to Site Actions -> Site Settings -> Advanced permissions.
3. Please click on New button to add the Agent account into the Farm Administrators group.

Granting SSP Admin permissions
1. Please log in to SharePoint Central Admin and click on the Shared Services Administration instance.
2. Please click on Personalization services permissions.
3. Please add DocAve Agent account with all permissions listed.

Adding a user to Web Application Policy - Moss 2007:
1. Please log in to SharePoint Central Admin.
2. Please go to Application Management -> Policy for Web application.
3. Please add DocAve Agent account with full control for the (specific) web application.

Adding a user to Web Application Policy - SharePoint 2010:
1. Please log in to SharePoint Central Admin and click on Manage web applications.
2. Please select the Web Application and click on the User Policy button.
3. Please click on Add Users and add DocAve Agent account with full control.

Three additional permissions need to be granted:
Act as part of the operation system, Log on as a batch job and Replace a process level token. Please follow the steps below to add the corresponding permissions for one user.
1. Navigate to Start->Run, enter gpedit.msc in the pop-up window.
2. Navigate to Computer Configuration->Windows Settings->Security Settings->Local Policies->User Rights Assignment and add the corresponding user to the three policies on the right of the window.

For Content Manager module, the following permissions are required:
1. The Read and Write permissions for the installation path of the Agent.
2. The permission to create Event Logs:
a. Navigate to Start->Run, enter regedit in the pop-up window.
b. Find the corresponding key:
c. Right click on the key and click Permissions to add the corresponding permissions for the user.
NOTE: If the module could not be used after you add the permissions above, please assign Local Admin permission to the corresponding user.

For Replicator module, Auditor module and the other functions under the Administration module
The Local Admin permission is required.
xaminmo: (Logo Tivoli Certified New)
[personal profile] xaminmo
Ok, so if you have to replace the OS on your TSM server, and you're not using AD, then be sure to re-take ownership of the storage volumes. I didn't notice problems with the FILE class stgpool volumes, but the DBB/DBS volumes failed with errors like this:
2011-04-11 06:00:30 ANR1360I Output volume H:\TIVOLI\TSM\SERVER1\02519629.DBS opened (sequence number 1). (SESSION: 2390, PROCESS: 234)
2011-04-11 06:00:30 ANR0132E lvmread.c(1245): Memory allocation failed: object Resync read page buffer, size 4096. (SESSION: 2390, PROCESS: 234)
2011-04-11 06:00:30 ANR9999D_1112316882 (iccopy.c:1625) Thread<26>: Unable to read from db volume. (SESSION: 2390, PROCESS: 234)

This kind of problem is more likely if you lose your user DB, because windows uses machine IDs to generate userIDs, and you don't really get to make your own UIDs. So, if you use AD and lose the user DB, or if you're not using AD and you replace the host but keep the stg drives, then this will be an issue.

I'm posting this because I couldn't find ANYTHING on the web about this. Very few hits about lvmread.c, and none matched.

I should probably put this in ADSM-L.
actlog from the lab )
xaminmo: (Logo Tivoli Certified)
[personal profile] xaminmo
Here's how to set up a TSM client inside of a non-root user's home directory.

First, copy /opt/tivoli/tsm or /usr/tivoli/tsm into the location appropriate to your environment. For me, this was /home/xaminmo/tsm

Next, modify your dsm.sys and dsm.opt files to match the new environment.

TSM assumes hard-coded paths for a bunch of things, so the run line is like this:
export DSM_CONFIG=/home/xaminmo/tsm/client/ba/bin/dsm.opt
export DSM_DIR=/home/xaminmo/tsm/client/ba/bin
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/home/xaminmo/tsm/client/api/bin
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/home/xaminmo/tsm/client/ba/bin
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/lib:/usr/lib:/opt/lib:/usr/local/lib

If you use AES encryption, you'll run into something like this:
2011-03-16 19:26:49 ANS1467E ICC routine ICC_Init returned: majRC = 4, minRC = 2, desc = '/opt/tivoli/tsm/client/icc32/icc/icclib/libicclib.so: cannot open shared object file: No such file or directory'.
2011-03-16 19:26:49 ANS1464S Cannot load ICC encryption library.

The "recommended" solution is to not use AES encryption, but what fun is that?

The fix is documented for a Windows PE defect, but is easily adapted to our needs:
ln -s /home/xaminmo/tivoli/tsm/client/icc32/icc /home/xaminmo/tivoli/tsm/client/ba/bin
echo "testflag localicc" >> /home/xaminmo/tivoli/tsm/client/ba/bin/dsm.opt

Finally, with PASSWORDACCESS GENERATE set, but non-root dsmtca, you'll see something like this:
2011-03-16 20:06:25 Unable to locate valid trusted communication agent.
2011-03-16 20:06:25 tcaPath is >/home/xaminmo/tsm/client/ba/bin/dsmtca<. rc is 138
2011-03-16 20:06:25 ANS1501E Trusted agent execution/owner permissions are invalid

The fix is again simple, but only documented in the API Programmer's guide:
chmod -R go-rwx /home/xaminmo/tsm
chmod 4500 /home/xaminmo/tsm/client/*/bin/dsmtca
chown -R xaminmo /home/xaminmo/tsm
echo "PASSWORDDIR /home/xaminmo/tsm/tivinv" >> /home/xaminmo/tivoli/tsm/client/ba/bin/dsm.sys

After that, ONLY xaminmo may run dsmc, but the password will be encrypted and stored in /home/xaminmo/tsm/tivinv/TSM.PWD.

Not pretty, but it's all documented from IBM, and it does work in my lab.
xaminmo: Josh 2016 (Default)
[personal profile] xaminmo
On Thu, 7 Feb 2002 14:41:06, I posted this to ADSM.ORG. Amazingly, other than the DB volume portion and the TIVOLI URL, it still pretty much applies today.

I've found out that IBM *and* consultants are using this text verbatim but stripping my name from it. I never put a copyright on this, but it's still very poor form not to give credit to your sources. You can search the web and find my post of this archived on ADSM.ORG, among other places.

Anyway, reposting here with a few minor tweaks below. I'm not really adding in the stuff for TSM 6.x base install due to complexity and platform variability. Ok, because I'm being lazy.

Basic In-Order TSM Server Setup Checklist
I whipped this up because I run into so many people who want to figure
it out on their own, but really are just lost in the slew of new
concepts.  Here is a basic list of things to do when setting up your tsm
server the first time.  Suggestions and corrections are welcome.


Physical Installation:
   Install physical devices
   Power on system
   Install o/s maintenance
   Install tsm server and drivers
   Define devices to the O/S
      349x, 357x, 358x and 359x use Atape/IBMTAPE/lmcpd
      all others use TSM drivers

Make a larger database and log: (Pre 6.x style)
   define dbvolume        (make space)
   define dbcopy          (mirror elsewhere)
   extend db              (tell tsm to use the new space)
   define logv            (make space)
   define logc            (mirror elsewhere)
   extend log             (tell tsm to use the new space)
   define spacetrigger    (auto-grow db and log)
   define dbbackuptrigger (only if SET LOGMODE ROLLFORWARD)

Ensure proper licensing:
   register license       (see the server/bin directory)

Storage setup inside TSM:
   define library          (top level of tape storage)
   define devclass         (points to a library)
   define drive            (points to a library)
   define stg              (points to a device class)
   define vol              (points to a devclass and storage pool)
   label libvol            (prepares a tape for TSM use)
   checkin libv            (makes tape show up in Q LIBVOL)

For Policy/Node Information:
   define domain           (top level of policy information)
   define policyset        (contained within a policy domain)
   define mgmtclass        (contained within policyset)
   define copygroup T=BACK (contained within a management class)
   define copygroup T=ARCH (contained within a management class)
   activate policy         (only one policyset active per domain)
   register node           (belongs to a policy domain)

Typical Storage Pool Hierarchy:
   Copygroup "destination" is disk pool
   Disk pool "NEXT" is tape pool
   An extra tape pool of type "COPYPOOL"

Other Important Things to Look Into:
   Administrator's Guide, Working With Network of TSM Servers
      Virtual Volumes
      Library Sharing
   Administrator's Guide, Chapter 1: Introduction
      Overview of storage hierarchy and TSM concepts
   Administrator's Guide, Protecting The Server
      Protection and recovery of the system
   Administrator's Guide, Disaster Recovery Manager
      Integrated, licensed tool for server protection
      client backup schedules
      server administrative schedules (don't overlap these)
         BACKUP STG (sync up copy pool)
         UPDATE STG RECLAIM=50 (reclaim free space from tapes)
         UPDATE STG RECLAIM=100 (turn off reclaimation)
         UPDATE STG HI=0 LO=0  (migrate the disk pool to tape)
         UPDATE STG HI=90 LO=70  (migrate only during overflow)
         BACKUP DB (TSM database is critical to server function)
         BACKUP DEVCONFIG (Device config DB in text format for DB recovery)
         BACKUP VOLHISTORY (List of volumes used in DB recovery)

In all procedures WATCH FOR ERRORS.

If you have questions, see Documentation at:
   * TSM v5.5: http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1
   * TSM v6.1: http://publib.boulder.ibm.com/infocenter/tsminfo/v6
   * TSM v6.2: http://publib.boulder.ibm.com/infocenter/tsminfo/v6r2

TSM Administrator's Guide is procedural information
TSM Administrator's Reference is command syntax
TSM Messages Guide is decyphering for ANR/ANS messages

Also, *the* reference from Richard B. Sims:
xaminmo: (Logo Tivoli Certified)
[personal profile] xaminmo
If you haven't seen TSM 6.1 sizing, it's 3x the 5.5 db and log size, unless you use dedupe, and then use a 5x multiplier instead. The reasoning is:
~1500 bytes per dedupe extent
~3500 bytes per file object

Note also that 6.1 is permanently in rollforward mode because of the use of DB2. What may not be obvious is that it takes TWO full DBBs to clear the logs.

Also, from inside TSM, you cannot see the size of the archive logs. The best I've come up with is to set ACTIVELOGSIZE in dsmserv.opt to the size of the log filesystem. (You ARE using dedicated log filesystems, right?) When you see log space utilization begin climbing, without a corresponding reduction at idle, that's when the archive logs have filled.

If the activelog fills because the archivelogs are full, then TSM goes down and stops DB2. You can grow the filesystem, and all is well. If you can't do that, recovery is more complicated and requires enough free space (can be temporary) to fit the activelogs and two DBBs.

SET DBRECOVERY is supposed to enable automatic database backups to prevent the activelogs from filling. Unfortunately, it doesn't seem to do anything on I'm still investigating, but at the least, it's not preempting tape drive use in time. Still, if it takes two full DBBs... Any input on this would be appreciated.

Server-side DEDUPE enabled storage pools should generally be large enough to not require migration. When deduplication occurs server-side, PCT Utilized drops, but the space is not free until reclamation occurs. I found that in one environment, "full" was around 79% at any given time.

Migrating and reclaiming deduplicated pools consumes a large amount of log space. I found on a 1TB pool it was easy to exceed 180G of log space (and crash TSM). Logs were empty at about 6pm. 90G of log space came in during backups. Most backups finished by midnight, with one at 1am and one at 6:48am. Many failed due to the PCT_UTIL issue above. RESTOREINTERVAL was 360. DEDUPEREQUIRESBACKUP was NO. Admin schedules ran at 6am. Reclaims were killed off around 8am. Exchange incrementals ran every 6 hours. TSM went down around 2:15pm with the 90g activelog dir full too (total 180G logs for a 25G DB). Exchange backups skip the dedupe pools, so I'm still a little puzzled about the log space consumption. By my calculations, it amounts to 55mil objects touched.

My plan is to set DEDUPEREQUIRESBACKUP (effectively disabling it for any new inbound data, but allowing it to dedupe stuff later which lingers on disk). I'll set RESTOREINTERVAL to 30, and set DBRECOVERY to FILECLASS and monitor closely.

Does anyone out there have any windows based monitoring scripts for TSM?
xaminmo: (Logo Tivoli Certified)
[personal profile] xaminmo
I didn't notice this in TSM 5.5, but in TSM 6.1, the string '' is not the same as the value NULL. I probably just missed it, but just in case...

This will fail:

select NODE_NAME,PLATFORM_NAME from nodes -
  where PLATFORM_NAME NOT in ('Linux86','WinNT') -

But this will work:

select NODE_NAME,PLATFORM_NAME from nodes -
  where PLATFORM_NAME NOT in ('Linux86','WinNT') -
xaminmo: (Logo Tivoli Certified)
[personal profile] xaminmo
The devconfig file has always had a bit of magic to it. It reads top down, and dependencies must be met, but I never would have guessed about libraryinventory lines.

In TSM 6.1, the libraryinventory lines *must* exist before the DEFINE PATH statements

TSM, since DEFINE PATH has existed, has built files this way.

In the past, reports indicate that you could deviate from this order.

If you're making your own during DR, TSM 6.1 requires this order to be retained.
xaminmo: (Logo Tivoli Certified)
[personal profile] xaminmo
TSM 6.1 was pretty much a complete rewrite of TSM. It's been out for a year, and there are still OS kernel panics, TSM Server crashes, data loss, and general reliability issues. was retracted because it introduced badness, and was replaced with

Honestly, I would recommend people stay at 5.5 until things with 6.x prove to be more reliable.

Some good references for fix history:


Developer Works: TSM 6.1 APARs
xaminmo: Josh 2016 (Default)
[personal profile] xaminmo
Has anyone run into this error?
ACUINI0029E The install version, $(acu.compatibleVersions), is not valid.

ACUINI0029E isn't documented anywhere. Since I ran into similar issues on Windows being unhappy with no TSMC installed, I installed TSMC No change.

Verified Kernel is AIX 64 bit and xlC.rte and xlC.aix61.rte are installed.

ADSM.org and IBM technotes don't indicate anything else is required.

Tried both TSMS and partner world value packs.

Here's the log excerpt from /var/tivoli/tsm/log.txt )


eserver: (Default)
IBM POWER servers

June 2017

45678 910


RSS Atom

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Oct. 23rd, 2017 09:36 am
Powered by Dreamwidth Studios