MaxRep: Retention LUN For Maxrep Will Not Stay Mounted

Asset ID:	1-72-2112671.1
Update Date:	2018-03-01
Keywords:

Solution Type Problem Resolution Sure

Solution 2112671.1 : MaxRep: Retention LUN For Maxrep Will Not Stay Mounted

Applies to:

Pillar Axiom Replication Engine (MaxRep) - Version 3.0 to 3.0 [Release 3.0]
Information in this document applies to any platform.

Symptoms

When a retention LUN is mounted using Maxrep Toolkit Map. Within 30 seconds the retention LUN will unmount on its own.

Changes

MaxRep 3.0.2 to 3.0.3 Upgrade

Cause

In the unlikely event that the retention LUN that was being used in a protection plan is no longer available the Retention LUN will need to be removed from the protection plan configuration.

If the Retention LUN is not removed from the Protection Plan configuration and the new Retention LUN is created with the same name, the engine will auto unmount the new Retention LUN.

This is a problem because new retention LUN contains a different LUID, it will auto unmount the LUN.

Solution

To remove the legacy retention LUN configuration information you will have to ssh into the MaxRep engine and follow the steps below.

1. Log into the MaxRep Engine using putty (or a similar SSH client program). Connect using SSH, MaxRep Engine login credentials can be found in <Document 2046703.1> FS System: Passwords Associated with the Oracle FS1-2 Flash Storage System
2. cd to folder /usr/local/
3. Use the vi command to edit the ro_mount_devices file, remove the legacy Retention LUN LUID info in the file, then save the file changes.
4. Manually remount the new retention LUN.

#mount /dev/mapper/<sanLunUID> <mountPoint>

5. Restart the protection plan replication services.

Access the MaxRep Engine support page, open a web-browser in the URL type http://<MaxRep IP>/support
From the left menu under Management Tasks click Shutdown/Restart Services link
From the Host list, select the Replication Engine that is running the Oracle MaxRep replication services
Select radio button Restart Replication services
To restart the replication services, click Save Task.

Attachments

This solution has no attachment