Backup failures - Node exceeded max num of mount points

[unixandtsm]

Hi all,

Backups fail often and when i check the act log i see below error messages often.

ANS0326E This node has exceeded its maximum number of mount points

I tried to query the node on TSM server but couldn't get to see the value of MAXNMP parameter in the output.
Below is the output of q node.

q node <node_name> f=d

                     Node Name: <node_name>
                      Platform: Linux86
               Client OS Level: 2.6.18-12
                Client Version: Version 5, release 5, level 1.0
            Policy Domain Name: STANDARD
         Last Access Date/Time: 08/14/2012 16:43:59
        Days Since Last Access: <1
        Password Set Date/Time: 05/12/2012 06:16:18
       Days Since Password Set: 94
         Invalid Sign-on Count: 0
                       Locked?: No
                       Contact:
                   Compression: Client
       Archive Delete Allowed?: Yes
        Backup Delete Allowed?: No
        Registration Date/Time: 01/18/2011 04:58:02
     Registering Administrator: ADMIN
Last Communication Method Used: Tcp/Ip
   Bytes Received Last Session: 1,527
       Bytes Sent Last Session: 5,229
      Duration of Last Session: 8.35
   Pct. Idle Wait Last Session: 0.00
  Pct. Comm. Wait Last Session: 0.00
  Pct. Media Wait Last Session: 0.00
                     Optionset:
                           URL:
                     Node Type: Client
    Password Expiration Period: 240 Day(s)
             Keep Mount Point?: No
  Maximum Mount Points Allowed: 1
        Auto Filespace Rename : No
             Validate Protocol: No
                   TCP/IP Name: Node_name
                TCP/IP Address: <IP_address>
            Globally Unique ID: 8f.0e.84.fa.22.de.11.e0.b0.09.00.13.21.0a.68.ee
         Transaction Group Max: 0
               Data Write Path: ANY
                Data Read Path: ANY
            Session Initiation: ClientOrServer
            High-level Address:
             Low-level Address:
        Collocation Group Name:
              Proxynode Target:
               Proxynode Agent:
                   Node Groups:
                 Email Address:

how to increase MAXNMP parameter ?
what are the requirements to increase this parameter ?

Most of the time all of the tape drives available on this TSM server are busy so will increasing the MAXNMP do the trick for me ?
So many questions

 

[Trident]

Maximum Mount Points Allowed: 1

upd node XXXXXXX MAXNUMMP=10

 

[unixandtsm]

Thank you Trident.

how to find how much we can increase the value of MAXNMP ?
Will increasing the MAXNMP parameter 10 require high number of tape drives available ?
what exactly this increase will do ?
Thanks in advance!

 

[Trident]

Maximum Mount Points is relevant for devicetype of file and tape. So, if you send data to a fileclass, you need to have devclass mount limit higher to compensate. If you send datato tape, then you need more drives available.

The actual amount to enter depends on your bandwidth from the client, compresion status, type data, and what type of tape hardware you have.

1 Gb link to LTO3/4 (No Compression with compressible data) = 1
1 Gb link to LTO3/4 (Compression) = 2

For lanfree, it depends on your FC infrastructure. But between 2 and 4 should be OK.

With some hw info, it would be easier to estimate these figures.

 

[inestler]

Hi all,

Most of the time all of the tape drives available on this TSM server are busy so will increasing the MAXNMP do the trick for me ?
So many questions

No, you have to have more mount points - if you are limited by tape drives just use a disk storagepool and it makes a better performance if you backup a lot of small files.

 

[unixandtsm]

I am getting confused here with the term "mount points"
what are the mount points if the data is going to disk ?
i assume if the data is going to tape then mount point would be "tape drive" is this right ?

Little background here:

As for the node in question, the copygroup is "STANDARD" and the data in this copygroup is destined to a disk pool called BACKUPPOOL and next stgpool for that disk pool is a tape pool BKUPJA of 3592 tape device class.

>q copy STANDARD ACTIVE f=d

                 Policy Domain Name: STANDARD
                    Policy Set Name: ACTIVE
                    Mgmt Class Name: STANDARD
                    Copy Group Name: STANDARD
                    Copy Group Type: Backup
               Versions Data Exists: 2
              Versions Data Deleted: 1
              Retain Extra Versions: 30
                Retain Only Version: 1,825
                          Copy Mode: Modified
                 Copy Serialization: Shared Static
                     Copy Frequency: 0
                   Copy Destination: [B]BACKUPPOOL[/B]
