If you can't get internal storage,....
This server is an old IBM, running Win, with old and small disks on it that only accept very specific (and expansive) disks in its array. For sure a bad ROI.
But, for this issue I think it could be possible as an extreme action to plug a external hdd, in order to have enough disk space wich allow the reclamation, migration and expiration procedures. Could this work? If yes, I'll need to learn how to create this new pool and redirect the backups to it.
Ok migration starts and stops likely because you don't have any tapes that are in a filling state. Everything is likely marked as full.
In fact, "q vol" shows this one:
Code:
524AGJL4 TAPEPOOL DEVCLASS_- 1.5 T 30.5 Filling
When I say disable client sessions the command is 'disable sessions' to enable sessions its 'enable sessions'.
Since "q event * * " reports that almost all tasks have been running ok, and I have several backup copies. My bet is I have just the Database incremental logs to be concerned with. So, I've disable the sessions.
Bit of a jam here...
For any backup solution, one must have space for backups!
Absolutely right
To reply to some of your more direct questions:
So a setting of 0 says if it needs to migrate right away, do it!
Done!!
-- lomig and himig is when TSM will start and stop migration of data automatically to the next storage pool. In this case, tape.
More questions:
Code:
tsm: JACARANDA>q copyg Policy Policy Mgmt Copy Version- Version- Retain Retain
Domain Set Name Class Group s Data s Data Extra Only
Name Name Name Exists Deleted Versions Version
--------- --------- --------- --------- -------- -------- -------- -------
PD_ORA ACTIVE ORA_DSK STANDARD No Limit No Limit 0 0
PD_ORA ACTIVE ORA_LBR STANDARD No Limit No Limit 0 0
PD_ORA PS_ORA ORA_DSK STANDARD No Limit No Limit 0 0
PD_ORA PS_ORA ORA_LBR STANDARD No Limit No Limit 0 0
PD_SQL ACTIVE 15D_DSK STANDARD No Limit No Limit 15 15
PD_SQL ACTIVE 15D_LBR STANDARD No Limit No Limit 15 15
PD_SQL ACTIVE 30D_DSK STANDARD No Limit No Limit 30 30
PD_SQL ACTIVE 30D_DSK_- STANDARD No Limit No Limit 30 30
ABS
PD_SQL ACTIVE 30D_LBR STANDARD No Limit No Limit 30 30
PD_SQL ACTIVE 30D_LBR_- STANDARD No Limit No Limit 30 30
ABS
PD_SQL ACTIVE 365D_DSK STANDARD No Limit No Limit 365 365
PD_SQL ACTIVE 365D_DSK- STANDARD No Limit No Limit 365 365
_ABS
PD_SQL ACTIVE 365D_LBR STANDARD No Limit No Limit 365 365
PD_SQL ACTIVE 365D_LBR- STANDARD No Limit No Limit 365 365
_ABS
PD_SQL PS_SQL 15D_DSK STANDARD No Limit No Limit 15 15
PD_SQL PS_SQL 15D_LBR STANDARD No Limit No Limit 15 15
PD_SQL PS_SQL 30D_DSK STANDARD No Limit No Limit 30 30
PD_SQL PS_SQL 30D_DSK_- STANDARD No Limit No Limit 30 30
ABS
PD_SQL PS_SQL 30D_LBR STANDARD No Limit No Limit 30 30
PD_SQL PS_SQL 30D_LBR_- STANDARD No Limit No Limit 30 30
ABS
PD_SQL PS_SQL 365D_DSK STANDARD No Limit No Limit 365 365
PD_SQL PS_SQL 365D_DSK- STANDARD No Limit No Limit 365 365
_ABS
PD_SQL PS_SQL 365D_LBR STANDARD No Limit No Limit 365 365
PD_SQL PS_SQL 365D_LBR- STANDARD No Limit No Limit 365 365
_ABS
PD_UNIX ACTIVE 15D_DSK STANDARD No Limit No Limit 15 15
PD_UNIX ACTIVE 15D_LBR STANDARD No Limit No Limit 15 15
PD_UNIX ACTIVE 30D_DSK STANDARD No Limit No Limit 30 30
PD_UNIX ACTIVE 30D_DSK_- STANDARD No Limit No Limit 30 30
ABS
PD_UNIX ACTIVE 30D_LBR STANDARD No Limit No Limit 30 30
PD_UNIX ACTIVE 30D_LBR_- STANDARD No Limit No Limit 30 30
ABS
PD_UNIX ACTIVE 365D_DSK STANDARD No Limit No Limit 365 365
PD_UNIX ACTIVE 365D_DSK- STANDARD No Limit No Limit 365 365
_ABS
PD_UNIX ACTIVE 365D_LBR STANDARD No Limit No Limit 365 365
PD_UNIX ACTIVE 365D_LBR- STANDARD No Limit No Limit 365 365
_ABS
PD_UNIX PS_UNIX 15D_DSK STANDARD No Limit No Limit 15 15
PD_UNIX PS_UNIX 15D_LBR STANDARD No Limit No Limit 15 15
PD_UNIX PS_UNIX 30D_DSK STANDARD No Limit No Limit 30 30
PD_UNIX PS_UNIX 30D_DSK_- STANDARD No Limit No Limit 30 30
ABS
PD_UNIX PS_UNIX 30D_LBR STANDARD No Limit No Limit 30 30
PD_UNIX PS_UNIX 30D_LBR_- STANDARD No Limit No Limit 30 30
ABS
PD_UNIX PS_UNIX 365D_DSK STANDARD No Limit No Limit 365 365
PD_UNIX PS_UNIX 365D_DSK- STANDARD No Limit No Limit 365 365
_ABS
PD_UNIX PS_UNIX 365D_LBR STANDARD No Limit No Limit 365 365
PD_UNIX PS_UNIX 365D_LBR- STANDARD No Limit No Limit 365 365
_ABS
PD_WIN ACTIVE 15D_DSK STANDARD No Limit No Limit 15 15
PD_WIN ACTIVE 15D_LBR STANDARD No Limit No Limit 15 15
PD_WIN ACTIVE 30D_DSK STANDARD No Limit No Limit 30 30
PD_WIN ACTIVE 30D_DSK_- STANDARD No Limit No Limit 30 30
ABS
PD_WIN ACTIVE 30D_LBR STANDARD No Limit No Limit 30 30
PD_WIN ACTIVE 30D_LBR_- STANDARD No Limit No Limit 30 30
ABS
PD_WIN ACTIVE 365D_DSK STANDARD No Limit No Limit 365 365
PD_WIN ACTIVE 365D_DSK- STANDARD No Limit No Limit 365 365
_ABS
PD_WIN ACTIVE 365D_LBR STANDARD No Limit No Limit 365 365
PD_WIN ACTIVE 365D_LBR- STANDARD No Limit No Limit 365 365
_ABS
PD_WIN PS_WIN 15D_DSK STANDARD No Limit No Limit 15 15
PD_WIN PS_WIN 15D_LBR STANDARD No Limit No Limit 15 15
PD_WIN PS_WIN 30D_DSK STANDARD No Limit No Limit 30 30
PD_WIN PS_WIN 30D_DSK_- STANDARD No Limit No Limit 30 30
ABS
PD_WIN PS_WIN 30D_LBR STANDARD No Limit No Limit 30 30
PD_WIN PS_WIN 30D_LBR_- STANDARD No Limit No Limit 30 30
ABS
PD_WIN PS_WIN 365D_DSK STANDARD No Limit No Limit 365 365
PD_WIN PS_WIN 365D_DSK- STANDARD No Limit No Limit 365 365
_ABS
PD_WIN PS_WIN 365D_LBR STANDARD No Limit No Limit 365 365
PD_WIN PS_WIN 365D_LBR- STANDARD No Limit No Limit 365 365
_ABS
STANDARD ACTIVE STANDARD STANDARD 2 1 30 60
STANDARD STANDARD STANDARD STANDARD 2 1 30 60
Is expire inventory running? Lets check this month:
Code:
SELECT DATE(start_time) as "DATE", TRANSLATE('a bc:de:fg', DIGITS(end_time-start_time), '_______abcdefgh_____',' ') as "ELAPTIME (D HHMMSS)", -
affected, number, successful FROM summary WHERE activity='EXPIRATION' AND entity IS NULL AND SUBSTR(CHAR(start_time),1,7) = '2018-11' ORDER BY "DATE"
Code:
DATE ELAPTIME (D HHMMSS) Unnamed[3] NUMBER SUCCESSFUL
----------- -------------------- --------------------- ------------ -----------
2018-11-01 0 00:01:11 -470424 5 YES
2018-11-01 0 00:00:03 0 6 YES
2018-11-02 0 00:00:49 -470276 8 YES
2018-11-02 0 00:00:04 0 9 YES
2018-11-03 0 00:00:03 0 12 YES
2018-11-03 0 00:02:26 -536189 11 YES
2018-11-04 0 00:00:06 -5737 14 YES
2018-11-04 0 00:00:11 0 15 YES
2018-11-05 0 00:29:53 -2116807 17 YES
2018-11-05 0 00:00:52 0 4 YES
2018-11-06 0 00:02:30 -591321 7 YES
2018-11-06 0 00:00:33 0 9 YES
2018-11-07 0 00:02:00 -478464 12 YES
2018-11-07 0 00:00:03 0 13 YES
2018-11-08 0 00:05:46 -537614 20 YES
2018-11-08 0 00:00:52 0 4 YES
2018-11-09 0 00:00:06 0 11 YES
2018-11-09 0 00:00:47 -470359 8 YES
2018-11-10 0 00:02:18 -498952 17 YES
2018-11-10 0 00:00:33 0 18 YES
2018-11-11 0 00:02:36 -66297 20 YES
2018-11-11 0 00:00:44 0 21 YES
2018-11-12 0 00:32:40 -1668185 23 YES
2018-11-12 0 00:00:19 0 24 YES
2018-11-13 0 00:00:44 -72148 33 YES
2018-11-13 0 00:00:03 0 36 YES
2018-11-14 0 00:02:33 -458919 40 YES
2018-11-14 0 00:00:02 0 42 YES
2018-11-14 0 00:00:02 0 44 YES
2018-11-14 0 00:00:03 0 43 YES
2018-11-14 0 00:00:32 0 45 YES
2018-11-14 0 00:00:33 0 46 YES
2018-11-14 0 00:00:02 -10 53 YES
2018-11-14 0 00:00:02 0 54 YES
2018-11-14 0 00:00:03 0 58 YES
2018-11-14 0 00:00:02 -6 57 YES
2018-11-15 0 00:02:25 -457683 61 YES
2018-11-15 0 00:00:03 0 62 YES
2018-11-16 0 00:02:15 -372887 64 YES
2018-11-16 0 00:00:33 0 66 YES
2018-11-17 0 00:06:54 -380056 76 YES
2018-11-17 0 00:00:03 0 77 YES
2018-11-18 0 00:02:49 -72015 79 YES
2018-11-18 0 00:00:03 -21 80 YES
2018-11-19 0 00:23:31 -1856622 82 YES
2018-11-19 0 00:00:14 -177 83 YES
2018-11-20 0 00:00:03 -166 86 YES
2018-11-20 0 00:00:36 -150419 85 YES
2018-11-21 0 00:07:39 -471714 88 YES
2018-11-21 0 00:00:03 0 89 YES
2018-11-21 0 00:00:52 0 3 YES
2018-11-22 0 00:02:16 -674514 253 YES
2018-11-22 0 00:00:02 0 302 YES
2018-11-22 0 00:00:03 0 376 YES
2018-11-23 0 00:03:44 -377222 602 YES
Output of 'q db f=d' - lets check database backup.
Code:
JACARANDA>q db f=d
Database Name: TSMDB1
Total Size of File System (MB): 456,941
Space Used on File System(MB): 396,555
Space Used by Database(MB): 30,408
Free Space Available (MB): 60,386
Total Pages: 1,415,172
Usable Pages: 1,414,716
Used Pages: 1,389,212
Free Pages: 25,504
Buffer Pool Hit Ratio: 99.9
Total Buffer Requests: 805,213,542
Sort Overflows: 0
Package Cache Hit Ratio: 99.8
Last Database Reorganization: 11/18/2018 17:58:39
Full Device Class Name: DEVCLASS_LTO4
Number of Database Backup Streams: 1
Incrementals Since Last Full: 0
Last Complete Backup Date/Time: 11/23/2018 10:00:22
Compress Database Backups: No
output of 'q log f=d' - I'm concerned if database backups haven't ran and if we get lucky....we may run out of log space.
Code:
tsm: JACARANDA>q log f=d
Active Log Directory: E:\TSM_BD_LOG\LOG
Total Space(MB): 32,768
Used Space(MB): 202
Free Space(MB): 32,566
Archive Log Directory: E:\TSM_BD_LOG\ARCHLOG
Total Size of File System (MB): 456,941.00
Space Used on File System (MB): 396,554.93
Free Space(MB): 60,386.07
Archive Log Compressed: No
Mirror Log Directory:
Total Size of File System (MB):
Space Used on File System (MB):
Free Space(MB):
Archive Failover Log Directory:
Total Size of File System (MB):
Space Used on File System (MB):
Free Space(MB):
Lets take a step to the side here and look at where your database backup's are going to.
q volhist type=dbb
Code:
q volhist type=dbb
Date/Time: 11/22/2018 10:01:02
Volume Type: BACKUPFULL
Backup Series: 67
Backup Operation: 0
Volume Seq: 100,001
Device Class: DEVCLASS_LTO4
Volume Name: 986AGIL4
Volume Location:
Command:
Database Backup ID High: 0
Database Backup ID LOW: 0
Database Backup Home Position: 0
Database Backup HLA:
Database Backup LLA:
Database Backup Total Data Bytes (MB) : 0
Database Backup total Log Bytes (MB) : 0
Database Backup Block Num High: 0
Database Backup Block Num Low: 0
Database Backup Stream Id: 1
Database Backup Volume Sequence for Stream: 100,001
Date/Time: 11/23/2018 10:01:04
Volume Type: BACKUPFULL
Backup Series: 68
Backup Operation: 0
Volume Seq: 100,001
Device Class: DEVCLASS_LTO4
Volume Name: 479AGJL4
Volume Location:
Command:
Database Backup ID High: 0
Database Backup ID LOW: 0
Database Backup Home Position: 0
Database Backup HLA:
Database Backup LLA:
Database Backup Total Data Bytes (MB) : 0
Database Backup total Log Bytes (MB) : 0
Database Backup Block Num High: 0
Database Backup Block Num Low: 0
Database Backup Stream Id: 1
Database Backup Volume Sequence for Stream: 100,001
q volhist type=dbs
No match fond
The above commands should show all information regarding database backups of Full + incremental if any. Then database snapshots. My hope is that database backups are going to the LTO tapes and we have several versions of them to work with.
