IBM Tivoli Storage Manager Express Ver: 5.3.7.3

Question I had to media tapes available at the moment, maybe this was the cause of the error?

No, it was the mount of at least one input volume that failed.

What could be a replacement for running monthly backup? What is your suggestion?


Thanks

GENERATE BACKUPSET is not a monthly backup! It just collects existing active backed up data to form a single object out of them.

One of the possible  "normal" TSM ways would be taking weekly full image backups and daily incremental filesystem backups, both targeted to your file pool (V:\TSM\BACKUPDATA, I assume).

In order to free up space on the file pool and to move the data onto tapes which maybe are to be stored in a safe location, define a NEXTSTGPOOL for your file pool and do a MIGRATE STGPOOL either manually or triggered by "High Mig Pct" and "Low Mig Pct" values configured for the file pool.

Should your file pool be big enough to hold all your backup data, you could use BACKUP STGPOOL instead of MIGRATE STGPOOL, to copy the data to a COPYSTGPOOL (tape DEVCLASS) defined by you for that purpose.


wmp

woolmilkporc:

Question:

How to would I make this possible? What are the steps?

Thanks

 

Which "version" do you prefer? MIGRATE or BACKUP?
This is a question of the capacity of your filepool

I believe that using Backup would consume less space.

Unfortunately not! BACKUP would leave all data in the filepool (while creating a backup copy), whereas MIGRATE would empty the filepool, thus making room for future client backups.

OK lets use Migrate backup copy.

Here you go:

I don't know the names of your existing storage pools, so I will call the pool containing your file volumes (e.g. V:\TSM\BACKUPDATA\00002EC1.BFS) "filepool" and I will call the pool containing your tapes "tapepool".

1) Issue UPD STGPOOL filepool NEXTSTGP=tapepool

2a) for automatic migration set the upper threshold (x % capacity filled where migration should start) and the lower threshold (y % capacity filled where migration should stop): UPD STGPOOL filepool HIGHMIG=x LOWMIG=y
Migration from disk to tape will start automatically once HIGHMIG is reached, and will stop once LOWMIG is reached.

2b) for manual migration: UPD STGPOOL filepool HIGHMIG=100
Issue on a regular basis (maybe via TSM scheduler): MIGRATE STGPOOL filepool

wmp

Good Morning woolmilkporc,

I am a beginner in tivoli so if you could tell me how to find the name of my existing pools.

Thanks

QUERY STGPOOL

... but, if it wasn't you, who configured those pools?

NO It was configured by external consultants before starting to work here.

MY STORAGE POOL NAME IS DATAPOOL ,IS THER ANOTHER COMMAND TO VERIFY THE TAPEPOOL.

THANKS

Did only one storage pool show up? There is no other command to display those pools!

If you use tapes and files you need at least two pools, because you cannot mix these media in one pool.

woolmilkporc:

This is shows when runing command


tsm: S250>QUERY STGPOOL

Storage      Device       Estimated    Pct    Pct  High  Low  Next Stora-
Pool Name    Class Name    Capacity   Util   Migr   Mig  Mig  ge Pool
                                                    Pct  Pct
-----------  ----------  ----------  -----  -----  ----  ---  -----------
DATAPOOL     IBM_DATAC-    20,215 G    4.1    5.0    90   70
              LASS

tsm: S250>QUERY TAPEPOOL
ANR2000E Unknown command - QUERY TAPEPOOL.
ANS8001I Return code 2.

tsm: S250>

That's very strange!

Could it be that you don't use any tapes with TSM?

Please post the output of "Q STGPOOL DATAPOOL F=D" and "Q DEVC IBM_DATACLASS F=D"

btw. there is no command "q tapepool". Pools of tape volumes are storage pools (stgpools), just as pools of  file volumes are.

tsm: S250>Q STGPOOL DATAPOOL F=D

               Storage Pool Name: DATAPOOL
               Storage Pool Type: Primary
               Device Class Name: IBM_DATACLASS
              Estimated Capacity: 20,201 G
              Space Trigger Util: 82.4
                        Pct Util: 3.9
                        Pct Migr: 4.7
                     Pct Logical: 97.0
                    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:
               Overflow Location:
           Cache Migrated Files?:
                      Collocate?: Group
more...   (<ENTER> to continue, 'C' to cancel)

           Reclamation Threshold: 60
       Offsite Reclamation Limit:
 Maximum Scratch Volumes Allowed: 9,999
  Number of Scratch Volumes Used: 470
   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): SERVER_CONSOLE
           Last Update Date/Time: 12/04/2007 16:16:25
        Storage Pool Data Format: Native
            Copy Storage Pool(s):
         Continue Copy on Error?:
                        CRC Data: No
                Reclamation Type: Threshold


