Skip to main content
  • 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.

Dell NetWorker 19.9 Administration Guide

Differences between FTDs, AFTDs, and DD Boost devices

The following table lists the functional differences between traditional file type devices (FTDs), AFTDs, and DD Boost devices.

The NetWorker Data Domain Boost Integration Guide provides details on DD Boost devices.

Table 1. Differences between disk devices
Function or operation File type device (FTD) Advanced file type device (AFTD) DD Boost device
Create a device
  • Device Property Window

    Select the media type: file.

    UNIX/Linux storage node:
    local or NFS only.

    Windows storage node: local
    path only. CIFS is not supported for
    FTDs.

  • Device Configuration Wizard
  • Device Property Window

    Select media type: adv_file.

    UNIX/Linux storage node: local
    or NFS only.

    Windows storage node: local or
    CIFS using UNC path or using NFS:
    Remote user, Password.

  • Device Configuration Wizard
  • Device Property Window

    Select media type:
    Data Domain

Storage location
  • Specified in the Name attribute.
  • Specified in the Device Access Information attribute.
  • Specified in the Device Access Information attribute.
Concurrent save set operations

Concurrent AFTD recovery operation limitations provides
more information about performing
concurrent recovery operations from an
AFTD.

  • No.
  • Yes.
  • Yes.
Reclaiming or recovering space
NOTE: For Read-only disk type volumes, nsrim does not reclaim/recover the space.
  • The nsrim program removes both aborted and expired save sets, once every 24 hours, by the Expiration action, at the time defined in the Server backup workflow (if you have set volume recycle to Auto).
.
  • Aborted save sets immediately removed.
  • The nsrim program removes expired save sets from the media database once every 24 hours, by the Expiration action, at the time defined in the Server backup workflow (if you have set volume recycle to Auto). NetWorker removes space on the AFTD as specified in the Reclaim Space Interval of the staging policy.
  • Reclaims only data that is unique, not required by other existing backups.
  • NetWorker does not immediately remove aborted save sets, but marks them recyclable. A restarted save can be deduplicated. Otherwise, NetWorker removes the aborted save set during the next Recover Space operation.
Volume default capacity for devices
  • If the file type device was used before setting the Volume Default Capacity attribute, the data for that file type device must be staged or cloned to another device.
  • Does not apply.
  • Does not apply.
AFTD Percentage Capacity
  • Does not apply.
  • A setting determines the capacity that NetWorker software should stop writing to an AFTD: spans from 1% to 100%.
  • Does not apply.
When file system or volume is full
  • Waiting message is displayed if no writable volume available or until volume becomes available.
  • Volume marked full and is no longer available for backups until the volume becomes appendable.
  • Message is displayed stating file system requires more space.
  • The nsrim program invoked to reclaim space for expired save set on AFTD.
  • Notification is sent by email stating device is full.
  • Device waits until space become available. The volume is never marked as full.
  • Backup to a DD Boost device fails and stops when full.
Save set continuation
  • Yes.
  • No. Save sets that start on an AFTD must be completed on the same device.
  • No. Save sets that start on a DD Boost device must be completed on the same device.
Data format in device
  • Open Tape Format (OTF).
  • Save stream (uasm) format (uses less space).
  • Deduplicated
Client Direct backup: 
the storage node manages the devices for the NetWorker clients, but the clients send their backup data directly to the devices via network access, bypassing the storage node.
  • No.
  • Yes.

    Clients send their own backup data
    directly to the storage devices. If Client
    Direct backup is not available, a traditional
    storage node backup is performed.

    NetWorker archive operations are
    not supported for Client Direct backup.

  • Yes.

    Clients use DD Boost
    DSP functionality to deduplicate
    their own backup data before
    sending it directly to the storage
    devices. If Client Direct backup is not
    available, a traditional storage
    node backup is performed.

    NetWorker archive
    operations are not supported for
    Client Direct backup.

NOTE:Starting NetWorker 19.9, you can configure up to 160 DD boost devices per storage node.

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