> CommCell Console > Backup and Restore Agents > Backup Agents > OpenVMS > Troubleshooting

Troubleshooting Restore - OpenVMS File System iDataAgent

The following section provides information on some of the troubleshooting scenarios related to restore:

Restore Failures

Some of the files included in the user-defined subclient are not restored.

You may be performing the restore of user-defined subclient along with the restore of default subclient.

When you are recovering data backed up by the default subclient, you cannot recover the data backed up by a user-defined subclient.

Browse from default subclient displays No Backup at Time error

Ensure that you do not include the root directory (/) as the subclient content.

When performing point-in-time restore from the default subclient, include the data/folders under the root directory as the subclient content.

Restore fails when trying to restore to a Unix FAT32 directory

You may be restoring the full contents of a Unix directory that contains more than 32,767 files to a single Unix FAT32 directory.

The number of entries in a single FAT32 directory cannot exceed 32,767.

Error while loading shared libraries

On Linux clients, the below error appears when we run any process or service: 

 
<process name>: error while loading shared libraries: <lib>.so: cannot enable executable stack as shared object requires: Permission denied

For example,

#./ifind_scan -getmnt -all
 ./ifind_scan: error while loading shared libraries: libCvOnTap.so: cannot enable executable stack as shared object requires: Permission denied

As a workaround, do the following steps:

  1. Check if ASL (Atomic Secured Linux) is configured on client. 

    #uname –r
 2.6.32.59-17.art.i686.PAE

    .art indicates that ASL is configured on the client.

  2. Check for the presence of the below logs in /var/log/messages file. 

    May 24 22:01:08 rhel6 kernel: Aborting core
 May 24 22:01:08 rhel6 kernel: PAX: execution attempt in: <anonymous mapping>, bfc46000-bfc5b000 bffeb000
 May 24 22:01:08 rhel6 kernel: PAX: terminating task: /usr/libexec/paxtest/mprotstack(mprotstack):13201, uid/euid: 0/0, PC: bfc5acf4, SP: bfc5acdc
 May 24 22:01:08 rhel6 kernel: PAX: bytes at PC: c3 1a a3 ae 2b ac 9f ae f4 0f 9f ae 00 00 00 00 f4 0f 9f ae

  3. Run the following command. 

     
    chpax –ps ../iDataAgent/process/service

    E.g.:

    #chpax –ps /opt/commvault/iDataAgent/ifind_scan

Restores from Unix to Windows fails

Restores from Unix to Windows may fail in the following circumstances:

  • If the files contain Unix-specific device files such as block, character, or named pipe.

  • If the Unix files contain the "?" character in their filename.

  • Windows allows 1024 characters for filenames, including the path. A filename, including the path, with more than 1024 (1023 for AIX) characters will not be restored from a Unix computer to a Windows computer.

    Make sure to avoid these while restoring the file system from Unix to Windows.

    Case-Sensitive Filenames Will Not Restore from Unix to Windows:

    Case-sensitive filenames will not restore from Unix to Windows because Windows does not maintain case-sensitive filenames. For example, if you are trying to restore files named "CASE_SENSITIVE" and "case_sensitive" from Unix to Windows, then whichever file is restored last will overwrite the first one that was restored.

ACLs and other extended attributes may not be restored.

Sometimes, when you restore data to a NFS-mounted file system, ACLs and other extended attributes may not be restored.

Restore fails when trying to restore a running executable file.

Ensure that you are not including any running executable files in the restore operation.

Page contents

×

Loading...