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

Identifying connection lost to device

When a device loose connection with NetWorker server, the Device Connectivity Check (DCC) framework discovers device unavailability. Upon discovery of the device unavailability, NetWorker server notifies the user through NMC console, NetWorker logs, or by email.

The various scenarios where the devices become unavailable are as follows:
  • Data Domain hosting the devices becomes unavailable.
  • Data Domain administrator accidently deletes the MTree having the devices.
  • The mount point hosting the AFTD devices becomes offline.
  • The AFTD device folder is deleted accidently from the operating system file system.
NOTE:Starting with NetWorker 19.3, DCC framework is enhanced to verify the existence and availability of DD, DDCT, and AFTD devices. In addition, post NetWorker 19.7, DCC framework is enhanced to involve SmartScale devices.
The NetWorker DCC framework provides the following capabilities:
  • The DCC framework periodically checks the device connectivity.
  • The DCC feature is enabled by default. It is visible in the diagnostic mode under NMC console.
  • The NetWorker storage node reports DCC result to NetWorker server.
  • NetWorker server parses the report and moves the device either to normal or suspected state and informs the broker about the status of the device.
  • If the suspect status of the device has changed, NetWorker server reports this event to customer, through NMC console, NetWorker logs or through email.
The supported NetWorker device types are:
  • DD and DDCT device.
  • AFTD device.
  • SS device.
The limitations are as follows:
  • DCC does not check the existence of savesets residing in a volume. However, it checks the existence of VolHdr file created inside the volume to determine the device availability and accessibility.
  • In case of DDCT devices , NetWorker metadata is still stored in the cloud tier volume and the actual saveset file might have moved to the cloud storage. DCC checks the availability and accessibility of only the DDCT device and not the cloud unit configured which may or may not be available.

Starting NetWorker 19.7, DCC framework is enhanced to raise a single alert when the device is unavailable, instead of raising an alert at every configured DCC interval. The raised alert is cleared, and the message Media Event Cleared is logged in daemon and NMC log pane when the device is back online. This prevents the issue of overloading NMC or NWUI with DCC suspect alerts. Daemon log continues to log the alerts for the configured DCC time interval.

Starting Networker 19.8, DCC framework is enhanced to raise an alert on NMC and NWUI when the DD username and password are changed.

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: <>()\