Chapter 10. Save/Restore Planning

This chapter discusses options for backup and recovery and provides examples to help you develop and implement your save/restore strategy. 

A major benefit with the Integrated PC Server and Integration for NetWare is the ability to include your NetWare backup procedure with your AS/400 backup procedure. 

When you load NetWare onto an Integrated PC Server, the Integrated PC Server stores the NetWare data on AS/400 disk space. This allows you to use the AS/400 save/restore support to back up your NetWare data. For complete information on backing up and restoring your system, see Backup and Recovery - Basic and Backup and Recovery - Advanced

You also have the option of including Integrated PC Server-based NetWare servers in your NetWare backup procedure. For example, you can access these NetWare servers from RCONSOLE and then backup and restore the NetWare data by using either SBACKUP or ARCserve** for NetWare Version 6. 


Save/Restore Overview

Before you begin to save and restore network data, you need to know where this data is stored on the Integrated PC Server and AS/400. 

Figure 10-1 shows where the NetWare and OS/2 data, as well as the network server description (NWSD), are stored on AS/400. 

Figure 10-1. NetWare and OS/2 Data for an Integrated PC Server
 
Server Storage Spaces Network Server

Storage Spaces

AS/400

* figure                      diskstor not displayed.

* figure                      diskstor not displayed.

* figure                      diskstor not displayed.

* figure                      diskstor not displayed.

* figure                      diskstor not displayed.

* figure                      diskstor not displayed.

* figure file                      not displayed.
C: Drive D: Drive E: Drive F: Drive System User NWSD
OS/2 Boot Disk OS/2 Disk NetWare Boot Drive NetWare Programs NetWare System Volume NetWare User Volume Server Description
QUSRSYS QFPINT QUSRSYS QFPINT QFPNWSSTG QFPNWSSTG QSYS

Storage Spaces

Storage spaces contain your NetWare data. You may decide to create two or more storages spaces for each NWSD. In this way, you can store data, such as PC programs, that do not change often in one storage space. And you can store user data that changes often in another storage space. Now, you can save the user data more often, and possibly save the PC program data only when you save the entire AS/400. 

Integration for NetWare creates two kinds of storage spaces: 

  • Server storage spaces   

  •  

     

    These storage spaces are used by the server to install and run NetWare 4.1. They contain licensed programs and system files, such as OS/2 and NetWare files, device drivers, Integrated PC Server administration applications, CONFIG.SYS, STARTUP.NCF, SWAPPER.DAT, and dump files. 

    Server storage spaces are *SVRSTG type objects. They are stored in AS/400 system libraries (not in the integrated file system), and they are created when you install Integration for NetWare. 

  • Network server storage spaces, also simply called storage spaces 

  •  

     

    Network server storage spaces contain the system volume and other volumes you choose to create to contain your directories and files, including AUTOEXEC.NCF. These storage spaces are stored in integrated file system directories. 

    Throughout this chapter the term "storage space" refers to network server storage spaces, unless otherwise indicated. 

AS/400 Libraries and Directories for Storage Spaces and NWSD Information

Integration for NetWare stores the NetWare information from the storage spaces in the following integrated file system directories and libraries, as shown in Figure 10-1

Library QSYS: This library contains a copy of your network server description. 

Library QUSRSYS:  This library contains NetWare server configuration information, such as the data needed for booting OS/2 and NetWare, including the CONFIG.SYS and STARTUP.NCF files. The server storage spaces in this library are also known as the C: Drive and the E: Drive. To save this library, specify *ALLUSR when you use the SAVLIB command. 

Library QFPINT:  This library contains licensed program information, including PTFs for 5716-SA2. The server storage spaces in this library are also known as the D: Drive and the F: Drive. 

The F: drive contains the NetWare product files for creating a NetWare server. These files were copied to this drive when you used the INSNTWSVR command. 

To save this library, specify *IBM when you use the SAVLIB command. 

Integrated file system directory /QFPNWSSTG:  This directory contains the network server storage spaces that you link to the NWSDs. These storage spaces are also known as the NetWare SYS (or system) volume and user volumes. Each storage space appears as a NetWare storage device. 

When you save data from this directory, you must save the entire storage space. Thus, you must restore the entire storage space; you cannot restore individual files and directories that were saved from this directory. 

Saving Individual Files and Directories

