Managing Inventory Items

Unless an item is added to the list of inventory items for a scope, it will not be available for use in the scope. By default, all items are not added to newly created scopes; only the Default Scope has all items added.

Tip

If an item is added to more than one scope, it will appear more than once in the list of inventory items — once for each scope. To view the relevant scope memberships, use the search fields displayed on the item tabs.

To modify the list of items available for a scope:

  1. Switch to the Administration page.
  2. Navigate to Inventory.
  3. Switch to the necessary tab.
  4. Select an item that you want to add to the scope:
  1. Click Add scope.
  2. In the Add to Scope window, select the scope from the drop-down list, and click Apply.

 

Tip

You can simultaneously edit the list of inventory items available for multiple scopes. To do that, select check boxes next to the required items and click Edit Scope. After you select a scope from the drop-down list in the Edit Scope window, the changes will be applied to all the selected item at the same time.

 

Managing Inventory Items

After you add an item to a scope, Plan Authors will be able to use this item when building recovery plans for the scope, particularly:

  • Use template jobs to protect machines included in replica and restore plans for the scope.
  • Use credentials when configuring the Windows Credentials and SQL Credentials parameters for plan steps for the scope.
  • Use recovery locations for restore and cloud plans in the scope, and also when running failback.

For more information on creating and editing recovery plans, see Working with Replica Plans, Working with CDP Replica Plans, Working with Restore Plans and Working with Cloud Plans.

Note

By design, the list of available recovery locations will always display VMware and Microsoft Azure recovery locations only. For storage recovery locations, there is no need to allow access — Orchestrator automatically identifies the locations to be used when running storage plans. For more information on the way Orchestrator analyzes storage recovery locations, see Storage Failover.

Page updated 4/15/2024

Page content applies to build 7.1.0.278