RMAN Recovery Catalog on production server
Has anyone put there RMAN catalogue database on a live/production server.
Our current catalogue is on a server that is being decommissioned. The RMAN backups only run overnight and we only have 10 databases being backed up by this method. I imagine the resources required for catalogue db are quite low but interested if anyone with more experience has any input..
Has anyone had any issues with doing this?
The servers are Solaris 10.
I was also thinking we could set the catalogue up on a Windows VM but never done this. I presume no problem having the catalogue db on Windows when our production databases are on Solaris?
well it makes sense to have it on a separate server as if the live server goes down, you then have no catalog to restore from
You must host RMAN in a different server, there is no problem hosting it in a windows server (or VM).
Originally Posted by skhanal
Yes to me it is a must if you don't want to be caught in a situation where your production system gets fried. This is simple best practice.
No one is stopping you from putting all eggs in one basket.
Should versus must semantics. For example: Your control files must match per the parameter file. You should have more than one control file. You should put the RC on a separate server; it is not an absolute (that's all he was pointing out).
Just curious, has anybody setup a database just to hold catalogs using
primary and standby setup. So if the primary DB goes down you can open
up a standby DB for read/write access? Until the primary is backup? Or is
this way overkill?
Things can be said without being condescending
Thanks folks, incredibly guilty of asking without thinking (was exceptionally busy is my excuse!)
Got the recovery catalog set up on a Windows VM and working just fine.
Thanks for the replies.
Click Here to Expand Forum to Full Width