tsm: S250tsm: S250>Q DEVC IBM_DATACLASS F=D

             Device Class Name: IBM_DATACLASS
        Device Access Strategy: Sequential
            Storage Pool Count: 1
                   Device Type: FILE
                        Format: DRIVE
         Est/Max Capacity (MB): 2,048.0
                   Mount Limit: 50
              Mount Wait (min):
         Mount Retention (min):
                  Label Prefix:
                  Drive Letter:
                       Library:
                     Directory: V:\TSM\BACKUPDATA
                   Server Name:
                  Retry Period:
                Retry Interval:
                      Twosided:
                        Shared:
            High-level Address:
              Minimum Capacity:
                          WORM: No
               Scaled Capacity:

I'm clueless ...

How can you work with tapes (as you told me) without an appropriate storage pool and device class?

Or did I understand you wrong and you actually take your backups to disk files only?

??

wmp

The TSM actually works with disk backups and afterwards copied the dialy backups to Media Tapes.

Which is the IBM System Storage TS3100 Tape Library for backups.

Thanks

Now I begin to understand this strange "CREATE BACKUPSET" thing!

Creating a backupset is the only (!) way to write data onto TSM tapes without having a storage pool for these media.
Believe it or not, I'm working with TSM for nearly 15 (fifteen) years, and up to now I never met people doing it this way.

Doesn't your disk storage pool get full over time? A backupset is only a copy, not a migration.
Did you ever have to restore data from a backupset (e.g. because of a damaged disk file)? If not, I'd strongly advise you to test it!

Anyway, since this method seems to work for you, and since changing it would mean redesigning nearly all of your backup strategy, you should go on with it.

This said, back to your original question. Is your "mount failed"/"media inaccessible" problem solved, or is there still something I could help you with?

wmp

Would it be a pain to redesign to whole backup strategy ? IS their a way to create a backup pool for the media? without having to reconfigure the whole thing.
Actually this is taking upo very much space on out drives.

Well,
in order to decide what should be changed I need to know rather exactly what you're doing now.
What backup jobs resp. schedules do you run? What are they doing, "backup image"? "incremental filesystem"? "incremental image" (hopefully not)?
How much tapes do you have, how much of them are filled with backupsets?
Do you have an elaborate recovery plan? If so, this would be the biggest drawback, because we would have to redesing this plan, too.
How is the DEVCLASS for the tapes defined?

Please post as much of the above info as possible.

Anyway, it can be done, I'm sure.

wmp

Is their a command i could run to verify all backup jobs that are schedules? or the only option is through GUI?

select SCHEDULE_NAME, DESCRIPTION, ACTION, OPTIONS, OBJECTS, PERIOD, PERUNITS, DAYOFWEEK from CLIENT_SCHEDULES

q devc * f=d

select VOLUME_NAME, STGPOOL_NAME, PCT_UTILIZED, DEVCLASS_NAME from volumes

Do you run jobs not scheduled by TSM?

             Device Class Name: DC_01
        Device Access Strategy: Sequential
            Storage Pool Count: 0
                   Device Type: LTO
                        Format: DRIVE
         Est/Max Capacity (MB):
                   Mount Limit: DRIVES
              Mount Wait (min): 60
         Mount Retention (min): 60
                  Label Prefix: ADSM
                  Drive Letter:
                       Library: LIBRERIA-KEVANE
                     Directory:
                   Server Name:
                  Retry Period:
                Retry Interval:
                      Twosided:
                        Shared:
            High-level Address:
              Minimum Capacity:
                          WORM: No
               Scaled Capacity:
more...   (<ENTER> to continue, 'C' to cancel)

Last Update by (administrator): EXCELLERE
         Last Update Date/Time: 10/16/2008 13:42:23

             Device Class Name: DISK
        Device Access Strategy: Random
            Storage Pool Count: 0
                   Device Type:
                        Format:
         Est/Max Capacity (MB):
                   Mount Limit:
              Mount Wait (min):
         Mount Retention (min):
                  Label Prefix:
                  Drive Letter:
                       Library:
                     Directory:
                   Server Name:
                  Retry Period:
                Retry Interval:
                      Twosided:
                        Shared:
            High-level Address:
              Minimum Capacity:
more...   (<ENTER> to continue, 'C' to cancel)

                          WORM: No
               Scaled Capacity:
Last Update by (administrator):
         Last Update Date/Time: 12/04/2007 16:15:12

             Device Class Name: IBM_DATACLASS
        Device Access Strategy: Sequential
            Storage Pool Count: 1
                   Device Type: FILE
                        Format: DRIVE
         Est/Max Capacity (MB): 2,048.0
                   Mount Limit: 50
              Mount Wait (min):
         Mount Retention (min):
                  Label Prefix:
                  Drive Letter:
                       Library:
                     Directory: V:\TSM\BACKUPDATA
                   Server Name:
                  Retry Period:
                Retry Interval:
                      Twosided:
                        Shared:
more...   (<ENTER> to continue, 'C' to cancel)

            High-level Address:
              Minimum Capacity:
                          WORM: No
               Scaled Capacity:
