Hi With the option of set drmprimstgpool, you do not have to do any of the below. It would be just like setting up the DRM for Copystgpools. DRM manages and dictates which tapes would have to go offsite and which tapes comes back onsite.
You would not encounter problems like what you are having as DRM would show you which tapes are empty/scratched. Let DRM manage your primary storage pool volumes. This is what TSM is designed to do. You do not have to re-invent the process. The process is done for you. With DRM managing your primary storage pools, look at the following option: 1) move drmedia 2) checkin libvol This will fix all your problems... Allow DRM to do the work for you. At the moment you would have to do a complete manual inventory of whats onsite and whats offsite to get all tapes/carts back in-sync. The way you do this is by checking in the primary storage pool what volumes have valid data or valid carts to what you have offsite. This should fix your problem and after this follow the DRM process. Thks Sean -----Original Message----- From: Uwe Schreiber [mailto:[EMAIL PROTECTED] Sent: Friday, April 02, 2004 3:13 PM To: [EMAIL PROTECTED] Subject: Re: vaulting primary storage pool volumes Hi, i'am using the move media functionality to vault primary stgpool volumes created by TDP for R/3. i use the following commands in a checkout-script for the checkout mov med * stg=tape_db_t1 wherestatu=full wheresta=mountablei ovfloc=Tresor-Securitas days=0 remove=bulk acc=readw mov med * stg=tape_db_t2 wheresta=mountablei ovfloc=Tresor-Securitas days=0 remove=bulk acc=readw mov med * stg=tape_db_t3 wheresta=mountablei ovfloc=Tresor-Securitas days=0 remove=bulk acc=readw -------------- i build a list of empty tapes for this diskpools via q med * stg=tape_db_t* wherestatu=empty wherest=mountablen --------------- a special checkin-script checks wether the requested tapes where checked-in the library and then makes a move media with which the tapes will be deleted from the storagepool and then check them in again as scratch pg /adsmscripts1/checkin_primary | while read line do set $line BAND=`echo $4` CAT=`mtlib -l /dev/lmcp0 -qE -V$BAND | grep category | cut -c29-32` if [ "$CAT" = "FF00" ] then $CMD1 "move media $BAND stg=tape_* wherestate=mountablenotinlib" >> $LOGFILE sleep 3 $CMD1 "checkin libv tsmlib1 $BAND stat=scr devt=3590 checkl=no" >> $LOGFILE echo "========================================================" >> $LOGFILE else echo $BAND >> $ERRORFILE fi done Mit freundlichen GrÃÃen / Best Regards Uwe Schreiber [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 02.04.2004 14:03 Please respond to [EMAIL PROTECTED] To [EMAIL PROTECTED] cc Subject Re: vaulting primary storage pool volumes Hi Have you looked at the option of set drmprimstgpool. These primary storage pools with the above option would be managed by DRM. You would not have the below problem. DRM/TSM would manage all of this for you. Thks Sean -----Original Message----- From: Bill Boyer [mailto:[EMAIL PROTECTED] Sent: Friday, April 02, 2004 1:44 PM To: [EMAIL PROTECTED] Subject: Re: vaulting primary storage pool volumes These is a TDP Informix backup tape(s). The DBA runs the onbar backup with 3-streams direct to tape over the SAN. He wants to be able to restore the database in the case of a disaster using those same 3-streams. If TSM copies the data to a copypool, then the data will probably be combined onto a single tape and he says that the recovery time will be a lot more. That's why they elected to vault the primary pool. But if the MOVE MEDIA command has an option WHERESTATUS=EMPTY I'm assuming that if the tapes are managed via MOVE MEDIA then they will go to EMPTY state and stay there. According the the MOVE MEDIA in the admin reference, doing the MOVE MEDIA WHERESTATE=MOUNTABNOTINLIB, if the tape is EMPTY it will be returned to scratch status with this command. I'm just asking if anyone uses this command and if that's how it really does work. Bill Boyer DSS, Inc. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Stapleton, Mark Sent: Thursday, April 01, 2004 11:10 PM To: [EMAIL PROTECTED] Subject: Re: vaulting primary storage pool volumes From: ADSM: Dist Stor Manager on behalf of Bill Boyer I have a client that wishes to vault a primary storage pool volumes on a daily basis. Unfortunately they didn't have Autovault <grin>. So for the DBbackup and copypool tapes I configured a script that uses MOVE DRMEDIA and for the primary storage pool, I got a list of tapes in the library for that storage pool and then did a CHECKOUT on each volume and the UPD VOL ACC=UNAVAIL LOC="Vault". This works just fine, but when these tapes have all their data expired and they go empty, TSM scratches the tapes. All this before I can get a list of tapes with STATUS=EMPTY. Doing some research I found the MOVE MEDIA command. Now the question is will tapes that are MOUNTABLENOTINLIB processed with the MOVE MEDIA and they go empty, will TSM leave them in this status=empty until I issue another MOVE MEDIA command to bring them back? The reports haven't been showing any tapes to come back. The empty tapes are immediately returned to scratch even though they are UNAVAIL and LOC=Vault. Right now the operators are comparing todays full vault list with yesterdays to figure out which tapes need to come back. ======================== I'm reminded of the fellow that was always breaking wooden pegs when he used them to nail together 2x4s... Your client is working directly against one of the strengths of TSM. Why would anyone want to vault their primary storage pool? That prevents using TSM to restore accidently deleted files. Further, primary pool tapes *will* go immediately to scratch status when they're no longer members of a storage pool. -- Mark Stapleton âThis e-mail is sent on the Terms and Conditions that can be accessed by Clicking on this link http://www.vodacom.net/legal/email.asp " “This e-mail is sent on the Terms and Conditions that can be accessed by Clicking on this link http://www.vodacom.net/legal/email.asp "
