KNOWLEDGE BASE

Knowledge Base Article: 000187008

OneFS: Error when copying files using the isi_vol_copy_vnx utility (000187008)
Version:7

Audience: Level 30 = Customers Article Type: Break Fix

Last Published: Fri Mar 06 10:44:18 GMT 2015 Validation Status: Final Approved

Summary: Standard NDMP backups and isi_vol_copy_vnx can affect each other and the data backed up by the two NDMP clients.

Issue: Issue
When attempting to migrate files from a VNX system using the isi_vol_copy_vnx utility, new files added to new
directories between incremental data transfers are not migrated.
Symptoms
When you run the isi_vol_copy_vnx -incr command to complete an incremental data transfer, the process fails
and an error similar to the following appears in the command-line interface:
Unable to enc_fstatat name:./a.xz00/u.130/XZ00130701_UGM.00.000.jt parent:11
err:[2]No such file or directory
Unable to enc_fstatat name:./a.xz00/u.130/XZ00130701_UGM.00.000.prt parent:11
err:[2]No such file or directory

Environment: Isilon
Isilon OneFS

Cause: Each time an NDMP backup is done on the VNX, the VNX will record the directory backed
up, the level of the backup and the time it was started. This is recorded in
/nas/rootfs/slot_X/.etc/BackupDates on the VNX.

When the next incremental backup is started the VNX will search this file to get the
reference date, that is the date that is compared to the modified date on the file. If the files
date is newer than the reference date, then it will be backed up otherwise it will ignored.

The VNX cannot distinguish between who is doing the backup, the Isilon isi_vol_copy_vnx
script or the third party backup software. Therefore the following can happen:
1. A full copy (full NDMP backup) with the isi_vol_copy_vnx is run. This updates the
reference date for level 0 backup for the directory in the BackupDates file.
2. Sometime later a full copy with the backup server on the same directory is completed. This
will again update the reference date on the VNX in the BackupDates file for the directory.
3. Then when an incremental isi_vol_copy_vnx (effectively an NDMP incremental backup) is
done and it will only copy over data modified since the full backup done by the backup
software. The files modified between the isi_vol_copy_vnx full copy and the full backup by
the backup server will not get copied because the backup software caused the reference
date to be changed.

Resolution: Workaround 1:
Disable all backup jobs during data migration. Backup jobs can be re-enabled after data migration is complete.
CAUTION!
If you are continuing to use your existing VNX storage and backup software, you must run another full backup after data
migration is complete to ensure all files are copied correctly.
Workaround 2:
As the BackupDates file records backup times and levels based on the directory being
backed up, a special checkpoint needs to be created on the filesystem. This checkpoint
will be used by the isi_vol_copy_vnx script. Then the backup server will record backup
times and levels for the filesystem and where it is mounted and the isi_vol_copy_vnx will
make the VNX record backup times and levels for the path to the checkpoint. This will
avoid the two NDMP clients affecting each other.

1.
 1. Create a checkpoint on the FS:
# fs_ckpt <FSname> -name <FSname>_isi_vol_copy_vnx_ckpt –Create

2. Run a full copy using the isi_vol_copy_vnx script on the path

/<FSname>_isi_vol_copy_vnx_ckpt
Note: If the checkpoint is mounted on a VDM the path to the checkpoint will be similar to
/root_vdm_<VDMid>/<FSname>_isi_vol_copy_vnx_ckpt
# isi_vol_copy_vnx <DM IP>:/<FSname>_isi_vol_copy_vnx_ckpt /ifs/data/<destDir> -sa
<ndmpUser>:<passwd> -full -no_snap

3. When an incremental copy is needed, refresh the checkpoint.

# fs_ckpt <FSname>_isi_vol_copy_vnx_ckpt –refresh

4. Run the incremental copy with isi_vol_copy_vnx

# isi_vol_copy_vnx <DM IP>:/<FSname>_isi_vol_copy_vnx_ckpt /ifs/data/<destDir> -sa
<ndmpUser>:<passwd> -incr -no_snap
Steps 3 and 4 can be repeated as many times as needed (daily or weekly) while the migration is being done.
These steps will need to be done just before the cut-over to Isilon to ensure all data from theVNX is copied over.

Notes: The "-no_snap" option is currently not documented in the man page of the isi_vol_copy_vnx command. Nor is it
displayed in the "Usage" output from the command. This is being corrected by Engineering.

The "-no_snap" option stops the VNX from creating an automatic checkpoint on the filesystem as the NDMP backup is
being run on a checkpoint.

Product: Isilon, Isilon OneFS,Isilon OneFS7.0,Isilon OneFS7.1,Isilon OneFS7.2,Isilon OneFS8.0,Isilon OneFS6.5.5,Isilon

OneFS7.0.0,Isilon OneFS7.0.1,Isilon OneFS7.0.2,Isilon OneFS7.1.0,Isilon OneFS7.1.1,Isilon OneFS7.2.0.0,Isilon
OneFS7.2.0.1,Isilon OneFS7.2.1.0,Isilon OneFS8.0.0,Isilon OneFS6.5.5.0,Isilon OneFS6.5.5.1,Isilon
OneFS6.5.5.10,Isilon OneFS6.5.5.11,Isilon OneFS6.5.5.12,Isilon OneFS6.5.5.13,Isilon OneFS6.5.5.14,Isilon
OneFS6.5.5.15,Isilon OneFS6.5.5.16,Isilon OneFS6.5.5.17,Isilon OneFS6.5.5.18,Isilon OneFS6.5.5.19,Isilon
OneFS6.5.5.2,Isilon OneFS6.5.5.20,Isilon OneFS6.5.5.21,Isilon OneFS6.5.5.22,Isilon OneFS6.5.5.23,Isilon
OneFS6.5.5.24,Isilon OneFS6.5.5.26,Isilon OneFS6.5.5.27,Isilon OneFS6.5.5.28,Isilon OneFS6.5.5.29,Isilon
OneFS6.5.5.3,Isilon OneFS6.5.5.4,Isilon OneFS6.5.5.5,Isilon OneFS6.5.5.6,Isilon OneFS6.5.5.7,Isilon
OneFS6.5.5.8,Isilon OneFS6.5.5.9,Isilon OneFS7.0.0.0,Isilon OneFS7.0.1.0,Isilon OneFS7.0.1.1,Isilon
OneFS7.0.1.10,Isilon OneFS7.0.1.11,Isilon OneFS7.0.1.2,Isilon OneFS7.0.1.3,Isilon OneFS7.0.1.4,Isilon
OneFS7.0.1.5,Isilon OneFS7.0.1.6,Isilon OneFS7.0.1.7,Isilon OneFS7.0.1.8,Isilon OneFS7.0.1.9,Isilon
OneFS7.0.2.0,Isilon OneFS7.0.2.1,Isilon OneFS7.0.2.10,Isilon OneFS7.0.2.12,Isilon OneFS7.0.2.2,Isilon
OneFS7.0.2.4,Isilon OneFS7.0.2.5,Isilon OneFS7.0.2.7,Isilon OneFS7.0.2.8,Isilon OneFS7.0.2.9,Isilon
OneFS7.1.0.0,Isilon OneFS7.1.0.1,Isilon OneFS7.1.0.2,Isilon OneFS7.1.0.3,Isilon OneFS7.1.0.4,Isilon
OneFS7.1.0.5,Isilon OneFS7.1.0.6,Isilon OneFS7.1.1.0,Isilon OneFS7.1.1.1,Isilon OneFS7.1.1.2,Isilon OneFS8.0.0.0