In order to optimize the performance when saving to disk, in the catalog entry the values for primary and secondary allocation should be adjusted to the expected volume of data to be saved. When the values are too small, a correspondingly large number of file extents is created, which can have a negative effect on the access times.
The same holds true for backups to the extended S1 level in an SM environment and to S1-SM pubsets in an SF environment. In these cases values that are too small cause the creation of save files with the subsequent number on volume sets already in use. This can cause problems with subsequent restore or recall requests.
When saving to Net-Storage, the primary allocation is automatically assigned a correspondingly high value.