Saving independent ASPs

You can save independent ASPs (also known as independent disk pools in iSeries™ Navigator) separately or you can save them as part of a full system save (GO SAVE: Option 21), or when you save all user data (GO SAVE: Option 23). In either case, make the independent ASPs available before you perform the save. Refer to the following scenarios and choose the option that best fits your needs.

Saving the current ASP group

Perform the following commands to save the current independent ASP group (the primary ASP and any associated secondary ASPs).

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 prior to the save. You may also want to consider Backup, Recovery and Media Services.

SETASPGRP ASPGRP(primary-ASP-name)
SAVSECDTA ASPDEV(*CURASPGRP)
SAVLIB LIB(*ALLUSR) ASPDEV(*CURASPGRP)
Unmount any QDEFAULT user-defined file systems in the current independent ASP group
SAV OBJ(('/dev/*')) UPDHST(*YES) ASPDEV(*CURASPGRP)
Mount any QDEFAULT user-defined file systems that were unmounted in an earlier step

Saving UDFS ASP

Perform the following commands to save an available UDFS ASP.

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

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

If you make independent ASPs available, they will be included in an Option 21 save.¹ 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 perform a SETASPGRP command; Option 21 will perform the necessary commands to save the independent ASPs that you have made available. In addition to the commands listed in Save your whole system with GO SAVE: Option 21, the system performs 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 performs the following command for each available user-defined file system (UDFS) ASP.

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

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

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

If you make independent ASPs available, they will be included in an Option 23 save.¹ 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 perform a SETASPGRP command; Option 23 will perform the necessary commands to save the independent ASPs that you have made available. In addition to the commands listed in Save user data with GO SAVE: Option 23, the system performs 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 performs the following command for each available user-defined file system (UDFS) ASP.

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

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

1: If your system includes independent ASPs that are geographically mirrored, it is recommended that you eliminate them from this GO SAVE option by making them unavailable. You should 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 required. Synchronization can be a very lengthy process.

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

When you choose to perform 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.