| Archive | Recover |
The following section provides information on some of the troubleshooting scenarios related to Windows file archiving:
The space quota for an object such as volume, directory or user is set lower than the amount already in use. Doing so may cause improper results for data protection or recovery operations.
Do not set a quota for an object such as a volume, directory, or user that is lower than the amount that has already been used.
Archived files will not get stubbed when the job results path is a UNC path. Therefore, it is recommended to save job results in a local file such as the default path as opposed to specifying the UNC path.
Some file servers do not support stubbed files with "offline" attributes leading to the stub not being recognized during the restore operation. So the stubs that do not get recognized are skipped thereby leading to a loss in the data being restored. The CheckForStub registry key is perform additional checks to validate it as a stub.
.When file recall is initiated for a PDF file on a DFS volume, the Adobe reader cannot open the file and displays the following error:
There was an error opening this document. Access denied.
This issue occurs because the application opens by default in protected mode, with the introduction of Adobe reader 10.x.x.
To resolve this issue, de-select the Enable Protected Mode at startup option in the Preferences dialog box.
When you double click a stub to perform a recall, the recall operation fails with the message Access Denied. You will receive an error in the CommCell Console which says Recall abort due to exported media. Afile-Data=[number].
This happens because the Archiver Services perform a pre-check to see if the required media is available in the library.
Import the required media into the library. We recommend you to have a latest backup cycle available always so that the stubs can be recalled from that cycle. Backup operations performed on disk libraries enable faster recalls as they are not bound by the read and seek rules binding to the tape drives.
If you have PGP Disk Encryption tool used by SAP installed on your computer, you might find that the stubs (archived data) are recalled automatically without triggering a recall operation.
This is because certain permissions might be enabled in the PGP Options dialog box.
To resolve this issue, make sure that the Overlay PGP icon on secured files and folders and Protect individual files options are disabled in the PGP Options (Netware tab) dialog box.
The following procedure describes the steps involved in recovering data associated with the following entities:
This procedure can be performed when the following are available:
See License Administration for more details.
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.
| When you start the Command Line Interface to capture data, use the name of the standby CommServe in the -commcell argument. |
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.)
|
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. |
During recalls the File Archiver recall popup message is not being sent even though the Enable Recall Popup Message has been selected from the system tray settings of the notification enabler.
When file recall operations are initiated from Vista, Windows 7, Windows 2008 or Windows 2008 R2 operating systems, the server may lock up. This issue occurs because the Server Message Block (SMB) worker thread that handles SMB 2.x requests are not available thereby not responding to file share requests.
When two computers communicate with each other through the SMB share, the connection is controlled by the highest version of SMB supported by both operating systems. The recall process works correctly if the computer on which the file share is hosted and the computer from which recall process is triggered have either Windows 2003, 2003 R2 or XP operating systems. Computers with Windows 2003, 2003 R2 or XP operating systems recalls the file correctly because they use SMB 1.0.
You will observe the following error in the logs.
[CVD ] slSendMsg: send() failed. socket=10612 SndSize =
8192 Error = [1][10054][An existing connection was forcibly closed by the remote
host.]
[NET_WRITER ] Critical Network Error:: rc = 10054 ABORTING pipeline
On the Data Archiver Agent machines with SMB 2.x Windows operating system starting with the release of Vista, make sure that the following settings are made.
Prior to any editing of the registry, make sure that you follow Microsoft's standards for registry backup, editing and restore operations available in Microsoft KB article 322756.
HKEY_LOCAL_MACHINE\CurrentControlSet\Services\LanmanServer\Parameters\MaxThreadsPerQueue
Change the DWORD Decimal Value to 1024.
HKEY_LOCAL_MACHINE\CurrentControlSet\Services\LanmanServer\Parameters\MaxMpxCt
HKEY_LOCAL_MACHINE\CurrentControlSet\Services\LanmanServer\Parameters\MaxCmds
Change the DWORD Decimal Value to 125 for each of them.
For more information, refer to Change registry settings to maximize server service performance.
Use the following registry keys to modify the default behavior of the Migration Archiver Agent:
| Topic | Registry Key(s) | Description | |||
| Access and Modified Times | GXHSMSERVICEKEEPTIMES | Migration archiving and stub recovery operations change the access and modified time on files. An enhancement that allows the recovery administrator to preserve the original file access time and modified time during migration archiving and stub recovery. See Registry Keys (GXHSMSERVICEKEEPTIMES and GXHSMSTUBKEEPTIMES) for more information on enabling this feature for all instance types except Celerra. | |||
| GXHSMSERVICEKEEPTIMES | Stub pruning looks at the modified time of the file to determine eligibility for pruning stubs. If you use the GXHSMSERVICEKEEPTIMES and GXHSMSTUBKEEPTIMES registry keys, the modified time will be preserved. This means that when you run a migration with these registry keys enabled, the preserved modified time will always be older than the time that the file was stubbed. As such, if you use the Prune stub only after n days option, you should ensure that the modified time is not being preserved. Therefore, be sure to disable the GXHSMSERVICEKEEPTIMES and GXHSMSTUBKEEPTIMES registry keys (which are enabled by default) when you use this option. | ||||
| Stub Recalls | GXHSMSERVICEMINRECALLFREESPACE | If you would like to ensure that there is sufficient free space on a volume before initiating stub recalls, you can use the GXHSMSERVICEMINRECALLFREESPACE registry key to enable this feature. | |||
| nRETRY_RECALL_TIMEOUT | Two registry keys are available for administering the timing of recalls. The nRETRY_RECALL_TIMEOUT registry key allows you to set the time of duration for a recall attempt. Once this time expires, the recall attempt will stop. The nRETRY_RECALL_DELAY key indicates the delay time for a recall attempt. Once this time expires, the recall attempt will resume. These keys work hand-in-hand with each other, and they are especially useful if the CommServe goes down. | ||||
| EVMGRC_REMOTE_PORT_OVERRIDE | For File Archiver for Windows, you can override the stub file port number by using the EVMGRC_REMOTE_PORT_OVERRIDE registry key. Use this key when the port number changes. Keep in mind that using this key defeats the benefit of being able to recall data using different port numbers for multiple Agents. When the key does not exist, the File Share Archiver client uses the stub content to determine port number. For 7.0 stubs, refer to the EVMGRC_REMOTE_PORT registry key. | ||||
| GXHSM_DISABLE_ARCHIVE_FILE_RECALL_AND_RESTORE | This registry key disables stub recalls at the driver level and allows
service to send custom popup messages. This key should be used with a service
level key
GXHSM_DISABLE_ARCHIVE_FILE_RECALL_AND_RESTORE_MESSAGE.
It is created in computers which has File Share Archiver Client installed. |
||||
| DMReadMaxMountRetryVal | By default no failure message is displayed when a recall job waits for the media to be imported. This key allows for setting a finite number of mount retries during restore. | ||||
| Stub Recall History | nDMRSendFileStatus |
The stub recall history is viewable at the client and agent levels in the Commcell Console and is associated with the first instance, which was created in the Migration Archiver agent. Stub recall history can be turned on by creating nDMRSendFileStatus key and setting the value to 1.
|
|||
| GXHSM_ENABLE_INPLACE_RESTORE | By default the recalls occur on a staged path, and then the recalled files are copied to the target path. This is a user defined key which allows the user to direct the recalls in place rather than the staging path. | ||||
| GXHSM_ALTERNATE_GXHSMCACHE_PATH | By default at the time of stub recall the stubs are stored in a stub cache path, which is generally in the root volume path. The Maximum supported path length for it is 1000. Any path longer than this specified length will get proportionately reduced if this key is specified. This user defined key allows the user to specify the path for all recalls. | ||||
| Persistent Pipelines | nDMRSIDLETIMEOUT |
To change the default value of how long the persistent pipeline of this Archiver Agent will stay open during idle periods of a recovery operation, you can use the nDMRSIDLETIMEOUT registry key to accomplish this task. The pipeline stays persistent for 24 hours by default.
|
|||
| nDMRMaxRestoreThreads | If you would like to spawn multiple persistent pipelines when stub recall requests are from different archive file IDs, the nDMRMaxRestoreThreads registry key can be used to accomplish this task. | ||||
| Recall Messages and Pop-Ups | GXHSM_MAGNETIC_MSG_NAME | You can use the GXHSM_MAGNETIC_MSG_NAME key to replace the default "MAGNETIC" key word for a recall message with a message of your choice. | |||
| GXHSMNOPOPUP | To enable the display of a pop-up message for stub recoveries indicating
that the recovery operation has completed and showing the location of the
file that was recovered, change the
GXHSMNOPOPUP
registry key value to N. To disable
the pop-up, create the
GXHSMNOPOPUP
registry key and set the value to Y.
This is enabled by default on the local client for the File Archiver for Windows Agent when configured for NAS archiving.
|
||||
| GXHSM_DISABLE_ARCHIVE_FILE_RECALL_AND_RESTORE_MESSAGE | This is a service level key used in conjunction with the driver level
key
GXHSM_DISABLE_ARCHIVE_FILE_RECALL_AND_RESTORE on computers where
File Share Archiver Cleint is installed. The key allows for customizing
the popup message when
GXHSM_DISABLE_ARCHIVE_FILE_RECALL_AND_RESTORE is used to disallow
the recall. The key can be used with the following to get desirable popup messages:
|
||||
| GXHSM_MAX_DISPLAY_TIME_FOR_DISABLERECALLRESTORE_MESSAGE | The key is used in conjunction with GXHSM_DISABLE_ARCHIVE_FILE_RECALL_AND_RESTORE_MESSAGE as it allows the user to set a desired popup message display time. | ||||
| Log Files | GXHSMSTUBLOGFAILFILESTRUNCATE | For File Archiver for Windows, you can determine whether the existing log file associated with your job should be truncated or appended to. See GXHSMSTUBLOGFAILFILESTRUNCATE in Registry Keys for more information. | |||
| Sparse Files | GXHSMSTUBCREATESPARSE | If you have enabled the archive option to create stub files that are not sparse files (using the GXHSMSTUBCREATESPARSE registry key), you must use WordPad — not Notepad — to open the resulting text files. | |||
| GXHSM_NAS_REMOVESPARSE_ON_RECALL | In case of archiving FPolicy and Network File Share data, use GXHSM_NAS_REMOVESPARSE_ON_RECALL to remove the sparse attribute upon recall if the stub has been created as a sparse file. |