Encrypted Volume and File System v2.0 Administrator Guide HP-UX 11i v3

format. Therefore, any executable that uses file system utilities to read or write data can operate
only on cleartext data.
Network file sharing utilities, such as NFS, CIFS, FTP, or rcp will transmit files in cleartext,
even if the original files reside on an EVFS volume.
• For EVFS volumes configured in EVS mode, to use a backup utility that performs incremental
backups or that backs up individual files, you must enable the EVFS volume. The backup utility
will read the data in cleartext, even if the original files reside on an EVFS volume. If the target
backup device is another EVFS volume, the target EVFS volume will re-encrypt the data.
If the target backup device is a tape device or other non-EVFS device:
◦ You must back up the volume as a volume device (as a single unit), not as a file system
or group of files, to create encrypted backup media. You can create encrypted backup
media using block device utilities, such as dd.
◦ You cannot create encrypted backup media using file-based utilities with EVFS volumes
configured for EVS.
• EVFS is not supported by SAM or SMH.
• The evfsadm trace command is intended for use by support personnel only. HP does not
support this feature on customer environments.
• During inline encryption, the volume is not accessible until the entire operation is completed.
• The Multi Volume File System feature of Veritas, which is not supported by EVFS.
• EVFS is currently available in English only.
• Secure Sessions limit: 16K secure sessions per system.
• Volume limit: 1023 encrypted volumes per system.
• ServiceGuard version A.11.18 or later using modular packages supports EVFS volumes without
a file system.
• On a EFS volume, the file size is limited to a maximum file size minus the size of the EMD
(4k).
• Writing to a EVFS device that is not mapped by EVFS (for example, when EVFS is not running),
can cause data corruption.
• The maximum user name, group name, or key name length supported by EVFS is 100.
• The user IDs and group IDs must be unique for user keys and group keys to work properly (for
example, users cannot share the same user ID and groups cannot share the same group ID).
18 Overview