Last Update by (administrator): SERVER_CONSOLE
         Last Update Date/Time: 12/04/2007 16:16:25

             Device Class Name: IBM_DBBKUPFILE
        Device Access Strategy: Sequential
            Storage Pool Count: 0
                   Device Type: FILE
                        Format: DRIVE
         Est/Max Capacity (MB): 2,048.0
                   Mount Limit: 5
              Mount Wait (min):
         Mount Retention (min):
                  Label Prefix:
                  Drive Letter:
                       Library:
                     Directory: V:\TSM\DBBACKUP
                   Server Name:
                  Retry Period:
                Retry Interval:
more...   (<ENTER> to continue, 'C' to cancel)

                      Twosided:
                        Shared:
            High-level Address:
              Minimum Capacity:
                          WORM: No
               Scaled Capacity:
Last Update by (administrator): SERVER_CONSOLE
         Last Update Date/Time: 12/04/2007 16:16:26

             Device Class Name: IBM_MEDIACOPIES
        Device Access Strategy: Sequential

W

            Storage Pool Count: 0
                   Device Type: FILE
                        Format: DRIVE
         Est/Max Capacity (MB): 2,048.0
                   Mount Limit: 50
              Mount Wait (min):
         Mount Retention (min):
                  Label Prefix:
                  Drive Letter:
                       Library:
                     Directory: V:\TSM\BACKUPDATA\MEDIACOPIES
                   Server Name:
more...   (<ENTER> to continue, 'C' to cancel)

                  Retry Period:
                Retry Interval:
                      Twosided:
                        Shared:
            High-level Address:
              Minimum Capacity:
                          WORM: No
               Scaled Capacity:
Last Update by (administrator): SERVER_CONSOLE
         Last Update Date/Time: 12/04/2007 16:16:25


tsm: S250>q devc * f=d

             Device Class Name: DC_01
        Device Access Strategy: Sequential
            Storage Pool Count: 0
                   Device Type: LTO
                        Format: DRIVE
         Est/Max Capacity (MB):
                   Mount Limit: DRIVES
              Mount Wait (min): 60
         Mount Retention (min): 60
                  Label Prefix: ADSM
                  Drive Letter:
                       Library: LIBRERIA-KEVANE
                     Directory:
                   Server Name:
                  Retry Period:
                Retry Interval:
                      Twosided:
                        Shared:
            High-level Address:
              Minimum Capacity:
                          WORM: No
               Scaled Capacity:
more...   (<ENTER> to continue, 'C' to cancel)

Last Update by (administrator): EXCELLERE
         Last Update Date/Time: 10/16/2008 13:42:23

             Device Class Name: DISK
        Device Access Strategy: Random
            Storage Pool Count: 0
                   Device Type:
                        Format:
         Est/Max Capacity (MB):
                   Mount Limit:
              Mount Wait (min):
         Mount Retention (min):
                  Label Prefix:
                  Drive Letter:
                       Library:
                     Directory:
                   Server Name:
                  Retry Period:
                Retry Interval:
                      Twosided:
                        Shared:
            High-level Address:
              Minimum Capacity:
more...   (<ENTER> to continue, 'C' to cancel)

                          WORM: No
               Scaled Capacity:
Last Update by (administrator):
         Last Update Date/Time: 12/04/2007 16:15:12

             Device Class Name: IBM_DATACLASS
        Device Access Strategy: Sequential
            Storage Pool Count: 1
                   Device Type: FILE
                        Format: DRIVE
         Est/Max Capacity (MB): 2,048.0
                   Mount Limit: 50
              Mount Wait (min):
         Mount Retention (min):
                  Label Prefix:
                  Drive Letter:
                       Library:
                     Directory: V:\TSM\BACKUPDATA
                   Server Name:
                  Retry Period:
                Retry Interval:
                      Twosided:
                        Shared:
more...   (<ENTER> to continue, 'C' to cancel)

            High-level Address:
              Minimum Capacity:
                          WORM: No
               Scaled Capacity:
Last Update by (administrator): SERVER_CONSOLE
         Last Update Date/Time: 12/04/2007 16:16:25

             Device Class Name: IBM_DBBKUPFILE
        Device Access Strategy: Sequential
            Storage Pool Count: 0
                   Device Type: FILE
                        Format: DRIVE
         Est/Max Capacity (MB): 2,048.0
                   Mount Limit: 5
              Mount Wait (min):
         Mount Retention (min):
                  Label Prefix:
                  Drive Letter:
                       Library:
                     Directory: V:\TSM\DBBACKUP
                   Server Name:
                  Retry Period:
                Retry Interval:
more...   (<ENTER> to continue, 'C' to cancel)

                      Twosided:
                        Shared:
            High-level Address:
              Minimum Capacity:
                          WORM: No
               Scaled Capacity:
Last Update by (administrator): SERVER_CONSOLE
         Last Update Date/Time: 12/04/2007 16:16:26

             Device Class Name: IBM_MEDIACOPIES
        Device Access Strategy: Sequential
            Storage Pool Count: 0
                   Device Type: FILE
                        Format: DRIVE
         Est/Max Capacity (MB): 2,048.0
                   Mount Limit: 50
              Mount Wait (min):
         Mount Retention (min):
                  Label Prefix:
                  Drive Letter:
                       Library:
                     Directory: V:\TSM\BACKUPDATA\MEDIACOPIES
                   Server Name:
more...   (<ENTER> to continue, 'C' to cancel)

                  Retry Period:
                Retry Interval:
                      Twosided:
                        Shared:
            High-level Address:
              Minimum Capacity:
                          WORM: No
               Scaled Capacity:
Last Update by (administrator): SERVER_CONSOLE
         Last Update Date/Time: 12/04/2007 16:16:25

hat I understand by this is the backup are sequential and that each volume created hold up to 2.0 GIG
of space.I presume its daily. i ran the command q devc * f=d  to find the info that appeared.
elect SCHEDULE_NAME, DESCRIPTION, ACTION, OPTIONS, OBJECTS, PERIOD, PERUNITS, DAYOFWEEK from CLIENT_SCHEDULES
I did not find these options in GUI.Maybe because I have the Express version of Tivoli.

I found this information on how the tsm devise class work In our case we have a sequential Access Devise Cllass:

The Device Class for Random Access Devices
Devices that access their media randomly share a common TSM device type. TSM provides a single, random-access device class, named DISK. You cannot define other random access device classes. You do not define a TSM library for random access devices.

Random access device types store data in blocks of storage that can be scattered across the available space on a disk. As the server deletes data that has expired, the space occupied by that data can be reused.


Device Classes for Sequential Access Devices
Tape devices, optical disk devices, FILE device types, and SERVER device types are members of the sequential access category of devices. All of these devices access their data sequentially. A device class for a sequential device contains a device type and media management information.

For tape and optical sequential devices, the device class also specifies a library. Figure 6 shows the contents of a device class for a typical sequential access device.

Figure 6. Contents of a Device Class for Sequential Access Devices





Sequential access device types begin to store data at the beginning of a volume, and append new data after existing data. As data is deleted or expired, the space is not immediately reused. The server can reclaim space later by using the reclamation process (see Reclaiming Space in Sequential Access Storage Pools for details).


Device Type
Every sequential access device class requires one of the TSM device types as part of its definition. A device type identifies a device as a member of a group of devices that share similar media characteristics. TSM provides device types for many devices. For example, TSM provides an 8MM device type for tape drives that use 8mm tape.

FILE is a sequential device type in TSM that allows the administrator to create sequential volumes by creating files on disk storage. To the TSM server, these files have the characteristics of a tape volume.

A device type called REMOVABLEFILE supports devices that have removable media and are attached to the server as local, removable file systems. TSM sees each unit of media, for example an optical disk, as a single, sequential access file.

The sequential device type called SERVER allows the server to store data on another TSM server. This data has the characteristics of a tape volume from the view of the source server. On the target server, this data appears as archived files that belong to a special type of node.


Library
For sequential access device types (excluding FILE and SERVER), you must specify a library in the device class definition. The library you specify must be one that you have defined to TSM, as discussed in Library.

The "select" thing is an SQL query. I don't know if you can run such queries from the GUI. Don't you have the dsmadmc CLI?

Anyway, I'll check your info till tomorrow.

Thanks talk to you soon.

>> In our case we have a sequential Access Device Class <<

Congratulations! You're learning fast!

Hi again,

if you don't manage to get the "select" to work, I will at least need the output of

Q LIBVOLUME  LIBRERIA-KEVANE

Please post!

Hey I was thinking of running a restore from media before doign any changes.
I think it would be a good idea, because we've really have not restored from media yet?
Maybe we could restore a small file.

tsm: S250>Q LIBVOLUME  LIBRERIA-KEVANE
Library Name  Volume Name  Status      Owner       Last Use   Home     Device
                                                              Element  Type
------------  -----------  ----------  ----------  ---------  -------  ------
LIBRERIA-KE-  650CCCL3     Private                 BackupSet  4,106
 VANE
LIBRERIA-KE-  658CCCL3     Private                 BackupSet  4,115
 VANE
LIBRERIA-KE-  666CCCL3     Private                 BackupSet  4,105
 VANE
LIBRERIA-KE-  670CCCL3     Private                 BackupSet  4,099
 VANE
LIBRERIA-KE-  672CCCL3     Private                 BackupSet  4,101
 VANE
LIBRERIA-KE-  674CCCL3     Private                 BackupSet  4,100
 VANE
LIBRERIA-KE-  675CCCL3     Private                 BackupSet  4,116
 VANE
LIBRERIA-KE-  676CCCL3     Private                 BackupSet  4,096
 VANE
LIBRERIA-KE-  677CCCL3     Private                 BackupSet  4,110
 VANE
LIBRERIA-KE-  679CCCL3     Private                            4,112
more...   (<ENTER> to continue, 'C' to cancel)

 VANE
