There are three options available to recover from a failed data transfer:

1. Re-run the [date]-[date].XferData script with the '-r' flag.
2. Use the UDR Collection Manager (UCM) command line utility to recover the Manager run that failed to transfer the data.
3. Transfer the data using the best1collect run command from the command line
4. Manually transfer the data using an external tool such as ftp or scp

Option A: Re-run the [date]-[date].XferData script

This recovery path can be triggered via the Gateway Manager UI by selecting Gateway Manger -> Status /Recover Runs -> Select run -> Click the 'Recover' button.  Selecting that option in the UI will then trigger the XferData script execution described below.

The [date]-[date].XferData script supports a new '-r' recovery option to allow it to automatically recover failed data transfer and initiate data processing.

If the *.XferData script is being kept in the Manager Output Directory (not automatically deleted) after the Manager run completes it can be re-run to re-transfer and then execute re-processing for the Manager run.

For example, to re-try data transfer for the Manager run in the '/bmc/perform/manager/run1/Mar-16-2008.15.16' Manager Output Directory for the April 24th 00:00 - 23:59 Manager run:
The [date]-[date].XferData script will initiate udrCollectMgr processes to handle the data transfer and then once the transfer phase is complete it will initiate the [date]-[date].ProcessDay script to re-process the data.

 

Option B: Use the UCM Command Line Utility

To recover failed data transfer using the UCM command line executable:
For example:
The -r parameter restarts Manager runs that have been aborted, or runs that are already complete. Specify this option along with the required run date and the script file name (VCMDS), which identifies the run.

The '-r' recovery parameter can be replaced with a '-R' forced recovery option which is able to recover an additional set of failed data transfers where the TSCO Gateway Server never sent the data collection request but the data is available on the TSCO Agent side due to the 'Days in Advance' data collection.

When run after the run has finished (so in transfer recovery mode) the command will only attempt to re-transfer data from the nodes defined as part of the specified Manager run that failed to transfer data previously. It will not attempt to re-transfer data from nodes that already successfully sent their data to the console.
 

Option C: Transfer the data using the best1collect

Transfer the data using the best1collect command from the command line. However, this method requires that you know a good deal about exactly where the data resides on the remote computer.

The following is an example of the command:
 
$BEST1_HOME; Generally specified as /usr/adm/BEST1_V.V.VV, where V.V.VV is the product version number

-n NODENAME; The hostname of the agent node

-B BEST1_COLLECT_HOME; Generally specified as /usr/adm/best1_V.V.VV.

-D MANAGING_NODE_DATA_REPO; The data repository on the managing node (where you want the data to end up)

-b DATE_TIME_STAMP_DIR; The date/time stamp directory where the data resides on the agent node. This is in the format Mmm-dd-yyyy.hh.mm - for Manager run started data collection, hh.mm will typically be '00.00' (midnight).

-p PULL_DELETE; The type of data transfer to use.  The PULL_DELETE is the best option and is the standard transfer mechanism used by the nightly Manager runs.

The following is an example of the command that would transfer the data from a UNIX agent computer that would transfer data from the default agent repository directory on the agent computer topgun to the /best1data directory on the managing node:
 
For a Windows agent computer, use the same parameters but specify Windows paths instead, as shown in the following example:
 
For Windows, make sure that if there are spaces in the paths that the command line parameter is enclosed in double-quotes (as in the example above). Also ensure that the directory separators are specified as two backslashes, not a single backslash.
 

Option D: Manually transfer the data

Transfer the UDR data using an external transfer tool if necessary.
 

The TSCO Gateway Server Manager on the Windows managing console assumes that the data is already present on the managing node when executing a Manager run that uses the Use existing data option. Therefore, you need to use another method to get the data to the managing node before running Manager again to reprocess the data.
 

Option A: Use the 'Recover' option in the TSCO Gateway Manager UI GUI

A recovery request for a Manager run can be triggered under Administration -> Gateway Manager -> Gateway Operations -> Status/Recover Runs.  Selecting the desired Manager run(s) to recover and clicking the 'Recover' button will attempt to recover data transfer and data processing for the run.

Option B: Using the UCM Command Line Utility

To recover failed data transfer using the UCM command line executable:
The -r parameter restarts Manager runs that have been aborted, or runs that are already complete. Specify this option along with the required run date and the script file name (VCMDS), which identifies the run.

When run after the run has finished (so in transfer recovery mode) the command will only attempt to re-transfer data from the nodes defined as part of the specified Manager run that failed to transfer data previously. It will not attempt to re-transfer data from nodes that already successfully sent their data to the console.
 

Option C: Using the Collect Data Wizard

The Collect Data Wizard includes functionality to transfer this type of data in this type of situation.
 
Start the Collect Data Wizard by choosing Start => Programs => BMC PATROL => Perform => Collect Data.
 
The Collect Data Wizard window is displayed. Click the Start a collect process on a
Console or Agent computer option (the icon shows a green traffic light).
 
Click Next on the Welcome to the Collect Wizard window.
 
The Select the Collection Mode window is displayed. Click Standard Mode, and then click Next.
 
The Select Computers window is displayed. On this window there are two options.

a. Select the Agent computer or network address radio button, and in the edit box, type in the list of computers from which to transfer data, separated by commas.

b. Alternately, if the list of computers is long, create a text file (using a text editor such as Notepad) that contains a list of all the computers from which you want to transfer data. This text file should contain a list of computers, with one computer name on each line in the text file. Once the text file is created, Choose the Select a file that contains the computers to collect radio button and then either type the full path to the file into its edit box, or click the Browse button to browse to the file.
 

---

NOTE: The agent nodes must have the same remote data repository path for the text file method to work.

---

 
In the Repositories and Actions window, fill in the following three edit boxes:

a. Top box: The directory on the managing computer where the data should be transferred.
b. Middle box: Where does the data reside on the agent computer (it needs to be the same for all computers).
c. Bottom box, choose the data transfer type. The options are Pull data or Push data.
 
Click the Next button.
 
The Data Collection Frequency window is displayed. Enter how frequently you want the data collected, summarized, and saved. Click Next.
 
The Collection Schedule window is displayed. In the Begin and End by Date and Time section, enter the date and time that corresponds to the date/time stamp directory of the data on the remote computer. Manager passes this directory from the managing computer so it will be the same on all remote computers (if Manager initially collected the data).
 
Click the Next button.
 
The Completing the Collect wizard window is displayed. This lists the command that is going to be run. Click Finish here to get back to the main collect data window.
 
The messages generated by the transfer will appear in the messages window. Check each computer and make sure that the message Request was completed successfully on node: [nodename] was generated. For each computer that failed to transfer the data, it may be necessary to try a different transfer type (such as PULL instead of PUSH) or to manually transfer the data.

General Manager coordinates and controls Manager runs by integrating multiple BMC Performance Assurance consoles on UNIX and Windows hosts under a single umbrella.

General Manager consists of the General Manager Client component and the General Manager Server component. The server and client communicate via web services.

The General Manager Server resides on the same node as the Manager console. The General Manager Client user interface is integrated with the BMC Capacity Optimization Console as a separate section under the Administration tab, and with BMC Performance Perceiver as a separate tab in the Perceiver interface

Do one of the following:

• If you are accessing General Manager from BMC Capacity Optimization, on the Administration tab, expand GENERAL MANAGER.
• If you are accessing General Manager from BMC Performance Perceiver, click the General Manager tab.

Click Recover Runs option.

Select a Manager console or [All] option.

Under Recover Manager Runs, click the Summary tab.

To filter the list of runs, select a Console, Manager Run, or, in the Manager Run Filter, type a string, and then click the filter icon.
You can include wildcard expressions (for example: test*, t*, *st, test?1, and so on) in the Manager Run Filter, which is case-sensitive.

To sort the list of runs, click one of the following table column headers: Run Name, Run Date, Status, Console, or Last Recovered.

To view detailed status, and completion information on recovered runs, click the Detail tab.

Select one or more runs.

Click Recover.