Use RMAN for recovery from different machine backups (WIN platform)

In some cases, if the database server is under disk space pressure or costs control, you need to back up the data files to a different machine, and RMAN can be used to complete this work. Based on Windows

In some cases, if the database server is under disk space pressure or costs control, you need to back up the data files to a different machine, and RMAN can be used to complete this work. Based on Windows

In some cases, if the database server is under disk space pressure or costs control, you need to back up the data files to a different machine, and RMAN can be used to complete this work. The Configuration Based on the Windows platform is relatively simple, just adding an account and using the new account to start the database service and set the sharing path.

The following is a detailed description.

1. Configure the database server and backup target host
1. Account configuration (assume that host A and host B are used as the database server, and host B is used as the backup destination and can ping each other)
If host A and host B use the same Administrator password, and OracleServiceDBNAME and OracleOraHome92TNSListener services on host A both use
Local System Account Login"
If host A and host B use different Administrator passwords and are not considered to be the same in terms of security, you can create A new user on host A and host B separately.
Set DBA_oracle on host A and set the password to ORA_PWD. This user is also created on host B (the user name can be different and the password must be the same). The password is also set to ORA_PWD.
. Add the user on the host to the Aministrators group.
2. Set the startup account for the OracleServiceDBNAME service and OracleOraHome92TNSListener service. Enter services. msc at run. Set this account on host
User Login, that is, using the DBA_oracle just created, enter the password to start, this setting needs to be effective after restart
3. Set the shared folder on host B, such as RMAN_Shared, and set its permissions to full control (use \ IP \ RMAN_Shared on host A to test whether files can be written)

Ii. Check RMAN configuration and database information

3. Back up and shut down the database and delete the system01.dbf File
Use the backup script to back up the database.

D: \> rman target robinson/robin @ testhh export file = D: \ oracle \ oradata \ testHH \ backup. rman log = D: \ oracle \ ora

Data \ testHH \ backup. log

4. Restore and restore data from different hosts
1. Close the database 2. Delete the system01.dbf data file for test recovery

SQL> ho del D: \ oracle \ oradata \ testHH \ SYSTEM01.DBF

3. Restart the instance and receive an error message. 4. Use RMAN to restore and restore the instance. 5. Conclusion
From the above backup and recovery, there is no much difference between the use of backup and recovery from different machines and the use of local server backup and recovery operations, but the database performance is subject to a certain
. That is, the backup and recovery speed is lower than the backup and recovery speed on the local server. In a large production environment with extremely high real-time requirements, try to avoid exceptions
Backup and recovery. However, backup to recovery from different machines is still an optional solution.

V. RMAN backup script