Skip to main content
NetApp Knowledge Base

Does BlueXP Backup and Recovery perform integrity checks on backups taken?

  1. Last updated
  2. Save as PDF
Views:
47
Visibility:
Public
Votes:
0
Category:
cloud-manager
Specialty:
ds_cbs
Last Updated:

Applies to

  • BlueXP Backup & Recovery
  • ONTAP Snapshots

Answer

  • Snapshot-Based Backups: BlueXP leverages NetApp Snapshot technology for backups. Snapshots are inherently consistent at the storage level because they capture the state of the data at a specific point in time. The integrity of the data within the snapshot is ensured by the storage system itself.
  • Data Verification During Backup: BlueXP performs checks during the backup process to ensure that the data is successfully transferred to the backup target (e.g., object storage in the cloud). These checks typically involve verifying the integrity of the data blocks and ensuring that all data has been successfully written.
  • Metadata and Index Validation: BlueXP maintains metadata and indices for the backed-up data to facilitate quick recovery. These indices are validated periodically to ensure that they remain consistent and accurate.
  • Recovery Integrity: During data recovery, BlueXP verifies the integrity of the restored data. It checks that the recovered data matches the original backup and ensures that there is no corruption during the restore process.
  • Cloud Provider Features: If the backup target is object storage in the cloud (e.g., AWS S3, Azure Blob Storage, or Google Cloud Storage), the cloud provider may also perform its own integrity checks. For example, AWS S3 uses checksums to verify the integrity of stored objects.

Additional Information

Write Order Consistency: 
ONTAP snapshots are write-order consistent, meaning they capture the state of the file system at a specific point in time. This ensures that the snapshot reflects a consistent view of the data as it existed at the moment the snapshot was created. This is particularly important for applications and databases to ensure data integrity.

 

Application Consistency: 

While ONTAP snapshots are inherently consistent at the storage level, they may not always be application-consistent unless additional steps are taken.
By default, ONTAP snapshots are crash-consistent, meaning the snapshot captures the data exactly as it would appear after a sudden power failure or system crash. This is sufficient for many workloads.

For applications like databases (e.g., Oracle, SQL Server) that maintain in-memory data and transaction logs, you may need to quiesce the application (e.g., flush memory to disk) before taking the snapshot. Tools like SnapCenter or application-specific integrations help achieve application-consistent snapshots.

 

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.