Frequently Asked Questions - Install

Table of Contents

How do We Identify the Third-Party Application files installed with the CommServe?

Can I install the Software using a sudo user account?

How to Change the Group ownership for Simpana files and directories after installing any software?

Can we install the software components in a PowerBroker™ Environment from CommCell Console?

Can I install CommServe using an existing instance of SQL Server?

How to Change the Permissions for Simpana files and directories after installing any software?

How to fix the Permissions after installing any software?

What are the files/folders created and changes done during installation?

How to use the physical node interface for backups on virtual machines in a cluster?

Can we install software binaries to an NFS drive?

How do We Identify the Third-Party Application files installed with the CommServe?

The following third-party application files are installed along with the CommServe.

<software_install_path>\Base\AutoMapper.dll

<software_install_path>\Base\Borland.Janeva.Runtime.dll

<software_install_path>\Base\Borland.Janeva.Runtime.Private.dll

<software_install_path>\Base\Borland.Janeva.Services.dll

<software_install_path>\Base\Borland.Janeva.Services.Private.dll

<software_install_path>\Base\ChilkatDotNet2.dll

<software_install_path>\Base\ctreedbs.dll

<software_install_path>\Base\ctreestd_trans.dll

<software_install_path>\Base\CVChunkLister.exe

<software_install_path>\Base\CVctreestd.dll

<software_install_path>\Base\CvMsoIrmProtector.dll

<software_install_path>\Base\CvSMTPMgr.dll

<software_install_path>\Base\CvSnapLSI.dll

<software_install_path>\Base\CVSQLite3.dll

<software_install_path>\Base\DLLOA64.DLL

<software_install_path>\Base\DSAPIDotNet.dll

<software_install_path>\Base\DSModelDotNet.dll

<software_install_path>\Base\eql_psapi.dll

<software_install_path>\Base\Esp-Searchapi.dll

<software_install_path>\Base\FPCore.dll

<software_install_path>\Base\FPLibrary.dll

<software_install_path>\Base\FPOS64.dll

<software_install_path>\Base\FPParser.dll

<software_install_path>\Base\FPStreams.dll

<software_install_path>\Base\FPUtils.dll

<software_install_path>\Base\FPXML.dll

<software_install_path>\Base\HTMLConverter.dll

<software_install_path>\Base\HtmlConverterX.exe

<software_install_path>\Base\ICSharpCode.SharpZipLib.dll

<software_install_path>\Base\Interop.GENEVTINFLib.dll

<software_install_path>\Base\Libeay32.dll

<software_install_path>\Base\MonadCmdLetSrvr.dll

<software_install_path>\Base\MSVCR71.dll

<software_install_path>\Base\NTAPAdmin.dll

<software_install_path>\Base\ONCRPC.dll

<software_install_path>\Base\PAI_module.dll

<software_install_path>\Base\pcre.dll

<software_install_path>\Base\pcrecpp.dll

<software_install_path>\Base\pegclient.dll

<software_install_path>\Base\pegcommon.dll

<software_install_path>\Base\pegslp_client.dll

<software_install_path>\Base\PLink.exe

<software_install_path>\Base\SnapCleanup.exe

<software_install_path>\Base\SSLeay32.dll

<software_install_path>\Base\stlport.5.0.dll

<software_install_path>\Base\unzip.exe

<software_install_path>\Base\Xalan-C_1_10.dll

<software_install_path>\Base\XalanMessages_1_10.dll

<software_install_path>\Base\xerces-c_2_6.dll

<software_install_path>\Base\xerces-c_2_7.dll

<software_install_path>\Base\zip.exe

<software_install_path>\Base\zlib1.dll

<software_install_path>\Base32\ErrorMonitor.exe

<software_install_path>\Base32\msvcr71.dll

<software_install_path>\Base32\python25.dll

C:\Windows\system32\DRIVERS\RsFx0103.sys

These files are not signed and will not have complete file version information in the file's Properties dialog box.

For example:

<software install path>\Base\AutoMapper.dll does not have a valid Company name and Product Name properties.

However, note that having incomplete file version information on these files does not affect the performance of the software.

Can I install the Software using a sudo user account?

Yes, you can install the software using a sudo user account if it is configured on your client computer.

