Nutanix_NCP_DB_breakdown_19 - itnett/FTD02H-N GitHub Wiki

Here’s a detailed breakdown of Section 5 – Protect NDB-managed Databases Using Time Machine, Objective 5.5: Apply Policies to Protect Databases. This section focuses on applying Service Level Agreements (SLAs) and creating manual snapshots to ensure that databases within Nutanix Database Service (NDB) are properly protected.

Objective 5.5: Apply Policies to Protect Databases

1. Apply an SLA

• What It Is:

  • Applying an SLA (Service Level Agreement) involves assigning a predefined set of policies to a database that dictates how it will be protected. These policies typically include backup frequency, retention periods, and other data protection measures.

• Key Steps:

  • Choose the Appropriate SLA: Select an SLA that meets the database's data protection requirements, considering factors such as Recovery Point Objective (RPO), Recovery Time Objective (RTO), and regulatory compliance.
  • Apply the SLA in NDB: Use the NDB interface to apply the chosen SLA to the target database, ensuring that it automatically adheres to the specified protection policies.
  • Monitor Compliance: After applying the SLA, regularly monitor the database to ensure it is being protected according to the SLA’s terms. This includes checking that backups are occurring as scheduled and that retention policies are being enforced.

• Key Considerations:

  • Ensure the SLA aligns with business and compliance requirements, particularly in terms of how frequently backups are taken and how long they are retained.
  • Be mindful of the impact on storage resources when applying an SLA, especially if it involves frequent snapshots or long retention periods.

• What It Is Not:

  • Applying an SLA is not about managing individual backups or snapshots manually; it automates the protection process according to predefined rules.
  • It is not a one-time action; SLAs should be reviewed and adjusted as business needs change.

• Reference:

  • SLA Management

2. Create a Manual Snapshot

• What It Is:

  • Creating a manual snapshot involves taking an on-demand, point-in-time copy of a database. This is useful for immediate protection before a significant change, such as before an upgrade, or when preparing for testing and development environments.

• Key Steps:

  • Determine the Need for a Snapshot: Identify scenarios where a manual snapshot is necessary, such as before making major changes to the database or when performing tests that could impact data integrity.
  • Create the Snapshot in NDB: Use the NDB interface to manually trigger the creation of a snapshot. Ensure that the snapshot is labeled and documented for future reference.
  • Verify Snapshot Integrity: After the snapshot is created, verify that it is complete and that it accurately reflects the database’s state at the time of creation.

• Key Considerations:

  • Manual snapshots should be used judiciously to avoid excessive consumption of storage resources.
  • Document the purpose of the snapshot and the conditions under which it was taken, as this can be crucial for recovery or auditing purposes.

• What It Is Not:

  • A manual snapshot is not part of a scheduled backup process; it is an ad-hoc action taken to protect the database at a specific moment.
  • It is not a replacement for regular, scheduled backups or snapshots; it is supplementary protection.

• Reference:

  • Create Snapshots (Manual)
  • Database Protection

Summary of Key References

• SLA Management: Instructions on how to manage and apply SLAs within NDB, ensuring consistent and automated data protection across databases.
• Database Protection: General best practices for protecting databases using SLAs, snapshots, and other tools within NDB.
• Create Snapshots (Manual): Guide on how to create manual snapshots, providing an extra layer of protection at specific points in time.

Key Takeaways for Exam Preparation

• SLA Application: Be proficient in applying SLAs to databases, ensuring they are automatically protected according to business and regulatory requirements.
• Manual Snapshots: Understand when and how to create manual snapshots, providing immediate protection for databases before critical operations.

By mastering these concepts related to database protection, you’ll be well-prepared to answer questions related to Objective 5.5 on the NCP-DB 6.5 exam.