Product

Platform

Operating system

Error

Symptoms

If you try to restore a job to a location other than where it was archived from, Archiver will fail to retrieve the job with the error message: "Error processing file \\servername\share_name\jobfolder\filename. The system cound not find the environment option that was entered" "Error processing file \\servername\share_name\jobfolder\filename. The network name cannot be found."

Cause

Solution

For Prinergy 1.1 and 2.0. You can use the PChangeJobShare stored procedure to change the machine name and share name of a particular job or all files located in the database. Permenant fix, a new feature to rename job will come out.

Note:

1. If using the -j option, you can change the machine name and/or share name of all the files within the job folder of a particualar job. However, if any files outsides the job folder fail to retrieve, then you need to change the entire file locations on the name server and share.

2. There must be a valid machine name and share_name on the primary server to run the PChangeJobShare command.

3. You must shut down Prinergy to run PChangeJobShare.exe.

To retrieve a job to a different location other than where it was archived from, see the following commands:

Purpose: Utility (PChangeJobShare.exe) to change file locations and jacket home node within the database. Changing file locations within the database is required to allow jobs to be moved from one share to another. (The corresponding files must be moved manually, the metadata records are updated by this utility.)

PChangeJobShare.exe runs in six modes, as described below:

1. Modify all file locations within a named jobs root folder

e.g. PChangeJobShare.exe LORAX AraxiVolume_LORAX_E -j myJob

In this mode, -j specifies the job name (case insensitive.) All file locations under the jobs root folder are updated to the new server and share. Assume 'myJob' exists under server = ATHENA, SHARE = AraxiVolume_Athena_A and path = Jobs\myJob (the jobs home folder is \\Athena\AraxiVolume_Athena_A\Jobs\myJob) the example command given above would update all file locations that matched the pattern \\Athena\AraxiVolume_Athena_A\Jobs\myJob\* to \\LORAX\AraxiVolume_LORAX_E\Jobs\myJob\*

2. Modify all file locations on the named server and share

PChangeJobShare.exe LORAX AraxiVolume_LORAX_E -h PEQUOD -s araxiVolume_LORAX_C

In this mode, all file locations on server = PEQUOD and Share = AraxiVolume_LORAX_C will get updated to Server and Share LORAX, AraxiVolume_LORAX_E respectively.

3. Recovery mode completes a previously initiated operation

PChangeJobShare.exe -r

4. System startup mode, is used by araxi when it starts up to ensure all partially run instances of ChangeJobShare.exe are completed.

PChangeJobShare.exe -c

5. Modify the jacket daemon's host node given the jacketName and the target server.

e.g PChangeJobShare.exe -z JOB1 -n LORAX

In this mode, -z specifies the job name (case insensitive.) The home node of this job is updated to the target server.

6. Modify the jacket daemon's host node given the source server and the target server.

e.g PChangeJobShare.exe -n LORAX -o OBELIX

In this mode, -n specifies the target server and -o specifies the source server. All jobs having home nodes of OBELIX are updated to LORAX.

Restrictions:

1. If a jobs root folder is to be moved then the destination share must be a well known share and the destination server must be an araxi node. A jobs root folder can be moved explicitly thorough the -j option, or implicitly by using the -h -s options, and specifying a share that contains at least one jobs home folder. This check is not done if the destination server cannot be found. This allows for cases where a machine is being renamed, or where the change of meta data is being done at a different locations.

2. Job folders cannot be partially moved. This means if any job has a root folder above a source share, the move is not allowed.

3. Only one instance of this utility may run at any given time.

4. Araxi must be shut down before running this utility.

5. This utility can only be run from the primary node.

Usage Notes: This utility will IRREVERSIBLY modify the database. When moving files from a source location to a target location, the following steps should be followed:

1. Shut down araxi.

2. Export the database. Use the oracle8 EXP80 utility. Exp80 user/password@dbAlias

3. Move the files in the file system. Ideally the location the files will be moved to will not exist; this will avoid any potential file system conflicts. In the case where the target file location does exist, then the following steps are recommended:

a) Backup up the target location to tape or disk.

b) Copy the source files to the target location and resolve any conflicts if they occur. If conflicts cannot be resolved, then all files in the target location should be deleted, and the backup of the target location should be restored.

4. Use this utility to move the corresponding meta data, capture the output to a file to keep a record of the file locations that have been updated.

Permanent fix:

See also

Keywords

archiver - retrieve

Technical contact(s)

Amy Chan

Submitted by

Date submitted