LIBRERIA-KE-  680CCCL3     Scratch                            4,097
 VANE
LIBRERIA-KE-  681CCCL3     Private                 BackupSet  4,098
 VANE
LIBRERIA-KE-  685CCCL3     Scratch                            4,108
 VANE
LIBRERIA-KE-  689CCCL3     Scratch                            4,114
 VANE
LIBRERIA-KE-  693CCCL3     Private                 BackupSet  4,104

Is this the complete output of Q LIBVOL?

Do you really have only three scratch tapes? Do you delete the one or other backupset from time to time?

With such a small number of free tapes it wouldn't make any sense to define a storage pool over the DC_01 device class, as it's capacity would be exhausted soon.

It's always a good idea to test a restore. Use "restore backupset" to restore from media. The GUI should give some help for that.

wmp

I only have three scratch tapes available.
To be more clear on how i checkin the media tapes for my daily backups.

Every week to checkin Tapes I have to run this command.LABEL LIBVOL LIBRERIA-KEVANE SEARCH=YES WAITTIME=0 CHECKIN=SCRATCH LABELSOURCE=BARCODE OVERWRITE=YES

WHAT THIS COMMAND EXECUTES IS A SCRATCH WHICH OVERWRITES THE DATA OF THE MEDIA?
CORRECT ME IF IÁM WRONG.
QUESTION:
WHEN YOU SAY to define a storage pool over the DC_01 device class, as it's capacity would be exhausted soon.WHAT DO YOU MEAN BY THIS?

THANKS

I assume you insert new tape(s) before issuing LABEL LIBVOL ... ? If so, only the newly inserted tape(s) will be overwritten.

When we define a storage pool over DC_01, we could either

- add the three free tapes to that pool -> No more GENERATE BACKUPSET possible  or

- allow for using scratch -> backupset and pool would compete for the free tapes. We could probably do one or two migrations and one GENERATE BACKUPSET and the library would be full.

How much slots does the lib have? If there were enough, why not purchase a bunch of tapes and check them all in?

wmp

Yes that is correct the newly inserted tapes are being overwritten.

Correct me if iám wrong your saying that the storage pool over DC_01 which is the device class.
We are adding three tapes to that device class with GENERATE BACKUPSET

i THINK THE MONTHLY GENERATE  BACKUP SET SHOULD BE REMOVE RIGHT?

I should isue  (ssue UPD STGPOOL filepool NEXTSTGP=tapepool)
Also another  possible way of doing is  "normal" TSM ways would be taking weekly full image backups and daily incremental filesystem backups, both targeted to your file pool (V:\TSM\BACKUPDATA, I assume). As mentioned ealier by you.
Actually I know we run a reclamation thresold in the morning, but I dont know the reclamtion thresold %.
Maybe I could lower this percent for it to run more often to make up more space and then run the proces mentioned.


 

The library has 23 slots and slot number 23 has the slot reserved for the cleaning tape.
I have only only available one slot to insert a tape.
The rest have tapes, and the reason the tapes cannot be used is because they have not expired.
The another thing I would like to work on, maybe I lower the time for expiration on the tapes.

I coul I find the RELAMATION THRESHOLD on tivoli

Q STGPOOL DATAPOOL F=D
.
.
Reclamation Threshold: 60

But this applies only to the files on disk. You don't have a storage pool for tapes!

GENERATE BACKUPSET creates tapes using the DC_01 deviceclass. These are not STORAGE POOL tapes!
TSM knows about them, but there is no reclamation or the like. Reclamation is a feature for storage pool volumes only!
A BACKUPSET expires over time (default 1 year) and the tape becomes free that way, or by issuing DELETE BACKUPSET. No other way, no reclamation!

Btw. would you please post the job which generates the backupsets?

Because there is no tapepool, the statement UPD STGPOOL datapool NEXTSTGP=tapepool would fail!

We must first create a tape pool, but not before we're agreed what to do with it!

>> The library has 23 slots and slot number 23 has the slot reserved for the cleaning tape.
I have only only available one slot to insert a tape. <<

Why does Q LIBVOL  LIBRERIA-KEVANE show only 15 tapes then?

You can only give up the practice of creating monthly backupsets all of a sudden if there is no elaborate recovery strategy at your site which takes those backupsets into account!

wmp

So it would be impossible to complete a full restore with the way we have the tsm configured, to be more clear actually I cannot complete a full restore without my storage pool volumes and only using the tape backups.

Maybe we could create a tape pool for tsm to migrate the files from storage pool volumes to tapes.

Also is their any way lower the expiration for the tapes to expire at a less time frame?

I dont know why i read only 15 tapes using the Q LIBVOL  LIBRERIA-KEVANE command.

Observation:

If i log on to the library through GUI interface I could find the 23 slots available with each tape in the slots.

First, please don't worry, you can do a complete restore using RESTORE BACKUPSET.
But, as you correctly state, if your disk pool (the V: volume) was broke, it could happen that in the worst case you could only restore 1 month old data.