The following section describes the steps involved in configuring the sudo user account:

  1. Install the sudo software package if sudo is not available on the UNIX client computer.
  2. Create a UNIX user which will act as a sudo user. For example, consider a user named user1.

    Add the following lines in the sudoers file located under /etc.

    Host_Alias CVNJ = x.x.0.0/<subnet>

    User_Alias INSTALLUSERS =user1

    #Install commands

    Cmnd_Alias DVDINSTALLCMDS = =<absolute path of cvpkgadd>cvpkgadd (This is the location where cvpkgadd is mapped in the client machine).

    #<Install directory>/Simpana

    Cmnd_Alias INSTALLDIRCMDS = /opt/Simpana/*

    #System shared libraries location

    Cmnd_Alias SHAREDLIBLOCATION = /lib/*

    #Binaries location

    Cmnd_Alias BINLOCATION = /usr/bin/Simpana

    INSTALLUSERS CVNJ = DVDINSTALLCMDS,INSTALLDIRCMDS,SHAREDLIBLOCATION,BINLOCATION

  3. Logon to the client computer using sudo user account.
  4. Install Simpana software using one of the following commands:

How to Change the Group ownership for Simpana files and directories after installing any software?

You can use a script available in the <software Install directory> . Follow the steps to change the group ownership for Simpana files and directories:

  1. Ensure that no jobs are running in any Simpana instance.
  2. From the Command Prompt, navigate to <Simpana Install> directory.
  3. Enter the command ./cvpkgchg.
  4. Select option 1.
  5. Type the new group name and press Enter.
  6. Restart The Simpana services for all instances to change the group ownership.

Can we install the software components in a PowerBroker Environment from CommCell Console?

Yes, you can install the software components in a PowerBroker™ environment from CommCell Console. For more information, see Install Software in a PowerBroker™Environment from CommCell Console.

Can I install CommServe using an existing instance of SQL Server?

Yes. If you want to use an existing instance of SQL server that was not installed by Simpana , then make sure to configure the szUserSQLInstanceName registry key on the computer on which you want to perform the installation.

Use the following steps to configure the szUserSQLInstanceName registry key:

  1. Log on to the CommServe computer as an Administrator.
  2. Click Windows Start button, click Run, type regedit and then click OK to open the Registry editor.
  3. Navigate to HKEY_LOCAL_MACHINE \SOFTWARE\GalaxyInstallerFlags
  4. Right click the GalaxyInstallerFlags and select New -> String value.
  5. Specify the Value name as szUserSQLInstanceName.
  6. Double-click szUserSQLInstanceName, in the Value data box, type the name of the SQL instance that you want to use.
  7. Click OK.
  8. Close the Registry editor.

How to Change the Permissions for Simpana files and directories after installing any software?

By default, the root user and all users in that group have full permissions on all Simpana files and directories. For other users, you can assign required permissions as follows:

  1. Ensure that no jobs are running on any Simpana instance. You have to restart Simpana services for all instances to change the permissions.
  2. From the Command Prompt, navigate to <software Install directory>.
  3. Enter the command ./cvpkgchg.
  4. Select option 2.
  5. Select the type of permission that you want to assign to other users and press Enter.
  6. Type Yes to change the permissions.
  7. Restart The Simpana services for all instances to change the permissions.

Depending on the file type, the actual permissions set might be more restrictive. For example, a text file may not have the executable bit turned on.

If you run the installer to add more instances or modules, you need to rerun this utility to fix certain files changed during the install. Do not use this script for multiple Simpana instances from different releases.

When you change groups and permissions for any Database iDataAgent files, make sure permissions for other users are set to read-write-execute.

If the snapshots are mounted within the <software Install directory>, you may get the following error:

Executables(/opt/InstallDir) ... FAILED

You can ignore this error and continue running the script.

How to fix the Permissions after installing any software?

When you add any new Simpana agent to the existing <software Install directory>,you may need to fix the permissions for newly added files and directories. Follow the steps given below to fix the permissions:

  1. Ensure that no jobs are running in any Simpana instance.
  2. From the Command Prompt, navigate to <software Install directory>.
  3. Enter the command ./cvpkgchg.
  4. Select option 3.
  5. Type Yes to change the permissions for the new files and folders. The permissions assigned will be same as the existing files and directories in the <software Install directory>.
  6. Restart The Simpana services for all instances to change the permissions.

What are the files/folders created and changes done during installation?

File System iDataAgent

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

/usr/bin/simpana

/usr/bin/cvpkgrm

/usr/bin/cvpkgcheck

/usr/sbin/simpana

/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

Solaris /opt/simpana/Base/simpana

/usr/bin/simpana

/usr/bin/cvpkgrm

/usr/bin/cvpkgcheck

/usr/sbin/simpana

/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 /usr/kernel/drv copied /cxbf.conf Driver to /usr/kernel/drv/amd64 for X86 and /usr/kernel/drv/sparcv9 copiert for Sparc

File /usr/sbin/cvsnap is created (copied from the installation package)

Create file /usr/sbin/cv_vxfreeze.

File /usr/sbin/cv_vxunfreeze is created (copied from the installation package)

File /usr/sbin/cvsnap32 is created (copied from the installation package)

File /usr/sbin/cxbf-bootscript1.rc.example is created

File /usr/sbin/cxbf-bootscript2.rc.example is created

/ Etc /devlink.tab is updated

File /usr/sbin/cxbf-bootscript1.rc is created

File /etc/rc3.d/S66CVCXBF is created

File /etc/rcS.d/S96CVCXBF is created

/etc/system (solaris2.8 and 2.9 only when user selected to modify IPC settings)

/etc/system.gal.$$ (solaris2.8 and 2.9 only; backup if user selected yes for IPC change OR suggested settings if user selected not to change IPC this time; $$ is pid)

The file /etc/rc0 adjusted accordingly (if selected during install)

Startup Scripts: <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 for solaris 10+ if this did not exist in /etc/inittab then we use 3

<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 for solaris 10+ if this did not exist in /etc/inittab then we use 3

AIX /opt/simpana/Base/simpana

/usr/bin/simpana

/usr/bin/cvpkgrm

/usr/bin/cvpkgcheck

/usr/sbin/simpana

/usr/sbin/cvpkgrm

/usr/sbin/cvpkgcheck

/etc/galaxy (only when OSSV Plug-in is installed)

/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

None

Startup Scripts:

/etc/inittab.galaxy.$$ (only when installed using cvpkgcfg)

backup for original /etc/inittab)

/etc/inittab

/etc/rc.galaxy

Macintosh /opt/simpana/Base/simpana

/usr/bin/simpana

/usr/bin/cvpkgrm

/usr/bin/cvpkgcheck

/usr/sbin/simpana

/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

/etc/sysctl.conf (Darwin and FreeBSD when user selected to change IPC)

etc/sysctl.conf.gal.bak (Darwin and FreeBSD only; backup if user selected yes for IPC change OR suggested settings if user selected not to change IPC this time)

/etc/rc (Darwin only when user selected to change IPC)

/etc/rc.bak<n> where <n>=””, 1, 2, …… (backup if user selected yes for IPC change)

Startup Scripts:

/Library/StartupItems/Galaxy/StartupParameters.plist

/Library/StartupItems/Galaxy/Galaxy

MediaAgent

Platforms Folders Created Files Created Other changes
Linux None None Creating and setting up the tape drive device mappings () in / dev / rmt / [xyz]
Solaris None None Creating and setting up the tape drive device mappings () in / dev / rmt / [xyz]
AIX None None Creating and setting up the tape drive device mappings () in / dev / rmt / [xyz]

File Archiver

Platforms Folders Created Files Created Other changes
Linux For each directory monitored we create folder ".cxfs_restore" under the mountpoint root when the drivers start monitoring in FSDM mode. The files being recalled are hardlinked inside this directory for the duration of the recall.

Stub cache Directory : <InstallationDIR>/JobResults/StubCache

Redhat - /lib/modules/”uname –r”/updates/cdr.ko

SUSE -  /lib/modules/”uname –r”/extra/cdr.ko

None
Solaris For each directory monitored we create folder ".cxfs_restore" under the mountpoint root when the drivers start monitoring in FSDM mode. The files being recalled are hardlinked inside this directory for the duration of the recall.

Stub cache Directory : <InstallationDIR>/simpana/StubCache

Sparc - /usr/kernel/drv/sparcv9/cvfsf

X86 - /usr/kernel/drv/amd64/cvfsf

None
AIX Create .cxbf_restore under the mountpoints monitored.

Stub cache Directory : <InstallationDIR>/JobResults/StubCache

/dev/fsdm1

/etc/fsdmd.conf

/usr/lib/drivers/flrdd

None
HP Create .cxbf_restore under the mountpoints monitored.

Stub cache Directory : <InstallationDIR>/JobResults/StubCache

/usr/conf/mod/cvfsf  

Image Level iDataAgent

Platforms Folders Created Files Created Other changes
Linux For SnapShots configured according to the user specified during the setup for the CXBF driver and creates a cache directory in the specified path

/dev/cxbf

/lib/modules/`uname -r/drivers/char/cdr.ko

SUSE - /lib/modules/uname –r/extra/cxbf.ko

If additional file systems are configured for the cxbf driver, set up under / dev / cxbf according to new devices. For each new device is also an additional entry in the fstab created (Linux: / etc / fstab,). The originals of all modified system files are decompressed to the original location as <filename>. Backup stored.

Dynamic Mount FS-Snaps or images via / etc / fstab

/etc/rc.d/rc.sysinit – modify with /etc/init.d/cxbf start

Solaris For SnapShots configured according to the user specified during the setup for the CXBF driver and creates a cache directory in the specified path /r/kernel/drv/cxbf.conf

/usr/kernel/drv/sparcv9/cxbf

/usr/kernel/drv/amd64/cxbf

/dev/cxbf/*

If additional file systems are configured for the cxbf driver, set up under / dev / cxbf according to new devices. For each new device is also an additional entry in the vfstab created (Solaris: / etc / vfstab,). The originals of all modified system files are decompressed to the original location as <filename>. Backup stored.

Dynamic Mount FS-Snaps or images via / etc / fstab
AIX None /usr/lib/drivers/cxbf

/usr/lib/methods/cfgcxbf

/usr/lib/methods/ucfgcxbf

/usr/lib/methods/undcfbf

PdDv changed

CuDv changed

/dev/cxbf/cxbfctrl

/dev/cxbf/cxbflog_*

/dev/cxbf/cxbf*/*

