I'm with Riaan - how big is this catalog?
If Image Cleanup takes 20 hours - how long does a Catalog backup take?
How often is catalog backup done?
You need to consider how long a catalog restore will take should the master suffer a catastrophic failure.
This may be a good time to have a good look at business needs and distinguish between recovery needs and retention requirements.
Backup of a server's OS is normally only needed for system recovery. Here only the most recent backup is needed and there should be no need for lengthy retention periods.
The data on the servers may need to be kept for extended periods.
Here you need to find out what the legal requirements are - there is hardly ever a need for Infinity.
Lots of users simply select Infinity because NBU does not have retention periods such as 5, 7 or 10 years by default.
Retention levels 10 - 24 can be customized to meet business retention requirements.
Big file servers, sharepoint servers and mail servers normally contain lots of old, unreferenced data.
So, investigating and deploying an Archive solution such as Enterprise Vault may be a big benefit in this environment.
This will ensure lengthy retention periods without burdening the backup environment.
Excellent session at Vision this year about NBU sizing and Tuning:
NetBackup 7.6 Best Practices: Optimizing Performance
Here you will see that NBU catalog should not exceed 1TB.
(Plus lots of other useful info....)
