Skip to main content
Sign Out

Welcome to Dell

My Account
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.
Sign In Create an Account Dell Financial Services Premier Sign In Partner Program Sign In
Contact Us

Your Dell.com Carts

Dell NetWorker 19.9 Administration Guide

PDF

Troubleshooting policies

This section provides information about issues related to the configuration and management of policy resources.

Remote system error - Cannot assign requested address

This message appears intermittently when a single workflow has more 2000 save sets and the backup and clone operations occur concurrently. In this scenario the number RPC connections that the configuration requires exceeds the available number of RPC ports. To resolve this issue, split the workflow with a large number of save sets into multiple workflows, up to a maximum of 2000 save sets in each workflow and stagger the workgroup start times by 30 minutes.

Unable to start because the Group for this workflow is empty

This message appears when you use the Start Individual Client option to start actions for specific clients in the Server backup workflow. NetWorker does not support the Start Individual Client option for the Server backup workflow. To resolve this issue, start all actions for all the clients in the workflow.

Running actions from the command line

NetWorker 19.9 and later provide you with the ability to run actions from a command line for debugging purposes only.

To debug an action, use the action binary, for example, nsrworkflow, nsrpolicy, savegrp, or nsrnassnap_index with the following options:

  • --policy_name—Specifies the name of the policy that contains the action. This option is required.
  • --workflow_name—Specifies the name of the workflow that contains the action. This option is not required when a policy only contains one workflow.
  • --action_name—Specifies the name of the action. This option is not required when a workflow only contains one action.
  • -Z action_type—Required for the savegrp binary. Specifies the action type of the action. Supported values are backup:traditional, backup:snapshot and probe. If you do not specify this option, savegrp defaults to the backup:traditional action type.
  • --driven_by_action—Specifies the source of the input work items for an action, for example a list of backup save set. Sources include one of the following options:
    • jobid—Specifies the jobid of the driving action.
    • stdin—Instructs the action binary to read the items from stdin.
    • file:absolute_path_to_file—Instructs the action binary to read the items from a file.
    NOTE:This option is only required when the action is not the first action in a workflow.

Debugging an action by using stdin

In the following example, a backup of the save set /baz failed for host foo.com. The name of traditional backup action for the save set is backup. A workflow named traditional1, which is in a policy named Backup contains the action.

To troubleshoot the backup action, perform the following steps:

  1. Connect to the NetWorker Server with an administrator account.
  2. From a command prompt, start the nsradmin program:

    nsradmin

  3. From the nsradmin prompt, define the attributes that nsradmin will display for a resource, for example, the resource name and the save set value, by typing the following command:

    show name; save set

  4. Enable nsradmin to display the hidden resource ID attribute for the NetWorker resources:

    option resource id

  5. Display a list of client resources, by typing the following command:

    p type: nsr client

  6. From the output, record the resource identifier that appears for the client resource that contains the save set associated with the action that you want to debug. For example, output similar to the following appears:

    name:foo.com;
    saveset:/baz;
    resourceidentifier:70.0.77.10.0.0.0.0.208.36.124.87.128.222.109.22(1);

    name:foo.com;
    saveset:/foo,/bar;
    resourceidentifier:93.0.89.114.0.0.0.0.55.25.124.87.128.222.109.22;(9)

    NOTE:The resource ID does not include the brackets or the number contained within the brackets.
  7. Use the savegrp command and the resource ID to start the action:

    echo resource_ID|savegrp --policy_name=policy_name --
    workflow_name=workflow_name --action_name=action_name -v --
    driven_by_action=stdin

    For example:

    echo 93.0.89.114.0.0.0.0.55.25.124.87.128.222.109.22|savegrp --policy_name=Backup --
    workflow_name=traditional1 --action_name=backup -v --driven_by_action=stdin

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\