Administrator Guide

Table Of Contents
DNS might not be configured.
NTP might not be configured.
Workaround When configuring the FluidFS cluster to connect to an Active Directory domain:
1. Ensure that you use a FQDN and not the NetBIOS name of the domain or IP address of the
domain controller.
2. Ensure that the user has permissions to add systems to the domain.
3. Use the correct password.
4. Configure DNS.
5. The FluidFS cluster and Active Directory server must use a common source of time. Configure
NTP and verify the system time is in sync with the domain controller time.
6. If multiple NAS appliances are used, ensure that you set different NetBIOS names. The system
defaults to SMB Storage as the name.
Troubleshoot Backup Issues
This section contains probable causes of and solutions to common NDMP problems.
Troubleshooting Snapshots
Description Snapshot creation and deletion fails.
Cause Probable causes might be:
There are many client I/O requests waiting to be serviced, including a request to remove a large
directory.
There are many snapshot creation/deletion requests being currently processed.
Another snapshot request for the NAS volume is currently being executed.
The total number of snapshots reached the system limit.
The wrong IP address was specified in the backup job.
Workaround
For a manual request failure, retry taking or deleting the snapshot after a minute or two.
If the request originated from the snapshot scheduler, wait another cycle or two. If the failure
persists, try taking or deleting the snapshot manually on the same NAS volume.
If the system is under a heavy workload, wait until the workload decreases and reissue the
snapshot request.
Check the snapshot schedule. A very dense snapshot schedule has a negative impact on
the overall performance of the system. The accumulated snapshot rate must not exceed 20
snapshots per hour per system.
Check the total number of snapshots in the system. If the number is in the thousands, delete a
few snapshots and retry.
Ensure the client VIP is specified in the backup job.
Check if a recent delete of a big volume (TB) was executed. If so, wait for some time and retry
the activity.
Troubleshooting an NDMP Internal Error
Description
Backup or restore fails with an internal error.
Cause NDMP internal errors are indicators of a file system not being accessible or a NAS volume not being
available.
Workaround If the backup application cannot connect to a FluidFS cluster:
1. Verify that NDMP is enabled.
2. Verify that the backup application IP address is configured in NDMP.
If the backup appliance can connect to a FluidFS cluster, but cannot log in:
1. Use the default user name backup_user configured in Storage Manager for the NDMP client
while setting up the NDMP backup/restore in your backup application.
480 FluidFS Administration