TRY NOW
book meeting
BACK TO KB LIST

Preserving Restored InterSystems IRIS Data Before Removing a Storage System

KB ID: 4883
Product: Veeam Backup & Replication | 13.1
Published: 2026-08-01
Last Modified: 2026-09-17
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please, try again later.

Article Applicability

This article expands on the following note from Epic EHR System Protection > Restoring from Storage Snapshot in the Veeam Backup & Replication User Guide:

Before you start the restore wizard, create an auxiliary host for the LUN mount in the storage system interface, using any name except the vim aux prefix. If you do not, Veeam Backup & Replication creates this host automatically with the vim aux prefix and deletes all hosts that have this prefix when the storage system is removed from the Veeam Backup & Replication infrastructure, which can break the link between the target host and its volumes.

Summary

Epic EHR System Protection, introduced in Veeam Backup & Replication 13.1, can restore an InterSystems IRIS instance either from a backup or from a storage snapshot. When Restoring from Backup, data is copied from the backup repository to the target ODB (operational database) server, and is not affected by the issue described in this article.

A restore from a storage snapshot behaves differently. Veeam Backup & Replication creates a thin clone of each selected snapshot on the source storage system through the Universal Storage API and mounts the clones directly to the target ODB server. No data is retrieved from a backup repository. Because a restore point can span multiple original production volumes (for example, when LVM striping is used), a restore typically creates and mounts more than one clone, from one or more storage systems. Access to the mounts requires a host record for the target ODB server on each storage system involved (an initiator group, host group, or storage group, depending on the storage system). If a host record is not created in advance, Veeam Backup & Replication creates one automatically under a reserved name.

Neither the clones nor the host records are removed when the restore finishes. For a restore to the original location, the documented pre-restore steps include unmounting the original production disks and removing their LUN masking, after which the clones are the only copies of the instance data.

If the storage system is later removed from the Veeam Backup & Replication infrastructure (for example, when the Veeam Backup Server is moved to a new host and the old host is cleaned up, when the backup infrastructure is reorganized, or when the storage system is decommissioned), the objects that Veeam Backup & Replication created for the restore are removed with it. Veeam Backup & Replication identifies its own objects by name prefix, for example VeeamAUX-, VeeamCL_, VEEAM-StorageLUNClone-, or _vih.. When those are deleted, the restored instance either loses access to its data or the data is deleted outright, depending on the storage system. The InterSystems IRIS restore points based on that storage system's snapshots also become unavailable for restore.

Note: When a storage system is removed, a confirmation prompt is displayed. However, the prompt does not preserve the restored data.

Solution

Permanent Data Loss on Some Storage Systems

On some storage systems, removing the storage system from Veeam Backup & Replication triggers a cleanup operation that may permanently impact restored data, with no way to recover it afterward.

If a restore from snapshot for Epic EHR System Protection has been performed, review the guidance below for the storage system in use and complete the advised actions before removing the storage system from Veeam Backup & Replication.

To prevent the restored data from being affected by the cleanup that occurs when a storage system is removed from Veeam Backup & Replication, the data must be made independent of Veeam Backup & Replication. The method varies by storage system.

Identify and expand the storage system in use below for the steps that apply to it.

A restore from snapshot typically creates more than one clone, for example one per original production volume, mounted from one or more storage systems. Complete the applicable steps below for every clone and host record the restore created, on every storage system involved.

Note: The CLI commands and console paths in this article are examples and may differ across storage OS and management console versions. Check the vendor documentation referenced for the storage system in use for the exact syntax and menu names.

DataCore SANsymphony
What is Created During Restore From Snapshot

Veeam Backup & Replication creates thin clones with an Alias beginning with VeeamClone, production snapshots named VeeamProduction-*, and a host record carrying a Veeam Description ("Veeam-registered ESX server" or "Veeam proxy server").

What is Removed During Storage System Removal

When the storage system is removed, clones whose Alias begins with VeeamClone, and host records with one of those Descriptions, are deleted.

Action Required to Make Data Independent
  • Change the host record Description (Host > Edit > Description) so that it no longer contains either Veeam string.
  • Identify clones with Aliases beginning with VeeamClone and rename each clone's Alias so that it no longer begins with VeeamClone, for example:
Set-DcsVirtualDiskProperties -VirtualDisk "<current>" -Alias "<new>"

Since only the Alias and the Description are checked, renaming the host record name does not prevent deletion.

Creating an Independent Copy (Optional)

Promote the clone to a full snapshot, then split it using ConvertTo-DcsFullSnapshot followed by Split-DcsSnapshot. In the console, the same operations are available under Virtual Disk > Snapshots > Promote to Full Snapshot, then Split.

Vendor Documentation

DataCore SANsymphony: Snapshot Operations

Dell PowerMax
What is Created During Restore From Snapshot

Veeam Backup & Replication creates a clone device whose Volume Identifier starts with VeeamAUX-, and a storage group named VEEAM_*.

What is Removed During Storage System Removal

When the storage system is removed, devices whose Volume Identifier starts with VeeamAUX- are reclaimed.

Action Required to Make Data Independent

Change the device Volume Identifier so that it no longer starts with VeeamAUX-.

  • In Unisphere, edit the identifier under Storage > Volumes.
  • Alternatively, edit the identifier with Solutions Enabler, using:
symconfigure -sid <SID> -cmd "set dev <SymDev> device_name='<NewName>';" commit
Creating an Independent Copy (Optional)

Link a TimeFinder SnapVX snapshot in Copy mode, then unlink it once the copy completes:

symsnapvx -sid <SID> -sg <SrcSG> -lnsg <TgtSG> -snapshot_name <name> -gen <gen> link -copy
symsnapvx -sid <SID> -sg <SrcSG> -lnsg <TgtSG> -snapshot_name <name> -gen <gen> unlink
Vendor Documentation

Dell Solutions Enabler CLI User Guide, for setting a device identifier, and Dell PowerMax and VMAX All Flash: TimeFinder SnapVX Local Replication (PDF).

Dell PowerStore
What is Created During Restore From Snapshot

Veeam Backup & Replication creates a restore clone named VeeamAUX-RESTORECLONE-<snapshotId> and a temporary iSCSI host record named VeeamAUX-*.

What is Removed During Storage System Removal

When the storage system is removed, objects carrying the VeeamAUX- prefix are deleted. A restore clone that is still mapped to a host record is skipped.

Action Required to Make Data Independent

Either:

  • Keep the restore clone mapped to the target ODB server so that it is skipped by the cleanup operation.

    or
  • Rename the restore clone so that the name no longer starts with VeeamAUX-.
    • To rename the clone, open Storage > Volumes, select the volume, click Modify, and edit the Name field.
    • To rename the host record, use Compute > Hosts > Modify > Rename.
Creating an Independent Copy (Optional)

No additional step is needed. A PowerStore thin clone is already independent of the snapshot it was created from.

Vendor Documentation

Dell PowerStore: Configuring Volumes (PDF), sections "Change volume properties" and "Thin clones".

Dell SC Series (Compellent)
What is Created During Restore From Snapshot

Veeam Backup & Replication creates View Volumes named VeeamView-VeeamBackup-<n>_* and a server object.

What is Removed During Storage System Removal

When the storage system is removed, unmapped Veeam volumes and an unmapped server object are deleted. Mapped volumes are skipped.

Action Required to Make Data Independent

Keep the restore volumes mapped to the server object. Nothing is deleted while the volumes are mapped, and access to the restored data is preserved. If the volumes are unmapped before the storage system is removed from Veeam Backup & Replication, both the volumes and the server object are deleted, and the restored data is lost.

Creating an Independent Copy (Optional)

Use Copy, Mirror, or Migrate a Volume, or use replication.

Vendor Documentation

Dell Storage Manager 2020 R1 Administrator's Guide (PDF), sections "Rename a Volume" and "Copying Volumes".

Everpure FlashArray (formerly Pure Storage FlashArray)
What is Created During Restore From Snapshot

Veeam Backup & Replication creates restore clone volumes named VEEAM-StorageLUNClone-<id> and a host record named VEEAM-StorageHost-<host>.

What is Removed During Storage System Removal

When the storage system is removed, the Veeam clone volumes are destroyed and eradicated, so the data cannot be recovered. If SafeMode or an eradication timer is enabled, the volumes stay in the destroyed bin until the timer expires, after which they are gone.

Action Required to Make Data Independent

Rename both objects before the storage system is removed:

  • Rename each clone volume so that it no longer carries the VEEAM-StorageLUNClone- prefix. This is what protects the data.
  • Rename the host record so that it no longer carries the VEEAM-StorageHost- prefix. This is what preserves the mapping. For example:

Note: The VEEAM-StorageHost- host record is created only for hosts connected over iSCSI. For Fibre Channel-attached hosts, the customer creates the host record in advance, so it does not carry the Veeam prefix and is not affected by storage system removal unless it was manually given a name matching that prefix.

purevol rename <old> <new>
purehost rename <old> <new>
Vendor Documentation

FlashArray Admin and CLI Reference Guides, for purevol and purehost.

Fsas ETERNUS AF/DX Series (formerly Fujitsu ETERNUS)
What is Created During Restore From Snapshot