To lower the expiration you can use UPDATE BACKUPSET, but hat command is a bit complex. To decide how to use it I actually need the exact command which you use to generate the backupset.

Yes, creating a tape pool and migrating regularly is a good thing. To ask it once more: How about your recovery plans? Do they rely on backupsets?

As for the tapes in the library - I will have to ponder on that. I'll tell you tomorrow!

Good night!

wmp

Good Morning,

 What iám going to try to do is create a restore plan using the RESTORE BACKUP SET to restore one month back data.

Speaking of lowering the expiration how do I find the command for generating the backup set.

Relying on backups sets is a safe thing , as long as it works. My question is how far back I could restore
data using backup sets?

Thanks

Good afternoon,

if you don't use to run commands by means of some kind of OS scheduler, the GENERATE BACKUPSET thing must sit in a TSM schedule.
Please check your TSM schedules, particularly the ACTION, OPTIONS and OBJECTS filelds.

You can restore data as far back as you do have backup sets. Issue QUERY BACKUPSET and you will see them all. As I wrote, the default retention is 1 year.
And remember, in case of a loss of your V: drive, the backupsets are all you have, the older the poorer (not like some good Bordeaux ...).

As for your tape library - well, there are tapes in it TSM doesn't know about. Is there something special with the tapes that show up in the library GUI and not in TSM? Is there something like "category"? If yes, compare the category definitions in the library to those found in TSM using QUERY LIBRARY LIBRERIA-KEVANE F=D

Attention - TSM displays the categories in decimal, while some libraries use HEX, e.g. category 556 in TSM might become 22C in the library.

wmp

I have several questions:

1- Does data type:image mean backup to Volume?
2-Does data type :File mean backup to Media Tapes?
Also why does retention period say 7 or 10,950
does 10,950 mean number of hours or days?
After understanding this we could go on to thenext step I dont want to get to lost.

Node Name: S550
             Backup Set Name: IBM_DAILY_DEFAULT.15675592
                   Data Type: Image
                   Date/Time: 09/01/2009 06:00:16
            Retention Period: 7
           Device Class Name: DC_01
                 Description: IBM_MEDIACOPY_DAILY
Has Table of Contents (TOC)?: Yes

                   Node Name: S550
             Backup Set Name: IBM_DAILY_DEFAULT.15701224
                   Data Type: Image
                   Date/Time: 09/02/2009 06:00:16
            Retention Period: 7
           Device Class Name: DC_01
                 Description: IBM_MEDIACOPY_DAILY
Has Table of Contents (TOC)?: Yes

                   Node Name: S550
             Backup Set Name: IBM_DAILY_DEFAULT.15725033
                   Data Type: Image
                   Date/Time: 09/03/2009 06:00:17
more...   (<ENTER> to continue, 'C' to cancel)

            Retention Period: 7
           Device Class Name: DC_01
                 Description: IBM_MEDIACOPY_DAILY
Has Table of Contents (TOC)?: Yes

                   Node Name: S550
             Backup Set Name: IBM_MONTHLY_DEFAULT.10491961
                   Data Type: File
                   Date/Time: 12/31/2008 02:00:04
            Retention Period: 10,950
           Device Class Name: DC_01
                 Description: IBM_MEDIACOPY_MONTHLY
Has Table of Contents (TOC)?: Yes

                   Node Name: S550
             Backup Set Name: IBM_MONTHLY_DEFAULT.11177696
                   Data Type: File
                   Date/Time: 01/31/2009 02:00:21
            Retention Period: 10,950
           Device Class Name: DC_01
                 Description: IBM_MEDIACOPY_MONTHLY
Has Table of Contents (TOC)?: Yes

more...   (<ENTER> to continue, 'C' to cancel)

                   Node Name: S550
             Backup Set Name: IBM_MONTHLY_DEFAULT.11808729
                   Data Type: File
                   Date/Time: 02/28/2009 02:00:01
            Retention Period: 10,950
           Device Class Name: DC_01
                 Description: IBM_MEDIACOPY_MONTHLY
Has Table of Contents (TOC)?: Yes

                   Node Name: S550
             Backup Set Name: IBM_MONTHLY_DEFAULT.12178539
                   Data Type: File
                   Date/Time: 03/31/2009 02:00:15
            Retention Period: 10,950
           Device Class Name: DC_01
                 Description: IBM_MEDIACOPY_MONTHLY
Has Table of Contents (TOC)?: Yes

                   Node Name: S550
             Backup Set Name: IBM_MONTHLY_DEFAULT.12708296
                   Data Type: File
                   Date/Time: 04/30/2009 02:00:02
            Retention Period: 10,950
more...   (<ENTER> to continue, 'C' to cancel)

           Device Class Name: DC_01
                 Description: IBM_MEDIACOPY_MONTHLY