/etc/rc.cxbf

/etc/rc modified

/sbin/cvsnap

/sbin/cxbf-bootscript1.rc

/etc/filesystems modified when configuring devices

None

Informix iDataAgent

Platforms Folders Created Files Created Other changes
Solaris None Create file under $INFORMIXDR/GalaxyRelinkInfo Create a link to ibsad001_64.so under /usr/lib/sparcv9

DB2 iDataAgent

Platforms Folders Created Files Created Other changes
Linux None None Symbolic links to Galaxy libraries under $DB2_HOME/sqllib/lib directory
Solaris None None Symbolic links to Galaxy libraries under $DB2_HOME/sqllib/lib directory
AIX None None Symbolic links to Galaxy libraries under $DB2_HOME/sqllib/lib directory

Continuous Data Replicator

Platforms Folders Created Files Created Other changes
Linux /dev/cvcdr

/dev/cvfsdm

Cdr Cache will be created under user-defined directory:

<userdefined DIR>/cvcdrcache

Redhat - /lib/modules/”uname –r”/updates/cdr.ko

SUSE - /lib/modules/”uname –r”/extra/cdr.ko

None
Solaris Cdr Cache will be created under user-defined directory:

userdefined DIR>/cvcdrcache

/usr/kernel/drv/cvfsf.conf

