Symptoms

A backup or clone operation is performed through NetWorker.The following error messages are observed. Waiting for number> writable volumes to backup pool 'pool>' family> on host>No matching devices; check storage nodes, devices, or pools. These messages can be found through: NetWorker Management Console (NMC): Monitoring > Policies > Policy_Name >orkflow_Name >ction_Name > Show Details > Failed Session > Show Messages > Get Full Log. For "Waiting for writable volume" issues, this message also appears in the Alerts window of the NMC. The NetWorker server's daemon.raw also reports these messages. How to use nsr_render_log: NetWorker: How to use nsr_render_log How to enable real time .raw rendering: NetWorker: How to automatically render daemon.raw to daemon.log in real time

Cause

The above alerts are caused when NetWorker cannot find any suitable volume on which to write a backup. They can be generated for one or more of the following reasons mentioned under Resolution section.

Resolution

Action Definitions The Policy > Workflow > Action configuration and media pools must be properly configured: Destination Pool The Destination Pool property of the action defines which pool the data is sent. A pool is a collection of volumes to which NetWorker writes data. The pool attribute is set in the NMC. Select a workflow within a policy and review the relevant action. The backup is sent to the pool which is defined in the 'Destination Pool' action parameter. NOTE: If 'Client Override Behavior' on the Action is set to 'Client Can Override', then the 'Pool' value from the client is considered as the first priority. The pool to which the data is being sent must contain an available volume. You can see the list of volumes and their pools in, for example, Media > Disk Volumes. For specific example, consult this article: NetWorker: The client can override settings that do not apply to the schedule if the level is set to skip at action level Destination Storage Node The Destination Storage Node attribute of the workflow action must be set correctly. This field specifies the hostname of the storage node that has the devices which receive the backup data. By default, the NetWorker server appears. To select a remote storage node, click the edit button to the right of the field and select each required storage node. NOTE: If 'Client Override Behavior' on the Action is set to 'Client Can Override', then the storage node defined in the client parameter called 'Storage Nodes' in the client 'Globals (2 of 2) is used as a priority. View > Diagnostic Mode must be enabled in the NMC to see the Storage Nodes field. By default the NetWorker server's storage node (nsrserverhost) is defined. Ensure that there are available (mounted) volumes in the devices on the storage node which you have selected. You can check this in the NMC, in Devices > Devices. NOTE: If the 'Volume Name' column is empty, the device is not mounted. The 'Volume Pool' column is not shown by default, but can be added. For specific examples, consult this article: NetWorker: Backup Fails with Error: 'Save: Error no matching devices: Check storage nodes, devices, or pools' Client Properties If the NetWorker client resource has 'Data Domain backup' selected, there must be an available Data Domain volume in the selected pool. NOTE: View > Diagnostic Mode must be enabled in the NMC to see the Deduplication Data Domain options. Bootstrap Backups The NetWorker server's bootstrap save set can only be saved to a volume mounted using the NetWorker server's embedded storage node (by design). That is, the NetWorker server's bootstrap save sets cannot be saved to remote devices (rd=storagenode_name:device_name). For specific example, consult this article: KB 39833 NMC Server DB Backup Failing With "no matching devices for save of client" Pool Properties The Device specified in the Devices attribute of the Destination Pool must have the correct path. The selected devices should be mounted under Devices > Devices: NOTE: If the 'Volume Name' column is empty, the device is not mounted. The 'Volume Pool' column is not shown by default, but can be added. Name Resolution Name resolutions observed with the NetWorker server, Storage Nodes, Clients, or Devices should also be verified. For specific examples, consult these articles: 000041288, Troubleshooting DNS and Name Resolution Issues 000004384, NetWorker: How to Use NetWorker nsradmin -C Resource Validation Cloning Considerations Cloning must be configured correctly. NetWorker requires two or more storage devices to perform a clone operation. One device contains the volume with the original data and one device contains the volume to which NetWorker writes the clone data. Source and destination must be two different volumes. Each clone volume can only contain one instance of a cloned save set. Cloning can be set up in several different ways in NetWorker. One common way is to setup a NetWorker group of type 'Save Set Query'. Use the policy action wizard for the group's workflow to define the 'Destination Storage Node' and 'Destination Pool.' This decides where exactly this clone data is written to. Ensure NetWorker volumes in this pool using this storage node don't already have a copy of this save set instance. Alternatively, Add a clone action after a backup action to clone save sets backed up by the previous action. The policy action wizard is used to define where to write the clone data. If no destination storage node is defined, clone data is written to the storage nodes in the 'Clone storage nodes' field or the NetWorker server storage node. This value is defined in the properties of the storage node resource 'Configuration' tab. Cloned data originating from this storage node is directed to the first storage node which has an enabled device and a functional media daemon (nsrmmd). Tape Devices Tape Device issues are causing NetWorker not to be able to write to the target device. AFTD Devices The NetWorker Advanced File Type Device (AFTD) is not working as expected:

Support Cases