Thanks for the reply Bob, you don't know how much hassle i've had trying to get HP to understand.
So those graphs showing the filenames are near full. isn't actually true? as the filenames will just grow as needed, because if thats teh case i can abort this job.
if so i can now abort the purge filenames which i'm running again and has beeen running for just over 5 hours now. I checked the purge log and its been stuck on below text
14/08/2014 10:55:15 ASM.4920.0 ["/db/dc/dcpurge/dcpurge.c $Rev: 39452 $ $Date:: 2013-10-10 20:51:21":1319] A.07.00 b105
[dcpurge_hosts] starting purge for host *servername*
Multiple passes needed. This will decrease the performance of purge session.
To improve performance increase the amount of memory purge is allowed to use.
You can control the amount of memory purge uses with PurgeBufferSize global option
i asked this of HP and they've not been too helpful with that either, they just says sometimes this can take several hours or even days!!!
which i've told them i can't leave this running for days with us making no backups.
I've also found out that the omnitrig -stop command they asked me to run stops scheduled backups, and they never asked me to to run omnitrig -start which is why the backups didn't run last, wish they would have told me that before
Thanks