You can run a transaction or cycle restore from either the Data Vault or a database archive. You can only perform a full restore from a database archive.
You can perform a restore job using the following methods:
Full restore
A full restore job restores the entire contents of a database archive. You might perform a full restore if you archived an entire database that must be returned to production. For optimal performance, conduct a full restore to an empty database. Performance is slow if you run a full restore to the original database.
Data Archive deletes the restored data from the database archive as part of the full restore job.
Cycle restore
A cycle restore job restores an archive cycle. You might restore an archive cycle if a cycle was archived in error, or if you must change numerous transactions in a cycle. To restore a cycle you must know the cycle ID. A cycle restore can also restore a specific table. To restore a specific table, use the Enterprise Data Manager to create an entity containing the table you want to restore.
By default, Data Archive deletes the restored data from the database archive or the Data Vault as part of the cycle restore job. If you do not want the restore job to delete the data from the archive location, you can specify that the restore job skip the delete step.
Transaction restore
A transaction restore job restores a single transaction, such as a purchase order or invoice. To restore a transaction, you must search for it by the entity name and selection criteria. If your search returns multiple transactions, you can select multiple transactions to restore at the same time.
By default, Data Archive deletes the restored data from the database archive or the Data Vault as part of the transaction restore job. If you do not want the restore job to delete the data from the archive location, you can specify that the restore job skip the delete step.