Methods for saving user data - IBM i Version 7.2. Systems management Backing up your system

You can use these link references to learn how you can save user data in your system.

An easy way to save all of your user data is with GO SAVE command, menu option 23.

The following commands enable you to manually save user data:

v Save Security Data (SAVSECDTA) v Save Configuration (SAVCFG) v Save Library (SAVLIB *ALLUSR)

v Save Document Library Object (SAVDLO) v Save Object (SAV)

Related tasks:

“GO SAVE: Option 23 (saving user data)” on page 31

Option 23 saves all user data. This information includes files, records, and other data that your users supply into your system.

Related information:

Save Configuration (SAVCFG) command Save Changed Objects (SAVCHGOBJ) command Save Document Library Object (SAVDLO) command Save Library (SAVLIB) command

Save Object (SAVOBJ) command Save (SAV) command

Methods for saving user libraries:

This information describes common save methods for saving user libraries.

Table 28. User libraries information

Item description When changes occur Contains user data or changes?

IBM-supplied data?

User libraries

User libraries change regularly.

Yes No

Common save method for user libraries Requires restricted state?

SAVLIB *NONSYS Yes

SAVLIB *ALLUSR No

SAVLIB library-name No¹

SAVCHGOBJ No¹

GO SAVE command, menu option 21 Yes

GO SAVE command, menu option 23 No^{1, 2}

1 Important:For procedures where the system does not require a restricted state, you must ensure

that the system can get the locks necessary to save the information. You should put your system in a restricted state whenever you save multiple libraries, documents, or directories, unless you use the save-while-active function.

2 When you use option 23 from the GO SAVE command menu, the default is to place your system in a restricted state. If you choose the prompting option, you can cancel the display that puts your system in a restricted state.

These library objects change when you update licensed programs.

“Saving libraries with the SAVLIB command” on page 50 explains how to save one or more libraries. This information also includes special SAVLIB parameters and how to select libraries on your system.

Related concepts:

“Save-while-active function” on page 106

The save-while-active function allows you to use your system during all or part of the save process, that is, save your system while it is active.

Related tasks:

“GO SAVE: Option 21 (saving the entire system)” on page 29

Option 21 saves everything on your system and allows you to perform the save while you are not there.

“GO SAVE: Option 23 (saving user data)” on page 31

Option 23 saves all user data. This information includes files, records, and other data that your users supply into your system.

Related information:

Save Library (SAVLIB) command

Save Changed Objects (SAVCHGOBJ) command Methods for saving Q libraries that contain user data:

This information describes common save methods for Q libraries that contain data.

Table 29. Q libraries that contain user data information

Item description When changes occur Contains user data or changes?

IBM-supplied data?

Q libraries that contain user data include QGPL, QUSRSYS, QDSNX, and others.

“Special values for the SAVLIB command” on page 51 includes a complete list of Q libraries that contain user data.

These libraries change regularly.

Yes Yes

To save the system directory files, you must end the QSNADS subsystem before saving the QUSRSYS library. You might also need to end the QSYSWRK, QSERVER, and ENDTCPSVR(*MGTC *DIRSRV) subsystems to save the QAO* files.

Common save method for Q libraries that contain user data Requires restricted state?

SAVLIB *NONSYS Yes

SAVLIB *ALLUSR No¹

SAVLIB library-name No¹

SAVCHGOBJ No¹

Common save method for Q libraries that contain user data Requires restricted state?

GO SAVE command, menu option 21 Yes

GO SAVE command, menu option 23 No^{1, 2}

1 Important:For procedures where the system does not require a restricted state, you must ensure that the system can get the locks necessary to save the information. You should put your system in a restricted state whenever you save multiple libraries, documents, or directories, unless you use the save-while-active function.

Related concepts:

“Save-while-active function” on page 106

The save-while-active function allows you to use your system during all or part of the save process, that is, save your system while it is active.

Related tasks:

“GO SAVE: Option 21 (saving the entire system)” on page 29

Option 21 saves everything on your system and allows you to perform the save while you are not there.

“GO SAVE: Option 23 (saving user data)” on page 31

Option 23 saves all user data. This information includes files, records, and other data that your users supply into your system.

Related information:

Save Library (SAVLIB) command

Save Changed Objects (SAVCHGOBJ) command Methods for saving distribution objects:

This information describes common save methods for distribution objects.

Table 30. Distribution objects information

Item description When changes occur Contains user data or changes?

IBM-supplied data?

Distribution objects

Distribution objects in QUSRSYS change regularly.

Yes No

Common save method for distribution objects Requires restricted state?

SAVDLO No¹

GO SAVE command, menu option 21 Yes

GO SAVE command, menu option 23 No^{1, 2}

GO SAVE command, menu option 30 Yes

