Central and decentralized administration

Central and decentralized administration and the respective advantages and disadvantages are presented on the following pages.

Central administration

Decentralized administration

All node S0s are administered centrally:
1 directory file for backup
1 directory file for archival

Each node S0 is administered separately:
1 directory file for backup per node S0
1 directory file for archival per node S0

+	Only 1 HSMS statement is required for all node S0s during backup

-	1 HSMS statement per node S0 is required for backup

-	Uses large directory files.

+	Uses smaller directory files, improving runtime performance and reducing access conflicts.

-	If a node S0 is moved to another BS2000 server, the backup is no longer available without additional intervention (COPY-NODE-SAVE-FILE).

+	If a node S0 is moved to another BS2000 server, the backup is still available. The directory file must be copied.

+	ARCHIVE automatically synchronizes the backup or archival of all node S0s.

-	/SECURE-RESOURCE-ALLOCATION synchronizes the tasks of different node S0s on the output device. Differences in node S0 sizes can cost time.

+	Optimum utilization of save volumes with small node S0s (1 volume per save run for multiple node S0s)

-	Uneconomical utilization of save volumes with small node S0s (1 volume per save run per node S0) However, utilization of the volumes can be enhanced through continuation during the subsequent backups/migrations.