IBM Tivoli Storage Manager for UNIX and Linux Backup-Archive ...

up from a VxFS file system will be restored to an UFS file system because thesefile systems support compatible ACLs. The ACL information will not berestored during cross file system type restores or retrieves if the original filesystem and the destination file system are incompatible with regard to ACLsupport or if the destination file system does not support ACLs.5. The standalone package LSCqfs 3.5.0 is the only supported version of QFS. Inaddition, the following restrictions also apply to the QFS file system:v Image backup is not supported on QFS file systems.vThe Solaris backup-archive client does not support the combination of QFSand SAM needed to archive files onto tertiary background storage, such astapes. Instead, it recalls files from tape to disk automatically if it findsmigrated files during a backup.v A QFS file system contains two hidden system files and a system directorythat cannot be backed up. This is acceptable because a backup of these filesis not needed. They contain internal data to manage the file system. Thisdata will be automatically excluded from a backup and recreatedautomatically by the file system itself if a restore of files in that file system isinvoked.6. Incremental, selective, filelist back up, archive, restore, and retrieve processingof the Veritas file system and its ACLs on AIX are supported. Restore of aVeritas volume on a Logical Volume Manager volume and vice-versa is allowedprovided both have the same file system type.7. On Mac OS X systems, the UFS and HFSX file systems are sensitive to casewhereas the HFS+ file system is case-insensitive but is case-preserving. Filesthat you back up from a UFS or HFSX file system (case-sensitive) might not berestored properly to an HFS+ file system (case-insensitive) file system. Forexample, on a UFS file system, files Afile and afile are seen as different files.However, on a HFS+ file system the two files are seen as identical.If Case-sensitive HFS+ or UFS file systems are used, it is very important thatthe data from the HFSX or UFS file system is not backed up to a HFS+ filesystem on the Tivoli Storage Manage server. Either a new name must be usedon the system or the existing file space on the Tivoli Storage Manager servermust be renamed. For example, consider a system that has a file system named/Volumes/fs2 and this system is repartitioned with a Case-Sensitive HFS+ filesystem. Either the /Volumes/fs2 file system on the Tivoli Storage Managerserver needs to be renamed, or a new name must be used on the local system.If this is not done, Tivoli Storage Manager will mix the HFSX case-sensitivedata with the HFS+ case-insensitive data that is already stored on the TivoliStorage Manager server.Aliases and symbolic links are backed up. However, Tivoli Storage Managerdoes not back up the data to which the symbolic links point.When files backed up from an HFS volume are restored to a UFS volume, theresource forks will not have the correct owner. This can be corrected by usingthe chown command on the resource fork file.8. On LinuxPPX, Linux390 and LinuxAMD, you must install libacl.so for theTivoli Storage Manager client to back up ACLs.Important: If you are running GPFS for AIX or GPFS for Linux x86/x86_64 in amultinode cluster, and all nodes share a mounted GPFS file system, Tivoli StorageManager processes this file system as a local file system. Tivoli Storage Managerbacks up the file system on each node during an incremental backup. To avoidthis, you can do one of the following:114 IBM Tivoli Storage Manager for UNIX and Linux Backup-Archive Clients Version 6.1: Installation and User’s Guide