DRM: Backup Stgpool - use existing "filling" copypool tapes

[pichelman]

Hi,

In the past - we have left tapes in the library for the next night's backup that are in the filling status/readwr and "not" in Error status and were just written the previous night.

All the machines that are backed up nightly are poart of the same Collocation group.

When/why does TSM decide "not" to fill an existing COPYPOOL tape when it needs a tape for Backing up it's DISKPOOL as it is running "bkp stgpool Copypool" - and there are COPYPOOL tapes with ample room?

Normally we use 3 LTO2 tapes nightly - Two for COPYPOOL(fills 1 1/4 tapes) and One for DB Backup.
We'd liek to keep writing on the second tape during the holidays - we have done this before but had an issue this weekend.



Here is one of the tapes TSM refused to write and use and wanted a scratch instead...

####################################################

tsm: WMNATCHTSM>q vol WS0030L2 f=d

Volume Name: WS0030L2
Storage Pool Name: COPYPOOL1
Device Class Name: LTOCLASS1
Estimated Capacity: 381.5 G
Scaled Capacity Applied:
Pct Util: 19.5
Volume Status: Filling
Access: Read/Write
Pct. Reclaimable Space: 0.0
Scratch Volume?: Yes
In Error State?: No
Number of Writable Sides: 1
Number of Times Mounted: 1
Write Pass Number: 1
Approx. Date Last Written: 12/18/2009 09:27:50
Approx. Date Last Read: 12/18/2009 09:01:58
Date Became Pending:
Number of Write Errors: 0
Number of Read Errors: 0
Volume Location:
Volume is MVS Lanfree Capable : No
Last Update by (administrator): PICHELS
Last Update Date/Time: 12/18/2009 12:42:58
Begin Reclaim Period:
End Reclaim Period:
Drive Encryption Key Manager: None

####################################################


And some of the data/contents - TDP - Domino DB + System state data...



####################################################

tsm: WMNATCHTSM>q con WS0030L2

Node Name Type Filespace FSID Client's Name for File
Name
--------------- ---- ---------- ---- --------------------------------------
WMNADOM1TDP Bkup WARMSN1.D- 1 \WINET\MARKETING\ WINETVALVESCOMBATKI-
OMDBS TS.NSF.DATA
WMNADOM1TDP Bkup WARMSN1.D- 1 \WINET\MARKETING\ WINETVALVESIMAGES.N-
OMDBS SF.DATA
WMNADOM1TDP Bkup WARMSN1.D- 1 \WINET\MARKETING\ WINETVALVESINSTALL.-
OMDBS NSF.DATA
WMNADOM1TDP Bkup WARMSN1.D- 1 \WINET\OPERATIONS\ EXCESS.NSF.DATA
OMDBS
WMNADOM1TDP Bkup WARMSN1.D- 1 \WINET\OPERATIONS\ GLOBALFOUNDRYDATA.-
OMDBS NSF.DATA
WMNADOM1TDP Bkup WARMSN1.D- 1 \WINET\OPERATIONS\ GLOBALMACHINE.NSF.-
OMDBS DATA
WMNADOM1TDP Bkup WARMSN1.D- 1 \WINET\OPERATIONS\ KANBAN.NSF.DATA
OMDBS
WMNADOM1TDP Bkup WARMSN1.D- 1 \WINET\OPERATIONS\ WINETCBN.NSF.DATA
OMDBS
WMNADOM1TDP Bkup WARMSN1.D- 1 \WINET\OPERATIONS\ WINETGLOBALLOGISTI-
OMDBS CS.NSF.DATA
WMNADOM1TDP Bkup WARMSN1.D- 1 \WINET\OPERATIONS\ WINETKANBAN.NSF.DA-
OMDBS TA
WMNADOM1TDP Bkup WARMSN1.D- 1 \WINET\OPERATIONS\ WINETOPRES.NSF.DATA
OMDBS
WMNADOM1TDP Bkup WARMSN1.D- 1 \WINET\OPERATIONS\ WINETPATTERNINFO.N-
OMDBS SF.DATA
WMNADOM1TDP Bkup WARMSN1.D- 1 \WINET\PURCHASING\ RAWRUBBER.NSF.DATA
OMDBS
WMNADOM1TDP Bkup WARMSN1.D- 1 \WINET\PURCHASING\ WINETCOMMODITIES.N-
OMDBS SF.DATA
WMNADOM1TDP Bkup WARMSN1.D- 1 \WINET\PURCHASING\ WINETKPISCHEDULE.N-
OMDBS SF.DATA
WMNADOM1TDP Bkup WARMSN1.D- 1 \WINET\PURCHASING\ WINETKPIUSERMANDEF-
OMDBS .NSF.DATA
WMNADOM1TDP Bkup WARMSN1.D- 1 \WINET\PURCHASING\ WINETLCSOURCE.NSF.-
OMDBS DATA
WMNADOM1TDP Bkup WARMSN1.D- 1 \WINET\PURCHASING\ WINETMONTHPURCHASE-
OMDBS REP.NSF.DATA
WMNADOM1TDP Bkup WARMSN1.D- 1 \WINET\PURCHASING\ WINETOUTLINEAGREE.-
OMDBS NSF.DATA
WMNADOM1TDP Bkup WARMSN1.D- 1 \WINET\PURCHASING\ WINETPURCHDOCS.NSF-
OMDBS .DATA
WMNADOM1TDP Bkup WARMSN1.D- 1 \WINET\PURCHASING\ WINETSUPPLIERAGREE-
OMDBS .NSF.DATA
WMNADOM1TDP Bkup WARMSN1.D- 1 \ WMDINTRANET.NSF.DATA
OMDBS
HADESTDP Bkup WARMSN2.D- 1 \WINET\PURCHASING\ WINETCOMMODITIES.N-
OMDBS SF.DATA
HADESTDP Bkup WARMSN2.D- 1 \ WSGTECHN.NSF.DATA
OMDBS
EXTERNAL4 Bkup SYSTEM 1 \WINDOWS\REPAIR\BACKUP\BOOTABLESYSTEM-
STATE STATE\ COMREGISTRATIONDATABASE
EXTERNAL4 Bkup SYSTEM 1 \WINDOWS\REPAIR\BACKUP\BOOTABLESYSTEM-
STATE STATE\COMREGISTRATIONDATABASE\
COMREGDB.BAK
EXTERNAL4 Bkup SYSTEM 1 \WINDOWS\REPAIR\BACKUP\BOOTABLESYSTEM-
STATE STATE\REGISTRY\ DEFAULT
EXTERNAL4 Bkup SYSTEM 1 \WINDOWS\REPAIR\BACKUP\BOOTABLESYSTEM-
STATE STATE\REGISTRY\ SAM
EXTERNAL4 Bkup SYSTEM 1 \WINDOWS\REPAIR\BACKUP\BOOTABLESYSTEM-
STATE STATE\REGISTRY\ SECURITY

###################################################

Many thanks for any ideas.


-SP

 

[BBB]

In my experience, when backup storage pool command runs out of space on a tape, it will usually grab a fresh scratch tape to start writing to. It would be better if it didn't but for whatever reason it appears to prefer to do that. Whereas when you start the "backup stgpool", it will often start out using a already filling tape. Sometimes this can lead to tapes in "filling" status hanging around for a long time, and can waste a lot of tapes if you are using collocation. I use a script to find these and manually reclaim them (move data vol recons=yes).