Troubleshooting Restore - FreeBSD File System
The following sections provide information on some of the troubleshooting scenarios related to restore:
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.
SolutionEnsure 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.
SolutionYou 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.
Restore fails when trying to restore a running executable file.
SolutionEnsure that you are not including any running executable files in the restore operation.
In a disaster recovery scenario, use the following procedure to recover data associated with the following entities:
- Deleted storage policy
- Deleted client, agent, backup set or instance
Before You Begin
This procedure can be performed when the following are available:
- You have a Disaster Recovery Backup that contains information on the entity that you are trying to restore. For example, if you wish to recover a storage policy (and the data associated with the storage policy) that was accidentally deleted, you must have a copy of the disaster recovery backup that was performed before deleting the storage policy.
- Media containing the data you wish to recover is available and not overwritten.
- If a CommCell Migration license was available in the CommServe when the disaster recovery backup was performed, no additional licenses are required. If not, obtain the following licenses:
- IP Address Change license
- CommCell Migration license
See License Administration for more details.
- A standby computer, which is used temporarily to build a CommServe.
Recovering Deleted Data
- Locate the latest Disaster Recovery Backup that contains the information on the entity (storage policy, client, agent, backup set or instance) you are trying to restore.
- Check the Phase 1 destination for the DR Set or use Restore by Jobs for CommServe DR Data to restore the data.
- If the job was pruned and you know the media containing the Disaster Recovery Backup, you can move the media in the Overwrite Protect Media Pool. See Accessing Aged Data for more information. You can then restore the appropriate DR Set associated with the job as described in Restore by Jobs for CommServe DR Data.
- If the job is pruned and you do not know the media containing the Disaster Recovery Backup, you can do one of the following:
- If you regularly run and have copies of the Data on Media and Aging Forecast report, you can check them to see if the appropriate media is available.
- If you do not have an appropriate report, and know the media that contains the DR Backup, catalog the media using Media Explorer. Once the cataloging process is completed, details of the data available in the media are displayed.
- On a standby computer, install the CommServe software. For more information on installing the CommServe, see Install the CommServe.
- Restore the CommServe database using the CommServe Disaster Recovery Tool from the Disaster Recovery Backup described in Step 1. (See CommServe Disaster Recovery Tool for step-by-step instructions.)
- Verify and ensure that the NetApp Client Event Manager NetApp Communications Service (EvMgrS) is running.
- If you did not have a CommCell Migration license available in the CommServe when the disaster recovery backup was performed, apply the IP Address Change license and the CommCell Migration license on the standby CommServe. See Activate Licenses for step-by-step instructions.
- Export the data associated with the affected clients from the standby CommServe as described in Export Data from the Source CommCell.
When you start the Command Line Interface to capture data, use the name of the standby CommServe in the -commcell argument.
- Import the exported data to the main CommServe as described in Import Data on the Destination CommCell.
This brings back the entity in the CommServe database and the entity is visible in the CommCell Browser. (Press F5 to refresh the CommCell Browser if the entity is not displayed after a successful merge.)
- You can now browse and restore the data from the appropriate entity.
As a precaution, mark media (tape media) associated with the source CommCell as READ ONLY before performing a data recovery operation in the destination CommCell.
Error while loading shared libraries.
SolutionOn 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
#./ifind -getmnt -all
./ifind: error while loading shared libraries: libCvOnTap.so: cannot enable executable stack as shared object requires: Permission denied
As a workaround, do the following steps:
- Check if ASL (Atomic Secured Linux) is configured on client.
.art indicates that ASL is configured on the client.
- 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
- Run the following command.
chpax –ps ../iDataAgent/<process/service>
#chpax –ps /opt/snapprotect/iDataAgent/ifind
Command line operation fails with error.
SolutionCommand Line Operation fails with the following error:
Fatal error 'Spinlock called when not threaded.' at line 87 in file /usr/src/lib/libpthread/thread/thr_spinlock.c (errno = 0)
This error occurs if the command line operation does not have thread library support. Use the following steps to provide thread library support for the command line operation.
- Create the /etc/libmap.conf file on the client.
- Add the following entries in the libmap.conf file: