We run 2 types of backups at out company:
1) Daily Backups
"D:\Program Files\NetApp\SnapManager for Exchange\SMEJobLauncher.exe" new-backup -Server 'EVS' -CCRActiveNode $False -ManagementGroup 'Standard' -NoTruncateLogs $False -RetainBackups 4 -StorageGroup 'First Storage Group','Second Storage Group','Third Storage Group','Fourth Storage Group','Fifth Storage Group','Sixth Storage Group' -Verify -VerificationServer 'cgyprdccr02' -UpdateMirror -BackupCopyRemoteCCRNode $False
2) Frequent Recovery Point Backups
"D:\Program Files\NetApp\SnapManager for Exchange\SMEJobLauncher.exe" new-backup -Server 'EVS' -CCRActiveNode $False -NoTruncateLogs $False -StorageGroup 'First Storage Group','Second Storage Group','Third Storage Group','Fourth Storage Group','Fifth Storage Group','Sixth Storage Group' -RecoveryPoint -UpdateMirror
Job #1 works perfectly fine and keeps 4 online copies on the PROD filer....it also snapmirrors to the DR Filer. Backups are ran from the Passive Node
Job #2 works perfectly fine on the Passive node. It adds the FRP logs to the SnapInfo directory for each respective storage group. The problem is that it also adds the FRP logs to the SnapInfo directory on the Active node??
This causes issues with our Backup and Recovery strategy, as we never run backup jobs on the Active Node. This means that the SnapInfo Directory continues to grow, and the SnapInfo Logs never become purged!
Is this a known issue with SME 5.0?
Has anyone seen this in the past?