unixadmin.free.fr just another IBM blog and technotes backup

17nov/15Off

Why Are Tapes with PRIVATE Status Not Found in QUERY VOLUME Output?

Technote (FAQ)

Question

QUERY LIBVOLUME shows tape volumes with status of PRIVATE, but the same volumes do not show up with the command: Q VOL

Why are these tapes PRIVATE?

Answer

QUERY VOLUME will only return information about volumes that belong to stgpools, but there are other types of volumes that can have valid data on them: DB backups, exports, backupsets and remote volumes that belong to a Library Client server.

The volume history will keep a record of all volumes and you can display these other types of non-stgpool volumes with the following commands:

q volh type=dbb
q volh type=dbs
q volh type=export
q volh type=backupset
q volh type=remote

If a PRIVATE volume is not part of a stgpool and does not display in any of the above Q VOLH commands then you can set it to scratch using the command:

UPDATE LIBVOL <library_name> <vol_name> STATUS=SCRATCH

If you do have a library sharing environment it is recommended to run an AUDIT LIBRARY on the Library Client servers prior to changing the status of a volume to scratch on the Library Manager server.

Remplis sous: TSM Commentaires
30oct/15

Using ‘dd’ to verify Tivoli Storage Manager tape volume labels

Question
How can I use the Unix 'dd' command to verify a tape volume label?

Answer
The first step that may be necessary to verify a tape volume label is to find out the block size in use on that tape volume. This parameter is typically set on the physical tape library console interface and will vary between manufacturers so the ideal place to search is on the manufacturer website.
There is a method to manually find out the block size as follows:

On most Unix systems, the 'dd' command will output a message indicating a read failed from a tape drive (and corresponding tape volume) along with insufficient memory message. For example on AIX:

    bash$ dd if=/dev/rmt1 of=/tmp/test.file ibs=32 count=1
    dd: 0511-051 The read failed.
    : There is not enough memory available now.
    0+0 records in.
    0+0 records out.

The 'if' parameter must reference a valid path to a drive that contains the volume you are seeking information about. This volume may be loaded using a utility such as tapeutil or directly from the physical library's console management. The drive should not be in use by Tivoli Storage Manager at the time the command is run and it is recommended to take the drive offline to Tivoli Storage Manager.

The 'ibs' parameter indicates the block size to use in bytes unless a 'k' is specific, in which case the parameter is read as kilobytes. A value of 32 bytes, as in the example above, is a good starting value. If this command returns a memory related error message then the value can be doubled.

    bash$ dd if=/dev/rmt1 of=/tmp/test.file ibs= 64 count=1
    dd: 0511-051 The read failed.
    : There is not enough memory available now.
    0+0 records in.
    0+0 records out.

The value specified for the block size is still smaller than what is actually on the volume so another error is generated. The value must be increased (each time doubling it) until no error message is reported:

    bash$ dd if=/dev/rmt1 of=/tmp/test.file ibs= 128 count=1
    0+1 records in.
    0+1 records out.

Once the correct block size has been discovered, the 'dd' command should not generate a memory error when reading from the volume.
Now that the block size is known, the data on the first block of the tape can be dumped to a file:
dd bs= conv=ascii if= of=/tmp/.out

For example:

    bash$ dd bs=128 conv=ascii skip=0 count=1 if=/dev/rmt1 of=/tmp/block1.out
    0+1 records in.
    0+1 records out.

Once the file is file '/tmp/block1.out' is written, the file may be viewed in any text editor or the cat command can be used:

    bash$ cat /tmp/block1.out
    VOL1200312

In this case the 'VOL1200312' is the label of the tape volume residing in the drive /dev/rmt1.

Source: IBM Technote

Remplis sous: TSM Aucun commentaire
27oct/15

NMON Visualizer

Pour ceux qui utilise l'outil de collecte de performance nmon développé par Nigel Griffiths et disponible pour IBM AIX/VIOS et Linux (Power, x86, x86_64, Mainframe & now ARM (Raspberry Pi)), comme vous le savez il faut se servir du fichier excel nmon analyser pour visualiser les fichiers de collecte nmon.

En complément de cet outil je vous conseille de tester NMONVisualizer, un projet IBM démarré par Hunter Presnall qui est un excelent outil pour comparer et analyser les fichiers nmon issue des collectes de performances de plusieurs systèmes ou VM AIX / Linux.

NMONVisualizer http://nmonvisualizer.github.io/nmonvisualizer/index.html

NMON
https://www.ibm.com/developerworks/aix/library/au-analyze_aix/

https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Power+Systems/page/nmon

http://nmon.sourceforge.net

Nmon analyser
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Power%20Systems/page/nmon_analyser