GO SAVE command, menu option 32 Yes

Related concepts:

“Save-while-active function” on page 106

The save-while-active function allows you to use your system during all or part of the save process, that is, save your system while it is active.

Related tasks:

“GO SAVE: Option 21 (saving the entire system)” on page 29

Option 21 saves everything on your system and allows you to perform the save while you are not there.

“GO SAVE: Option 23 (saving user data)” on page 31

Option 23 saves all user data. This information includes files, records, and other data that your users supply into your system.

Related reference:

“Saving document library objects” on page 88

The system provides the capability to store documents and folders in a hierarchy (documents within a folder within another folder). Document library objects (DLOs) are documents and folders.

Related information:

Save Document Library Object (SAVDLO) command Methods for saving network server storage spaces:

This information describes common methods for saving network server storage spaces.

You can save and restore network server storage spaces, also known as virtual disks, that are associated with an integrated Windows server or integrated Linux server.

Table 31. Network server storage spaces information

Item description When changes occur Contains user data or changes?

IBM-supplied data?

Network server storage spaces

Network server storage spaces for integrated server licensed programs

(QFPNWSSTG directory) change regularly.

Yes Yes

Common save method for network server storage spaces Requires restricted state?

SAV⁴ No

GO SAVE command, menu option 21¹ Yes

GO SAVE command, menu option 23¹ No^{2, 3}

1 You must vary off the network servers. You can perform this option from the GO SAVE command menu if you select option 21, 22, or 23. Select the integrated server you want to vary off from the Specify Command Defaults screen.

3 Important:For procedures where the system does not require a restricted state, you must ensure that the system can get the locks necessary to save the information. You should put your system in a restricted state whenever you save multiple libraries, documents, or directories, unless you use the save-while-active function.

4 Network server storage spaces can be linked to the following network server descriptions:

*IXSVR, *ISCSI, and *GUEST NWSD. You can use the save-while-active function when the disk is linked to *ISCSI and *GUEST NWSD, but not when the disk is linked to *IXSVR.

Related tasks:

“Using save-while-active with network server storage spaces” on page 114

You can use the save-while-active function to save the network server storage spaces while keeping the integrated server online. The save-while-active function reduces or eliminates your outage for save operations.

“GO SAVE: Option 21 (saving the entire system)” on page 29

Option 21 saves everything on your system and allows you to perform the save while you are not there.

“GO SAVE: Option 23 (saving user data)” on page 31

Option 23 saves all user data. This information includes files, records, and other data that your users supply into your system.

“Saving data for IXS and IXA-attached integrated Windows servers” on page 105

You can do a full-system backup of the integrated Windows server to IBM i, save individual Windows files and directories, or save the network server description, configuration objects, and the associated disk drives.

“Saving data for iSCSI-attached integrated servers” on page 105

You can do a full-system backup of an iSCSI-attached integrated server to IBM i, or save the network server description, configuration objects, and the associated disk drives. You also can back up individual files and directories for the integrated Windows server .

Related information:

Save Object (SAV) command

Methods for saving user-defined file systems:

This information describes common save methods for user-defined file systems information.

Table 32. User-defined file systems information

Item description When changes occur Contains user data or changes?

IBM-supplied data?

User-defined file systems

User-defined file systems change regularly.

Yes Some

You might want to unmount all user-defined file systems (UDFSs) before you perform the save operation.

You can perform this option from the GO SAVE command menu if you select option 21, 22, or 23. Then select Y at the Unmount file systems prompt on the Specify Command Defaults display.

When you save a mounted UDFS, all file system information is saved. You can restore a mounted UDFS by specifying the RBDMFS(*UDFS) parameter on the RST command.

Common save method for user-defined file systems (UDFS) Requires restricted state?

SAV No¹

GO SAVE command, menu option 21 Yes

Related tasks:

“GO SAVE: Option 21 (saving the entire system)” on page 29

Option 21 saves everything on your system and allows you to perform the save while you are not there.

Related information:

Save Object (SAV) command

Methods for saving directories in the Root and the QOpenSys file systems:

This information describes common save methods for directories in the Root and the QOpenSys file systems information.

Table 33. Directories in the Root and the QOpenSys file systems information Item description When changes occur Contains user data or

changes?

IBM-supplied data?

Directories in the Root and the QOpenSys file systems

Directories in the Root and QOpenSys file systems change regularly.

Yes Some

Common save method for directories in the Root and the QOpenSys file

systems Requires restricted state?

SAV No

GO SAVE command, menu option 21 Yes

GO SAVE command, menu option 23 No^{1, 2}

1 When you select menu option 23 of the GO SAVE command, the command menu option places your system in a restricted state by default. If you choose the prompting option, you can cancel the display that puts your system in a restricted state.

