ADSM-L

Re: [ADSM-L] Several simultaneous backups of an AIX client

2008-10-23 11:28:52
Subject: Re: [ADSM-L] Several simultaneous backups of an AIX client
From: "Hart, Charles A" <charles_hart AT UHC DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 23 Oct 2008 10:27:36 -0500
If multiple file systems you could make sure there's a stream for each,
you could break it in small chunk with more stream using the Virtual
Mount point option then increase the Resource Util and Maxnummp for the
CLIent, other wise tar up all the files and send to TSM but you may end
up backing up stuff that hasn't changed.


Examples Options file: virtualmountpoint /afs/xyzcorp.com/home/ellen
virtualmountpoint /afs/xyzcorp.com/home/ellen/test/data
The virtualmountpoint option defines a virtual mount point for a file
system if you want to consider files for backup that begin with a
specific directory within that file system. Using the virtualmountpoint
option to identify a directory within a file system provides a direct
path to the files you want to back up, saving processing time. It is
more efficient to define a virtual mount point within a file system than
it is to define that file system using the domain option, and then to
use the exclude option in your include-exclude options list to exclude
the files that you do not want to back up. Use the virtualmountpoint
option to define virtual mount points for multiple file systems, for
local and remote file systems, and to define more than one virtual mount
point within the same file system. Virtual mount points cannot be used
in a file system handled by automounter.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Joni Moyer
Sent: Thursday, October 23, 2008 10:20 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Several simultaneous backups of an AIX client

Hello everyone,

I have a situation with an AIX TSM client which is at the 5.5.0.6
release on a TSM server which is on AIX and is at 5.5.1.1.  The client
has 18 million files to inspect when doing a daily incremental backup
that begins at 9PM and as you can see below took almost 11 hours.  As
you can guess this just isn't acceptable to run for this long period of
time.  Does anyone have any suggestions on what could be done in order
to get this server backed up incrementally in a quicker fashion?  Any
suggestions are greatly appreciated!

10/23/08 07:59:24     ANE4952I (Session: 40206, Node: CHRS141)  Total
number of
                       objects inspected: 18,540,895(SESSION: 40206)
10/23/08 07:59:24     ANE4954I (Session: 40206, Node: CHRS141)  Total
number of
                       objects backed up:  225,018(SESSION: 40206)
10/23/08 07:59:24     ANE4958I (Session: 40206, Node: CHRS141)  Total
number of
                       objects updated:          0(SESSION: 40206)
10/23/08 07:59:24     ANE4960I (Session: 40206, Node: CHRS141)  Total
number of
                       objects rebound:          0(SESSION: 40206)
10/23/08 07:59:24     ANE4957I (Session: 40206, Node: CHRS141)  Total
number of
                       objects deleted:          0(SESSION: 40206)
10/23/08 07:59:24     ANE4970I (Session: 40206, Node: CHRS141)  Total
number of
                       objects expired:      3,376(SESSION: 40206)
10/23/08 07:59:24     ANE4959I (Session: 40206, Node: CHRS141)  Total
number of
                       objects failed:           0(SESSION: 40206)
10/23/08 07:59:24     ANE4961I (Session: 40206, Node: CHRS141)  Total
number of
                       bytes transferred: 25.57 GB(SESSION: 40206)
10/23/08 07:59:24     ANE4963I (Session: 40206, Node: CHRS141)  Data
transfer
                       time:                31,313.02 sec(SESSION:
40206)

10/23/08 07:59:24     ANE4966I (Session: 40206, Node: CHRS141)  Network
data
                       transfer rate:          856.53 KB/sec(SESSION:
40206)
10/23/08 07:59:24     ANE4967I (Session: 40206, Node: CHRS141)
Aggregate
data
                       transfer rate:        685.82 KB/sec(SESSION:
40206)

10/23/08 07:59:24     ANE4968I (Session: 40206, Node: CHRS141)  Objects
                       compressed by:                    0%(SESSION:
40206)
10/23/08 07:59:24     ANE4964I (Session: 40206, Node: CHRS141)  Elapsed
                       processing time:            10:51:47(SESSION:
40206)

                     Node Name: CHRS141
                      Platform: AIX
               Client OS Level: 5.3
                Client Version: Version 5, release 5, level 0.6
            Policy Domain Name: AIX
         Last Access Date/Time: 10/23/08 10:55:10
        Days Since Last Access: <1
        Password Set Date/Time: 08/24/04 12:55:29
       Days Since Password Set: 1,521
         Invalid Sign-on Count: 0
                       Locked?: No
                       Contact: Open Systems
                   Compression: No
       Archive Delete Allowed?: Yes
        Backup Delete Allowed?: Yes
        Registration Date/Time: 08/24/04 12:55:29
     Registering Administrator: LIDZR8V
Last Communication Method Used: Tcp/Ip
   Bytes Received Last Session: 241.55 M
       Bytes Sent Last Session: 3,157
      Duration of Last Session: 10.16
   Pct. Idle Wait Last Session: 5.16
  Pct. Comm. Wait Last Session: 47.67
  Pct. Media Wait Last Session: 0.00
                     Optionset:
                           URL: http://chrs141:1581
                     Node Type: Client
    Password Expiration Period:
             Keep Mount Point?: No
  Maximum Mount Points Allowed: 4


********************************
Joni Moyer
Highmark
Storage Systems, Storage Mngt Analyst III Phone Number: (717)302-9966
Fax: (717) 302-9826
joni.moyer AT highmark DOT com
********************************


This e-mail, including attachments, may include confidential and/or 
proprietary information, and may be used only by the person or entity to 
which it is addressed. If the reader of this e-mail is not the intended 
recipient or his or her authorized agent, the reader is hereby notified 
that any dissemination, distribution or copying of this e-mail is 
prohibited. If you have received this e-mail in error, please notify the 
sender by replying to this message and delete this e-mail immediately.