Saving independent ASPs

You can save independent auxiliary storage pools (ASPs) in IBM Navigator for i separately, as during a full system save (GO SAVE Option 21), or during an all user data save (GO SAVE: Option 23). Independent ASPs are also known as independent disk pools.

In either case, you must make the independent ASPs available before you run the save operation. Refer to the following scenarios and choose the option that best fits your needs.

Scenario: Saving the current ASP group

Run the following commands to save the current independent ASP group (the primary ASP and any associated secondary ASPs).
Note: If you are saving independent ASPs that are geographically mirrored, it is recommended that you save the production copy. Quiesce any applications that affect the data in the independent ASP before the save operation. You might also want to consider Backup, Recovery, and Media Services.
  1. SETASPGRP ASPGRP(primary-ASP-name)
  2. SAVSECDTA ASPDEV(*CURASPGRP)
  3. SAVLIB LIB(*ALLUSR) ASPDEV(*CURASPGRP)
  4. Unmount any QDEFAULT user-defined file systems in the current independent ASP group.
  5. SAV OBJ(('/dev/*')) UPDHST(*YES) ASPDEV(*CURASPGRP)
  6. Mount any QDEFAULT user-defined file systems (UDFSs) that were unmounted in an earlier step.

Scenario: Saving UDFS ASP

Run the following commands to save an available UDFS ASP.

  1. SAVSECDTA ASPDEV(ASP-name)
  2. Unmount any QDEFAULT user-defined file systems in the UDFS ASP that you are saving.
  3. SAV OBJ(('/dev/*')) UPDHST(*YES) ASPDEV(ASP-name)
  4. Mount any QDEFAULT user-defined file systems that were unmounted in an earlier step.

Scenario: Saving independent ASPs as part of a full-system save (Option 21)

If you make independent ASPs available, they are included in an Option 21 save operation.1 Follow the checklist in Use GO SAVE: Option 21, 22, and 23, and note extra requirements if you are operating in a clustered environment. Before you end subsystems and restrict your system, make sure that your current job does not use integrated file system objects in the independent ASP. Also, do not run a SETASPGRP command; Option 21 runs the necessary commands to save the independent ASPs that you made available. In addition to the commands listed in Save your whole system with GO SAVE option 21, the system runs the following commands for each available ASP group during an Option 21 save -

  • SETASPGRP ASPGRP(asp-group-name)
  • SAVLIB LIB(*NONSYS) ASPDEV(*CURASPGRP)
  • SAV OBJ(('/dev/*')) UPDHST(*YES) ASPDEV(*CURASPGRP)
The system then runs the following command for each available user-defined file system (UDFS) ASP:
SAV  OBJ(('/dev/*')) UPDHST(*YES) ASPDEV(udfs-asp-name)

The system also runs a CHKTAP ENDOPT(*UNLOAD) command after the last SAV command it processes.

Saving independent ASPs when you save all user data (Option 23)

If you make independent ASPs available, they are included in an Option 23 save operation.1 Follow the checklist in Use GO SAVE: Option 21, 22, and 23, and note extra requirements if you are operating in a clustered environment. Before you end subsystems and restrict your system, make sure that your current job does not use integrated file system objects in the independent ASP. Also, do not run a SETASPGRP command; Option 23 runs the necessary commands to save the independent ASPs that you made available. In addition to the commands listed in Save user data with GO SAVE Option 23, the system runs the following commands for each available ASP group during an Option 23 save -

  • SETASPGRP ASPGRP(asp-group-name)
  • SAVLIB LIB(*ALLUSR) ASPDEV(*CURASPGRP)
  • SAV OBJ(('/dev/*')) UPDHST(*YES) ASPDEV(*CURASPGRP)

The system then runs the following command for each available user-defined file system (UDFS) ASP:

  • SAV OBJ(('/dev/*')) UPDHST(*YES) ASPDEV(udfs-asp-name)

The system also runs a CHKTAP ENDOPT(*UNLOAD) command after the last SAV command it processes.

1
If your system includes independent ASPs that are geographically mirrored, eliminate them from this GO SAVE option by making them unavailable. Save independent ASPs that are geographically mirrored separately, as described in Save the current ASP group. If the geographically mirrored ASPs remain available during the GO SAVE operation, geographic mirroring is suspended when the system becomes restricted. When you resume mirroring after the save, a complete synchronization is needed. Synchronization can be a lengthy process.

Example of save order for independent ASPs with GO SAVE: Option 21 or 23

When you choose to run a full-system save (Option 21) or to save all user data (Option 23), independent disk pools are saved alphabetically. Secondary ASPs are saved along with their primary.
Save order Independent ASP name Independent ASP type What is saved Command
1 Apples Primary Libraries SAVLIB LIB (*NONSYS or *ALLUSR)
Cantaloupe Secondary
2 Apples Primary User-defined file systems SAV OBJ(('/dev/*'))
Cantaloupe Secondary
3 Bananas UDFS User-defined file systems SAV OBJ(('/dev/*'))