Has Table of Contents (TOC)?: Yes

                   Node Name: S550
             Backup Set Name: IBM_MONTHLY_DEFAULT.9656481
                   Data Type: File
                   Date/Time: 10/31/2008 02:00:23
            Retention Period: 10,950
           Device Class Name: DC_01
                 Description: IBM_MEDIACOPY_MONTHLY
Has Table of Contents (TOC)?: Yes

                   Node Name: S600
             Backup Set Name: IBM_MONTHLY_DEFAULT.10491961
                   Data Type: File
                   Date/Time: 12/31/2008 02:00:04
            Retention Period: 10,950
           Device Class Name: DC_01
                 Description: IBM_MEDIACOPY_MONTHLY
Has Table of Contents (TOC)?: Yes

                   Node Name: S600
more...   (<ENTER> to continue, 'C' to cancel)

             Backup Set Name: IBM_MONTHLY_DEFAULT.11177696
                   Data Type: File
                   Date/Time: 01/31/2009 02:00:21
            Retention Period: 10,950
           Device Class Name: DC_01
                 Description: IBM_MEDIACOPY_MONTHLY
Has Table of Contents (TOC)?: Yes

                   Node Name: S600
             Backup Set Name: IBM_MONTHLY_DEFAULT.11808729
                   Data Type: File
                   Date/Time: 02/28/2009 02:00:01
            Retention Period: 10,950
           Device Class Name: DC_01
                 Description: IBM_MEDIACOPY_MONTHLY
Has Table of Contents (TOC)?: Yes

                   Node Name: S600
             Backup Set Name: IBM_MONTHLY_DEFAULT.12178539
                   Data Type: File
                   Date/Time: 03/31/2009 02:00:15
            Retention Period: 10,950
           Device Class Name: DC_01
more...   (<ENTER> to continue, 'C' to cancel)

                 Description: IBM_MEDIACOPY_MONTHLY
Has Table of Contents (TOC)?: Yes

                   Node Name: S600
             Backup Set Name: IBM_MONTHLY_DEFAULT.12708296
                   Data Type: File
                   Date/Time: 04/30/2009 02:00:02
            Retention Period: 10,950
           Device Class Name: DC_01
                 Description: IBM_MEDIACOPY_MONTHLY
Has Table of Contents (TOC)?: Yes

                   Node Name: S600
             Backup Set Name: IBM_MONTHLY_DEFAULT.13145182
                   Data Type: File
                   Date/Time: 05/31/2009 02:00:29
            Retention Period: 10,950
           Device Class Name: DC_01
                 Description: IBM_MEDIACOPY_MONTHLY
Has Table of Contents (TOC)?: Yes

                   Node Name: S600
             Backup Set Name: IBM_MONTHLY_DEFAULT.9656481
more...   (<ENTER> to continue, 'C' to cancel)

                   Data Type: File
                   Date/Time: 10/31/2008 02:00:23
            Retention Period: 10,950
           Device Class Name: DC_01
                 Description: IBM_MEDIACOPY_MONTHLY
Has Table of Contents (TOC)?: Yes

                   Node Name: S800
             Backup Set Name: IBM_MONTHLY_DEFAULT.10491961
                   Data Type: File
                   Date/Time: 12/31/2008 02:00:04
            Retention Period: 10,950
           Device Class Name: DC_01
                 Description: IBM_MEDIACOPY_MONTHLY
Has Table of Contents (TOC)?: Yes

                   Node Name: S800
             Backup Set Name: IBM_MONTHLY_DEFAULT.11177696
                   Data Type: File
                   Date/Time: 01/31/2009 02:00:21
            Retention Period: 10,950
           Device Class Name: DC_01
                 Description: IBM_MEDIACOPY_MONTHLY
more...   (<ENTER> to continue, 'C' to cancel)

Has Table of Contents (TOC)?: Yes

                   Node Name: S800
             Backup Set Name: IBM_MONTHLY_DEFAULT.11808729
                   Data Type: File
                   Date/Time: 02/28/2009 02:00:01
            Retention Period: 10,950
           Device Class Name: DC_01
                 Description: IBM_MEDIACOPY_MONTHLY
Has Table of Contents (TOC)?: Yes

                   Node Name: S800
             Backup Set Name: IBM_MONTHLY_DEFAULT.12178539
                   Data Type: File
                   Date/Time: 03/31/2009 02:00:15
            Retention Period: 10,950
           Device Class Name: DC_01
                 Description: IBM_MEDIACOPY_MONTHLY
Has Table of Contents (TOC)?: Yes

                   Node Name: S800
             Backup Set Name: IBM_MONTHLY_DEFAULT.12708296
                   Data Type: File
more...   (<ENTER> to continue, 'C' to cancel)

                   Date/Time: 04/30/2009 02:00:02
            Retention Period: 10,950
           Device Class Name: DC_01
                 Description: IBM_MEDIACOPY_MONTHLY
Has Table of Contents (TOC)?: Yes

                   Node Name: S800
             Backup Set Name: IBM_MONTHLY_DEFAULT.13145182
                   Data Type: File
                   Date/Time: 05/31/2009 02:00:29
            Retention Period: 10,950
           Device Class Name: DC_01
                 Description: IBM_MEDIACOPY_MONTHLY
