Frequently Asked Questions - Linux File System

What permissions does the restored data acquire After the restores?

When performing restore operations (other than in-place restores), the restored data assumes the rights (i.e., permissions) of the parent directory.

How are case-sensitive files restored from unix to windows clients?

Windows operating system does not maintain case-sensitivity of the file names. Hence, when you perform a cross-platform restore from a Unix client to a Window Client, if there are two case-sensitive files with same name, the case sensitivity of the files are ignored and the files are overwritten. For example, if you are trying to restore files named SAMPLE and sample from Unix to Windows, the file which is restored last will overwrite the first one that was restored.

How are file names with \ character handled when restoring from Unix to Windows Clients?

When you restore a file with a \ character in its name (for example, file\.dat) to a Windows client computer, Windows interprets the \ as a delimiter in the path name and creates a folder on the Windows computer named file, which will contain a file named .dat. However, the contents of the files file\.dat and .dat are identical.

When does a Non-Full Backup Automatically get Converted to a Full Backup?

A non-full backup is automatically converted to a full backup in the following situations:

What are the two types of file locks and how are they backed up?

The Unix file system uses two types of file locks: Advisory locks and Mandatory locks. Files with an advisory locks are available to multiple users and applications. Files with mandatory locks cannot be used by any other user or application other than the current user.

Files with advisory locks are included in the backups by default. On the other hand, files with mandatory locks are skipped during the backup process and their file names and paths are logged to the Backup Job History log. You can use the CommCell Console to examine this log to determine if any files were skipped. The system automatically attempts to obtain any skipped files in the next backup.

You can backup mandatory locks when you install and enable Qsnap. For comprehensive information on configuring backups for files with mandatory locks, see Configuring Backups for Locked Files for step-by-step instructions.

How do we identify and exclude file system types without a name from backups?

File system types that do not have a corresponding name can be identified by their numeric value. The numeric value of such file systems can be found printed in the FileScan.log log file located in the /var/log/calypso/Log_Files/ directory, as shown below.

For example:

Find::GetFsType() - add fstype '391' for '/home' to cache (st_dev:17)

Find::GetFsType() - add fstype 'ext3' for '/testData/uxpermissions' to cache (st_dev:FC08)

This numeric value of file system type from above example can be used in conjunction with the ignoreFStype registry key to skip the file system type from backups.

For example,

ignoreFStype :391:.

What are the Folders/Files Created and Changes Done During Install of this Agent?

Platforms Folders Created Files Created Other changes
Linux /opt/calypso/Base/calypso

/usr/bin/calypso

/usr/bin/cvpkgrm

/usr/bin/cvpkgcheck

/usr/sbin/calypso

/usr/sbin/cvpkgrm

/usr/sbin/cvpkgcheck

/usr/bin/cvpkgchg

/usr/sbin/cvpkgchg

/etc/galaxy

/dev/cxbf

/usr/bin/LaunchBrowser $INSDIR/$INSSUBDIR/GUI/LaunchBrowser (only when CVGxGUI is installed)

/usr/bin/console (only when CVGxGUI is installed)

/usr/sbin/console (only when CVGxGUI is installed)

/tmp/.gxsetup directory (during install and after install if failed )

/var/log/.gxsetup directory (after install)

/etc/gxsetup_guid

Driver configuration file to / lib / modules / $ UTS / kernel / copied drivers /block /sbin /cvsnap (copied from the installation package)

/etc /init.d / cxbf

/etc /rc.d / boot.localfs

/etc /rc.d / rc.sysinit is updated (if selected during install)

/usr/bin/<sscript>

/usr/sbin/<sscript>

where sscript = simpana|HitachiHDS| Calypso|snapprotect|StorageServices |StorageProtection)

Startup Scripts: /etc/init.d/Galaxy ( Linux using insserv such as Suse)

<dir>/K01Galaxy where <dir>=/etc/rc.d/rc0.d; /etc/rc0.d ; /sbin/rc.d/rc0.d ; sbin/rc0.d ; /etc/init.d/runlevels/%0 only if <dir> exists

<dir>/K01Galaxy where <dir>=/etc/rc.d/rc6.d; /etc/rc6.d ; /sbin/rc.d/rc6.d ; sbin/rc6.d ; /etc/init.d/runlevels/%6 only if <dir> exists

<dir>/S99Galaxy where <dir>=/etc/rc.d/rc2.d; /etc/rc2.d ; /sbin/rc.d/rc2.d ; sbin/rc2.d ; /etc/init.d/runlevels/%2 only if <dir> exists

<dir>/S99Galaxy where <dir>=/etc/rc.d/rc4.d; /etc/rc4.d ; /sbin/rc.d/rc4.d ; sbin/rc4.d ; /etc/init.d/runlevels/%4 only if <dir> exists

<dir>/S99Galaxy where <dir>=/etc/rc.d/rc3.d; /etc/rc3.d ; /sbin/rc.d/rc3.d ; sbin/rc3.d ; /etc/init.d/runlevels/%3 only if <dir> exists (Linux only except Ubuntu)

<dir>/S99Galaxy where <dir>=/etc/rc.d/rc5.d; /etc/rc5.d ; /sbin/rc.d/rc5.d ; sbin/rc5.d ; /etc/init.d/runlevels/%5 only if <dir> exists (Linux only except Ubuntu)

<dir>/K99Galaxy where <dir>=/etc/rc.d/rc3.d; /etc/rc3.d ; /sbin/rc.d/rc3.d ; sbin/rc3.d ; /etc/init.d/runlevels/%3 only if <dir> exists (Linux only except Ubuntu)

<dir>/K99Galaxy where <dir>=/etc/rc.d/rc5.d; /etc/rc5.d ; /sbin/rc.d/rc5.d ; sbin/rc5.d ; /etc/init.d/runlevels/%5 only if <dir> exists (Linux only except Ubuntu)

<dir>/S99Galaxy where <dir>=/etc/rc.d/rc<n>.d; /etc/rc<n>.d ; /sbin/rc.d/rc<n>.d ; sbin/rc<n>.d ; /etc/init.d/runlevels/%<n> only if <dir> exists, where <n> is the second field in line “id:2:initdefault:” of /etc/inittab

<dir>/K99Galaxy where <dir>=/etc/rc.d/rc<n>.d; /etc/rc<n>.d ; /sbin/rc.d/rc<n>.d ; sbin/rc<n>.d ; /etc/init.d/runlevels/%<n> only if <dir> exists, where <n> is the second field in line “id:2:initdefault:” of /etc/inittab