A customer has NearSync configured. When the administrator tries to restore a snapshot from 3 minutes ago, it is not available. The snapshots are happening at 15-minute intervals instead of at the 5-minute configured interval. When the protection domain was initially set up, the snapshots were happening at the expected 5-minute interval.
What should the customer do to enable the snapshots to happen at the expected interval?
A . Utilize Metro Availability to meet this requirement
B . Change the protection domain to use Async DR
C . Fix a connectivity issue because the protection domain reverted to Async
D . Configure the protection domain to take snapshots on 15-minute intervals
Answer: C
Explanation:
If the administrator observes that the snapshot intervals have changed from the initially configured 5-minute intervals to 15-minute intervals, it indicates a potential issue with the setup. Option C, "Fix a connectivity issue because the protection domain reverted to Async," addresses the likely cause―a connectivity problem that caused the system to revert to longer, asynchronous DR snapshot intervals.
NearSync typically allows for very frequent snapshots, but if there is a connectivity or configuration issue, it might fall back to less frequent asynchronous DR settings. Identifying and resolving any connectivity issues would allow the NearSync configuration to operate as initially intended.
Reference: The mechanics of NearSync and its behavior under connectivity issues are discussed in detail in Nutanix’s documentation and troubleshooting guides, which describe how the system handles
fallback scenarios and how to rectify them.
Latest NCS-Core Dumps Valid Version with 191 Q&As
Latest And Valid Q&A | Instant Download | Once Fail, Full Refund