TSM: Replicate Node fails with ANR9999D_2930690409 and rc=1120

I have had a problem when running replicate node between two TSM / Spectrum Protect servers, replication failed with nothing saying error message ANR9999D_2930690409 and rc=1120.

02/12/2019 12:30:47     ANR9999D_2930690409 SmReplServerSession(smrepl.c:2609) Thread<1537>: Replication session 246 for TSM on Linux/x86_64 failed, rc=1120 (SESSION: 246)
02/12/2019 12:30:47     ANR9999D Thread<1537> issued message 9999 from: (SESSION: 246)

Root cause was missing archive copy group on target server, wow, one may think that this could be common configuration mistake when configuring replication, but IBM doesn't think so when showing message which You can not understand :)

You can compare and validate policies on source and replication servers by command:

VALIDATE REPLPOLICY TARGET_TSM_SERVER_NAME

IBM DB2: Diagnosing database corruption

Summary:  Learn how to identify and categorize the most common corruption issues while using IBM DB2®. In this article, learn corrective and preventive techniques you can implement to combat corruption issues.

Read more on this link:
http://www.ibm.com/developerworks/data/library/techarticle/dm-1208corruptiondb2/index.html?cmp=dw&cpb=dwinf&ct=dwnew&cr=dwnen&ccy=zz&csr=082412

VIOS Sizing tool WLE (Workload estimator)

VIOS Advisor to make assessments and provide recommendations

IBM Storage Provider v 1.1.0 for VMware and IBM XIV

IBM Storage Provider for VMware VASA, Version 1.1.0

For IBM Storage and VMware users, the IBM Storage Provider for VMware VASA (referred to as 'VASA Provider') improves VMware vSphere's ability to monitor and automate storage related operations. The VASA Provider is a standard vSphere management plug-in that is deployed once on each vCenter server to interact with vSphere APIs for Storage Awareness (VASA). This tool is used to manage storage from vCenter server.

IBM Techdocs - the Technical Sales Library

IBM Power HW - Facts and features reports

IBM TotalStorage SAN Hosts Data Gathering

This TIP discusses IBM TotalStorage SAN hosts data gathering.

Upgrading IBM Information Archive to software version 2.1.2

DS3950/4000/5000 Recommended Firmware Levels

Speaking UNIX - Customize your shell in AIX

VMware vStorage API (VADP) and TSM 6.2.2

TSM 6.2.2 supports VADP backups:
- VADP for file-level proxy backup
- VADP for Full backups (direct read from VMDK files for backup and restore)
- Auto discovery of New VMware guests (Virtual Machines)

Proxy platforms:
- Windows Server 2003 - 2008 (32 - 64bit, 2008R2 - 64 bit only)
VMware patforms
- ESX / ESXi - 3.5, 4.0 - 4.1

Useful HMC key combintaions: Switch to shell, restart xserver

CTRL-ALT-F1: Switch to Linux command line; no login possible. If you then click on CTRL-ALT-DEL the system will reboot.
CTRL-ALT-F2: Takes you back to the Xserver window.
CTRL-ALT-BACKSPACE: Kills of the Xserver and will start a new -fresh- one, so you can login again.

LPAR and VIO on IBM AIX UNIX Servers

Virtual I/O (VIO) and Virtualization

Briefly What is Virtualization?

The Virtual I/O Server is part of the IBM System p5 Advanced Power Virtualization hardware feature. Virtual I/O Server allows sharing of physical resources between LPARs including virtual SCSI and virtual networking. This allows more efficient utilization of physical resources through sharing between LPARs and facilitates server consolidation.

This allows a single machine to run multiple operating system (OS) images at the same time but each is isolated from the others. POWER4 based machines started this in 2001 by allowing many Logical Partitions (LPAR) to run on the same machine using but each using different CPUs, different memory sections and different PCI adapter slots. Next came with POWER4, the ability to dynamically change the CPU, memory and PCI adapters slots with the OS running. With the introduction of POWER5 in 2005, further Virtualization items have been added:

1. Less than a whole CPU can be allocated to a LPAR
2. The LPARs sharing CPUs can be setup to allow automatic load balancing (in milliseconds)
3. The sharing of disks, networks, optical devices (CD/DVD) using a VIO Server (see below)

For whole article read:
http://www.ibm.com/developerworks/wikis/display/virtualization/VIO
Source: IBM DeveloperWorks Wiki

THE TSM SERVER 6.2.2 UPGRADE CAN DELETE DB2 INSTANCES - Manually upgrading server instances from Tivoli Storage Manager Version 6.1 to Version 6.2

During the upgrade to TSM 6.2.2, the installer attempts to determine the currently installed version of DB2 using the command 'db2level'. If the db2level command fails, the TSM server (including DB2) is then uninstalled and reinstalled rather than being upgraded. Uninstalling DB2 results in all DB2 instances being deleted. The deleted instances are not rebuilt post the upgrade.
The db2level command has been seen to fail with
        # LANG=C /opt/tivoli/tsm/db2/bin/db2level
        SQL10007N Message "-1390" could not be retrieved.  Reason
        code: "3".

Local fix:
Use the steps outlined in the technote:
        Manually upgrading server instances from Tivoli Storage
        Manager Version 6.1 to Version 6.2
        http://www-01.ibm.com/support/docview.wss?uid=swg27018195
        to recreate the instances that were deleted.

How to define and update script in TSM server

Here are some tips when managing scripts in TSM server.

• Defining script in TSM:

DEFine SCRipt script_name command_line Line=number

Example:
tsm: TSMSERVER> DEFine SCRipt test_scrit "q sch t=a" Line=5

• Updating script in TSM:

UPDate SCRipt script_name command_line Line=1 DESCription=description

IBM HMC: Accessing the Product Engineering Shell (PESH) Command Line

On this site you can find manual how to access PESH in HMC.
http://www-01.ibm.com/support/docview.wss?uid=nas1dba3b86d228b9b6c862570d1008009fd

It can be used when solving problem with too big /var/hsc/log/hmclogger.log file and need to do any operation under root.
http://www-01.ibm.com/support/docview.wss?uid=isg3T1011162


The procedure in this document can be used to obtain an unrestricted shell on the HMC and log on as root.
Prerequisites: Obtain a pesh password from IBM support.
Right-click on the HMC desktop, select Terminals > rshterm . Run the lshmc -v command to obtain the HMC serial number (as stored in the BIOS). The serial number is listed in the SE field (in bold blue below):