1st thing first -
redo log backup = archive (brarchive)
When you say "backup" you should refer to the overall backup, and just call the redo log backup an "archive" so as to keep things straight.
Additionally the database backup takes about an hour, what happens to the backups every 15 mins? Do they fail, do the mess up the database backup?
You obviously can't run a script every 15 min if the backup takes an hour. (how often are you taking the backup, anyway? or did you mean the archive job here?)
It is never a good idea to try to run these types jobs in tandem on the same database -
after all, they are using the very same resources...
Can you try staggering it out (the archive job) to say, 1.5 hours without filling the dir up?
I was thinking about doing something like that but I'm afraid that the database backup will get missed because dsmc schedule will be running new backups every 15 mins.
Also I would assume that you need SCHEDMODE POLLING vs. PROMPTED.
Your perl script should have nothing to do with the dsmc scheduler - right?
Because you were not using the TSM server to manage this - hence not knowing if the backup failed or not. (at least that is how I understood this)
If you were to use the scheduler to call your perl script, you don't need all the time interval stuff in the perl script as the TSM server would run it at a set interval for you.
You would, in this case, need to use SCHEDMODE PROMPTED to accomplish that.
Hope that helps / makes sense to you.
-Chef.