2012-02-14 04:24 AM
We are currently experiencing an issue where old snapshots taken by SnapManager for Exchange are not getting deleted. We have 2 storage groups which are getting backed up, for one of the storage groups the snaps are sucesfully deleted. The second storage group the snaps are not getting deleted. The problem is only occuring on the Daily backup job. Weekly seems to be working ok.
We are running SnapManager for Exchange v126.96.36.199 on Exchange 2003 SP2.
The jobs scheduled to run are:
"C:\Program Files\NetApp\SnapManager for Exchange\SMEJobLauncher.exe" new-backup -Server 'EXCHANGE' -ManagementGroup 'Daily' -NoTruncateLogs $False -RetainBackups 8 -StorageGroup 'First Storage Group','Second Storage Group' -Verify -VerificationServer 'EXCHANGE' -UseMountPoint -MountPointDir 'C:\Program Files\NetApp\SnapManager for Exchange\SnapMgrMountPoint' -BackupCopyRemoteCCRNode $False -noutm
"C:\Program Files\NetApp\SnapManager for Exchange\SMEJobLauncher.exe" new-backup -Server 'EXCHANGE' -ManagementGroup 'Weekly' -NoTruncateLogs $False -RetainBackups 5 -StorageGroup 'First Storage Group','Second Storage Group' -Verify -VerificationServer 'EXCHANGE' -UseMountPoint -MountPointDir 'C:\Program Files\NetApp\SnapManager for Exchange\SnapMgrMountPoint' -BackupCopyRemoteCCRNode $False
2012-02-17 12:39 PM
Since you have not gotten an answer, you may want to ask this question in the NetApp Support Community. The current customers, partners and internal Subject Matter Experts are addressing technical product questions there.
2012-10-02 02:51 AM
Try updating to Snap Manager for Exchange 6.0.4, it has some new bug fixes especially 518953:
518953 Title: When a new Storage Group/Database is added to the existing SnapManager for
Exchange (SME) backup management group, the SME backup retention is executed
based on the "least amount of backups found" for any Storage Group/Database
Description: For a backup job that contains two or more Storage Groups SG (or in
Exchange 2010, Mailbox Databases) that share a common LUN for Logs and SnapInfo,
SnapManager for Exchange (SME)deletes the oldest number of database snapshots
from each Storage Group LUN based on the "least number of backups found"
algorithm for any of the StorageGroup/Database in the backup group.
In a scenario when an Exchange Administrator adds a new SG/Database to an existing
Backup Job, and the new SG/Database shares the Log/SnapInfo LUN with the existing
SG/Databases, the number of backups for each will become asymmetric and not even.
As a result of current SME deletion algorithm system may end up in a temporary
situation that snapshots are not being deleted for a time period (despite the retention
policy), until the SG/Database with a least amount of backups exceeds the backup
group retention number.