Results 1 to 7 of 7
  1. #1
    Member
    Join Date
    Jun 2011
    Posts
    94
    Thanks
    2
    Thanked 0 Times in 0 Posts

    Default Significance of STGNEW,STGDELETE,STGREUSE volume history entries

    Hi Team

    Our environment uses TSM6.2 Server.

    Can anyone explain the significance of STGNEW,STGDELETE,STGREUSE in volume history. Is it still relevant in TSM 6.2 ???

    We backup Database every day and just before the database backup, We use the following script "delvolh" daily to clear out the Volume history entries

    Name Line Command
    Number
    ---------- ------ ------------------------------------------------------------
    DELVOLH 5 del volh tod=today t=DBS
    10 del volh tod=today t=STGN
    15 del volh tod=today t=STGR
    20 del volh tod=today t=STGD
    25 del volh tod=today t=DBB

    The script is run in the follwing order

    1 ba stg disk offsite w=y
    5 ba stg onsite offsite w=y
    10 ru delvolh ( Volume history deletion script )
    15 ba db dev=lto5 t=dbs w=y
    20 ru delvolh ( Volume history deletion script )
    25 ba db dev=lto5 t=f w=y
    30 ru delvolh ( Volume history deletion script )
    35 ba volh filename=/home/pzatsm/recoverydir/volhist.out
    40 ba devconf filename=/home/pzatsm/recoverydir/devconf.out

    Please confirm if this is ok ???

  2. #2
    Moderator moon-buddy's Avatar
    Join Date
    Aug 2005
    Location
    Somewhere in the US
    Posts
    5,935
    Thanks
    4
    Thanked 233 Times in 228 Posts

    Default

    Do you use DRM? If you use DRM, you should not be using DEL VOLHIST.

    STGNEW - new volume added to a stgpool
    STGDELETE - deleted volume from a stgpool
    STGREUSE - scratch tapes


    They are all relevant in TSM even for 6.2

    Your script looks fine but 'del volhist' removed IF you use DRM.
    Ed

  3. #3
    Member
    Join Date
    Oct 2007
    Location
    Australia
    Posts
    92
    Thanks
    0
    Thanked 9 Times in 9 Posts

    Default

    I'd amend moon-buddy's comments slightly. DEL VOLHIST on STGNEW, STGDELETE, and STGREUSE is not unreasonable (in my opinion, in the general case), but on DB backups, it certainly is a bad thing if you use DRM; I would be using DRM to manage the cycling of database backup tapes, rather than relying on volume history manipulations.

    Why? Simply put: tape leaks. If you do a DEL VOLHIST TYPE=DBB, it circumvents the normal DRM expiration process, and forcibly removes all record of the database backup(s) in question. Unless you have other ways to track DR volumes, that means that you lose track of those tapes. Extremely dodgy.

  4. #4
    Member
    Join Date
    Jun 2011
    Posts
    94
    Thanks
    2
    Thanked 0 Times in 0 Posts

    Default

    Hi Moon-buddy,

    We use DRM..

    We run the script everyday in Production after all the backups and move the copy tapes to DR Site nearby

    We do a DR restore on the same day on a daily basis.

    Hope this is fine. Please confirm.

  5. #5
    Member
    Join Date
    Oct 2007
    Location
    Australia
    Posts
    92
    Thanks
    0
    Thanked 9 Times in 9 Posts

    Default

    Quote Originally Posted by anandgmenon View Post
    Hi Moon-buddy,

    We use DRM..
    Then I would ditch - completely - the line that says "del volh tod=today t=DBB", and amend the other del volh commands to keep at least a few days - a month, perhaps, or even two - worth of volume history. The DBS history entries should also not be deleted. Use the MOVE DRM command to manage the offsite tapes instead, and look into the DB expiration option in the DRM options (QUERY DRMSTATUS will tell you what it's set to, and the help for that command will give you other relevant commands; sorry, I'm not in front of TSM right now.)

  6. #6
    Member
    Join Date
    Jun 2011
    Posts
    94
    Thanks
    2
    Thanked 0 Times in 0 Posts

    Default

    Hi Sjl,

    Every day in DR we do a point in time restore of the latest TSM DB and then proceed with the DR Client restores.

    This ensures that DR and Production are having the same data backup.

    I hope this is perfect. . Is it not ???

  7. #7
    Moderator moon-buddy's Avatar
    Join Date
    Aug 2005
    Location
    Somewhere in the US
    Posts
    5,935
    Thanks
    4
    Thanked 233 Times in 228 Posts

    Default

    Quote Originally Posted by anandgmenon View Post
    Hi Sjl,

    Every day in DR we do a point in time restore of the latest TSM DB and then proceed with the DR Client restores.

    This ensures that DR and Production are having the same data backup.

    I hope this is perfect. . Is it not ???
    As mentioned - get away from del volhist for the DB volumes -

    What a tedious way of syncing your systems. There are more effecient and less tedious ways of doing this.
    Ed

Similar Threads

  1. Volume history entries
    By wesd in forum TSM Database
    Replies: 3
    Last Post: 03-10-2009, 07:05 AM
  2. delete a particular volume from volume history
    By sathishdas in forum TSM Server
    Replies: 2
    Last Post: 02-21-2008, 10:16 PM
  3. Volume history
    By Ashok in forum TSM Documentation,Tips and Tricks
    Replies: 1
    Last Post: 06-13-2005, 11:45 AM
  4. Delete Volume History
    By rischard in forum Backup / Archive Discussion
    Replies: 2
    Last Post: 08-05-2003, 02:36 AM
  5. What's the volume history really for?
    By cabec in forum TSM Server
    Replies: 3
    Last Post: 07-30-2003, 08:13 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •