[DOCS-5001] Need to document behaviour, notifications and actions to be taken when a resync fails during backup Created: 13/Mar/15  Updated: 27/Jul/16  Resolved: 18/Apr/16

Status: Closed
Project: Documentation
Component/s: Ops Manager
Affects Version/s: mms-1.5, mms-1.6
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Joe Drumgoole (Inactive) Assignee: Anthony Sansone (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Amadeus


Issue Links:
Related
related to DOCS-5002 Update Resync Page with more information Closed
Participants:
Days since reply: 8 years, 48 weeks, 5 days ago
Epic Link: C/OM Backup
Story Points: 2

 Description   

When a backup daemon fails to resync the on-premise documentation does not document this event.

Need to document how this is detected, steps we take to recover and why its a bad idea to automatically recover from this event.



 Comments   
Comment by Joe Drumgoole (Inactive) [ 13/Mar/15 ]

This covered in the On-prem docs but needs more detail. How does the customer setup and alert. Why don't we automatically recover.

Comment by Joe Drumgoole (Inactive) [ 13/Mar/15 ]

Note this is specifically required for MMS On Prem.

Generated at Thu Feb 08 07:49:22 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.