MaxRep: Managing MaxRep3 Engine Configuration Backups

Asset ID:	1-72-2280591.1
Update Date:	2017-07-23
Keywords:

Solution Type Problem Resolution Sure

Solution 2280591.1 : MaxRep: Managing MaxRep3 Engine Configuration Backups

Applies to:

Pillar Axiom Replication Engine (MaxRep) - Version 3.0 to 3.0 [Release 3.0]
Oracle FS1-2 Flash Storage System - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Symptoms

MaxRep3 configuration information is no longer being backed up.

Changes

The backup directory contains a collection of tar bundles of the MaxRep database backup. Examples include protection plans, recovery snapshot information, audit logs, dashboard alerts etc. It can grow in size as the replication scope increases.

Cause

Configuring a backup plan allows users to backup configuration data through scheduled intervals that enable automatic, continuous data protection. When the filesystem that contains the backup directory fills up, configuration backups will no longer be performed.

NOTE: The name of the backup directory is an option selected during the creation of the these backups.

Solution

What can be done to avoid the files from growing too much?

Limit the frequency of the collections. It is only really required if configuration changes happened and can be done manually as well.
How do I configure the frequency that they are created?

By changing the scheduling of the collections. From the Protect tab, select the "More>>" link and then Protected Files/Folders.
What is the impact if the File System /backup gets full?

The latest backup config files will not be copied into the backup LUN if it already gets full, but it will not have any impact to the replication. Older tar bundles can safely be deleted to create more space.
Why do we see backup files generated manually in the path /usr/local/InMage/Fx/appliancebackup?

MaxRep will initially copy the files locally into the folder(/usr/local/InMage/Fx/appliancebackup) and then moves to backup LUN. This is temporary storage to maintain latest tar bundles."

Oracle MaxRep for SAN User’s Guide Map the Backup LUN

References

<BUG:26326051> - FULL FILE SYSTEM /BACKUP
<NOTE:1428513.1> - Pillar Axiom: MaxRep Engine - Initial Troubleshooting Steps

Attachments

This solution has no attachment