OS : Linux Redhat
Software : TSM 6.3.3.100

Error: ANR3619W The user limit for open files is below the recommended minimum value of 4096

 [root@omer ~]# ps -ef | grep dsmserv
tsminst1 12003     1 20 Oct25 ?        3-11:59:24 /opt/tivoli/tsm/server/bin/dsmserv -u tsminst1 -i /home/tsminst1/tsminst1 -q
root     29357 27628  0 18:03 pts/1    00:00:00 grep dsmserv

[root@omer ~]# cat /proc/12003/limits
Limit                     Soft Limit           Hard Limit           Units
Max cpu time              unlimited            unlimited            seconds
Max file size             unlimited            unlimited            bytes
Max data size             unlimited            unlimited            bytes
Max stack size            10485760             unlimited            bytes
Max core file size        unlimited            unlimited            bytes
Max resident set          unlimited            unlimited            bytes
Max processes             212992               212992               processes
Max open files            1024                 1024                 files
Max locked memory         32768                32768                bytes
Max address space         unlimited            unlimited            bytes
Max file locks            unlimited            unlimited            locks
Max pending signals       212992               212992               signals
Max msgqueue size         819200               819200               bytes
Max nice priority         0                    0
Max realtime priority     0                    0

Stop TSM SERVER
Set new limit for open file

[root@omer tsmdb]# ulimit -n 65535

Start TSM SERVER

[root@omer tsmdb]# ps -ef | grep dsmserv
tsminst1 29562     1  0 18:08 pts/1    00:00:00 /opt/tivoli/tsm/server/bin/dsmserv -u tsminst1 -i /home/tsminst1/tsminst1 -q
root     29810 27628  0 18:08 pts/1    00:00:00 grep dsmserv
[root@omer tsmdb]# cat /proc/29562/limits
Limit                     Soft Limit           Hard Limit           Units
Max cpu time              unlimited            unlimited            seconds
Max file size             unlimited            unlimited            bytes
Max data size             unlimited            unlimited            bytes
Max stack size            10485760             unlimited            bytes
Max core file size        unlimited            unlimited            bytes
Max resident set          unlimited            unlimited            bytes
Max processes             212992               212992               processes
Max open files            65535                65535                files
Max locked memory         32768                32768                bytes
Max address space         unlimited            unlimited            bytes
Max file locks            unlimited            unlimited            locks
Max pending signals       212992               212992               signals
Max msgqueue size         819200               819200               bytes
Max nice priority         0                    0
Max realtime priority     0                    0

For resolve the problem:

I logged  to esxi server via ssh
I find the  WorldNumber of virtual machine with thi command:

For view HW configuration of my host esxi, from ssh shell start:

smbiosDump

I need to rename appoggiovg volumegroup

root@paul:/#lsvg
hpsanvg
rootvg
oraexpvg
dati2vg
dati3vg
dati4vg
dati5vg
appoggiovg

Appoggiovg is create over hdisk7

I need:

varyoffvg appoggiovg
exportvg appoggiovg

root@paul:/#lspv
hdisk2          00c655c40fab3811                    rootvg          active
hdisk0          00c7662d78e1b21f                    hpsanvg         active
hdisk1          00c655c4d544cca6                    oraexpvg        active
hdisk3          00c655c444918136                    dati2vg         active
hdisk4          00c655c4db40e342                    dati3vg         active
hdisk5          00c655c428a07b90                    dati4vg         active
hdisk6          00c655c428a0de52                    dati5vg         active
hdisk7          00c655c4ae67c723                    None

root@paul:/#importvg -y dati6vg hdisk7

root@paul:/#lspv
hdisk2          00c655c40fab3811                    rootvg          active
hdisk0          00c7662d78e1b21f                    hpsanvg         active
hdisk1          00c655c4d544cca6                    oraexpvg        active
hdisk3          00c655c444918136                    dati2vg         active
hdisk4          00c655c4db40e342                    dati3vg         active
hdisk5          00c655c428a07b90                    dati4vg         active
hdisk6          00c655c428a0de52                    dati5vg         active
hdisk7          00c655c4ae67c723                    dati6vg         active

Monitoraggio EVA 8100 con HP SIM, installazione HP COMMAND VIEW 10.2 e HP System Insight Manager sullo stesso server windows 2008 r2 standard

– Installare prima HP SIM  e poi COMMAND VIEW 10.2  per evitare conflitto di porte tcp

– Verificare post installazione il corretto uso delle porte  tcp WBEM/WMI e SMI-S  (il primo installato con HP SIM e il secondo con il command view)
C: netstat –anb >netstat.txt

TCP 0.0.0.0:5988 0.0.0.0:0 LISTENING 1712 [JavaWrapper.exe]
TCP 0.0.0.0:5989 0.0.0.0:0 LISTENING 460 [WMIServer.exe]
. . . . . . . . .
TCP 0.0.0.0:60000 0.0.0.0:0 LISTENING 1712 [JavaWrapper.exe]

Nel caso evidenziato  :

WBEM/WMI utilizzala porta 5989
SMI-S utilizza le porte 5988 e 60000

aggiungere a : C:Program FilesHPSystems Insight Managerconfig
identificationwbemportlist.xml le righe in BLUE

<?xml version=“1.0” encoding=“UTF-8”?>
<wbemportlist>
               <port id=“5989” protocol=“https”>
                    <cimnamespacelist>
                         <cimnamespace name=“root/cimv2”/>
                         <cimnamespace name=“vmware/esxv2”/>
                         <cimnamespace name=“root/hpq”/>
                   </cimnamespacelist>
                  <interopnamespacelist>
                         <interopnamespace name=“root/pg_interop”/>
                         <interopnamespace name=“root”/>
                         <interopnamespace name=“root/emulex”/>
                         <interopnamespace name=“root/qlogic”/>
                         <interopnamespace name=“root/ibm”/>
                         <interopnamespace name=“root/emc”/>
                         <interopnamespace name=“root/smis/current”/>
                         <interopnamespace name=“root/hitachi/dm51”/>
                         <interopnamespace name=“interop”/>
                         <interopnamespace name=“root/interop”/>
                         <interopnamespace name=“root/switch”/>
                         <interopnamespace name=“root/cimv2”/>
                   </interopnamespacelist>
              </port>
             <port id=“60000” protocol=“https”>
                   <interopnamespacelist>
                         <interopnamespace name=“interop”/>
                  </interopnamespacelist>
             </port>
</wbemportlist>

Salvare il file e e riavviare servizio hp sim
E rilanciare da HP SIM il discovery del server su cui sono installati i componenti command view e hp sim

Maggiori info  qua HP SIM and COMMAND VIEW whitepaper

[tsminst1@omer ~]$ db2 connect to tsmdb1

   Database Connection Information

 Database server        = DB2/LINUXX8664 9.7.5
 SQL authorization ID   = TSMINST1
 Local database alias   = TSMDB1

[tsminst1@omer ~]$ db2 “select substr(tbsp_name,1,30) as Tablespace_Name, tbsp_type as Type,
> substr(tbsp_state,1,20) as Status, (tbsp_total_size_kb / 1024 ) as Size_Meg,
> smallint((float(tbsp_free_size_kb)/ float(tbsp_total_size_kb))*100)as Percent_Free_Space,
> int((tbsp_free_size_kb) / 1024 )as Meg_Free_Space from sysibmadm.tbsp_utilization”
;

TABLESPACE_NAME                TYPE       STATUS               SIZE_MEG             PERCENT_FREE_SPACE MEG_FREE_SPACE
—————————— ———- ——————– ——————– —————— ————–
SYSCATSPACE                    DMS        NORMAL                                192                  6             12
TEMPSPACE1                      SMS        NORMAL                                118                  0              0
USERSPACE1                      DMS        NORMAL                              15520                  0             24
TSMTEMP                           SMS        NORMAL                                  0                  0              0
IDXSPACE1                         DMS        NORMAL                              44224                  0             25
LARGESPACE1                   DMS        NORMAL                               8832                  0             20
LARGEIDXSPACE1           DMS        NORMAL                               7904                  0             21
LGTMPTSP                         SMS        NORMAL                                  4                  0              0
SYSTOOLSPACE                DMS        NORMAL                                 32                 94             30
SYSTOOLSTMPSPACE     SMS        NORMAL                                  0                  0              0
REPLTBLSPACE1               DMS        NORMAL                                 32                 82             26
REPLIDXSPACE1               DMS        NORMAL                                 32                 85             27
  12 record(s) selected.

Dopo aver avuto alcune notizie sull’imminente arrivo di TSM 6.4 (che da quanto ho potuto capire la parte server rimarra come 6.3.x mentre i componenti come  il VE diventera’ 6.4) ecco le prime info che ho trovato  per data protection for vmware :

– Incrementale forever … come per i backup standard di tsm si utilizzeranno  nel backup delle virtual machine di vmware su utilizzera il CBT in maniera differente come policy dalla 6.3 non piu
Full-Inc-Full-Inc  etc … ma Full-Inc-Inc-Inc ….  con connesso la schedulazione  di un solo job per il backup (non come adesso uno per il full e uno per l’inc..)

– Risparmio di spazio l’utilizzo di solo e sempre gli incrementali permettera’ anche di consolidare i block utilizzai eliminando quelli non utilizzaiti (se non mi sbaglio lo fa gia’ Veeam..)

– Si potra’ backuppare un singolo VMDK… invece che solamente l’intera VM.

