Troubleshooting Restore - Macintosh File System iDataAgent

Restore

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 perform an out-of-place restore.	Ensure that the file name along with the directory path to which the file is restored does not exceed 1024 characters.
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 -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. #uname –r 2.6.32.59-17.art.i686.PAE .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> E.g.: #chpax –ps /opt/calypso/iDataAgent/ifind

ACLs are not 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.

Restore operation fails when special characters are included in the data

Restore operations on files containing [], /or the \ characters fail when restored without browsing. In order to restore these files using a browse operation, the directory that contains these files, or a higher level directory, must be selected in the browse window as content to restore.

For example, if there is a file named file[]name in the /opt directory, then you must select the /opt directory or any directory that contains /opt for restore. If you select only the file, the restore will fail.

Browse and Restore Failure

When you browse the latest data on the default subclient after a full backup, the browse window will incorrectly display the top-level directories of any user-defined subclients that have not been backed up. Attempts to restore data from user-defined subclients that have not been backed up will fail.
If you do a framed browse (i.e., select both a begin and end date/time for the browse) and select the entire resulting data tree for restore by selecting the top-most (or root) node, an erroneous error message is displayed stating that the restore operation failed. Restores under these circumstances are successful regardless of the error message. To avoid this error message, select the data to be restored from the next-to-highest level in the tree.

Recovering Data Associated with Deleted Clients and Storage Policies

The following procedure describes the steps involved in recovering 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 which 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 which 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 will be used temporarily to build a CommServe.

Recovering Deleted Data

Locate the latest Disaster Recovery Backup which contains the information on the entity (Storage Policy, Client, Agent, Backup Set or Instance) that you are trying to restore.
- You can 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.
On a standby computer, install the CommServe software. For more information on installing the CommServe, see CommServe Deployment.
Restore the CommServe database using the CommServe Disaster Recovery Tool from the Disaster Recovery Backup described in Step 1. (See Restore a Disaster Recovery Backup for step-by-step instructions.)
Verify and ensure that the Bull Calypso Client Event Manager Bull Calypso 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 will bring back the entity in the CommServe database and the entity will now be visible in the CommCell Browser. (Press F5 to refresh the CommCell Browser if the entity is not displayed after a successful merge.)
If you have additional data that was backed up after the disaster recovery backup and before the deletion of the entity, use the procedure described in Import Metadata from a Tape or Optical Media to obtain the necessary information.
You can now browse and restore the data from the appropriate entity.

As a precaution, mark media (tape and optical media) associated with the source CommCell as READ ONLY before performing a data recovery operation in the destination CommCell.

Macintosh OS System Restore Failed Due to Kernel Panic

During disaster recovery, when rebuilding the operating system, the computer does not restart correctly due to kernel panic. In such cases, refer Apple documentation to recover the system from kernel panic and resume the disaster recovery operation.