Technical Note: XTN1304

Handling of Delete and Rename Records

Updated Nov. 19, 2013

Introduction
To make each archival cartridge (e.g. an LTO cartridge) self contained, even when a file is deleted or renamed after the cartridge becomes nominally full, we have made a change from version 6.11 of XenData6 Server software to the way delete and rename operations are handled.

In versions prior to 6.11, the delete or rename record is written to the current writable archival volume which is not necessarily the archival volume to which the file was written. From version 6.11 of XenData6 Server these records are written to the archive volume that contains the last version of the file.

How Delete and Rename Records are Handled from Version 6.11
From version 6.11 of XenData6 Server software, changes have been implemented to ensure that each archival cartridge (e.g. an LTO cartridge) has a self contained set of files and folders. Consequently, delete and rename records are written to the cartridge on which the file being deleted or renamed was last written. The applicable cartridge(s) must be available for writing i.e. mounted in a standalone drive or library under XenData control. This applies to both TAR and LTFS formatted LTO cartridges and will apply to Optical Disc Archive (ODA) cartridges that will be supported in future releases.

If the cartridge on which the file was last written is offline, it will be impossible to rename or delete the file and a message will be written to the Windows Event Log stating that the required cartridge(s) is offline and giving the cartridge barcode(s). After the cartridge is made available near-line, you will be able to perform the rename or delete operation.

If the file is written to a replicated volume, then only one of the replica cartridges needs to be near-line for the delete or rename to be successful. In this case, the offline replica cartridge will be identified in the XenData Management Console as "Needs updating", and will be updated when it is put back into the library or inserted in a stand alone drive.

If a file that is fragmented and spans more than one cartridge is deleted or renamed, the delete or rename record will be written to all cartridges that contain that file.

Applicable Operating Systems

  • Windows Server 2012 R2
  • Windows Server 2016
  • Windows Server 2019

Applicable XenData Software
This technical note is applicable to:

  • Version 6 – Server Editions of Archive Series software
  • Version 7 – Server Editions of Archive Series software including the Cloud File Gateway