Poi altre modifiche su schedulazioni e processi di backup ma gia’ quelli che vi ho indicato mi spingono a pensare che almento il sottoscritto per il 2013 potrebbe vedere bene un bel aggiornamento alla  6.4

Mentre navigavo sul sito dell’IBM per verificare alcune compatiblita’ di client  mi sono imbattuto …

http://www-01.ibm.com/common/ssi/cgi-bin/ssialias?infotype=AN&subtype=CA&htmlfid=897/ENUS212-382&appname=USN

Speriamo che ci siano anche dei miglioramenti a livello di interfaccia grafica dell’administration center …. (magari verso l’interfaccia dell XIV, attualmente riutilizzata per SVC,V7000 e TPC…)

Dopo aver aggiornato TSM dalla 6.2.2 alla 6.3  ho preparato il TSM server per effettuare l’automatic deploy degli agent via Administration Center , ho utilizzato come documentazione l’infocenter dell’IBM.

Per prima cosa creo due filesystem sul server (nel mio caso linux redhat) dove uno mi servira’ per appoggiare i pacchetti di aggiornamento (.exp) nel caso voglia fare io il download dal sito IBM (l’automatic deploy permette anche di delegare a lui il downlaod e l’import sul TSM), mentre l’altro file system mi servira’ per definirci la device class per dove il tsm si archiviera’ gli agent.

# Creo la devclass  associata al file system dove verra’ messo il pacchetto da importare
define devclass ibm_client_deploy_import devtype=file directory=/import_agent

# definisco il storage pool dove verra’ messo il pacchetto (agent e’ una device class definita gia’ prima)

tsm: SERVER1>q devclass agent f=d
             Device Class Name: AGENT
        Device Access Strategy: Sequential
            Storage Pool Count: 1
                   Device Type: FILE
                        Format: DRIVE
         Est/Max Capacity (MB): 1,500.0
                   Mount Limit: 20
              Mount Wait (min):
         Mount Retention (min):
                  Label Prefix:
                       Library:
                     Directory: /clientdeploy
                   Server Name:
                  Retry Period:
                Retry Interval:
                        Shared:
            High-level Address:
              Minimum Capacity:
                          WORM: No
              Drive Encryption:
               Scaled Capacity:
       Primary Allocation (MB):
     Secondary Allocation (MB):
                   Compression:
                     Retention:
                    Protection:
               Expiration Date:
                          Unit:
      Logical Block Protection:
Last Update by (administrator): ADMIN
         Last Update Date/Time: 10/02/2012 17:23:53

# definisco lo storage pool
define stgpool AgentPool agent maxscratch=20

# definisco  domain policyset etc…
define domain ibm_client_deploy
define policyset ibm_client_deploy ibm_client_deploy
define mgmtclass ibm_client_deploy ibm_client_deploy ibm_client_deploy
define copygroup ibm_client_deploy ibm_client_deploy ibm_client_deploy
standard type=archive destination=AgentPool retver=nolimit
assign defmgmtclass ibm_client_deploy ibm_client_deploy ibm_client_deploy
activate policyset ibm_client_deploy ibm_client_deploy

#definisco il mio server
set serverhladdress=server.serveraddress.com

Alcune note sui parametri utilizzati:

•ibm_client_deploy_import is the temporary location from where the deployment packages are imported. This parameter is defined by the deployment manager.
•import_directory is a previously defined directory that is accessible from the server.
•stgpool_name is the name of a storage pool of your choosing where the deployment packages are stored on the server. The storage pool name is based on a previously defined device class. That device class is different from the one which is used to perform IMPORT operations.
•storage_dc_name represents the device class where the deployment packages are stored on the server.
•retention_value (RETVER) of the DEFINE COPYGROUP command sets the retention time for the package. You can set it to NOLimit or to a number of days. If you specify a number, you must take into account the number of days that the package was on the FTP site. The days spent on the FTP site are included in the number.
 The default for the Administration Center is five years.
•server.serveraddress.com is the server IP address or host name from which you scheduled the client automatic deployment.

Prossimamente spieghero’ come importare in automatico i pacchetti e fare il vero e proprio upgrade degli agent

Ho aggiornato su due nuovi DS3500 il fw con l’ultima release e ho trovato molte novita’ interessanti dai Dynamic Disk Pool al supporto del VAAI per  vmware, gia’ queste due primi miglioramenti sono molti interessanti per il target a cui e’ proposto questo storage soprattutto paragonato ad altri storage, della stessa fascia, di altri vendor.

Ecco un confronto tra il DDP (Dynamic Disk Pool) e il tradizionale RAID

Una nota negativa del DDP che richiede un minimo di 11 Drive installati nel cassetto dello storage.

Mentre per il VAAI non c’e’ molto da spiegare …