AMM now works with ASM on primary server(s).

[Mike Donovan]

New feature in version 6.0.30.

Prior to version 6.0.30 Dbvisit Standby had functionality to access ASM archive logs on the primary server, copy them out of ASM to the filesystem and then transfer to the standby server. So in this respect you were not restricted to filesystem archive logs alone, as your primary database could have an ASM archive log destination defined.

However the AMM module could only check/delete filesystem archive logs on the primary server.

This has changed with the release of version 6.0.30. This version can delete both filesystem and ASM archive logs on the primary server according to defined thresholds. Space limit thresholds can now be set for ASM diskgroups, to send an alarm when free space on an ASM diskgroup falls below the threshold.

Please note: Functionality for the AMM module on the standby/DR server has not changed as archive logs shipped from the primary are stored in a filesystem location defined by variable ARCHDEST in the Dbvisit Standby DDC file.