![]() ![]() The destination host is the host on which you intend to create the duplicate database. The source host is the database on which the source database resides. The auxiliary instance must be started with the NOMOUNT option. The instance of the duplicate database is called the auxiliary instance. RMAN must be connected as AUXILIARY to the instance of the duplicate database. Prerequisites Common to All Forms of Duplication The prerequisites vary depending on the type of duplication. RMAN creates duplicate files from RMAN backups and copies that were placed in a designated BACKUP LOCATION. RMAN creates duplicate files from pre-existing RMAN backups and copies.īackup-based duplication without a connection to target or a recovery catalog This mode is useful when the target database is not available or a connection to it is not desirable (as mandated by security policy restrictions or a firewall).īackup-based duplication with a target connection This form requires a connection to an auxiliary instance and a recovery catalog. The DUPLICATE command must have been issued with the DATABASE clause. RMAN creates duplicate files from pre-existing RMAN backups and copies. Backup sets offer several advantages, including unused block compression and encryption.īackup-based duplication without a target connection RMAN duplicates the files directly from either an open or mounted database.Īctive duplication can use image copies or backup sets. RMAN can perform the duplication in any of the following supported modes: A standby database is not assigned a new DBID. Typically, duplicate databases are used for testing.Ī standby database, which is a special copy of the source database (called a primary database in a Data Guard environment) that is updated by applying redo data from the primary database. Because a duplicate database has a unique DBID, it is independent of the source database and can be registered in the same recovery catalog. RMAN can create either of the following types of databases:Ī duplicate database, which is a copy of the source database (or a subset of the source database) with a unique DBID. The status code of duplicacy backup will be provided in the firstĪrgument ( $1) in the post-backup script.Use the DUPLICATE command to create a copy of a source database. You can return a non-zero code in pre-backup script to inhibit the If you specify either pre- or post-backup scripts, it will disable the scripts/post-backup.sh so they will get invoked accordingly. ![]() Mount your scripts at /scripts/pre-backup.sh or You can provide pre/post-backup scripts that runs before and after theīackup. ![]() If provided it will generate the pre/post-backup script automatically. Pruning will not run if this environment variable is not set. You can customize the behavior using the following environment variables: variableĭefault cron-like spec on when to run cron-like spec on when to run prune. Then docker-compose up -d to start the service. You can customize it with environment variables, see the Customization section. LocalSettings.php:/data/LocalSettings.php:ro ![]() preferences:/data/.duplicacy/preferences # mount files/directories below /data as readonly duplicacy_store:/data # mount the preferences file duplicacy_remote:/dest # base directory, any files mounted below /data will be included in the backup # mount remote position, which is not needed if you use a storage other than local folder Image: shouya/duplicacy-autobackup:latest environment: Suppose you have the following docker-compose file for a sample mediawiki service: You may want to initialize the repo in different ways other than those limitedly supported by the scriptĪs a result, you need to initialize the backup repository manually outside Docker, and then directly provide duplicacy’s preferences file via a mount.The image is tidier, and using the image doesn’t require as many environment variables.In this project, docker-duplicacy, I intentionally dropped the initialization feature, for two reasons: I also added support for hooks and healthchecks.io reporting. report to healthchecks.io with status and logsĬhristophetd/duplicacy-autobackup implemented the periodic backup feature.īased on which I forked shouya/duplicacy-autobackup, which bumped the version of duplicacy and converted the base image to s6 to support running the jobs non-root users.Understanding of basic usage of duplicacy is expected. This Docker image contains a daemon that backup files using duplicacy. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |