Determination of the NAS backup location
When IBM Storage Protect uses NDMP to protect NAS file servers, the IBM Storage Protect server controls operations. During this time, the NAS file server transfers the data, either to an attached library or directly to the IBM Storage Protect server.
You can also use a backup-archive client to back up a NAS file server by mounting the NAS file system on the client computer and then backing up as usual. You can use either a Network File System (NFS) mount or a Common Internet File System (CIFS) map.
For a description of the backup-and-restore methods, see Table 1.
Tip: You can use a single method or a combination of methods in your individual storage environment.
| Property | NDMP: File server to server | NDMP: File server to attached library | Backup-archive client to server |
|---|---|---|---|
| Network data traffic | All backup data goes across the LAN from the NAS file server to the server. | The server controls operations remotely, but the NAS device moves the data locally. | All backup data goes across the LAN from the NAS device to the client and then to the server. |
| File server processing during backup | Less file server processing is required, compared to the backup-archive client method, because the backup does not use file access protocols such as NFS and CIFS. | Less file server processing is required, compared to the backup-archive client method, because the backup does not use file access protocols such as NFS and CIFS. | File backup operations require more server processing resources for file access protocols such as NFS and CIFS. |
| Distance between devices | The IBM Storage Protect server must be within SCSI or Fibre Channel range of the tape library. | The IBM Storage Protect server can be distant from the NAS file server and the tape library. | The IBM Storage Protect server must be within SCSI or Fibre Channel range of the tape library. |
| Firewall considerations | More stringent than filer-to-attached-library because communications can be initiated by either the IBM Storage Protect server or the NAS file server. | Less stringent than filer-to-server because communications can be initiated only by the IBM Storage Protect server. | Client passwords and data are encrypted. |
| Security considerations | Data is sent decrypted from a NAS file server to an IBM Storage Protect server. | This method must be used in a trusted environment because port numbers are not secure. | Port number configuration allows for secure administrative sessions within a private network. |
| Load on the IBM Storage Protect server | Higher CPU workload is required to manage all back-end data processes (for example, migration). | CPU workload is reduced because migration and reclamation are not supported. | Higher CPU workload is required to manage all back-end data processes. |
| Backup of primary storage pools to copy storage pools | Data can be backed up only to copy storage pools that have the NATIVE data format. | Data can be backed up only to copy storage pools that have the same NDMP data format (NETAPPDUMP, CELERRADUMP, or NDMPDUMP). | Data can be backed up only to copy storage pools that have the NATIVE data format. |
| Restore of primary storage pools and volumes from copy storage pools | Data can be restored only to storage pools and volumes that have the NATIVE data format. | Data can be restored only to storage pools and volumes that have the same NDMP format. | Data can be restored only to storage pools and volumes that have the NATIVE data format. |
| Moving NDMP data from storage pool volumes | Data can be moved to another storage pool only if it has a NATIVE data format. | Data can be moved to another storage pool only if it has the same NDMP data format. | Data can be moved to another storage pool only if it has a NATIVE data format. |
| Migration from one primary storage pool to another | Supported | Not supported | Supported |
| Reclamation of a storage pool | Supported | Not supported | Supported |
| Simultaneous-write operations during backups | Not supported | Not supported | Supported |
| Export and import operations | Not supported | Not supported | Supported |
| Backup set generation | Not supported | Not supported | Supported |
| Cyclic Redundancy Checking (CRC) when data is moved by using IBM Storage Protect processes | Supported | Not supported | Supported |
| Validation by using IBM Storage Protect audit commands | Supported | Not supported | Supported |
| Disaster recovery manager | Supported | Supported | Supported |