Complete recovery is fully utilized the archive log files, back to failure before the last commit,
And data migration is all the data to A repository database B, both feel the gap is not very big,
Everyone can give doubt dispels doubts about it, it is the fundamental difference between the two

CodePudding user response:

Recovery is a recovery, migration is a migration, you said that the use of file recovery is rman fully recovered, and the recovery archive alone is not enough, also need to have a base backup, full amount and increment, archive to be with you in hand to connect the database transaction, recovery can restore to other environment and also can restore to the original environment, of course, back to the original environment is the premise of the original environment hang, affirmation is to cut the database migration to other environment, the migration of many methods, nor is it merely by rman recovery,
You feel the problem is the language problem...

CodePudding user response:

Recovery is passive, such as your disk is broken, then is the database running status, the sudden disk is damaged, you need to restore the database to your disk damage before, due to disk damage is uncontrollable, began to recover data after the disk is damaged, data recovery may be to restore the native database rather than machine,
Data migration is active, subjective consciousness to operate this thing is you,

CodePudding user response:

reference 1st floor minsic78 response:

recovery is a recovery, migration is a migration, you said that the use of file recovery is rman fully recovered, and the recovery archive alone is not enough, also need to have a base backup, full amount and increment, archive to be with you in hand to connect the database transaction, recovery can restore to other environment and also can restore to the original environment, of course, back to the original environment is the premise of the original environment hang up and migration, affirmation is to cut the database to other environment migration method are many, also not only by rman recovery,
You feel the problem is the language problem...

Understand understand,
Today suddenly thought of this problem

CodePudding user response:

reference 1st floor minsic78 response:

recovery is a recovery, migration is a migration, you said that the use of file recovery is rman fully recovered, and the recovery archive alone is not enough, also need to have a base backup, full amount and increment, archive to be with you in hand to connect the database transaction, recovery can restore to other environment and also can restore to the original environment, of course, back to the original environment is the premise of the original environment hang up and migration, affirmation is to cut the database to other environment migration method are many, also not only by rman recovery,
You feel the problem is the language problem...

If using A library backup and the basis of A library archive, to achieve the B on the library, it is also equivalent to A library to do A restore,
If the library has been run on the basis of the A, and constantly pass B the archive libraries is DG,