| RMAN Implementation. [message #342923] |
Mon, 25 August 2008 09:50  |
liamadherne
Messages: 40
Registered: March 2008
Location: Philadelphia
|
Member |
|
|
Hello Everybody,
I have 8 Databases(10g) onto which I am supposed to Implement RMAN.
Total 8 DB size is 6.5 TB approx.
4 DB's are Hp/Unix based and 4 DB's are solaris based, catalog DB will be HPUX based.
I am trying to formulate RMAN in such a way, so that I will be having a seperate server which will act as a catalog DB for all the 8 databases.
What are the thing I should be taking care before proceeding for the plan.
Wll I be facing any challenges in the future if I would use a single server as a catalog for these 8 DB's.
Backup would be taken on DISK, and If I will connect the storage to the catalog DB as it would be the central repository , and all the storage will be mounted to the catalog server only then how could I specify the path for the RMAN backup sets.
Appreciate your suggestions and time spent on the replies.
Liam.
|
|
|
|
| Re: RMAN Implementation. [message #342925 is a reply to message #342923] |
Mon, 25 August 2008 10:00  |
 |
Mahesh Rajendran
Messages: 10708
Registered: March 2002
Location: oracleDocoVille
|
Senior Member
Account Moderator |
|
|
>>Wll I be facing any challenges in the future if I would use a single server as a catalog for these 8 DB's.
Depends on what you call as "challenge".
I run 30+ databases using one RMAN datdabase / RMAN catalog.
Have not faced any problem yet w.r.to the functionality of RMAN.
>>Backup would be taken on DISK, and If I will connect the storage to the catalog DB as it would be the central repository , and all the storage will be mounted to the catalog server only then how could I specify the path for the RMAN backup sets.
Please rephrase. It is very confusing.
RMAN catalog will just store the information on backupsets. It will NOT STORE the backupsets itself.
RMAN backupsets are OS dependent. So, If your database is running on Solaris, make sure your disk filesystem is a compatible one(where ever you are writing it to).
Also, You do not want to invoke RMAN executable (to backup) from the catalog server.
Run RMAN in local database server and avoid network traffic and CPU contention in catalog server. Catalog should be used ONLY TO store information about RMAN backupsets.
[Updated on: Mon, 25 August 2008 10:01] Report message to a moderator |
|
|
|
| Re: RMAN Implementation. [message #342932 is a reply to message #342923] |
Mon, 25 August 2008 10:30 |
liamadherne
Messages: 40
Registered: March 2008
Location: Philadelphia
|
Member |
|
|
Hi Mahesh
| Quote: | >>Backup would be taken on DISK, and If I will connect the storage to the catalog DB as it would be the central repository , and all the storage will be mounted to the catalog server only then how could I specify the path for the RMAN backup sets.
Please rephrase. It is very confusing.
|
I mean If we will connect the enough storage to the catalog DB, and configure the RMAN in such a way so that all the backup pieces in all the DB's will be stored on the catalog server storage and fom there it will written onto the tapes.
Will there be any challenges in doing so?
Thanks for your valuable suggestions!!
Liam
|
|
|
|
|
|
| Re: RMAN Implementation. [message #342954 is a reply to message #342923] |
Mon, 25 August 2008 11:15 |
liamadherne
Messages: 40
Registered: March 2008
Location: Philadelphia
|
Member |
|
|
Sounds good now.
I will invoke the RMAN from the DB server only and config the RMAN to take the backup pieces onto the local file system only....
Thanks a Lot for your time and suggestions 
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
