- Notes, Cautions, and Warnings
- About This Manual
- Introduction
- FluidFS Models and Platforms
- Software Update Path
- FluidFS File-System Metrics
- Client Network Capabilities
- Customer Environment Management Protocols
- SMB Support
- NFS Support
- FTP Support
- User and Group Quotas
- FluidFS Replication
- VMware and the FluidFS VAAI Plugin
- Antivirus Support
- Space Pre-Allocation
- Backup and Restore – NDMP
- Services and Ports
- Management
- Internationalization
Dell Fluid File System Version 5.0 Support Matrix
Backup and Restore – NDMP
#GUID-15AC1C81-3810-4BA8-B19C-861C3243D4E0__GUID-ED09108B-116E-4D1C-8301-2812006FF787 lists the supported backup and restore applications.
Refer to the application documentation for the minimal revision/service
pack supporting Dell FluidFS systems.
#GUID-15AC1C81-3810-4BA8-B19C-861C3243D4E0__GUID-A32F6F6E-090A-4D65-9EB2-1BAC1FBB9192 lists the supported tape libraries for 2–way NDMP backup
(Fibre Channel connections only).
#GUID-15AC1C81-3810-4BA8-B19C-861C3243D4E0__GUID-77EE5A34-7AE5-4E99-9C3D-009BC9B1EA7E lists the supported range for each of the NDMP characteristics.
| Functionality | Supported Range |
|---|---|
| NDMP version | v2, v3, v4 |
| DMA address type | IPv4 only |
| DMA servers configured | Up to 10 |
| Concurrent NDMP sessions | Up to 10 |
| DMA user-name length | 1–63 bytes (accepts Unicode) |
| DMA password length | 1–32 characters |
| Maximum number of include paths for an NDMP job | 32 |
| Maximum number of exclude paths for an NDMP job | 32 |
- NOTE: Your environment should allow ICMP (ping) traffic between the FluidFS controllers’ private IP addresses (not the access VIPs) and the backup server.
#GUID-15AC1C81-3810-4BA8-B19C-861C3243D4E0__GUID-E3397AA3-2BC0-40EC-87FD-AB4910C724E5 describes the NDMP environmental variables that are supported by FluidFS. Refer to the Data Management Application (DMA) documentation for a listing of the variables supported by DMA. If DMA does not set any of the variables, the NDMP server operates with the default value.
| Variable Name | Description | Default |
|---|---|---|
| TYPE | Specifies the type of backup/restore application. Valid values are
dump and
tar, and are case sensitive.
dump – NDMP server generates inode-based file history. tar – NDMP server generates file-based file history. |
dump |
| FILESYSTEM | Specifies the path to be used for backup. The path must be a directory. | Not applicable |
| LEVEL | Specifies the dump level for the backup operation. Valid values are 0 to 9. | 0 |
| HIST | Specifies how file history is to be generated. The supported values
are
d,
f,
y, and
n.
d specifies that node/dir format file history will be generated. f specifies that file-based file history will be generated. y specifies that the default file history type (which is the node/dir format) will be generated. n specifies that no file history will be generated. |
Y |
| DIRECT | Specifies whether the restore is a Direct Access Retrieval. Valid values are Y and N. | Y |
| UPDATE | Specifies whether the dump level and dump time for a backup operation should be updated on the NDMP server so that subsequent backups can reference the dump level from previous backups. Valid values Y and N. | Y |
| EXCLUDE | Specifies a pattern for file or directory names that are not to be backed up. The pattern is a comma-separated list of file or directory names, up to 32. Each name will be used to match to nodes encountered during backup. A name can contain an asterisk (*)as the wildcard character. The comma (,) or backslash (\ )characters in a name should be escaped with a backslash. | No default |
| RECURSIVE | Specifies whether the restore should be recursive or not. Valid values are Y and N. If this variable is set to N, only the files that are the immediate children of the restore target are restored. | Y |
| RESTORE_OVERWRITE | Specifies whether the restore operation should overwrite existing files with the backup data. Valid values are Y and N. | Y |
| LISTED_INCREMENTAL | Controls behavior similar to the
listed
incremental
option of the tar application. This variable
specifies whether an additional directory listing is added to the
backup stream during incremental backup so that the recovery operation
can handle files and directories deleted between the incremental backups.
During backup, if this variable is set, an additional directory listing is added to the backup data stream. Because of the additional process required, this addition could affect the backup data stream size and performance. During recovery, if this variable is set and if the backup data stream was generated with this variable turned on, the NDMP server handles deleting files and directories that are deleted between incremental backups. Setting this variable requires additional processing time and enlarges the backup data stream size (how much it changes depends on the number of elements in the backup data set). If this feature is not important to the end user, it should not be set. |
N |
| BASE_DATE | Used by TSM for token-based backup, as an alternative
to using the LEVEL environment variable.
When BASE_DATE is set to 0 0, a full backup is performed. After a full backup completes, a token can be retrieved by retrieving the DUMP_DATE environment variable. This token can then be passed in later backups as the value of BASE_DATE. The backup performed in this case is an incremental backup relative to the time when the token was generated. When BASE_DATE is set to -1, token-based backup is disabled. |
-1 |
| DEREF_HARD_LINK | Controls whether hard link files data content are backed up for all instances of the same file. Valid values are Y and N. | N |
Proporcione calificaciones (1 a 5 estrellas).
Proporcione calificaciones (1 a 5 estrellas).
Proporcione calificaciones (1 a 5 estrellas).
Seleccione si el artículo fue útil o no.
Los comentarios no pueden contener estos caracteres especiales: <>"(", ")", "\"