When you use Crosschecking on multiple nodes, you can configure the cluster so that each node in the cluster can access all Database backups, regardless of who generated the database backup. If your cluster is configured like this, you can allocate channels on any node during restore or crosscheck operations ).
If you do not CONFIGURE the cluster as mentioned above, you must use the CONNECT option of the configure channel command to allocate channels on multiple nodes during restore or crosscheck operations ), so that each backup can be accessed by at least one node in the cluster.
If no channel is configured for access to these backups during the crosscheck operation, these backups will be marked as EXPIRED.
Node 1 and node 2 both use the default configuration and perform a full backup on node 1.
[SQL]
- -- Rac1
- RMAN> crosscheck backup;
- Crosschecked backup piece: foundToBe'Available'
- Backup piece handle =/Oracle/backup/racdb_09n0hqle_1_1_12 recid = 8 stamp = 772336302
- -- Rac2
- RMAN> crosscheck backup;
- Crosschecked backup piece: foundToBe'Expired' -- It is marked as EXPIRED on rac2.
- Backup piece handle =/oracle/backup/racdb_09n0hqle_1_1_12 recid = 8 stamp = 772336302
Configure the degree of parallelism to 2 (number of nodes) on node 2, configure the channel, and then verify again
[SQL]
- -- Rac2
- RMAN> configure device type disk parallelism 2;
- New RMAN configuration parameters:
- Configure device type disk parallelism 2 BACKUP TYPETOBACKUPSET;
- New RMAN configuration parameters are successfully stored
- -- Racdb indicates the service name. You can also configure a single instance.
- RMAN> configure channel device type diskConnect='Sys/oracle @ racdb';
- New RMAN configuration parameters:
- CONFIGURE CHANNEL DEVICE TYPE DISKCONNECT '*';
- New RMAN configuration parameters are successfully stored
- RMAN> crosscheck backup;
- Crosschecked backup piece: foundToBe'Available' -- This is marked as AVAILABLE.
- Backup piece handle =/oracle/backup/racdb_09n0hqle_1_1_12 recid = 8 stamp = 772336302