Troubleshooting
Problem
Be aware of restrictions when saving files through QNTC.
Resolving The Problem
When using the file-level backup of Windows server on an iSeries system, you should be aware of these restrictions:
Requirements:
When you finish the necessary setup tasks, you are ready to back up Windows server files on IBM i. To be able to restore a directory or file by share name, you must specify that file or share name specifically on the SAV command.
Note: To avoid duplicating data, be careful specifying what you want to save on the SAV command. If you specify multiple share names that point to the same directory on Windows server, AS/400 saves the data multiple times.
To specify what you want IBM i to save, you should do the following:
These examples show how to refer with the SAV or RST commands to specific parts of Windows server for a server that is named server1:
Common Error Messages
Below is a list of some common error messages that may be reported when performing a file-level save through QNTC file system:
|
o |
This support is not available to a network-connected Windows servers because the code comes packaged with IBM i Integration for Windows Server. |
| o | This method does not back up files that are part of the IBM i Integration for Windows Server code. |
| o | Windows server provides no way to stop users from signing on and accessing data on the server while the Save (SAV) or Restore (RST) command is running. IBM i Integration for Windows Server can save a file that is in use as long as it can read the file. Consequently, you should back up Windows server files when you expect few users to be accessing the system. A note telling users to avoid accessing the server would be a good precaution. |
| o | This backup method is designed to be used for restoring a data in a specific share, a specific file, or in conjunction with the IBM i full system save for disaster recovery. |
| o | The Microsoft Windows server and domain names must be 15 characters or less. |
| o | The share name must be 12 characters or less in length. |
| o | Each component of the path name after the share name can be up to 255 characters. |
| o | Within QNTC, 130 levels of hierarchy are generally available. If all components of the path name are included as hierarchy levels, the directory hierarchy can be as many as 132 levels deep. |
| o | If a large quantity of data is saved using this method, the save may take an extended period of time. |
| o | The Windows server running on an Integrated NetFinity Server must be active and have a working TCP/IP internal LAN connection with IBM i. You must back up your Windows server files either before putting the system into restricted state to back up the rest of the IBM i files or after completing restricted state operations. | ||||||||||||||||
| o | Ensure that the person who is saving and restoring files has the same password on IBM i and Windows server. The easiest way is to enroll the IBM i user to Windows server. Create the user enrollment template so that the user is a member of the Administrators group. | ||||||||||||||||
| o | Create a share for each drive or volume that you want to save when you request to save all the files on a Windows server. IBM i Integration for Windows Server accesses the file system and translates these shares into path names. Using Microsoft system shares, for example, C$, D$, and so on, are not supported. Your own shares must be created. | ||||||||||||||||
| o | Add a member to the QAZLCSAVL file in QUSRSYS that lists the share names that you want to be able to save as follows: On an IBM i command line, type the following: ADDPFM FILE(QUSRSYS/QAZLCSAVL) MBR(servername) TEXT('description') + EXPDATE(*NONE) SHARE(*NO) SRCTYPE(*NONE) Press the Enter key. In the file member that you just created, list all the shares that you want to be able to save. List each share name that you defined for the server on a separate line. The maximum length that the Windows share name can be is 12 characters. Share names can have embedded blanks. For example, if you defined cshare, dshare, eshare, fshare, gshare, and my share as shares on WINSVR1, your member name WINSVR1 would look like this:
EDTF FILE(QUSRSYS/QAZLCSAVL) MBR(servername) Note: If multiple share names that point to the same directory are specified on Windows a server, the OS/400e or iSeries system saves the data multiple times for a "save all" request. To avoid duplicating data when you save it, do not include multiple shares that include the same directory or data. |
||||||||||||||||
| o | Be careful about trying to restore all files on all drives that you previously saved through the QNTC file system. Certain Windows system files (for example, files in the Recycle Bin) can cause unexpected results after you restore them. | ||||||||||||||||
| o | On Windows 2000, you need to give special consideration to System File Protection when you are backing up and recovering Windows system files. Refer to Microsoft documentation. |
When you finish the necessary setup tasks, you are ready to back up Windows server files on IBM i. To be able to restore a directory or file by share name, you must specify that file or share name specifically on the SAV command.
Note: To avoid duplicating data, be careful specifying what you want to save on the SAV command. If you specify multiple share names that point to the same directory on Windows server, AS/400 saves the data multiple times.
To specify what you want IBM i to save, you should do the following:
| o | On the IBM i command line, type SAV, and press F4. |
| o | In the Device field, specify the device on which you want IBM i to save the data. For example, 'QSYS.LIB/TAP01.DEVD' saves the data to tape. |
| o | In the Object field, specify OBJ('/QNTC/server1/*'). Note: The first time a save is run with this object path it may take an extended period of time and will each time it is run if the Change period parameter is not specified as described below |
| To Save or Restore This: | Specify This: |
| All Windows server objects. | OBJ('/QNTC*') SUBTREE(*ALL) |
| All objects for server1. | OBJ('/QNTC/server1/*') SUBTREE(*ALL) |
| All objects for server1 that changed since you last saved the files. | OBJ('/QNTC/server1/*') SUBTREE(*ALL) CHGPERIOD(*LASTSAVE) |
| All objects for server1 that changed during a certain period (in this case between 10/19/99 and 10/25/99). | OBJ('/QNTC/server1/*') SUBTREE(*ALL) CHGPERIOD('10/19/99' '00:00:00' '10/25/99' '23:59:59') |
| All directories, files, and shares to which a particular share (for example, fshare) refers. OS/400 does not save and restore the directory over which the share is built. | OBJ('/QNTC/server1/fshare/*') SUBTREE(*ALL) |
| Only files to which the specified share (for example, fshare) refers that match the specified pattern (pay*). OS/400 does not save directories nor shares. | OBJ('/QNTC/server1/fshare/pay*') |
| Only directories and shares (no objects) for fshare and its immediate children. | OBJ('/QNTC/server1/fshare') SUBTREE(*DIR) |
| Directories, shares, and files for terry and its subtrees (not directory terry). | OBJ('/QNTC/server1/fdrive/terry/*') SUBTREE(*ALL) |
| Only the specific file myfile.exe. | OBJ('/QNTC/server1/gdrive/myfile.exe') |
| The Windows server registry. | OBJ('/QNTC/server1/$REGISTRY') |
Common Error Messages
Below is a list of some common error messages that may be reported when performing a file-level save through QNTC file system:
| CPD3401 | Permission denied. The IBM i user profile does not exist on the Windows Server and/or the IBM i user profile does not have the correct authority to the shares. |
| CPDB050 RC=108 | Network error. This error could be generated because of any of the following: a) Network traffic. b) Master Browser failing to recognize or respond to the NetServer. c) Windows 95/98 clients have the Master Browser parameter in the registry set to FALSE. d) The IBM i DNS and Host table entries are incorrect. e) WINS server is not configured properly. f) On a Windows server, the Server service is disabled on the Internal Virtual Token-Ring adapter driver. |
| CPDB050 RC=109 | Session open rejected. The most common cause of this error is that the NetServer has stopped. |
| CPDB050 RC=110 | Session open rejected. Ensure that the Windows server name under QNTC matches the Computer Name of the Windows server. |
| CPDB050 RC=180 | Is caused by a network error. This is a return code from Microsoft networking protocol and is a result of a network issue. |
| CPDB058 RC=1 | Caused by incorrect path or typo to the object being moved / copied. |
[{"Type":"MASTER","Line of Business":{"code":"LOB68","label":"Power HW"},"Business Unit":{"code":"BU070","label":"IBM Infrastructure"},"Product":{"code":"SWG60","label":"IBM i"},"ARM Category":[{"code":"a8m0z0000000CRUAA2","label":"Integrated File System-\u003EQNTC"}],"ARM Case Number":"","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"All Versions"}]
Historical Number
22690419
Was this topic helpful?
Document Information
Modified date:
22 April 2025
UID
nas8N1017467