Hi Brian,

as I understand it, multiple restores streams of the same filesystem (on AIX, say) is 
dubious. And I doubt it would happen.

I have one very large filesystem , and I have done a couple of neat things to improve 
restores, and I've had to do it a couple of times.

The filesystem is /home/dbdumps (300 GBs, stores our database dumps). To speed up 
restores, I made several logical (or virtual) filesystems (as far TSM in concerned). 
This is what is in may dsm.opt file:
virtualmountpoint       /home/dbdumps/Daily/logical
virtualmountpoint       /home/dbdumps/Developers
virtualmountpoint       /home/dbdumps/Extra
virtualmountpoint       /home/dbdumps/Backup

Then when running a dsmc inc, you'll see:
Incremental backup of volume '/home/dbdumps'
Incremental backup of volume '/home/dbdumps/Daily/logical'
Incremental backup of volume '/home/dbdumps/Developers'
Incremental backup of volume '/home/dbdumps/Extra'
Incremental backup of volume '/home/dbdumps/Backup'

And in my inclexcl.list file:
Include         /home/dbdumps/.../*                     database
Include         /home/dbdumps/Daily/logical/.../*       database
Include         /home/dbdumps/Developers/.../*          database
Include         /home/dbdumps/Backup/.../*              database
Include         /home/dbdumps/Extra/.../*               database_onsite

and finally:
tsm: UNXR>q stg database f=d

               Storage Pool Name: DATABASE
               Storage Pool Type: Primary
               Device Class Name: 3580
         Estimated Capacity (MB): 94,020,767.0
                        Pct Util: 1.9
                        Pct Migr: 2.8
                     Pct Logical: 100.0
                    High Mig Pct: 90
                     Low Mig Pct: 70
                 Migration Delay: 0
              Migration Continue: Yes
             Migration Processes: 
               Next Storage Pool: 
            Reclaim Storage Pool: 
          Maximum Size Threshold: No Limit
                          Access: Read/Write
                     Description: Sybase Database backups - daily
               Overflow Location: 
           Cache Migrated Files?: 
                      Collocate?: Filespace
           Reclamation Threshold: 99
 Maximum Scratch Volumes Allowed: 500
   Delay Period for Volume Reuse: 1 Day(s)
          Migration in Progress?: No
            Amount Migrated (MB): 0.00
Elapsed Migration Time (seconds): 0
        Reclamation in Progress?: No
 Volume Being Migrated/Reclaimed: 
  Last Update by (administrator): PURDYM
           Last Update Date/Time: 02/19/03   14:00:11
        Storage Pool Data Format: Native
            Copy Storage Pool(s): 
         Continue Copy on Error?: 
                        CRC Data: No

Notice: collocate is filespace.

So now I can run 5 separate restores from 5 drives.

----------------------------------------------------------------------------------------------
Miles Purdy 
System Manager
Information Systems Team (IST),
Farm Income Programs Directorate (FIPD),
Agriculture and Agri-Food Canada (AAFC) 
Winnipeg, MB, CA
[EMAIL PROTECTED]
ph: (204) 984-1602 fax: (204) 983-7557

"If you hold a UNIX shell up to your ear, can you hear the C?"
-------------------------------------------------------------------------------------------------

>>> [EMAIL PROTECTED] 19-Feb-03 3:21:49 PM >>>
Hello,

AIX 5.1, TSM 4.2.2.8 (soon upgrading to 5.1)

I'm wondering if someone have good experiences with multiple restore
sessions. We have 4 drives in our library. When there are no other processes
and a client is starting a restore and files are spread over several tapes,
will there be up to 4 simultanious sessions for restoring?

Is it necessary to set collocation off, before you can use multiple restore
sessions, or with collocation enabled and data for one client spread over
more tapes it is also possible to get multiple restore-sessions?

Thanx,

Brian.





_________________________________________________________________
Hotmail en Messenger on the move
http://www.msn.nl/communicatie/smsdiensten/hotmailsmsv2/

Reply via email to