Overview - Unix File System iDataAgents

Choose from the following topics:

• Introduction
• Supported Data Types
  • File Systems Supported by the Unix File System iDataAgents
• Effect of Data Types on Browse Operations by Unix File System iDataAgents
• Effect of Data Types on Backups by Unix File System iDataAgents
• Effect of Data Types on Restores by Unix File System iDataAgents
• Tree Levels in the Unix File System iDataAgent
• License Requirement
• Holed Files in Subclient Content
• Disaster Recovery Considerations

Related Topics:

• Erase Backup/Archived Data

Introduction

The Unix File Systems iDataAgents are backup and restore vehicles for file system data (i.e., files and directories) residing on Unix computer systems. These File System iDataAgents are just several of a group of iDataAgents that provide backup and restore support for different kinds of data in what is often a heterogeneous network environment. The following figure shows one such example (for the Solaris File System iDataAgent).

Supported Data Types

In general, each Unix File System iDataAgent except for the IRIX File System iDataAgent supports data protection operations for the appropriate Unix File System (UFS) data. In some cases, operations for some other File System data (e.g., CD-ROM File System [cdfs]) may be also supported. Also, some iDataAgents support additional file systems.

File Systems Supported by the Unix File System iDataAgents

The Unix File System iDataAgents support the following file system types:

In addition, the following section and two tables provide specific information on the effect of supported data types on browses, backups and restores by the various Unix File System iDataAgents. The right-most column in each table provides references to the appropriate commentary, requirements, and/or restrictions for each scenario. If the reference is flagged by "*", be sure to check the referred section for further information if necessary.

Effect of Data Types on Browse Operations by Unix File System iDataAgents

For Browse operations involving On Demand backup sets, you can browse either a single symbolic link pointing to a raw device or the actual path leading to the device. You can also browse the same if the symbolic link points to one or more intermediate symbolic links and both the original link and the intermediate links are contents in the same subclient. However, if they are not part of the same subclient, you can browse only the contents of the symbolic link; you cannot browse the actual raw device data file in this case.

On the other hand, for Browse operations involving regular backup sets, you can browse only the symbolic link to the raw device that was provided as the subclient content during a backup; you cannot browse the path pointing to the actual raw device in this case. Under this scenario, you can browse the same if the symbolic link points to one or more intermediate symbolic links without regard as to whether the original link and the intermediate links are contents in the same subclient.

Back to Top

Tree Levels in the Unix File System iDataAgent

When the Unix File System iDataAgent is installed, the following levels are automatically created in the CommCell Browser.

papaya: Client File System: Agent defaultBackupSet: Backup Sets	default: Subclients

License Requirement

To perform a data protection operation using this Agent a specific Product License must be available in the CommServe^® Server.

Review general license requirements included in License Administration. Also, View All Licenses provides step-by-step instructions on how to view the license information.

Holed Files in Subclient Content

Holed files are files that, while not using large blocks of memory for actual data, do use empty blocks, inflating the file size. These files can be backed up. However, when they are restored, the size of empty blocks may not be the same as before. See also Backup Considerations for This Agent.

Back to Top

Disaster Recovery Considerations

• Before you use your agent, be sure to review and understand the associated full system restore (or disaster recovery) procedure. The procedure for some agents may require that you plan specific actions or consider certain items before an emergency occurs.  See Disaster Recovery for more information regarding your agent.

Back to Top