Each client is given a node name when it is registered with the server. The server views its registered clients as nodes that require services and resources from the server.
Typically, a node is equivalent to a machine as in the case of a backup-archive client installed on a user's computer for filesystem backups. However, multiple nodes can exist on a single machine as in the case of a SQL server machine containing both an application client for SQL database and transaction log backups, and a backup-archive client for filesystem backups.
File spaces are created the first time a client backs up the file system that maps to that file space. The number of file spaces a node has depends on the number of file systems on the client machine. For example, a Windows desktop system may have multiple drives, such as a C: and D: drive. The file spaces can grow as a client stores more data on the server. The file spaces decrease as backup and archive file versions expire and the server reclaims the space. TSM does not allow an administrator to delete a node unless the node's file spaces have been deleted.
For client nodes running OS/2 or DOS, a file space name identifies a logical partition, such as the volume label of a disk drive. For example, a volume with the label XYZ is a different file space from a volume with the label ABC.
For client nodes running AIX or SunOS, a file space name identifies a file system or file space defined by a user with the VIRTUALMOUNTPOINT option. With this option, users can define a virtual mount point for a file system to back up or archive files beginning with a specific directory or subdirectory. For information on the VIRTUALMOUNTPOINT option, refer to the appropriate Using the Backup-Archive Client.