/dev/cvfsf/*

/usr/kernel/drv/sparcv9/cvfsf

/usr/kernel/drv/amd64/cvfsf

None
AIX /dev/flr0

 

Cdr Cache will be created under user-defined directory:

<userdefined DIR>/cvcdrcache

PdDv changed

CuDv changed

/usr/lib/drivers/flrdd

/etc/flrdd.conf

/etc/fsfdd.conf

/usr/lib/methods/cfgflr

/usr/lib/methods/ucfgflr

/usr/lib/methods/undflr

None
HP Cdr Cache will be created under user-defined directory:

<userdefined DIR>/cvcdrcache

/usr/conf/mod/cvfsf  

Sybase iDataAgent

Platforms Folders Created Files Created Other changes
Linux None None Create a link to libSybGalaxy.so under $SYBASELIBPATH
Solaris None None Create a link to libSybGalaxy.so under $SYBASELIBPATH
AIX None None Create a link to libSybGalaxy.so under $SYBASELIBPATH

How to use the physical node interface for backups on virtual machines in a cluster?

In a clustered environment, you can use the physical node interface for backups on Virtual Machines using one of the following ways:

Executing the Qscript

After installing any software on a cluster, execute the SetClientProp.sql qscript on the client computer using the below steps:

1. From the command prompt on the client computer, navigate to the <software installation path>\Base> folder.  
2. Run the qscript using the qoperation execscript command. qoperation execscript -sn SetClientProp.sql -si c=clientName -si UsePhysicalnode=y

Using a Data Interface Pair

Once you install the software in a cluster, configure a Data Interface Pair between the Virtual Machine and the MediaAgent. When configuring  the Data Interface Pair, make sure to use physical node's Network Interface Card (NIC) IP address for the Virtual Machine. See Configuring Data Interface Pair for detailed information.

Configuring Veritas Clusters

For Veritas Clusters on Unix platforms, once you install the software on the physical node, use the following steps to install the Virtual Machines and also enable physical node interface for the backups on Virtual Machines. See Install the Unix Agents - Veritas Cluster Environment for detailed information on installing on Veritas Cluster.

1. Navigate to <software installation path>\Base> folder on the physical node.  
2. Run the cv_vcs_discover command with the given parameters.

./cv_vcs_discover -r <resource type name> -x <xml input file name> -p <DVD mount point> [-l <exclusion list file name> ] [-g] [-o] [-i] [-u <user name>] [s <password>] [-v]

where,

-r <resource type name> The service groups that contain a resource of this type will be configured. This resource type name depends upon the agent.

For example:

For Unix File System iDataAgent it is "Mount"

For Oracle iDataAgent it is "Oracle"

-x <xml input file name> This is the xml input file created during regular install. This xml file will be used as the basis to create VM specific silent install XML file.
  • If you have custom package xml file, then use complete path where the default.xml file is located. For example /opt/UnixCustomPackage/pkg/rec/default.xml
  • If you have user-defined xml file then specify complete location of the file. For example, /user_defined_dir/silent_answer.xml
-p <DVD mount point> Install media mount point. silent_install command from this media will be used to configure selected Service Groups.
-l <exclusion list file name> [Optional] Text File containing one VCS Service Group per line that should not be configured.
-g [Optional] This parameter is used to avoid creating client group with same name as VCS service group.
-o [Optional] Use this option only if you have same names for service groups in different cluster groups.
-i [Optional] This parameter enables to use the physical node interface for backups on Virtual Machines.
-u [Optional] This parameter is used to provide the CommCell admin user name. It is used along with the -i parameter.
-s [Optional] This parameter is used to provide the CommCell admin user password. It is used along with the -i parameter.
-v [Optional] This parameter is used to include the verbose logs.
./cv_vcs_discover -r Mount -x /cvbuild2/GALAXY/10.0/Build61/DVD3/silent_answer_example.xml -p /mounted/DVD3/ [-g] [-o] [-i] [-u user1] [-s 3e660ede7db8c] [-v]

Can we install software binaries TO an NFS drive?

Yes. All the Unix-based backup and recovery agents can be installed to an NFS drive.

Installing software binaries TO an NFS drive

If you want to install the software binaries to an NFS-mounted file system or an NFS drive, make sure the following prerequisites are met before proceeding with the installation:

If the directory is not exported, use the following steps to export the directory so that the required client has access to it. If you have a Solaris NFS server, follow the steps described in Exporting Directory on a Solaris NFS Server.

Navigate to etc/exports file on the NFS Server and open it in vi editor. A sample file is shown below.

/serv/nfs1/ client1.mydomain.com(rw,no_root_squash,no_all_squash,sync)

client2.mydomain.com(ro,no_root_squash,no_all_squash,sync)

client3.mydomain.com(ro,no_root_squash)

Navigate to /etc/dfs/ location, open the dfstab file in vi editor,

  1. Update the corresponding directory entry in the etc/exports file.

    /serv/nfs1/ client1.mydomain.com(rw,no_root_squash,no_all_squash,sync,insecure)

    client2.mydomain.com(ro,no_root_squash,no_all_squash,sync)

    client3.mydomain.com(ro,no_root_squash)

    where

    serv/nfs1 is the directory on the NFS server that you want to export.

    client1 is the client computer that will have read/write access to serv/nfs1 directory.

    client2 and client3 are the client computers that have read only access to this drive.

     add the following entry:

    share -F nfs -o rw,root=myclient1:mycompany.com /mynfsdr1

    Where:

    myclient1:mycompany.com is the fully qualified domain name of the client computer.

    mynfsdr1 is the name of the shared drive.

  2. Save the file and restart the NFS server.

Exporting Directory on a Solaris NFS Server

Use the following steps to export a directory on a Solaris NFS server:

  1. Navigate to /etc/dfs/ location and open the dfstab file in vi editor.
  2. Add the following entry in dfstab file:

    share -F nfs -o rw,root=myclient1.mycompany.com: /mysharednfsd

    Where:

    myclient1.mycompany.com is the fully qualified domain name of the client computer.

    mysharednfsd is the name of the shared drive.

  3. Save the file and restart the NFS server.