Commvault - Linux File System - Not Backing Up NFS
The Linux client backup process log /var/log/commvault/Log_Files/clBackupChild.log
The error log like this:
21020 521c 07/28 17:28:31 11 CFileReader::isLocked(682) – fcntl(/mnt/nfs/build/EZStart-USB-Silver/development/USB_Silver_Images/FDR/OEL_6SP3-V8.20/gUSB3650MB-Install-6.4.181-FDR-8.20-9309-OEL6U5.img.zip, F_GETLK) failed: Input/output error
The command simpana status can display current Linux client status detail information.
[root@phi-ora11gvm Log_Files]# simpana status
——————————— Instance001 ———————————
[ General ]
Version = 11(BUILD80) SP8
CommServe = H13-242
Home Directory = /opt/commvault/Base
Log Directory = /var/log/commvault/Log_Files
Core Directory = /opt/commvault
Temp Directory = /opt/commvault/Base/Temp
Platform Type = 6
Cvd Port Number = 8400
[ Package ]
1002/CVGxBase 11(BUILD80) = File System Core
1101/CVGxIDA = File System
1128/CVGxEDC = External Data Connector
1130/CVGxRP = Resource Pack
1301/CVGxMA = MediaAgent
1304/CVGxFibreMA = SAN Storage Server
[ Physical Machine/Cluster Groups ]
Display Name = phi-ora11gvm
– Client Hostname = phi-ora11gvm
– Job Results Directory = /opt/commvault/iDataAgent/jobResults
– Index Cache Directory = /opt/commvault/MediaAgent/IndexCache
Please try the following for resolve issue:
1)Log in the machine as root.
2)In the /etc/CommVaultRegistry/Galaxy/Instance001/FileSystemAgent directory
3) Edit/vi the .properties file and add the following lines. Those are not typos…it starts off with a small "s" and then a capital "S" ; a small "d" and a capital "L":
sSKIPLOCKF Y
dLOCKTEST 1
4) Stop/start Galaxy -> /etc/init.d/Galaxy restart
The dLOCKTEST key does if we try to back up a locked file, the OS will still give the error, but we will back up the file anyway. The sSKIPLOCKF key allows you to skip-detect the locked files and continue with the backup. This is recommended whenever an iDataAgent is backing up files on an NFS server where it fails to get locks on these files. Whenever the value is set to Y, clBackup skips getting the write-lock on files to be backed up and simply goes ahead with backing up the files. Backups may be inconsistent if the files are being accessed while backing up.
JW
FYI Document link http://documentation.commvault.com/commvault/v10/article?p=landing_pages/c_backup_agents.htm