Veeam Backup & Replication creates restore clones as SnapOPC+ snapshots named VeeamAUX_Restore_<date>_*, mapped through a Veeam LUN group and host affinity.

What is Removed During Storage System Removal

When the storage system is removed, only empty Veeam LUN groups are deleted.

Action Required to Make Data Independent

Keep the restore clone mapped. The LUN group is then not empty, nothing is deleted, and access to the restored data is preserved. This does not require downtime.

Creating an Independent Copy (Optional)

SnapOPC+ is a dependent snapshot, so a standalone volume requires a full copy. Run an OPC or QuickOPC copy from ETERNUS SF AdvancedCopy Manager or CCM:

acopc start -g <copyGroup>

The same operation is available in the Web GUI.

Vendor Documentation

For the Advanced Copy commands (OPC and QuickOPC), see the Fujitsu ETERNUS CLI User's Guide for the storage system's series.

Supported series are ETERNUS AF S2 and AF S3, ETERNUS DX S4, DX S5, and DX S6, and ETERNUS DX8900 S4. For current plug-in and firmware support details, see KB4043: Release Information for Fsas ETERNUS AF/DX Series Plug-In.

Hitachi VSP and VSP One Block
What is Created During Restore From Snapshot

Veeam Backup & Replication creates a clone LDEV whose label begins with VeeamCL and adds it to a Veeam snapshot group.

What is Removed During Storage System Removal

When the storage system is removed, a clone is deleted only when its label begins with VeeamCL.

Action Required to Make Data Independent

Rename the clone LDEV so that its name and label no longer begin with VeeamCL. The parent snapshot remains in place, so the data stays intact, and the rename does not require downtime:

raidcom modify ldev -ldev_id <id> -ldev_name <new>

The same change can be made in Storage Navigator under Edit LDEVs.

Creating an Independent Copy (Optional)

Create a ShadowImage full clone, then split the pair with paircreate followed by pairsplit -S. Use a ShadowImage or Thin Image clone-attribute full copy. Running pairsplit -S on a plain Thin Image snapshot pair discards the S-VOL data.

Vendor Documentation

Hitachi Command Control Interface Command Reference (PDF), for raidcom modify ldev, and the ShadowImage User Guide (SVOS) on the Hitachi Vantara documentation portal.

IBM FlashSystem (Spectrum Virtualize, SVC, Storwize)
What is Created During Restore From Snapshot

Veeam Backup & Replication creates a temporary host record named VeeamAUX_<host>_Restore.

What is Removed During Storage System Removal

When the storage system is removed, the host record is deleted. The restore clone volumes are not deleted, but they are left unmapped. The result is loss of access rather than loss of data.

Action Required to Make Data Independent

Rename the temporary host record so that it no longer carries the VeeamAUX_ prefix. The mapping is preserved, and the rename does not require downtime:

chhost -name <new> VeeamAUX_<host>_Restore

If the host record was already deleted, create a host record with the same initiator IQN and re-map the surviving clone volumes to it.

Creating an Independent Copy (Optional)

Use the FlashCopy Clone preset to create a full copy that is detached from the snapshot.

Vendor Documentation

IBM FlashSystem: chhost and IBM Storage FlashSystem documentation, for cloning snapshots.

INFINIDAT InfiniBox
What is Created During Restore From Snapshot

Veeam Backup & Replication creates a temporary host record named _vih.<host>-<id> and maps the restore clone, an auxiliary snapshot named _vas.Backup-<id>, to it.

What is Removed During Storage System Removal

When the storage system is removed, nothing is deleted as long as the restore volume is still mapped. InfiniBox does not delete a host record while volumes are mapped to it, and the clone volume itself is not targeted by removal.

Action Required to Make Data Independent

None, as long as the restore volume is left mapped. Access to the restored data is preserved. If the volume is unmapped first, the temporary host record is deleted, but the clone volume survives and can be re-mapped.

Vendor Documentation

InfiniBox InfiniShell CLI Reference, available from the INFINIDAT Support portal (sign-in required).

NEC Storage M Series
What is Created During Restore From Snapshot

Veeam Backup & Replication creates a clone FlashCopy volume (LD) named VeeamTMP_clon* and an LD Set named VeeamRest-*.

What is Removed During Storage System Removal

When the storage system is removed, clone LDs whose name matches a Veeam pattern (VeeamTMP, VeeamPDC, or VeeamAUX) are deleted.

Action Required to Make Data Independent

Rename the clone LD nickname so that it no longer matches a Veeam pattern. The LD Set also remains, and the rename does not require downtime. In iSM, change the nickname with:

iSMcfg rename-nickname
Creating an Independent Copy (Optional)

