We have a bit of a situation at our site. TSM is broken and is going to take a day or two to fix.
Our production databases have got FAILARCHPATH set to separate mount points on each server.
I am calculating from log size and the number of logs archived over the last 60 days how many days grace the FAILARCHPATH will give each database - or how long the engineers have got to fix the TSM server.
When FAILARCHPATH fills up, I take it DB2 will use the primary / secondary log location and that will gradually fill up as well?
An example using simple numbers. The database generates 5Gb of archive logs a day.
FAILARCHPATH has got 30Gb free
primary log location has got 10Gb free (allowing space for primary logs and secondaries created / removed)
Therefore have I got (30 + 10) / 5 = 8 days of archive log space?
It sounds reasonable to me. Although when TSM is fixed, will the log files from FAILARCHPATH get archived to TSM at that point? If not, and you are doing regular backups, then you can manually delete the older logs (> 2 days older than last backup) from the FAILARCHPATH. This would give you more time.