Let's assume you have your database on ServerA and you want to back up to disk on ServerB. One option is to create a network pointer to the disk on ServerB from ServerA. In Unix/Linux, this is called a cross mount. In Windows, this is called a file share. Once you can access ServerB's disks from ServerA, tell RMAN to configure a channel to this file share. RMAN will write to the disk, thinking it is local to ServerA, but the disk is really running on ServerB. RMAN will be running on ServerA but backing up to ServerB.
If you cannot create the file share, then you can install Oracle software on ServerB. Then configure a TNSNAMES.ORA entry to point to the database running on ServerA. In RMAN, you can connect to the database on ServerA with the following command:
CONNECT TARGET user/pswd@tns_aliasIn this situation, you are running RMAN on ServerB, backing up to disk on ServerB, but backing up the database running on ServerA.
Dig Deeper on Oracle database backup and recovery
Related Q&A from Brian Peasland
Oracle expert Brian Peasland answers one reader's question about common pitfalls when connecting Oracle to outside programs. Continue Reading
One reader asks expert Brian Peasland a question about datafile sizes with the Oracle RMAN duplicate 10g command. Continue Reading
Managing parent table-child table relations in Oracle SQL environments is key to efficient programming. Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.