My thanks to you all for a job very well done. :)

13oct/15

How to add a hardware error in AIX errlog

Comment générer des erreurs hardware dans l'errlog d'AIX. Utile pour tester des logiciels de supervision ou la gestion des évènements sous PowerHA.
Voir le fichier /usr/include/sys/errids.h pour les LABELS errpt.

echo "EPOW_SUS\nEMULATE\n1\ntexte1\ntexte2" | /usr/lib/ras/ras_logger
echo "SCSI_ERR1\nEMULATE\n1\ntexte1\ntexte2" | /usr/lib/ras/ras_logger
# errpt
IDENTIFIER TIMESTAMP  T C RESOURCE_NAME  DESCRIPTION
0502F666   1013162315 P H EMULATE        ADAPTER ERROR
74533D1A   1013162115 U H EMULATE        LOSS OF ELECTRICAL POWER
Remplis sous: AIX, HACMP Aucun commentaire
8oct/15

Virtual HMC for November 2015

The IBM Power Systems Hardware Management Console (HMC) virtual appliance can be used to manage any of the systems that are supported by the version 8 HMC, which includes Power Systems servers with IBM POWER6, POWER7, and POWER8 processors.

The Power Systems HMC virtual appliance offers these benefits:

Provides hardware, service, and basic virtualization management for your Power Systems servers
Offers the same functionality as the traditional HMC
Runs as a virtual machine on an x86 server virtualized either by VMware ESXi or Red Hat KVM

Source: IBM

Remplis sous: HMC Aucun commentaire
25sept/15

AIX Crash always on d_map_list_tce()

Problem

AIX 6100-04-05-1015 Crash always on d_map_list_tce() with with EMC Symmetrix FCP VRAID storage disk.

EMC.Symmetrix.aix.rte:5.3.0.5
EMC.Symmetrix.fcp.rte:5.3.0.5
EMCpower.base:5.3.1.1
EMCpower.encryption:5.3.1.1
EMCpower.migration_enabler:5.3.1.1
EMCpower.mpx:5.3.1.1

(3)> stack
pvthread+001B00 STACK:
[041C85A0]d_map_list_tce+000A40 (0000000000000000, 0000000000000000,F1000A0380145AF0, 0000000000001020, 0000000000000001 [??])
[04255138]04255138 ()
[0425A668]efc_start+000508 (??)
[04226D58]efc_intr+0001B8 (??)
[0024280C]i_poll_soft+00012C (??)
[00242180]i_softmod+000480 ()
[0013FB44]flih_util+000250 ()
 
(3)> dr iar
iar   : 00000000041C85A0
041C85A0      tweqi    r3,0                r3=0
 
(3)> lke 041C85A0
    ADDRESS          FILE             FILESIZE FLAGS    MODULE NAME
 
  1 F1000000A05F2500 041B0000 00030000 00080252 /usr/lib/drivers/pci/pci_busdd
 
(3)> symptom
Instruction:
PIDS/5765G6200 LVLS/610 PCSS/SPI1 MS/700 FLDS/d_map_lis VALU/e8610110 FLDS/04255138 VALU/342e6b64

Local Fix
Stop the replication between storage and DR site

IBM APAR
Not yet tested with replication

Remplis sous: AIX Aucun commentaire
17sept/15Off

IBM Spectrum Protect formerly Tivoli Storage Manager

Beginning with Version 7.1.3, IBM Tivoli Storage Manager is now IBM Spectrum Protect™.
Beginning with Version 4.1.3, IBM Tivoli Storage FlashCopy® Manager is now IBM Spectrum Protect™ Snapshot.

Product name cross reference

IBM System Storage Archive Manager IBM Spectrum Protect for Data Retention
Tivoli Storage FlashCopy Manager IBM Spectrum Protect Snapshot
Tivoli Storage Manager IBM Spectrum Protect
Tivoli Storage Manager Extended Edition IBM Spectrum Protect Extended Edition
Tivoli Storage Manager FastBack for Workstations IBM Spectrum Protect for Workstations
Tivoli Storage Manager FastBack for Workstations - Starter Edition IBM Spectrum Protect for Workstations - Starter Edition
Tivoli Storage Manager for Databases IBM Spectrum Protect for Databases
Tivoli Storage Manager for Mail IBM Spectrum Protect for Mail
Tivoli Storage Manager for Enterprise Resource Planning IBM Spectrum Protect for Enterprise Resource Planning
Tivoli Storage Manager for Space Management IBM Spectrum Protect for Space Management
Tivoli Storage Manager for Storage Area Networks IBM Spectrum Protect for SAN
Tivoli Storage Manager for Virtual Environments IBM Spectrum Protect for Virtual Environments
Tivoli Storage Manager HSM for Windows IBM Spectrum Protect HSM for Windows

