nutanix‐database‐automation‐ncp‐db‐ncp‐db‐65‐exam‐questions_20 - itnett/FTD02H-N GitHub Wiki

Here is an extensive "Do's and Don'ts" guide for Section 5: Protect NDB-Managed Databases Using Time Machine, Objective 5.1: Create, Delete, and Modify SLA Retention Policies in Nutanix Database Service (NDB). This guide will help you understand the key steps and best practices for managing SLA retention policies to ensure effective data protection for NDB-managed databases.

Objective 5.1: Create, Delete, and Modify SLA Retention Policies

Task Do Not Answer This (Incorrect Choice) Choosing This is the Safest Choice (Correct Answer)
Determine the Number of Snapshots "Set an arbitrary number of snapshots without considering storage impact or recovery needs." "Determine the number of snapshots based on recovery objectives, storage capacity, and workload requirements."
Determine Schedule Retention Policies "Use default retention policies for all databases without customization." "Customize schedule retention policies to match business requirements for recovery and compliance."
Create Custom SLAs "Rely only on built-in SLAs provided by NDB." "Create custom SLAs to fine-tune backup frequency, retention, and recovery points based on specific needs."
Determine Storage Requirements Based on a Policy "Ignore storage requirements; assume there is always enough space." "Calculate storage requirements carefully based on the number of snapshots, their frequency, and retention period."
Manage SLAs for Multiple Clusters "Use the same SLA for all clusters regardless of their size, workload, or importance." "Manage SLAs for multiple clusters separately to ensure each cluster's unique needs are met."
Modify Existing SLAs "Modify SLAs frequently without analyzing the impact on existing data." "Carefully analyze the impact of changes before modifying existing SLAs to avoid unintended data loss or storage overuse."
Delete SLAs "Delete SLAs without checking if they are still in use or linked to any databases." "Verify that SLAs are no longer in use and that dependent databases are reassigned before deletion."
Add Time Machine Data Access "Adding Time Machine data access is not necessary if storage is sufficient." "Ensure Time Machine data access is added for cross-cluster data protection and recovery options."

Explanations for Correct Choices:

  1. Determine the Number of Snapshots:

    • The number of snapshots should be based on recovery point objectives (RPOs), storage capacity, and workload requirements. Too few snapshots may not provide adequate recovery points, while too many can waste storage resources.

  2. Determine Schedule Retention Policies:

    • Retention policies should align with business needs, compliance requirements, and the criticality of the data. Customize retention schedules to balance between adequate data protection and efficient use of storage.

  3. Create Custom SLAs:

    • Creating custom SLAs allows for tailored backup strategies that align with specific recovery objectives, application needs, and storage constraints. Built-in SLAs may not be suitable for all use cases.

  4. Determine Storage Requirements Based on a Policy:

    • Calculate storage requirements to ensure there is enough capacity to store all snapshots without running out of space or affecting performance. Consider snapshot size, frequency, and retention period in the calculation.

  5. Manage SLAs for Multiple Clusters:

    • Different clusters may have different requirements based on size, workload, and criticality. Managing SLAs separately ensures that each cluster receives the appropriate level of data protection.

  6. Modify Existing SLAs:

    • Before modifying an SLA, analyze the potential impact on current backups, storage use, and recovery capabilities to avoid unintended consequences like data loss or excessive storage use.

  7. Delete SLAs:

    • Ensure SLAs are not in use and that all dependent databases have been reassigned to new SLAs before deletion. This prevents accidental loss of backup protection.

  8. Add Time Machine Data Access:

    • Configuring Time Machine data access is essential for enabling data recovery across clusters, especially in multi-cluster environments.

Key "Do's" for This Objective:

  • Do determine the number of snapshots carefully: Ensure that the number of snapshots meets your recovery objectives without overusing storage.
  • Do customize retention policies: Align retention schedules with business and compliance needs to ensure proper data protection.
  • Do create custom SLAs: Tailor backup and retention strategies to the specific needs of different databases and applications.
  • Do calculate storage requirements accurately: Consider all factors, including snapshot size, frequency, and retention periods, to avoid running out of storage.
  • Do manage SLAs separately for different clusters: Ensure that each cluster has the appropriate level of data protection.
  • Do analyze the impact before modifying SLAs: Consider the effect on existing backups and storage when making changes.
  • Do verify SLAs before deletion: Ensure no databases are dependent on an SLA before removing it.
  • Do add Time Machine data access: Enable cross-cluster data protection and recovery options by configuring Time Machine access.

Key "Don'ts" for This Objective:

  • Don't set an arbitrary number of snapshots: Always consider storage and recovery needs.
  • Don't use default retention policies for all databases: Customization is essential to meet different needs.
  • Don't rely solely on built-in SLAs: They may not provide the granularity needed for specific requirements.
  • Don't ignore storage requirements: Failing to calculate storage needs can lead to capacity issues.
  • Don't use a single SLA for all clusters: Different clusters have different needs and should be managed accordingly.
  • Don't modify SLAs without analysis: This could lead to unintended data loss or overuse of storage.
  • Don't delete SLAs without verification: Ensure they are not in use to prevent accidental data loss.
  • Don't skip adding Time Machine data access: It is crucial for cross-cluster recovery capabilities.

Best Practices for SLA Management in NDB:

  • Use a Risk-Based Approach: Set retention policies based on the criticality of the data and the potential impact of data loss.
  • Regularly Review SLAs: Periodically review SLAs to ensure they continue to meet business and compliance requirements.
  • Communicate Changes: Inform stakeholders of any changes to SLAs or backup policies to ensure alignment across the organization.
  • Automate Where Possible: Use automated tools to monitor SLA compliance and alert administrators to any deviations or issues.
  • Document All Policies: Keep clear records of all SLAs, their settings, and the databases they apply to, to facilitate audits and troubleshooting.

By following these "Do's and Don'ts," you will be well-prepared to manage SLA retention policies effectively, ensuring that your NDB-managed databases are adequately protected and meet your organization’s data protection needs.