2 Important:For procedures where the system does not require a restricted state, you must ensure that the system can get the locks necessary to save the information. You should put your system in a restricted state whenever you save multiple libraries, documents, or directories, unless you use the save-while-active function.

Related concepts:

“Save-while-active function” on page 106

The save-while-active function allows you to use your system during all or part of the save process, that is, save your system while it is active.

Related tasks:

“GO SAVE: Option 21 (saving the entire system)” on page 29

Option 21 saves everything on your system and allows you to perform the save while you are not there.

“GO SAVE: Option 23 (saving user data)” on page 31

Option 23 saves all user data. This information includes files, records, and other data that your users supply into your system.

Related information:

Save Object (SAV) command

Methods for saving IBM-supplied document library objects and folders:

This information describes common save methods for saving IBM-supplied document library objects.

Table 34. IBM-supplied document library objects and folders information

Item description When changes occur Contains user data or changes?

IBM-supplied data?

IBM-supplied document library objects and folders (usually start with Q, used by IBM i Access Family)

These library objects change when you update licensed programs.

No¹ Yes

1 You should avoid changing objects or storing user data in these IBM-supplied libraries or folders.

You could lose or destroy these changes when you install a new release of the operating system.

If you make changes to objects in these libraries, note them carefully in a log for future reference.

Common save method for IBM-supplied document library objects and

folders Requires restricted state?

SAVDLO² No³

GO SAVE command, menu option 21 Yes

GO SAVE command, menu option 23 No^{3, 4}

GO SAVE command, menu option 30 Yes

GO SAVE command, menu option 32 Yes

2 To ensure that the system saves all IBM i Access Family data, end subsystem QSERVER.

4 When you use option 23 from the GO SAVE command menu, the default is to place your system in a restricted state. If you choose the prompting option, you can cancel the display that puts your system in a restricted state.

Related concepts:

“Save-while-active function” on page 106

The save-while-active function allows you to use your system during all or part of the save process, that is, save your system while it is active.

“Saving changed document library objects” on page 70

You can use the Save Document Library Object (SAVDLO) command to save DLOs that have changed since a particular time.

Related tasks:

“GO SAVE: Option 21 (saving the entire system)” on page 29

Option 21 saves everything on your system and allows you to perform the save while you are not there.

“GO SAVE: Option 23 (saving user data)” on page 31

Option 23 saves all user data. This information includes files, records, and other data that your users supply into your system.

Related reference:

“Saving document library objects” on page 88

The system provides the capability to store documents and folders in a hierarchy (documents within a folder within another folder). Document library objects (DLOs) are documents and folders.

Related information:

Save Document Library Object (SAVDLO) command

Methods for saving user document library objects and folders:

This information describes common save methods for saving user document library objects.

Table 35. User document library objects and folders information

Item description When changes occur Contains user data or changes?

IBM-supplied data?

User document library

objects and folders User document library objects and folders change regularly.

Yes Some

Common save method for user document library objects and folders Requires restricted state?

SAVDLO No

GO SAVE command, menu option 21 Yes

GO SAVE command, menu option 23 No^{1, 2}

GO SAVE command, menu option 30 Yes

GO SAVE command, menu option 32 Yes

1 When you use option 23 from the GO SAVE command menu, the default is to place your system in a restricted state. If you choose the prompting option, you can cancel the display that puts your system in a restricted state.

Related tasks:

“GO SAVE: Option 21 (saving the entire system)” on page 29

Option 21 saves everything on your system and allows you to perform the save while you are not there.

“GO SAVE: Option 23 (saving user data)” on page 31

Option 23 saves all user data. This information includes files, records, and other data that your users supply into your system.

Related information:

Save Document Library Object (SAVDLO) command

Methods for saving IBM-supplied directories without user data:

This information describes common save methods for IBM supplied directories without user data information.

Table 36. IBM-supplied directories without user data information

Item description When changes occur Contains user data or changes?

IBM-supplied data?

IBM-supplied directories without user data

IBM-supplied directories without user data change when you apply Program Temporary Fixes (PTFs).

They also change when you install a new release of the operating system, or when you update licensed programs.

No Yes

Common save method for IBM-supplied directories without user data Requires restricted state?

SAV Yes

GO SAVE command, menu option 21 Yes

GO SAVE command, menu option 22 Yes

Related tasks:

“GO SAVE: Option 21 (saving the entire system)” on page 29

Option 21 saves everything on your system and allows you to perform the save while you are not there.

“GO SAVE: Option 22 (saving system data)” on page 30

Option 22 saves only your system data. It does not save any user data. Option 22 puts your system into a restricted state. This means that no users can access your system, and the backup is the only thing that is running on your system.

Related information:

Save Object (SAV) command

In document IBM i Version 7.2. Systems management Backing up your system (Page 101-109)