In the upgrade scenario, which action preserves data by relocating volumes to the new hardware?

In the upgrade scenario, which action preserves data by relocating volumes to the new hardware?

• A. Move the volumes from the old nodes to the new nodes.
• B. Create new volumes on the new cluster and ignore old data.
• C. Wipe all data on old nodes before migrating.
• D. Copy data to a single external backup repository.

Answer: (A)

During an upgrade, preserving data while moving to new hardware is achieved by relocating the actual data containers—volumes—from the old nodes to the new hardware. This keeps the data intact on the new controllers and maintains the existing volume configuration, access policies, snapshots, and QoS settings, allowing clients to continue operations with minimal disruption. It’s the most reliable way to ensure continuity because you’re not recreating data or relying on a separate backup copy; you’re transferring the live data path to the upgraded system. Creating new volumes on the new cluster and ignoring the old data would result in data loss or the need for a separate, potentially outdated restore. Wiping all data defeats upgrade goals entirely. Copying data to an external backup repository protects data as a backup, but it does not relocate active volumes onto the upgraded hardware for immediate use, so it doesn’t preserve the operational data path on the new system. Relocating volumes directly to the new hardware provides seamless data accessibility and integrity throughout the upgrade.

During an upgrade, preserving data while moving to new hardware is achieved by relocating the actual data containers—volumes—from the old nodes to the new hardware. This keeps the data intact on the new controllers and maintains the existing volume configuration, access policies, snapshots, and QoS settings, allowing clients to continue operations with minimal disruption. It’s the most reliable way to ensure continuity because you’re not recreating data or relying on a separate backup copy; you’re transferring the live data path to the upgraded system.

Creating new volumes on the new cluster and ignoring the old data would result in data loss or the need for a separate, potentially outdated restore. Wiping all data defeats upgrade goals entirely. Copying data to an external backup repository protects data as a backup, but it does not relocate active volumes onto the upgraded hardware for immediate use, so it doesn’t preserve the operational data path on the new system. Relocating volumes directly to the new hardware provides seamless data accessibility and integrity throughout the upgrade.