Loading...

FAQ - OpenVMS File System iDataAgent

Table of Contents

Are there any operational requirements for this agent?

When does a non-full backup automatically get converted to a full backup?

Can I back up multiple versions of a file?

Can I run command line backups from the proxy client?

How do I view volumes by their physical disk names instead of logical names when I perform a browse operation on the client computer?

What permissions does the restored data acquire after the restores?

When running cross-platform restores from OpenVMS to UNIX, why is the last character in the file being lost?

Where are the logs from the backup and restore processes stored?

What are the folders or files created and changes done during installation of this agent?

How do the OpenVMS and proxy clients communicate via Commvault processes?

What are the binaries are associated with this agent?

Are there any operational requirements for this agent?

The proxy client independently communicates with the OpenVMS client via TCP/IP to run the jobs and to receive job status for updating the CommServe. You can also use TCPWare 6.0 as a third-party TCP stack. Data is transferred from the OpenVMS client to the proxy client during backups, so ensure that the network connection between the OpenVMS client and the proxy client is on the same network switch and that it scales appropriately.

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:

  • First backup of the subclient.
  • Promote a secondary storage policy copy that is not synchronized with a primary copy (for all the subclients of a storage policy).
  • If you switch from a IntelliSnap backup to a traditional backup or vice versa.
  • CommCell Migration operation.

Can I back up multiple versions of a file?

Commvault software backs up and restores all versions of files on the disk. Each file version is treated as a separate file. To back up a specific file version, you must specify the file version. If no file version is specified, the latest file version is picked up automatically.

Can I run command line backups from the proxy client?

Yes. You can run command line backups from the proxy client by specifying the appropriate OpenVMS client, backup set, and subclient parameter values. For more information on command line operations, see Command Line Interface- Getting Started.

How do I view volumes by their physical disk names instead of logical names when I perform a browse operation on the client computer?

By default, the browse operation on the client computer displays OpenVMS volumes by their logical names. To display the volumes by their physical names instead, edit the CVOV_CONFIG.DAT file that is present in the Commvault directory (for example, DKA0:[SIMPANA]), and add the following entry under the IDA section:

[IDA]
{showDiskNames=1}/

Restart of services is not required.

What permissions does the restored data acquire after the restores?

When performing restore operations (other than in-place restores), the original user and group permissions are preserved.

When running cross-platform restores from OpenVMS to UNIX, why is the last character in the file being lost?

When restoring a stream file with record format set to STREAM_CR, STREAM_LF or STREAM, from OpenVMS to UNIX platform, the last character in the file like CR (carriage return), LF (line feed), and CR/ LF will be stripped out. Therefore, when restoring OpenVMS files that are not in text format, make sure the files are configured not to use any record delimiters.

Where are the logs from the backup and restore processes stored?

On the OpenVMS client, the backup and restore process logs are stored in the .log directory under the software installation folder. For example, if the software installation directory is DKA0:[SIMPANA], logs are stored in the DKA0:[SIMPANA.log] directory. The backup process logs are stored in CLIENTSCAN.log and CLIENTBACKUP.log. The restore process logs are stored in CLIENTRESTORE.log. The logs are automatically pruned.

You can access the logs only with the user account that you provided at the time of OpenVMS client creation.

What are the folders or files created and changes done during installation of this agent?

All Commvault programs, configuration files, and logs are stored under the software installation directory by default. No other system folders or files are added or changed.

Platform

Folders Created

Files Created

Other changes

OpenVMS

<base install folder path>

BIN

jobResults

log

cvov_config.dat

[.BIN]CVOV_STOP.COM - script to stop services on the OpenVMS client

 

Proxy computer( Linux)

/opt/commvault/

/etc/Commvault

/dev/cxbf

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

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

Driver configuration file to /lib/modules/$UTS/kernel/copieddrivers/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>

where sscript = Simpana|HitachiHDS|Calypso|SnapProtect|StorageServices|StorageProtection

/usr/bin/commvault

/usr/bin/cvpkgrm

/usr/bin/cvpkgcheck

/usr/bin/cvpkgchg

/etc/gxsetup_guid

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

How do the OpenVMS and proxy clients communicate via Commvault processes?

When you start a backup or restore job, the proxy client automatically checks the OpenVMS client to make sure that all Commvault binaries are present and up to date, and that the CVOV_LAUNCHD process is running. The CVOV_LAUNCHD process will be restarted if it is not running.

The CVOV_LAUNCHD process always keeps running on the OpenVMS client. The scan, backup, and restore jobs launch the CVOV_SCAN.EXE, CVOV_BACKUP.EXE, and CVOV_RESTORE.EXE binaries respectively via the CVOV_LAUNCHD process.

You can use the CVOV_START.COM and CVOV_STOP.COM processes to manually start and stop the Commvault services.

What are the binaries are associated with this agent?

The following binaries and executables are associated with the OpenVMS agent:

Binary name

Description

CVOV_BACKUP.EXE

Contains the primary backup code that reads the files to transfer.

CVOV_CLPROXY.SL

Code that transfers the file to the proxy client.

CVOV_CVIDASCAN.SL

Library containing code that scans the file system to find the files to transfer.

CVOV_LAUNCH.COM

Command script to launch the backup program with proper libraries.

CVOV_LAUNCHD.EXE

Executable daemon to launch the backup, restore, and scan programs.

CVOV_PKGCRC32.COM

Script to run the PKGCRC32 executable with a list of all the rest of the Commvault components.

CVOV_PKGCRC32.EXE

Matches components against their checksums.

CVOV_QIUTILS.SL

General utility library.

CVOV_RESTORE.EXE

Executable to restore.

CVOV_SCAN.EXE

Executable to scan the file system using code in the CVIDASCAN library.

CVOV_START.COM

Starts the LAUNCHD daemon program, if it is not already running.

CVOV_STOP.COM

Stops the LAUNCHD daemon program, if it is running.

Last modified: 1/12/2018 10:59:33 AM