Unsolved
This post is more than 5 years old
3 Posts
0
31216
February 25th, 2013 13:00
Schedule failed to delete the oldest replica according to max-keep limit? Is this a problem?
Hi All,
We've recently got our replications working as required (RPOs being met now thanks to some Silver Peak devices) and now we are getting a few warnings daily on some of our replicated volumes about not deleting the oldest replicas.
Example:
WARNING event from storage array BCSC-SATA
subsystem: MgmtExec
event: 8.3.45
time: Sun Feb 24 03:15:00 2013
Schedule BANPROD04-QUARTER_HOUR failed to delete the oldest replica according to the max-keep limit. Proceeding to create a new replica.
All 3 replicated volumes are set to keep 5 replicas.
Does anyone know what this Warning means and does it mean I may have an issue with replicas being retained - and therefore using array space unnecessarily?
Prod group is 2x PS4100 (12x SAS 600GB and 12x SAS 2TB) pooled.
Total space: 20.16TB
Volume reserve: 8.15TB
Snapshot reserve: 812GB
Replication reserve: 6.39TB
Delegated: 0MB
Free: 4.82TB
DR is 1x PS4100 (12 x SAS 3TB)
Total: 24.15TB
Volume reserve: 6.01TB
Snapshot reserve: 0MB
Replication reserve: 0MB
Delegated: 9TB
Free: 9.14TB
Both Prod and DR at FW 6.0.1.
Not quite sure where to look for more info on this.
Thanks
Pete
fish_351
3 Posts
0
February 25th, 2013 17:00
Thanks Don,
I have purged some old replicas (from like a month ago) when I began investigating this.
Right now the previous 5 replicas for each volume are the only ones remaining in the list (as configured and as I'd expect).
We do have replications staggered across each hour but they do sometimes run together if deltas get large.
Maybe its just a case of the replication engine not being able to process the deletion at that point but then "getting around to it" later but not notifying?
Thanks