Integration for NetWare provides support for saving and restoring individual NetWare files, directories, and volumes from both Integrated PC Server-based and PC-based NetWare servers. NetWare Tape Support allows you to use SBACKUP or ARCserve for NetWare to directly access AS/400 tape drives from your NetWare server and then save and restore NetWare data. Integrated file system directory /QNetWare:

With Enhanced Integration for NetWare installed, you can also save your NetWare volumes, files, and directories on local and remote Integrated PC Servers and PC-based NetWare servers accessed through the QNetWare directory. 

As shown in Figure 10-2, the QNetWare directory contains the QNetWare file system as a hierarchical structure of directories and files that you can save and restore individually or in groups. The objects in the SAV.RST directory are resources, which represent volumes, the bindery on a NetWare 3.12 server, and all of the NDS objects in a NetWare 4.1 tree. 

Figure 10-2. QNetWare Directory

Using the SAV command, you can save: 

  • Individual files and directories 
  • Entire network server storage spaces 
  • Resources in SAV.RST 
You can save NetWare objects and resources to tape, diskette, optical disk, or save files. See "Saving and Restoring NetWare Data from the QNetWare Directory" for more information. 

Save/Restore Strategies

Your strategy for saving and restoring Integration for NetWare and the data it manages is going to depend on your company's needs and practices. 

If your company's network is AS/400-centric, you might choose to save and restore all of your NetWare data using AS/400 save/restore commands. On the other hand, if your company's network is PC-centric, you might choose to save and restore your NetWare data using SBACKUP or ARCserve for NetWare Version 6. 

Note:
If you use SBACKUP or ARCserve to save NetWare data to a tape, the tape cannot also contain AS/400 data. You will need to have two sets of tapes, one set for NetWare data and one set for AS/400 data. 

Save Regularly

Your backup strategy should include saving the storage spaces (also sometimes called network drives) regularly. Create several storage spaces. Store data that changes infrequently on different storage spaces from data that changes frequently. Using this strategy, you can save the storage space containing the infrequently changed applications or data less often, perhaps only when you save the entire AS/400. 

Chapter 11. "Saving and Restoring Network Data" provides examples and tips on how to save the entire system, storage spaces only, and the other objects that are part of Integration for NetWare. 

It is important that you plan the frequency of your saves to ensure that you always have a usable backup available in the event of a system failure or disaster. For example, you may decide on the following strategy to ensure that your user data is thoroughly backed up. 

Weekly

If you are using AS/400 save/restore, save the network server storage spaces in the /QFPNWSSTG directory as a single block of data. This will allow you to restore the majority of your data in one command. To save the /QFPNWSSTG directory, you must vary off your Integrated PC Server. Alternatively, you can back up the network server storage spaces using either SBACKUP or ARCserve for NetWare. 

Daily

Consider saving your user volumes daily if data or applications on those volumes change on a daily basis.   Also consider using the Save user data option to save user data, including IBM-supplied libraries and directories with user data. 

Alternatively, you can either use NetWare tape support or save through /QNetWare to save incremental changes. 

If you have Enhanced Integration for NetWare installed, you can save, through /QNetWare, NetWare objects that have changed. You can do this by using the time and date parameters on the Save Object (SAV) display (press F10 for additional parameters). 

Time period for last change:

  Start date . . . . . . . . . .   *ALL          Date, *ALL, *LASTSAVE

  Start time . . . . . . . . . .   *ALL          Time, *ALL

  End date . . . . . . . . . . .   *ALL          Date, *ALL

  End time . . . . . . . . . . .   *ALL          Time, *ALL


Event Driven

Consider making the following saves whenever specific events occur: 

  • Save your E: drive whenever you make NetWare updates. 
  • Save the licensed program whenever you apply PTFs for 5716-SA2 or 5716-SA3. 
  • Save your SYS volume first whenever you plan to change your AUTOEXEC.NCF. This allows you to restore your server configuration in case errors occur in AUTOEXEC processing. 
  • Save your SYS volume whenever you made changes to NDS, such as adding servers or making changes to user objects or their authorities. This ensures that your NDS is current in case you need to restore your system volume. 
Performance Considerations

Your save/restore choices can have a significant effect on the time it takes to save AS/400. Consider the following carefully. 

Saving the entire network server storage space through /QFPNWSSTG is significantly faster than saving the QNetWare directory, unless you are saving only a small portion of the storage space. To save the QFPNWSSTG directory, you must vary off the Integrated PC Server before saving. 

However, if you must later restore the data, you must restore the entire storage space. If you save only a portion of the storage space (either by using SBACKUP or ARCserve or saving through /QNetWare), you can restore only the files you need. Also, you do not have to vary off the Integrated PC Server to perform this type of save operation. 


Save/Restore Options

Table 10-1 lists the options for saving your NetWare data and implementing your save/restore strategy:

Table 10-1. Save/Restore Options
 
Command/Application  Server Storage Spaces  Network Server Storage Spaces  QSYS.LIB 
C: Drive  D: Drive  E: Drive  F: Drive  SYS Volume  User Volume  NWSD 
SAVLIB *ALLUSER 
SAVLIB *IBM     
SAVCFG             
SBACKUP or ARCserve         
SAV.../QFPNWSSTG         
SAV.../QNetWare         

Options for Saving Network Server Storage Spaces

Depending on the save/restore option you choose, you can save and restore individual files and directories. You can also choose between using NetWare applications or AS/400 commands.
 
Support for...  /QFPNWSSTG  SBACKUP/ARCserve  /QNetWare 
Saving individual files and directories   
Using AS/400 SAV/RST commands   
Note: The NWSD must be varied on if you want to save and then restore individual files or directories through the QNetWare directory. 

Integrated PC Server On or Off?

If you use the AS/400 SAV command, the type of NetWare objects you save depends on whether the NWSD is varied on or off. 

Varied OFF

The Integrated PC Server must be varied off when you want to save entire storage spaces in /QFPNWSSTG or QUSRSYS (whether they are network server storage spaces or server storage spaces). You can restore entire NetWare volumes only. 

Varied ON: The Integrated PC Server must be varied on when you want to save files, directories, or SAV.RST resources through QNetWare. Then you can selectively restore the NetWare data you saved. 

Restricted State

Before you save or restore local files in the /QNetWare file system, decide if you want to place your server in a Restricted state. Placing a server in restricted state will end all remote connections and will prevent new remote connections from starting. Local connections remain unaffected. 
You can put the server in a Restricted state by ending the monitor job assocated with the network server. In order to place the server in a Restricted state, the monitor job must be communicating with the Enhanced Integration for NetWare NLM. 

Putting the Integrated PC Server into Restricted State--Example

To put the Integrated PC Server into Restricted state, end the monitor job: 
  1. Enter WRKNWSSTS to see the display shown in Figure 10-3 and make sure the NetWare server is active. Note that NetWare server, DOCSERV, is active. 

  2.  

     

    Figure 10-3. Network Server Status Display
     
     

+--------------------------------------------------------------------------------+
|                        Work with Network Server Status                         |
|                                                             System:   SYSAS400 |
| Server type  . . . . . :   *NETWARE                                            |
|                                                                                |
| Type options, press Enter.                                                     |
|   5=Display details     7=Display users   8=Work with configuration status     |
|   10=Start connection   11=Work with connections   14=Restart server           |
|   15=Work with storage   16=Work with volumes                                  |
|                                                                                |
| Opt  Server            Status                Location                          |
|      DOCSERV           ACTIVE                  *LCL                            |
|      J2962C            ACTIVE                  *RMT                            |
|      KCTST01           INACTIVE                *LCL                            |
|      MENG0002          INACTIVE                *LCL                            |
|      NEWDOG            ACTIVE                  *LCL                            |
|      NWSDNW12          ACTIVE                  *RMT                            |
|      NWSDNW14          ACTIVE                  *RMT                            |
|      NWSDNW16          INACTIVE                *RMT                            |
|                                                                        More... |
| Parameters or command                                                          |
| ===> wrkactjob                                                                 |
| F3=Exit   F4=Prompt   F5=Refresh   F6=Print list   F9=Retrieve                 |
| F11=Display entire server names    F12=Cancel      F24=More keys               |
|                                                                                |
+--------------------------------------------------------------------------------+

  1. Type WRKACTJOB and press Enter to see the display shown in Figure 10-4

  2.  

     

    The monitor job runs in the QSYSWRK subsystem, and the job name, DOCSERV, corresponds to the name of the Integrated PC Server. 

    Figure 10-4. Work with Active Jobs Display
     
     

+--------------------------------------------------------------------------------+
|                             Work with Active Jobs                     SYSAS400 |
|                                                             11/15/96  15:26:59 |
| CPU %:    4.4     Elapsed time:   00:03:46     Active jobs:   70               |
|                                                                                |
| Type options, press Enter.                                                     |
|   2=Change   3=Hold   4=End   5=Work with   6=Release   7=Display message      |
|   8=Work with spooled files   13=Disconnect ...                                |
|                                                                                |
| Opt  Subsystem/Job  User        Type  CPU  0.000000unction        Status       |
|        QSERVER      QPGMR       ASJ      .0                   EVTW             |
|      QSPL           QSYS        SBS      .0                   DEQW             |
|        PRT01        QSPLJOB     WTR      .0                   MSGW             |
|      QSYSWRK        QSYS        SBS      .0                   DEQW             |
|        DOCSERV      QSYS        BCH      .0  PGM-QFPAMONN     TIMW             |
|        QIPX         QSYS        BCH      .0                   DEQW             |
|        QMSF         QMSF        BCH      .0                   DEQW             |
|        QNETWARE     QSYS        BCH      .1  PGM-QFPANTWJ     DEQW             |
|        QPRFSYNCH    QSYS        BCH      .0  PGM-QFPAPRFJ     DEQW             |
|                                                                        More... |
| Parameters or command                                                          |
| ===>                                                                           |
| F3=Exit      F5=Refresh   F10=Restart statistics   F11=Display elapsed data    |
| F12=Cancel   F23=More options   F24=More keys                                  |
|                                                                                |
+--------------------------------------------------------------------------------+

  1. Type 5 in the Options column and then press Enter to display the job. 

  2.  

     

    Select option 10 to the display job log for the monitor job. Press PF10 to display the detailed messages. Review the job log and confirm that the monitor job has established communication with the Enhanced Integration for NetWare NLM and that enhanced functions are available. 

    Figure 10-5. Monitor Job Log--Example
     
     

+--------------------------------------------------------------------------------+
|01                               Display All Messages                           |
|02                                                              System: SYSAS400|
|                                                                                |
|03  Job . . :   DOCSERV       User . . :   QSYS          Number . . . : 001456  |
|                                                                                |
|04                                                                              |
|05   >> CALL PGM(QSYS/QFPAMONN) PARM('DOCSERV   ')                              |
|06      Monitor job for network server DOCSERV started.                         |
|07      Attempting contact with Enhanced Integration NLM on server DOCSERV.     |
|08      Network server BASE536 is active.                                       |
|09      Enhanced functions available for network server DOCSERV.                |
|10      Contact successful with Enhanced Integration NLM on server DOCSERV.     |
|11                                                                              |
|12                                                                              |
|13                                                                              |
|14                                                                              |
|15                                                                              |
|16                                                                              |
|17                                                                              |
|18                                                                              |
|19                                                                        Bottom|
|                                                                                |
|20  Press Enter to continue.                                                    |
|21                                                                              |
|22  F3=Exit   F5=Refresh   F12=Cancel   F17=Top   F18=Bottom                    |
|23                                                                              |
|24                                                                              |
+--------------------------------------------------------------------------------+

    If the monitor job is not in successful contact with the Enhanced Integration for NetWare NLM, it will be unable to place the network server in restricted state before it ends. Verify that the NLM is loaded and restart the monitor job by selecting option 14 (Restart server) on the WRKNWSSTS display. 
  1. Return to the Work with Active Jobs Display. 

  2.  

     

    After returning to the Work with Active Jobs display, type 4 in the Options column and then press Enter to end the monitor job. 

    Figure 10-6. Ending the Monitor Job--Example
     
     

+--------------------------------------------------------------------------------+
|                             Work with Active Jobs                     SYSAS400 |
|                                                             11/15/96  15:26:59 |
| CPU %:    4.4     Elapsed time:   00:03:46     Active jobs:   70               |
|                                                                                |
| Type options, press Enter.                                                     |
|   2=Change   3=Hold   4=End   5=Work with   6=Release   7=Display message      |
|   8=Work with spooled files   13=Disconnect ...                                |
|                                                                                |
| Opt  Subsystem/Job  User        Type  CPU  0.000000unction        Status            |
|        QSERVER      QPGMR       ASJ      .0                   EVTW             |
|      QSPL           QSYS        SBS      .0                   DEQW             |
|        PRT01        QSPLJOB     WTR      .0                   MSGW             |
| 4    QSYSWRK        QSYS        SBS      .0                   DEQW             |
|        DOCSERV      QSYS        BCH      .0  PGM-QFPAMONN     TIMW             |
|        QIPX         QSYS        BCH      .0                   DEQW             |
|        QMSF         QMSF        BCH      .0                   DEQW             |
|        QNETWARE     QSYS        BCH      .1  PGM-QFPANTWJ     DEQW             |
|        QPRFSYNCH    QSYS        BCH      .0  PGM-QFPAPRFJ     DEQW             |
|                                                                        More... |
| Parameters or command                                                          |
| ===>                                                                           |
| F3=Exit      F5=Refresh   F10=Restart statistics   F11=Display elapsed data    |
| F12=Cancel   F23=More options   F24=More keys                                  |
|                                                                                |
+--------------------------------------------------------------------------------+

    When the monitor job ends, it will attempt to place the network server in a restricted state. Messages will be sent both to the monitor job's job log and to the QSYSOPR message queue indicating whether this operation was successful. 

    In addition, the status value will be updated on the WRKNWSSTS display to indicate the new state of the network server. 

You cannot place the network server in a restricted state by placing the AS/400 system in a restricted state. Placing the system in a restricted state ends the QSYSWRK subsystem; however, the QSYSWRK subsystem must remain active while the network server is placed in restricted state because: 
  • Placing the network server in a restricted state requires the use of IPX support 
  • The QIPX job runs in the QSYSWRK subsystem in restricted state. 
Remote Servers

To save files from a remote server, AS/400 and the remote Integrated PC Server must be active. When AS/400 is in restricted state you CANNOT save remote data because you cannot start any of the system functions required to access the remote systems. 

Authority to Save NetWare Files and Directories

Before you can use SBACKUP or ARCserve to save or restore NetWare files and directories, you must have the necessary authority. Table 10-2 shows the authority that NetWare requires for specific backup and restore actions.

Table 10-2. Rights to NetWare files and directories
 
Action  Required Rights 
Read from a closed file  Read 
See a filename or directory  File Scan 
Write to a closed file  Write, Create, Erase, Modify 
See the root directory  Any of the eight rights 
Create and write to a file
Make a new directory 
Create 
Delete a file  Erase 
Change attributes
Rename a file 
Modify 
Copy files into a directory  Write, Create, File Scan 
Copy files from a directory  Read, File Scan 
Modify disk space restrictions
Change directory rights
Change trustee assignments 
Access Control 
Salvage deleted files  Read, File Scan, Create 

Authority to Save NetWare Data Through /QNetWare

Many organizations allow users to back up their AS/400 system (or certain components of it) and give those users *SAVSYS authority. The Enhanced Integration for NetWare environment works differently from the standard AS/400. Before you can perform save and restore operations, you must either have the necessary authority to the object or administrator authority on the NetWare server (equivalent to *ALLOBJ authority on AS/400). 

  *ALLOBJ special authority gives enough authority to save NetWare objects and their authority information only when: 

  • You are a defined NetWare user 
  • The NetWare server is an Integrated PC Server on a local AS/400 
Therefore, if you want to save both the storage space and file authority information, you must grant your NetWare user ID *ALLOBJ authority on AS/400 using the CHGUSRPRF command: 
  CHGUSRPRF USRPRF(JEFF) SPCAUT(*ALLOBJ)


Authority Information: The authority of a NetWare object is stored with the object, not with the user profiles that have the authority. Using the SAVSECDTA or SAVSYS commands does not save authority information for NetWare objects. See "Authorizing Users to Files and Directories" for more information. 

Groups: AS/400 allows group profiles to sign on. NetWare does not. Therefore, if a user ID, such as QSECOFR, is enrolled as a group to NetWare, that user profile cannot sign on, and cannot perform save or restore operations. Ensure that whichever user is to perform these operations is not using a user ID that is considered a group profile on NetWare. 

To determine which AS/400 profiles are considered group profiles on NetWare, enter: 

  WRKNWSENR PRFTYPE(*GROUP) SVRTYPE(*NETWARE)


The Work with NWS User Enrollment display shows the list of AS/400 profiles that are enrolled on NetWare as groups. If you find QSECOFR in the list and that user ID is to perform save or restore operations, use the CHGNWSUSRA command to enroll it as a member of a group that is enrolled on NetWare. See Chapter 21. "Managing User Enrollment" for more information. 

You can also display NetWare enrollment status for a specific user ID. For example, to display status for QSECOFR, enter WRKNWSENR USRPRF(QSECOFR). 


[ Top of Page | Previous Page | Next Page | Table of Contents | Index