Create a DynamicDataReplication (DDR) full clone, then separate it with iSMrc_replicate followed by iSMrc_separate.

Vendor Documentation

NEC Storage Manager Command Reference (IS052) and Data Replication User's Manual (DynamicDataReplication), available from NEC Storage documentation and NEC support. Command usage is also summarized in the OpenStack NEC Storage M Series driver documentation.

NEC Storage V Series
What is Created During Restore From Snapshot

NEC Storage V Series is managed with Hitachi Command Control Interface (raidcom), so its removal behavior matches Hitachi VSP. Veeam Backup & Replication creates clone LDEVs named VeeamCL_* in a dedicated pool, production snapshots named VeeamPR_*, and an iSCSI target or host group named VBR_iSCSI_<n>.

What is Removed During Storage System Removal

When the storage system is removed, a clone is deleted only when its label begins with VeeamCL.

Action Required to Make Data Independent

Rename the clone LDEV so that it no longer carries the VeeamCL prefix. The data is preserved and the rename does not require downtime:

raidcom modify ldev -ldev_id <id> -ldev_name <new>

The same change can be made in Storage Navigator under Edit LDEVs.

Creating an Independent Copy (Optional)

Create a ShadowImage full clone, then split it with pairsplit -S -g <group>.

Vendor Documentation

Hitachi Command Control Interface Command Reference (PDF), for raidcom.

NetApp ONTAP
What is Created During Restore From Snapshot

Veeam Backup & Replication creates restore clones as FlexClone volumes named VeeamAUX_Restore_<vol>_*, and an initiator group named VeeamAUX_<host>.

What is Removed During Storage System Removal

When the storage system is removed, the VeeamAUX_ initiator group and its LUN mappings are deleted, so the host loses its paths. The FlexClone volumes and their parent snapshots are left in place. The result is loss of access rather than loss of data.

Action Required to Make Data Independent

Rename the initiator group so that it no longer carries the VeeamAUX_ prefix. The group and its mappings are preserved, the host stays connected, and the rename does not require downtime:

lun igroup rename -vserver <svm> -igroup VeeamAUX_<host> -new-name <new>

If the initiator group was already deleted, create a new group with the host IQN and re-map the surviving VeeamAUX_Restore_* LUNs to it.

Creating an Independent Copy (Optional)

To detach the clone from its parent snapshot, run:

volume clone split start -vserver <svm> -flexclone <VeeamAUX_Restore_...>
Vendor Documentation

ONTAP CLI: lun igroup rename and Split a FlexClone volume from its parent volume.

NetApp SolidFire (Element)
What is Created During Restore From Snapshot

Veeam Backup & Replication creates restore clone volumes named SF-VEEAM-CLONEOF-<id> and a volume access group named SF-VEEAM-<host>.

What is Removed During Storage System Removal

When the storage system is removed, the clone volumes and the access group are deleted permanently. The volumes cannot be recovered from the deleted-volumes list. Element volume names cannot be changed, and removal matches on an internal Veeam attribute rather than on the name, so neither renaming nor keeping the volume mapped prevents this.

Action Required to Make Data Independent

Make an independent copy before the storage system is removed. CloneVolume creates a new, independent volume that survives removal. Alternatively, move the data at the host level onto storage that Veeam Backup & Replication does not manage.

Vendor Documentation

Element software API: CloneVolume

Tintri IntelliFlash
What is Created During Restore From Snapshot

Veeam Backup & Replication creates a clone named Veeam-Clone-RESTORE-*.

What is Removed During Storage System Removal

When the storage system is removed, it is instructed to delete every temporary object that Veeam Backup & Replication created, regardless of the name shown. Renaming therefore does not prevent deletion.

Action Required to Make Data Independent

Make an independent copy before the storage system is removed. Either run a full Data Copy on the storage system to a new LUN in a separate project, or move the data at the host level, for example with Linux LVM pvmove, onto storage that Veeam Backup & Replication does not manage. If Data Copy is used, verify that the target contains the full data set.

Vendor Documentation

IntelliFlash PowerShell Toolkit

Avoiding This Situation on Future Restores

The dependency can be avoided before it is created. Before starting the restore wizard, create the auxiliary host for the LUN mount manually in the storage system interface, using a name that does not carry the prefix Veeam Backup & Replication reserves for the host records it creates automatically. A host record created this way is not one of Veeam Backup & Replication's own objects, so it is not removed when the storage system is removed from the Veeam Backup & Replication infrastructure.

For the reserved prefix and the full procedure, see Restoring from Storage Snapshot in the Veeam Backup & Replication User Guide.

More Information

If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Start using Veeam:
Download the product
&
Activate the license key
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.