Has Table of Contents (TOC)?: Yes

                   Node Name: S800
             Backup Set Name: IBM_MONTHLY_DEFAULT.9656481
                   Data Type: File
                   Date/Time: 10/31/2008 02:00:23
            Retention Period: 10,950
           Device Class Name: DC_01
                 Description: IBM_MEDIACOPY_MONTHLY
Has Table of Contents (TOC)?: Yes
more...   (<ENTER> to continue, 'C' to cancel)


                   Node Name: S801
             Backup Set Name: IBM_MONTHLY_DEFAULT.10491961
                   Data Type: File
                   Date/Time: 12/31/2008 02:00:04
            Retention Period: 10,950
           Device Class Name: DC_01
                 Description: IBM_MEDIACOPY_MONTHLY
Has Table of Contents (TOC)?: Yes

                   Node Name: S801
             Backup Set Name: IBM_MONTHLY_DEFAULT.11177696
                   Data Type: File
                   Date/Time: 01/31/2009 02:00:21
            Retention Period: 10,950
           Device Class Name: DC_01
                 Description: IBM_MEDIACOPY_MONTHLY
Has Table of Contents (TOC)?: Yes

                   Node Name: S801
             Backup Set Name: IBM_MONTHLY_DEFAULT.11808729
                   Data Type: File
                   Date/Time: 02/28/2009 02:00:01
more...   (<ENTER> to continue, 'C' to cancel)

            Retention Period: 10,950
           Device Class Name: DC_01
                 Description: IBM_MEDIACOPY_MONTHLY
Has Table of Contents (TOC)?: Yes

                   Node Name: S801
             Backup Set Name: IBM_MONTHLY_DEFAULT.12178539
                   Data Type: File
                   Date/Time: 03/31/2009 02:00:15
            Retention Period: 10,950
           Device Class Name: DC_01
                 Description: IBM_MEDIACOPY_MONTHLY
Has Table of Contents (TOC)?: Yes

                   Node Name: S801
             Backup Set Name: IBM_MONTHLY_DEFAULT.12708296
                   Data Type: File
                   Date/Time: 04/30/2009 02:00:02
            Retention Period: 10,950
           Device Class Name: DC_01
                 Description: IBM_MEDIACOPY_MONTHLY
Has Table of Contents (TOC)?: Yes

more...   (<ENTER> to continue, 'C' to cancel)

                   Node Name: S801
             Backup Set Name: IBM_MONTHLY_DEFAULT.13145182
                   Data Type: File
                   Date/Time: 05/31/2009 02:00:29
            Retention Period: 10,950
           Device Class Name: DC_01
                 Description: IBM_MEDIACOPY_MONTHLY
Has Table of Contents (TOC)?: Yes

                   Node Name: S801
             Backup Set Name: IBM_MONTHLY_DEFAULT.9656481
                   Data Type: File
                   Date/Time: 10/31/2008 02:00:23
            Retention Period: 10,950
           Device Class Name: DC_01
                 Description: IBM_MEDIACOPY_MONTHLY
Has Table of Contents (TOC)?: Yes

1-2)

Please look at "Device Class Name:"

Whenever you find DC_01 there, the backupset has been created on tape, since DC_01 is the deviceclass of your tape library.
All of your backupsets are on tape, obviously.  

The difference between "image" and "file" -

A backupset of type "image" contains copies of image data previously created on disk volumes using the BACKUP IMAGE command.

A backupset of type "file" contains copies of  file level data previously created on disk volumes using either of  the commands INCREMENTAL or SELECTIVE.

3)

Retention is in days, so 10,950 means "30 years"
Your job obviously sets this value during generation of the backupset, because the default value is 365 days.

tsm: S250>QUERY LIBRARY LIBRERIA-KEVANE F=D
Session established with server S250: Windows
  Server Version 5, Release 3, Level 7.3
  Server date/time: 09/03/2009 11:44:27  Last access: 09/03/2009 10:48:15


                  Library Name: LIBRERIA-KEVANE
                  Library Type: SCSI
                        ACS Id:
              Private Category:
              Scratch Category:
         WORM Scratch Category:
              External Manager:
                RSM Media Type:
                        Shared: No
                       LanFree:
            ObeyMountRetention:
       Primary Library Manager:
                           WWN:
                 Serial Number: 00L2U78F7233_LL0
                     AutoLabel: OVERWRITE
                  Reset Drives: No
Last Update by (administrator): EXCELLERE
         Last Update Date/Time: 10/16/2008 11:19:4

These were the results for the QUERY LIBRARY LIBRERIA-KEVANE F=D

Under category definitions nothing appears.
How could I compare them?

Thanks

Obviously you can't.

Does your library tell you something about categories (using the library GUI)?

I did not find any info on types of categories using the library GUI.

Maybe i could run a command line to find out this info.

Thanks