Nutanix_NCP_DB_breakdown_18 - itnett/FTD02H-N GitHub Wiki

Here’s a detailed breakdown of Section 5 – Protect NDB-managed Databases Using Time Machine, Objective 5.4: Refresh Clones. This section focuses on managing and executing refresh operations for database clones within Nutanix Database Service (NDB), ensuring that clones remain up-to-date and aligned with their source databases.

Objective 5.4: Refresh Clones

1. Manage Refresh Schedules

  • What It Is:

    • Managing refresh schedules involves setting up and maintaining a timetable for automatically updating database clones with data from their source databases. Regular refreshes ensure that the clones stay current, which is crucial for use cases like development, testing, and reporting.
  • Key Steps:

    • Determine Refresh Frequency: Based on the business requirements, decide how often the clone needs to be refreshed (e.g., daily, weekly, hourly). Consider the use case for the clone and how current the data needs to be.
    • Configure the Schedule in NDB: Use NDB’s management interface to create or modify the refresh schedule, specifying the frequency and timing of refresh operations.
    • Monitor the Schedule: Regularly check that the scheduled refreshes are occurring as planned and that there are no issues impacting the refresh process.
  • Key Considerations:

    • Frequent refreshes can be resource-intensive, so balance the need for up-to-date clones with the available system resources.
    • Ensure that refresh operations do not conflict with other critical tasks or peak usage periods to avoid performance degradation.
  • What It Is Not:

    • Managing refresh schedules is not about creating clones; it focuses on keeping existing clones updated.
    • It is not a static setup; refresh schedules should be reviewed and adjusted based on evolving business needs.
  • Reference:

    • Creating a Clone Refresh Schedule

2. Execute a Manual Refresh

  • What It Is:

    • Executing a manual refresh involves updating a database clone immediately, outside of any scheduled refreshes. This might be necessary in scenarios where the clone needs to be refreshed urgently, such as before a major test or after significant changes to the source database.
  • Key Steps:

    • Identify the Need for Refresh: Determine the reason for executing a manual refresh, such as an unexpected change in the source database or an immediate business need.
    • Initiate the Refresh in NDB: Use the NDB interface to manually trigger the refresh process, selecting the clone and source database involved.
    • Verify the Refresh: After the manual refresh is complete, check the clone to ensure that the data is accurate and consistent with the source database.
  • Key Considerations:

    • Manual refreshes can impact system performance, so they should be executed during off-peak hours or when the system is under minimal load.
    • Document the reasons for manual refreshes to track their frequency and understand why they were necessary outside of the regular schedule.
  • What It Is Not:

    • A manual refresh is not part of the scheduled operations; it is an ad-hoc operation triggered by a specific need.
    • It is not a replacement for a well-planned refresh schedule; manual refreshes should be used sparingly.
  • Reference:

    • Refreshing Database Clones (Manual)

Summary of Key References

  • Creating a Clone Refresh Schedule: Instructions on setting up automated schedules to keep database clones in sync with their source databases.
  • Refreshing Database Clones (Manual): Guide on how to manually trigger a refresh operation for database clones, outside of the regular schedule.

Key Takeaways for Exam Preparation

  • Refresh Schedule Management: Understand how to configure and manage refresh schedules in NDB, ensuring that clones remain up-to-date according to business needs.
  • Manual Refresh Execution: Be proficient in executing manual refreshes, knowing when and how to trigger these operations to keep clones current outside of their regular refresh schedules.

By mastering these concepts related to clone refresh operations, you’ll be well-prepared to answer questions related to Objective 5.4 on the NCP-DB 6.5 exam.