Avamar: Remote backups which expired on Target are still visible on the Source

Avamar versions: v7.2, v7.3, v7.4, v7.5

On a replicating pair of Avamar systems where the remote backup management service (RBMS) is used, the Avamar Administrator backup management screen displays remote backups. These backups are displayed even after they have expired.

The screenshot below, taken on 23 August 2017 shows an Avamar source (in the background) and a target Avamar (in the foreground).



A backup was taken on 16 August and was due to expire on 20 August.

On 23 August, when the screenshot was taken we would expect that 16 August would not be highlighted in yellow, nor show any backups for that day.

In reality, the local expired backup has been delisted, but the 'Remote' expired backup is still visible.

The target Avamar's UI does not show any backups on this day for the client. 

mccli and avmgr commands are run on both servers to display backups from the MCS and GSAN perspectives. This confirms that the backup is no longer present on the system and that it has expired.


Other facts:

• The Remote Backup Manager Service is running on both Source and Target. The behavior does not change if the service is restarted.
• The mcserver.xml on both source and target is set with the following (default) values. 

<entry key="allow_dest_replica_management" value="false" />
<entry key="allow_manage_remote_backups_at_source" value="true" />
<entry key="show_external_backups" value="true" /> 

This is expected behavior.

No action is necessary. Engineering intend to improve the behavior in a future release. Contact Support for details.