RDB With Datapump Option a "REVOLUTION"
Here is a list of advantages to use "datapump" instead of "rman" backup
*Logical Backups with Oracle Datapump Export
*Automatic Tablespace Monitoring
*Support of Oracle Container Databases with Pluggable Databases inside.
*Support of Oracle Managed Files
*No security breach because of RMAN backups throughout the RDB application ( arc_xpi User )
*Crossversion Compatibility of Datapump Exports
*Crossplatform Compatibility of Datapump Exports
*Reducing the number of database files significantly
*Default database installation possible for most of the WinCC OA projects
*No offline Datafiles anymore
*Standard RMAN backups can be used without skipping offline datafiles
*Reduces the effort for Database Upgrades and Server Migrations
*Constant Database Size because of reusing empty blocks
So there are a lot of advantages using "datapump".
The datapump archiving feature is available in 3.15 ,3.16 and 3.17
If you need additional information please feel free to answer this post.
Oracle Database Consultant @ETM
way_of_backup = 'datapump'
similar to the old method also a backup directory must be specified.
For new projects datapump is the default and will be used automatically.
Regarding datapump migration :
New archiving projects or archiving projects where the RDB Schema can be recreated from scratch can easily be transferred to use the new datapump feature.
There is no straight forward upgrade procedure, for already running projects which cannot be recreated from scratch, with which you can enable the datapump feature in a database. Why ?
a.) Customers have to decide what to do with already backed up archives.
b.) To change to datapump Mode it is needed to recreate the schema and transfer the already archived data into the datapump schema.
Just contact us if you want to migrate to datapump feature for existing projects already in production. We will help you.
If you have questions feel free to contact us