Source:  IBM Technote

Remplis sous: TSM Commentaires
11sept/15

Scheduled « Backup VM » processes more virtual machines than expected.

Technote (troubleshooting)

Problem(Abstract)

Using an asterisk in the "objects" field of a schedule definition will override any domain.vmfull specifications in the dsm.opt file.

Symptom

Backup VM processes more virtual machines than expected.

Cause

Using an asterisk in the "Objects" line of a schedule definition tells the Tivoli Storage Manager client to backup all virtual machines thus overriding the domain.vmfull options.

Example:

Action: Backup VM
Objects: *
Options: -mode=IFINCR

Environment

Windows or Linux proxy

Any 6.1.x or newer Tivoli Storage Manager server.

Resolving the problem

Remove the asterisk from the schedule definition on the Tivoli Storage Manager server. To do so, update the schedule. For Example:

     update schedule standard vm_backups objects=""

After this change is saved, then restart the client scheduler service or CAD to ensure the update is in place for the next scheduled backup.

Remplis sous: TSM Aucun commentaire
5sept/15

TSM – Installation Manager fails to complete prereq check

Problem

The on screen message reports:
Exception caught while evaluating expression in bundle "com.tivoli.dsm.prereq.oscheck".

Symptom

Within the Installation Manager logs, the following messages are logged in the .xml log:

00:20.04 INFO: com.tivoli.dsm.prereq.utils.OSUtils.<init>(64) : Starting RXA session
00:20.22 ERROR: com.tivoli.dsm.prereq.utils.OSUtils.<init>(82) : An Exception was thrown while trying to get operating system information
00:20.22 ERROR: com.tivoli.dsm.prereq.utils.OSUtils.<init>(83) : CTGRI0039E An error occurred while attempting to execute a Visual Basic script. The following error information was returned:  | CScript Error: Failed to load the configuration. (Access denied. )

Cause

Incorrect user being used during installation/upgrade.

Resolving the problem

Review the following requirements for the user ID performing the installation/upgrade here:

Windows: Installing Tivoli Storage Manager by using the installation wizard

Ensure that the user ID that you plan to use during the installation is a user with local Administrator authority.

Installing the V7.1.1 server and verifying the upgrade

You must be logged on to the system with the administrative user ID that was used to install the V6.2 or V6.3 server.

Remplis sous: TSM Aucun commentaire
25août/15

SLOW STARTUP PERFORMANCE OF THE 7.1 SERVER ON WINDOWS

Abstract

The default value for the DB2 database parameter DB_MEM_THRESH changed in DB2 version 10.5 and can lead to slow startup performance of the 7.1 server on Windows.

Content

ERROR DESCRIPTION:
It is possible to see the server startup take significantly longer to start up than is expected. The delay is experienced when the DB2 DB_MEM_THRESH value is set to 100 and there are large bufferpools.

The delay affects either, newly installed Tivoli Storage Manager Version 7.1.x, or upgrades from Tivoli Storage Manager V5.x to 7.1.x on Windows systems.

Upgrades from V6.x to 7.1.0.00 or higher do not show this behavior, since the DB_MEM_THRESH value is not changed to 100. The delay does not affect normal server operations, only server startup.

Tivoli Storage Manager Versions Affected: 7.1

Customer/L2 Diagnostics: The following commands can be run on a
DB2 command line to verify the setting for DB_MEM_THRESH.

db2 connect to TSMDB1
db2 get db cfg for TSMDB1 | find "DB_MEM_THRESH"

Output should be similar to the following.

C:\Program Files\Tivoli\TSM\db2\BIN>db2 get db cfg for TSMDB1 |
find
"DB_MEM_THRESH"
Database memory threshold               (DB_MEM_THRESH) = 100

If you see DB_MEM_THRESH set to 100 and are running server version 7.1 on Windows then this APAR applies.

Initial Impact: Medium

Additional Keywords: startup start mem perf slow start up
performance

LOCAL FIX:
The following steps can be done while the TSM server is running and does not require that the TSM server be restarted.

The DB_MEM_THRESH value can be changed to the previous default
of 10 by issuing the following DB2 commands.

db2 connect to TSMDB1
db2 update db cfg for TSMDB1 using DB_MEM_THRESH 10

The output should look similar to the following.

C:\Program Files\Tivoli\TSM\db2\BIN>db2 update db cfg for TSMDB1
using
DB_MEM_THRESH 10
DB20000I  The UPDATE DATABASE CONFIGURATION command completed
successfully.

Remplis sous: TSM Aucun commentaire