Table of Contents (TOC) Destination:
     Last Update by (administrator): ADMIN
              Last Update Date/Time: 07/18/12   12:08:29
                   Managing profile:
                    Changes Pending: No

>q stg BACKUPPOOL f=d

               Storage Pool Name: BACKUPPOOL
               Storage Pool Type: Primary
               Device Class Name: [B]DISK[/B]
              Estimated Capacity: 101 G
              Space Trigger Util: 99.7
                        Pct Util: 0.1
                        Pct Migr: 0.1
                     Pct Logical: 100.0
                    High Mig Pct: 70
                     Low Mig Pct: 10
                 Migration Delay: 0
              Migration Continue: Yes
             Migration Processes: 1
           Reclamation Processes:
               Next Storage Pool: [B]BKUPJA[/B]
            Reclaim Storage Pool:
          Maximum Size Threshold: No Limit
                          Access: Read/Write
                     Description:
               Overflow Location:
           Cache Migrated Files?: No
                      Collocate?:
           Reclamation Threshold:
       Offsite Reclamation Limit:
 Maximum Scratch Volumes Allowed:
  Number of Scratch Volumes Used:
   Delay Period for Volume Reuse:
          Migration in Progress?: No
            Amount Migrated (MB): 196.39
Elapsed Migration Time (seconds): 3,358
        Reclamation in Progress?:
  Last Update by (administrator): ADMIN
           Last Update Date/Time: 08/14/12   19:36:44
        Storage Pool Data Format: Native
            Copy Storage Pool(s):
             Active Data Pool(s):
         Continue Copy on Error?: Yes
                        CRC Data: No
                Reclamation Type:
     Overwrite Data when Deleted:

>q stg BKUPJA f=d

               Storage Pool Name: BKUPJA
               Storage Pool Type: Primary
               Device Class Name: [B]3592H-C[/B]
              Estimated Capacity: 615,018 G
              Space Trigger Util:
                        Pct Util: 27.8
                        Pct Migr: 70.2
                     Pct Logical: 99.6
                    High Mig Pct: 90
                     Low Mig Pct: 70
                 Migration Delay: 0
              Migration Continue: Yes
             Migration Processes: 1
           Reclamation Processes: 1
               Next Storage Pool:
            Reclaim Storage Pool:
          Maximum Size Threshold: No Limit
                          Access: Read/Write
                     Description: 3592 Pool
               Overflow Location:
           Cache Migrated Files?:
                      Collocate?: Group
           Reclamation Threshold: 60
       Offsite Reclamation Limit:
 Maximum Scratch Volumes Allowed: 500
  Number of Scratch Volumes Used: 351
   Delay Period for Volume Reuse: 0 Day(s)
          Migration in Progress?: No
            Amount Migrated (MB): 0.00
Elapsed Migration Time (seconds): 0
        Reclamation in Progress?: No
  Last Update by (administrator): ADMIN
           Last Update Date/Time: 08/14/12   19:40:44
        Storage Pool Data Format: Native
            Copy Storage Pool(s):
             Active Data Pool(s):
         Continue Copy on Error?: Yes
                        CRC Data: No
                Reclamation Type: Threshold
     Overwrite Data when Deleted:

Please help me with this....thanks in advance!


AND also i updated the node with MAXNUMMP with 5 (from 1) but again i end up backup failure

 

[Trident]

Hi,

If all your backup goes to a stg with devtype=DISK, then all you need to do is update the node's dsm.opt file

resoureutil 10

Try some different values, and see what gives the best perfomance. Start with a low number, then increase until you have saturated your link.

 

[inestler]

MAXNUMMP limits only access to tape or sequential disk. How large are the files on this client (>100GB)? how many filessystems and virtuell mountpionts does the client have?

 

[unixandtsm]

yes the filesystems are in TB of size and there are about 26 filesystems need to be backedup and they are grouped into two sections to start at different times...so one group of 14 start at one time and another start after few hours of the first group backups...

 

[inestler]

guess your storagepool is to small (101GB) files greater than this will be written on tape directly. maybe 13 FS in one backup schedule need to much resources. another split can be helpfull.

 

[cwilloug]

MAXNMP info http://pic.dhe.ibm.com/infocenter/t...maxnummp.html?resultof="MAXNUMMP" "maxnummp"

 

[phil7]

hi
The actual amount to enter depends on your bandwidth from the client, compresion status, type data, and what type of tape hardware you have.
1 Gb link to LTO3/4 (No Compression with compressible data) = 1
1 Gb link to LTO3/4 (Compression) = 2
but tapes are 400/800gb does that mean i can increase my mount points to 6 or more cos one of my nodes has reached max mount point