V11 Service Pack 11

Overview - OnePass for UNIX File Systems

Note: If you are transitioning from the File Archiver for UNIX Agent, see Transitioning From Deprecated UNIX Archiver to OnePass.

OnePass for UNIX File Systems is a comprehensive solution incorporating the backup and archiving processes in a single operation. It enables you to move data to a secondary storage and use it to function as both backup and archive copy. You can back up and archive the data that resides on a file server. For more information, see Data Protection for NFS Shares, CIFS Shares, and UNC Paths.

Stubs are retained on the primary storage which point to the data moved as part of backup. The archived data will be available for quick and easy retrieval.

This integrated agent is able to selectively age off items based on data and stubs to reclaim space on your secondary storage.

Additionally this agent also provides analysis and reporting of the primary storage.

Comparison Chart

The following chart compares the traditional backup and the archiving agent with OnePass:

Key Features

OnePass for UNIX

UNIX File System iDataAgent

UNIX File Archiver Agent (Stand-Alone)

Data Backup


Data Archiving


Secondary Storage Space Reclamation using Synthetic Full Backups


Stub Restore


Data Restore

Stub Retention


Key Features

OnePass for Unix File Systems offers the following key features:

Simplified Data Management

OnePass enables you to easily manage the backed up data in your environment, by providing pre-defined archiving rules.

Point-in-Time Recovery

In the event of a serious system failure, such as the breakdown of hardware, software, or operating systems, the solution provides a point-in-time recovery of files at any given time.

Recall Throttling

You can configure the following stub recovery parameters:

  • Maximum Number of Stubs in a Recall Job
  • Time between recalls
  • Time to wait after maximum successive recalls limit is reached.

Item Level Retention

You can now specify the time period for which you want to retain the deleted files in the backup cycle. This enables you to restore the deleted files from the latest backup cycle. This will be useful for the OnePass clients where you perform frequent incremental backups.

Recursive Recall

On FreeBSD, you can recall more than one stubbed file at a given time. For example, if there are nested folders, you can recall all the stubs at the parent folder level.

What Is Archived

OnePass for UNIX File System archives the following file systems:

Operating System

Archived File Systems


Journal File System 2 (JFS2))

IBM General Parallel File System (GPFS)

Network File System (NFS). For step-by-step instructions to archive NFS volumes, see Archiving NFS Volumes on AIX and Linux Clients.

VERITAS File System (VxFS)

VERITAS Cluster File System (VxCFS)


Unix File System (UFS)

Zettabyte File System (ZFS)


VERITAS File System (VxFS)


'X' File System (XFS)

Extended 3 File System (ext3)

Extended 4 File System (ext4)

IBM General Parallel File System (GPFS)

Network File System (NFS). For step-by-step instructions to archive NFS volumes, see Archiving NFS Volumes on AIX and Linux Clients.

X9000 IBRIX File System (IBRIXFS) 6.x

PolyServe Matrix Server

VERITAS File System (VxFS)

VERITAS Cluster File System (VxCFS)

Lustre File System (Clustered File System)

Red Hat Linux 6.x

GFS2 (Clustered File System)

The default Extended 2 File System (ext2) gets archived when it is compiled as a module.

Novell OES2 Linux

NSS File System


Unix File System (UFS)

VERITAS File System (VxFS)

Zettabyte File System (ZFS on Solaris 10 6/06)

Note: For OnePass for FreeBSD File System to function, the file system should be mounted with the extended attribute option. If the extended attribute option is not enabled on the mount point, files will be backed up but not archived.

What Is Not Archived

The following file types/objects are automatically filtered out of archive operations by the system, and will not be archived.

  • Sparse files (Example: File Archiver stub files)
  • Install directory
  • Job Results directory
  • Log files directory
  • /usr system directory
  • /kernel system directory
  • /etc system directory
  • /tmp directory
  • Extended attributes in the OES Linux data
  • Stubs originating from an NSS volume on an OES Linux computer

Files with extensions *.a, *.ksh, *.csh, *.sh, *.lib, and *.so are automatically filtered out of the subclient content by default. Similarly, files in the following directories are also skipped from archiving on all Unix platforms.

  • /usr/**
  • /bin/**
  • /lib/**
  • /boot/**
  • /dev/**
  • /etc/**
  • /var/**
  • /tmp/**
  • /sbin/**
  • /lib64/**
  • /opt/**
  • /sys/**
  • /kernel/**
  • /devices/**
  • /proc/**
  • /selinux/**
  • /stand/**

In addition to the above, there are also platform specific files that are automatically filtered from archiving.

  • AIX - /**/*.imp, /**/*.exp
  • Mac OS X - /**/*.dylib, /**/*.scpt, /Applications/**, /Developer/**, /Library/**, /Network/**, /System/**, /Volumes/**, /private/**
  • Solaris - /platform/**
  • FreeBSD - /rescue/**



Archiving is a process of periodically moving unused or infrequently used data on a host computer to secondary storage, thereby reducing the size of data on the primary storage.


The stubbing phase starts after the archive phase succeeds. Stubs are placeholders of the original data after it has been moved to the secondary storage. Stubs replace the archived files in the location selected by the user during the archive. However, stubs will only be created if the subclient properties were configured to create them during archive.

Data Recovery


The archived and moved data can be recovered using the following methods:

  • Recovery of archived files per file paths provided using the CommCell Console.
  • Browse and Recovery of archived files using the CommCell Console.

Stub Recovery

If the subclient is configured to create stubs, you can perform a recall operation from any workstation for recovering the stubs. A recall is any action that causes an open and read to be executed on the stub, which automatically initiates a recovery operation.

Persistent Recovery

Multiple stub recoveries are submitted to the Job Controller as one job called a Persistent Recovery job. The job will wait for approximately 5 seconds in order to allow other stub recovery requests being submitted on the same client to be batched into the same job.


Last modified: 1/18/2018 12:33:34 PM