ADSM-L

Re: Directories problem ...

2003-05-08 03:08:50
Subject: Re: Directories problem ...
From: PAC Brion Arnaud <Arnaud.Brion AT PANALPINA DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 8 May 2003 09:07:42 +0200
Andy,

I see you're as persistent as I am ;-) Ok, let's go for the required
items :

----------------------- Dsm.sys : ------------------------ SErvername
server_a
COMMmethod         TCPip
TCPPort            1500
TCPServeraddress   xxxxxxxxxxxxxxxxxx                  
TCPWindow       64
TCPBuf          32
TXNBYTELimit    25600
TCPNodelay      yes
Schedlogret     1 
Schedlogname    /var/spool/log/dsmsched.log
Errorlogret     1
Errorlogname    /var/spool/log/dsmerror.log
Compression     off
Passwordaccess  generate
Schedmode       polling
Inclexcl        /usr/tivoli/tsm/client/ba/bin/inclexcl.list

----------------------- Dsm.opt : -----------------------------
SErvername     server_a                                   
Date            4
Num             5

------------------------- Dsmc q inclexcl :-------------------

*** FILE INCLUDE/EXCLUDE ***
Mode Function  Pattern (match from top down)  Source File
---- --------- ------------------------------ ----------------- No
exclude filespace statements defined.
Excl All       /proxy_3.5/proxy-pacrs040-proxy/logs
/usr/tivoli/tsm/client/ba/bin/inclexcl.list
Excl All       /var/spool/mqueue
/usr/tivoli/tsm/client/ba/bin/inclexcl.list
Excl All       /var/spool/log
/usr/tivoli/tsm/client/ba/bin/inclexcl.list
Excl All       /.../*.dsm
/usr/tivoli/tsm/client/ba/bin/inclexcl.list
Excl All       /.../core
/usr/tivoli/tsm/client/ba/bin/inclexcl.list
Excl All       /unix
/usr/tivoli/tsm/client/ba/bin/inclexcl.list
No DFS include/exclude statements defined.

-------------------- dsmc q mg -detail : ---------------------------

See attached file : mgmtdetail

----------------   q n pacrs040 f=d  :   ---------------------------


                     Node Name: xxxxxxxx
                      Platform: AIX
               Client OS Level: 5.1
                Client Version: Version 4, Release 2, Level 2.1
            Policy Domain Name: AIX
         Last Access Date/Time: 07.05.2003 17:18:27
        Days Since Last Access: <1
        Password Set Date/Time: 29.03.1999 13:01:55
       Days Since Password Set: 1.500
         Invalid Sign-on Count: 0
                       Locked?: No
                       Contact: xxxxxxxxxxxxxx
                   Compression: Client
       Archive Delete Allowed?: Yes
        Backup Delete Allowed?: No
        Registration Date/Time: 29.03.1999 13:01:55
     Registering Administrator: xxxxxxxxx
Last Communication Method Used: Tcp/Ip
   Bytes Received Last Session: 4.486
       Bytes Sent Last Session: 28,90 M
      Duration of Last Session: 1.521,77
   Pct. Idle Wait Last Session: 0,00
  Pct. Comm. Wait Last Session: 0,00
  Pct. Media Wait Last Session: 0,00
                     Optionset: AIX_USED
                           URL: xxxxxxxxxx
                     Node Type: Client
    Password Expiration Period: 
             Keep Mount Point?: No
  Maximum Mount Points Allowed: 0
        Auto Filespace Rename : No
             Validate Protocol: No
                   TCP/IP Name: 
                TCP/IP Address: 
            Globally Unique ID: 

-----------------  Q clo : ----------------------------
                     Optionset: AIX_USED
                   Description: sets schedmode=prompted
Last Update by (administrator): xxxxxxxxx
              Managing profile: 

         Option: SCHEDMODE
Sequence number: 0
       Override: No
   Option Value: prompted

         Option: TXNBYTELIMIT
Sequence number: 0
       Override: Yes
   Option Value: 2097152

------------------ dsmerror.log and dsmsched.log -----------------------

Not really sure I can post them here, they may contain sensitive data,
that I would avoid posting publicly : If you really need them, let me
know and I'll send them directly to you !


Hopefully, you'll not lose too much of your precious time on that one !
Thanks in advance .

Arnaud

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
| Arnaud Brion, Panalpina Management Ltd., IT Group     |
| Viaduktstrasse 42, P.O. Box, 4002 Basel - Switzerland |
| Phone: +41 61 226 19 78 / Fax: +41 61 226 17 01       | 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=



-----Original Message-----
From: Andrew Raibeck [mailto:storman AT US.IBM DOT COM] 
Sent: Wednesday, 07 May, 2003 16:39
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Directories problem ...


Well, with real detailed information to go on, we can only continue to
guess what is happening. For starters, we would need to see the
following
items:

- dsm.sys used by pacrs040
- dsm.opt used by pacrs040
- output from "dsmc q inclexcl"
- output from "dsmc q mg -detail"
- output from "q n pacrs040 f=d" (admin command)
- output from "q clo" if pacrs040 has a client options set associated
with it (admin command)
- complete dsmsched.log from last full incremental backup (last night?)
- complete dsmerror.log from last full incremental backup (last night?)

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.eyebm DOT com (change eye to i to reply)

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.




PAC Brion Arnaud <Arnaud.Brion AT PANALPINA DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> 05/07/2003
07:05 Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: Directories problem ...



Andy (and others !),

Thanks for your explanations and help : basically it goes in the same
direction as what I thought. Unfortunately none of your explanations
fits in our environment : unique dsm.sys stanzas per node, no dirmc
declared, and all filesystems backuped at the same time ... One thing's
for sure : data is saved, and for me that's the most important thing,
but I'd really liked to know what's happening here, for my personal
intellectual enrichment. If someone has further explanations, I'm still
taker ! Cheers.

Arnaud

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
| Arnaud Brion, Panalpina Management Ltd., IT Group     |
| Viaduktstrasse 42, P.O. Box, 4002 Basel - Switzerland |
| Phone: +41 61 226 19 78 / Fax: +41 61 226 17 01       |
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=



-----Original Message-----
From: Andrew Raibeck [mailto:storman AT US.IBM DOT COM]
Sent: Wednesday, 07 May, 2003 15:26
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Directories problem ...


Directories with no extended attributes associated with them are stored
as "metadata" in the TSM database. Directories containing extended
attributes (such as those commonly found on NetWare and Windows file
systems) are larger, and thus portions of those directories will also be
stored in the storage pools.

What you are observing is normal.

As to why some directories are bound to one management class and others
are bound to another... I can't say for sure, not knowing enough about
your TSM environment or how you do backups. For example, if you have a
dsm.sys file with multiple stanzas and one stanza has a DIRMC option
that differs from that of another, then depending on which stanza is
used for a particular backup operation, different directories can be
bound to different management classes. Or if your backups target some
file systems but not others (i.e. you back up /dev and /etc on a nightly
basis, but not /lib or /u), and if the management class with the longest
RETONLY setting is different since you last backed up the other file
systems, then this could explain the difference. These are just a couple
of possibilities.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.eyebm DOT com (change eye to i to reply)

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.




PAC Brion Arnaud <Arnaud.Brion AT panalpina DOT com>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> 05/07/2003
02:49 Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: Directories problem ...



Hi John,

> Do you actually have directory backups

Well actually, I believe so ! On the node I have :

 q backup /
             Size      Backup Date        Mgmt Class A/I File
             ----      -----------        ---------- --- ----
            1.024  02.05.2003 21:59:22    MGMT-SAP-L  A  /
              512  04.11.2002 14:08:17    MGMT-SAP-L  A  /.SPOT
              512  04.11.2002 14:08:19    MGMT-SAP-L  A  /CD
              512  23.04.2002 15:33:58    MGMT-SAP-L  A  /audit
              512  02.01.2003 19:15:08    MGMT-SAP-L  A  /cdrom
            2.560  23.04.2002 15:33:58    MGMT-SAP-L  A  /dev
            7.680  23.04.2002 15:33:58    MGMT-SAP-L  A  /etc
              512  04.11.2002 14:08:19    MGMT-SAP-L  A  /inst.log
              512  23.04.2002 15:33:58    MGMT-SAP-L  A  /installTSM
            3.584  23.04.2002 15:33:58    MGMT-SAP-L  A  /lpp
              512  23.04.2002 15:33:58    MGMT-SAP-L  A  /mnt
              512  23.04.2002 15:33:58    MGMT-SAP-L  A  /sbin
              512  23.04.2002 15:33:58    MGMT-SAP-L  A  /tftpboot
              330  04.11.2002 14:08:19    DEFAULT     A  /-m
                1  30.04.2003 19:17:20    DEFAULT     A  /.rhosts
              676  06.05.2003 22:28:56    DEFAULT     A  /.sh_history
                8  04.11.2002 14:08:19    DEFAULT     A  /bin
              903  02.05.2003 21:59:22    DEFAULT     A  /bosinst.data
               57  08.11.2002 06:46:44    DEFAULT     A  /dsmerror.log
            9.734  02.05.2003 21:59:22    DEFAULT     A  /image.data
                8  04.11.2002 14:08:19    DEFAULT     A  /lib
            5.658  04.11.2002 14:08:19    DEFAULT     A  /mbox
            4.481  02.04.2003 19:17:58    DEFAULT     A  /smit.log
              115  02.04.2003 19:17:58    DEFAULT     A  /smit.script
                5  04.11.2002 14:08:19    DEFAULT     A  /u

What looks strange to me is some directories are using default
mgmt_class (like /lib), and not the other ones ...

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
| Arnaud Brion, Panalpina Management Ltd., IT Group     |
| Viaduktstrasse 42, P.O. Box, 4002 Basel - Switzerland |
| Phone: +41 61 226 19 78 / Fax: +41 61 226 17 01       |
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=



-----Original Message-----
From: John Naylor [mailto:john.naylor AT SCOTTISH-SOUTHERN.CO DOT UK]
Sent: Wednesday, 07 May, 2003 11:37
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Directories problem ...


Sometimes directoriies are stored in the database.
Do you actually have directory backups




PAC Brion Arnaud <arnaud.brion AT panalpina DOT com> on 05/07/2003 10:08:30 AM

Please respond to "ADSM: Dist Stor Manager" <adsm-l AT vm.marist DOT edu>

To:   adsm-l AT vm.marist DOT edu
cc:    (bcc: John Naylor/HAV/SSE)
Subject:  Re: Directories problem ...



Hi Karel,

No I did'nt defined any DIRMC, either in a client option set, or locally
in the node's dsm.sys file, but the problem is not that directory
structure is using a specific management class, it is that the storage
pool corresponding that management class doesn't contain any files
related to directory structure of the node !

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
| Arnaud Brion, Panalpina Management Ltd., IT Group     |
| Viaduktstrasse 42, P.O. Box, 4002 Basel - Switzerland |
| Phone: +41 61 226 19 78 / Fax: +41 61 226 17 01       |
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=



-----Original Message-----
From: Karel Bos [mailto:Karel.Bos AT NUON DOT COM]
Sent: Wednesday, 07 May, 2003 10:57
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Directories problem ...


Do you use the DIRMC MGMT-SAP-L1 option in the client option
set/dsm.sys/dsm.opt? This directs the dirs to the correct management
class/storage pool.


-----Oorspronkelijk bericht-----
Van: PAC Brion Arnaud [mailto:Arnaud.Brion AT PANALPINA DOT COM]
Verzonden: woensdag 7 mei 2003 10:53
Aan: ADSM-L AT VM.MARIST DOT EDU
Onderwerp: Directories problem ...


Hi all,

Once again, a mystery concerning directories backups !

Environment : TSM server 5.1.6.2 on aix 4.3.3. client 4.2.2.1 on aix
4.3.3 Problem : a node named pacrs040, belonging a domain called "AIX"
uses a management class called "mgmt-sap-l1" to store it's directories
structure, but no file is written in the corresponding storage pool. How
do you explain that ?? Some details :

------------------- q mgmt aix active

Policy       Policy       Mgmt         Default      Description
Domain       Set Name     Class        Mgmt
Name                      Name         Class ?
---------    ---------    ---------    ---------
------------------------
AIX          ACTIVE       AIX-INF--    No           Logical logs for SAP
DB
                           SAP-LOGS                  v 1 d 0 re 0 ro 0
AIX          ACTIVE       AIX-SYST-    Yes          aix system files
default
                           EM                        mgmt class e 5 d 5
re
                                                     20 ro 60
AIX          ACTIVE       MGMT-SAP     No           sap database archive
                                                     level 0 v 5 d 0 re
                                                     nolimit ro nolimit
AIX          ACTIVE       MGMT-SAP-    No           Mgmt-class for
Level1
                           -L1                       BKUPS v 15 d 0 re
                                                     nolimit ro nolimit

----------------- q copy aix active mgmt-sap-l1 f=d

            Policy Domain Name: AIX
               Policy Set Name: ACTIVE
               Mgmt Class Name: MGMT-SAP-L1
               Copy Group Name: STANDARD
               Copy Group Type: Backup
          Versions Data Exists: 15
         Versions Data Deleted: 0
         Retain Extra Versions: No Limit
           Retain Only Version: No Limit
                     Copy Mode: Modified
            Copy Serialization: Shared Dynamic
                Copy Frequency: 0
              Copy Destination: TAPELTO1_SAP_DB
Last Update by (administrator): SAX021
         Last Update Date/Time: 18.04.2002 09:09:24

-----------------  show version pacrs040 8 namet=fsid (snippet of it,
normally thousands of entries)

/proxy_3.5 : / (MC: MGMT-SAP-L1)
Active, Inserted 11/08/02 06:47:32
ObjId: 0.172812824

/proxy_3.5 : / admin-serv (MC: MGMT-SAP-L1)
Active, Inserted 04/23/02 15:46:22
ObjId: 0.126105569

/proxy_3.5 : / adminacl (MC: MGMT-SAP-L1)
Active, Inserted 04/23/02 15:46:22
ObjId: 0.126105570

----------------  q occ pacrs040 stg=tapelto1_sap_db

ANR2034E QUERY OCCUPANCY: No match found using this criteria. ANS8001I
Return code 11.



I understand that TSM uses the mgmt_class having the longest retension
period to store the directory structure, but what escapes me is that I
can't find that data in the destination storage pool ! Off course, this
is only one example, I have several tens of nodes behaving like that ...
Would that mean that all directory structure for all those nodes (all
AIX) is stored in TSM DB ? Thanks for your explanations ;-) Cheers.

Arnaud

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
| Arnaud Brion, Panalpina Management Ltd., IT Group     |
| Viaduktstrasse 42, P.O. Box, 4002 Basel - Switzerland |
| Phone: +41 61 226 19 78 / Fax: +41 61 226 17 01       |
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=










**********************************************************************
The information in this E-Mail is confidential and may be legally
privileged. It may not represent the views of Scottish and Southern
Energy plc. It is intended solely for the addressees. Access to this
E-Mail by anyone else is unauthorised. If you are not the intended
recipient, any disclosure, copying, distribution or any action taken or
omitted to be taken in reliance on it, is prohibited and may be
unlawful. Any unauthorised recipient should advise the sender
immediately of the error in transmission.

Scottish Hydro-Electric, Southern Electric, SWALEC and S+S
are trading names of the Scottish and Southern Energy Group.
**********************************************************************


 

Attachment: mgmtdetail
Description: mgmtdetail

<Prev in Thread] Current Thread [Next in Thread>