You might want to consider the requirements for the catalog ie how much backup meta-data you can afford to lose in the event of recovery.
This will determine how often you run your catalog backups.
When I say lose, I mean data that is in the live catalog (which youve lost) but not on the backed up catalog.
Anything inbetween you will either have to accept as lost OR you could accept that you will react when theres a request of restore from such data.
So in my case I do two catalog backups per day, one after my daily backups have run ie early morning, the other after close of business. The first I do from the master server and which is taken offsite almost immediately with the rest of the overnight backups, the latter I do on remote site. I dont keep more than 7 days worth, and even that is probably overkill: I wouldnt ordinarily chose anything but the most recent catalog to recover from. Why would you? So essentially you might consider two copies of the same catalog and maintain only two generations.
Not sure about the thinking behind revaroos "month": some detail behind the thinking of that might prove interesting.
Jim
