Collocatebyfilespec
Use the collocatebyfilespec option to specify whether the Tivoli® Storage Manager client uses only one server session to send objects generated from one file specification.
Setting the collocatebyfilespec option to yes attempts to eliminate interspersing of files from different file specifications, by limiting the client to one server session per file specification. Therefore, if you store the data to tape, files for each file specification are stored together on one tape (unless another tape is required for more capacity).
Considerations:
- Use the collocatebyfilespec option only if the storage pool is going directly to tape. If you use this option going to a disk storage pool, you could affect some load balancing, and therefore, performance.
Supported Clients
This option is valid for all UNIX and Linux clients. The server can also define this option.
This option is valid for all Windows clients. The server can also define this option.
Options File
Place this option in the client user-options file (dsm.opt).
Place this option in the client options file (dsm.opt).
Parameters
- Yes
- Specifies that you want the Tivoli Storage Manager client to use only one server session to send objects generated from one file specification. Therefore, if you store the data to tape, files for each file specification are stored together on one tape, unless another tape is required for more capacity. Restore performance can increase as a result.
- No
- Specifies that the Tivoli Storage Manager client
can (depending on the execution dynamics and on the setting of the resourceutilization option
of 3 or higher), use more than one server session to send the files
from one file specification. This is the default.
Backup performance might increase as a result. If the files are backed up to tape, files are stored on multiple tapes. Generally, the files specified in the file specification are still contiguous.
Examples
- Options file:
- collocatebyfilespec yes
- Command line:
- -collocatebyfilespec=yes
This option is valid only on the initial command line. It is not valid in interactive mode.