Data Domain: How To Collect a Data Domain Support Bundle

A. DETERMINING WHETHER WEB-BASED ACCESS IS ENABLED:

1. Log in to the DD CLI
2. Check whether HTTP and/or HTTPS access are enabled using the following command:

   # adminaccess show

   For example:

   # adminaccess show
   Service   Enabled   Allowed Hosts
   -------   -------   -------------
   ...
   http      no        -            <=== HTTP access over port 80 (by default)
   https     no        -            <=== HTTPS access over port 443 (by default)
   -------   -------   -------------

ENABLING WEB-BASED ACCESS:

If web-based access is disabled (as shown above), enable it as follows:

1. Log in to the DD CLI
2. Enable HTTP and/or HTTPS access:

   # adminaccess enable [ http | https ]

   For example, to enable https access to a DD:

   # adminaccess enable https
   HTTPS Access:    enabled

Note: connections to the DD from a web browser may not work for up to 5 minutes after enabling web-based access. This is because it takes some time for the embedded web server to start up.

B. DETERMINING WHETHER FTP OR FTPS ACCESS IS ENABLED:

1. Log in to the DD CLI
2. Check whether FTP or FTPS access are enabled using the following command:

   # adminaccess show

   For example:

   # adminaccess show
   Service   Enabled   Allowed Hosts
   -------   -------   -------------
   ...
   ftp       no        -            <=== FTP access
   ftps      no        -            <=== FTPS access
   ...
   -------   -------   -------------

ENABLING FTP OR FTPS ACCESS:

1. Log in to the DD CLI
2. Enable FTP or FTPS access to the DD using the following command:

   # adminaccess enable [ ftp | ftps ]

3. Note: FTP and FTPS access are mutually exclusive - only one of these can be enabled at a time. As a result, it may be necessary to disable an existing service before enabling the required service. For example:

   # adminaccess enable ftps
   Enabling FTPS Failed: Disable FTP before enabling FTPS
   # adminaccess disable ftp
   FTP Access:    disabled
   # adminaccess enable ftps
   FTPS Access:    enabled

4. To allow FTP/S access to the DD for a specific client system, use the following command with the required service and IP address of the client:

   # adminaccess ftp add 9.8.7.6
   Security access lists updated
   The ftp access list is:
       9.8.7.6

   Alternatively, to allow FTP/S access to the DD by all clients, use the following command (again, specify the required service as necessary):

   # adminaccess ftp add *
   Security access lists updated
   The ftp access list is:
       *

C. DETERMINING WHETHER NFS ACCESS IS ENABLED:

1. Log in to the DD CLI
2. Check whether NFS access is enabled using the following command:

   # nfs enable

   For example:

   # nfs enable
   NFS server is already enabled.

ENABLING NFS ACCESS TO /ddvar/support:

1. Verify whether an NFS export already exists for the /ddvar/support directory. If it does, verify whether the corresponding NFS client has access. In this case, the directory is not exported:

   # nfs show clients
   Path                Client   Options
   -----------------   ------   ------------------------------------------------------
   /data/col1/backup   *        (sec=sys,rw,no_root_squash,no_all_squash,secure,nolog)
   -----------------   ------   ------------------------------------------------------

2. If no NFS export for /ddvar/support exists or the NFS client does not have access to an existing export, create a new export.
3. To allow access to the /ddvar/support export for a specific client system, use the following command:

   # nfs add /ddvar/support 9.8.7.6
   NFS export for "/ddvar/support" added.

4. Alternatively, use the following command to allow access to the /ddvar/support export from all client systems:

   # nfs add /ddvar/support *
   NFS export for "/ddvar/support" added.

   Specific client systems can be identified using hostname or IP address; however, hostnames must be resolvable by the DD if used.

D. DETERMINING WHETHER CIFS ACCESS IS ENABLED:

1. Log in to the DD CLI
2. Check whether CIFS access is enabled using the following command:

   # cifs enable

   For example:

   # cifs enable
   The filesystem is enabled and running.
   Starting CIFS access...

ENABLING CIFS ACCESS TO /ddvar:

1. Verify whether a CIFS share already exists for the /ddvar directory. If it does, verify whether the corresponding CIFS client has access. In this case, the directory is not shared:

   # cifs share show
   Shares information for: all shares
   --------------- share backup ---------------
   path: /data/col1/backup
   clients: *
   enabled: yes
   Shares displayed: 1

2. If no CIFS share exists for the /ddvar directory, create a new share. Specify the explicit hostname or IP address of the required CIFS clients:

   # cifs share create ddvar path /ddvar clients 9.8.7.6
   Share "ddvar" has been created.

   Alternatively, give access to all CIFS clients:

   # cifs share create ddvar path /ddvar clients *
   Share "ddvar" has been created.

3. If an existing CIFS share exists for the /ddvar directory but the required CIFS client is not listed against the share, add the client:

   # cifs share modify ddvar clients 9.8.7.6
   Share "ddvar" is modified for new connections.

E. DETERMINING WHETHER SCP ACCESS IS ENABLED:

1. Log in to the DD CLI
2. Check whether SCP access is enabled using the following command:

   # adminaccess show

   For example:

   # adminaccess show
   Service   Enabled   Allowed Hosts
   -------   -------   -------------
   ssh       yes       -            
   scp       yes       (same as ssh)
   ...

ENABLING SCP ACCESS:

1. To enable SCP access to a DD, use the following command:

   # adminaccess enable scp

   For example:

   # adminaccess enable scp
   SCP Access:    enabled

F. CREATING SUPPORT BUNDLES WITH NON-DEFAULT CONTENTS:

You can create SUBs with non-default contents. For example:

1. To create a SUB with default contents plus additional files:

   # support bundle create default with-files [file name]

2. To create a SUB without default contents and only include specific files:

   # support bundle create files-only [file name]

3. To create a SUB containing only the contents of the /ddr/var/traces directory:

   # support bundle create traces-only

• If a file name is specified:
  • The path must start with /ddvar rather than /ddr/var.
  • The file must exist in one of the following directories: /ddvar/certificates, /ddvar/core, /ddvar/log, /ddvar/releases, or /ddvar/traces.
  • The resulting archive file name contains the string "support-files" rather than "support-bundle".
• If the traces-only option is specified, the resulting archive name contains the string 'support-traces' rather than 'support-bundle'.
• The resulting archive file appears in the output of "support bundle list", but may NOT appear in the 'Support Bundles' section of the GUI. In these cases, the file cannot be collected from the GUI.