Skip to main content

 
IBM Power Systems software  >  IBM i  > Advantages  > 

IBM i integration
with BladeCenter and System x

  
Overview Solutions Operating systems Resources
Intro   |   Windows   |   VMware ESX   |   Linux   |  
 
Windows overview
Microsoft service packs
Logo'd by Microsoft
 
Backup
Tape devices for iSCSI
Tape devices for IXA/IXS
Windows Server 2008
blue_rule.gif

Backup for Windows servers

Because IBM i Windows integration support combines two operating systems (Windows® and IBM i), you can choose to manage backups by using either IBM i or Windows utilities or a combination of both. When you are planning your backup strategy for your Windows server on IBM i, see Backup options for suggestions. For more detailed information, refer to the Backing up and recovering integrated Windows servers topic in the Information Center for i 6.1 (iSCSI), i 6.1 (IXS/IXA), i 5.4, V5R3 or Chapter 7: Backup and recovery in Redbook Implementing Integrated Windows Server through iSCSI to System i5 (SG24-7230-00).

Many objects are created on IBM i as a result of installing IBM i integrated server support support. Some of these are system-related, others user-related. You need to save them all if you want to restore properly. When you want to back up IBM i objects, shut down the Windows Server by varying off the network server description to prevent users from updating files during the backup.

These objects are considered part of the IBM i system and are saved when you perform a full IBM i system save. One method of saving system and user data on i5/OS is to type GO SAVE on the IBM i command line and use option 21, 22, or 23.

Backing up your Windows Server using IBM i involves backing up both predefined storage spaces (the C and D drives) and storage spaces that you have defined.

You can see a table of user and system objects that you should save in topic  What objects to save and their location on IBM i in the Information Center for i 6.1, i 5.4 or V5R3.

You can also read an overview of your recovery options and suggestions for restoring system files.

 
 Backup options
 

Because IBM i integrated server support support combines two operating systems (Windows and IBM i), you can choose to manage your backups by using either i5/OS or Windows utilities or a combination of both.  

Integrated file save/restore from IBM i:

File-level backup and recovery of Windows data is enabled through IBM i. This support is enabled through the IBM i NetClient file system (QNTC) of the Integrated File System. This function enables customers to incorporate incremental saving of files and the Windows registry associated with a network server description into their existing IBM i backup procedures. In addition, the registry and files saved through this method can be individually restored if needed. Saving of Windows server files in this manner can be used with full IBM i system save procedures for disaster recovery.

Note: Here are some tips to achieve optimal file-level backup performance:

  • The TCP/IP send/receive buffer sizes need to be much larger than the default. It is recommended to use no smaller than 65535. The default is 8192. The maximum size is 8 MB, which is much larger than needed. Change these values as follows:
    1. Run command CFGTCP
    2. Select option 3 "Change TCP/IP attributes"
    3. Modify TCP receive and send buffer sizes to 65535
    4. Press Enter to apply the changes
    5. The changes take effect immediately.
  • Keep your Windows servers at the latest IBM i server integration service pack level.
  • The i5/OS QRETSVRSEC system value must be set to '1':
    CHGSYSVAL SYSVAL(QRETSVRSEC) VALUE(1)
  • Do  not use QSECOFR as the user profile for running the SAV or RST command - it will likely not work. Use some other user profile.
  • The user profile doing the backup or restore  must have administrator authority on the server being backed up or restored. This may be accomplished by making the user a member of the windows "administrators" group. If the target server is a domain member server, then you can make the user a member of the domain's "Domain Admins" group. The "Domain Admins" group is made a member of the local "administrators" group when the server joins the domain, indirectly making the user a member of the "local" administrators group.
Full IBM i backup:
A full IBM i system backup automatically backs up any IBM i integration with BladeCenter® and System x™ components that are on that system (unless someone has changed the backup and removed those components). To take a full system backup:
     1. On the IBM i command line, type GO SAVE and press Enter.
     2. On the Save screen that appears, choose:
        Option 21 to save the entire system
        Option 22 to save just system data
        Option 23 to save just user data
Windows operating system and registry:
The Windows operating system and the files required to start the Windows Server are located on the C and D drives of the server. The server storage spaces that contain these drives are in IFS directory QFPNWSSTG on IBM i. The architecture of the integrated server solutions allows you to save these drives on IBM i and restore them in case of damaged or deleted files. For example, to replace a deleted file or a damaged registry, you can restore the Windows system drive. You can effectively use this option to eliminate the BOOT disk, RDISK and registry backups that you would take with a PC-based Windows Server. Daily backup of the system drive is a good idea. You can save these files to tape or to a save file that is stored on IBM i. To save them to a save file, use the SAV command with the compression option enabled. For example:
     SAV DEV('/QSYS.LIB/BACKUP.LIB/SYSDRIVE.FILE')
     OBJ('/QFPNWSSTG/nwsdname1') DTACPR(*YES)
Note: With i 6.1, you can perform the above SAV command while the server is active by adding the following parameters to the SAV command:
     SAVACT(*YES) SAVACTOPT(*NWSSTG)

This takes advantage of the storage space snapshot support. For prior releases, the NWSD must be varied off prior to running the SAV command. See the backup and recovery topics listed at the top of this page.

User data (using user-defined storage spaces):

On IBM i you can save each user storage space with this command:

     SAV DEV('/QSYS.LIB/TAP01.DEVD') OBJ(('/QFPNWSSTG/stgspc'))
Prior to i 6.1: To save a storage space in a user auxiliary storage pools, use this command:
     SAV DEV('/QSYS.LIB/TAP01.DEVD')
         OBJ(('/QFPNWSSTG/stgspc')('dev/QASPnn/stgspc.UDFS'))
Note: With i 6.1, you can perform the first SAV command listed above while the server is active by adding the following parameters to the SAV command:
     SAVACT(*YES) SAVACTOPT(*NWSSTG)

</ p>This takes advantage of the storage space snapshot support. For prior releases, the NWSD must be varied off prior to running the SAV command. You cannot restore individual files from this backup. If you need to restore files or directories individually, use the file-level backup method.

User data (using individual files):

If you need the ability to restore individual files, use one of these options:

  • Integrated file save/restore from IBM i.
  • Windows Backup utility. On Windows, you can find the Backup icon in the Start menu under the Administrative Tools program group. See Windows documentation for information about using this utility.
    Note: This method can be combined with the dynamic disk drive unlinking support (See Unlinking integrated server disks in the Information Center). This provides an alternative method to include file-level backups of Windows data with IBM i backups.
  • Use iSeries NetServer to copy files from Windows Server into the i5/OS Integrated File System. Then use a suitable backup utility (for example, WinTAR) to save the files to the network drive.
 
Using IBM i tape devices from an integrated server as native Windows devices
 
The IBM i integration support allows native Windows applications that are running on the integrated server to access IBM i tape devices. For information on how to use IBM i tape devices from the integrated server, see the backup and recovery topics listed at the top of this page. The specific tape devices that are supported for a particular configuration depend on the version of Windows that is installed on the server, and the type of integrated server hardware that is being used. See the following pages for the latest list of IBM i tape devices that can be used with integrated servers.
 
 Third party backup and recovery applications
 

In releases V5R3, i 5.4 and i 6.1, the IBM i Integrated Server Support product is designed to work with several backup utilities. The IBM i Integrated Server Support and iSeries Integration for Windows Server products are designed to work with the Microsoft Windows Backup tool for Windows Server 2003 and the Microsoft Windows Backup tool for Windows 2000.

When using BladeCenter or System x models that are attached via the iSCSI host bus adapter (iSCSI HBA), the IBM i Integrated Server Support roduct has been tested with VERITAS™ Backup Exec™ 9.1 for Windows Servers, now from Symantec® and Symantec Backup Exec 10d for Windows Servers only when using third party tape device drivers. See the Tested tape devices for iSCSI attached Windows servers page for more information.

When using the Integrated xSeries Server (IXS) or System x models that are attached via the Integrated xSeries Adapter (IXA), the IBM i Integrated Server Support and iSeries Integration for Windows Server products are designed to work with some versions and builds of VERITAS Backup Exec for Windows NT and Windows 2000. The IBM i Integrated Server Support and IBM iSeries Integration for Windows Server products are designed to work with versions and builds of VERITAS Backup Exec version 8.0, build 3311 or before when running on Windows 2000 and Windows Server 2003 on IBM i V5R3. The IBM i Integrated Server Support and iSeries Integration for Windows Server products are designed to work with VERITAS Backup Exec version 9.1, build 4691 only when using third party tape device drivers. See the Supported tape devices for IXS and IXA attached Windows servers and tape driver migration pages for more information.

Attempting to run backup applications for which the IBM i Integrated Server Support or iSeries Integration for Windows Server product is not designed may yield unexpected results.

With respect to the IBM i Integrated Server Support and iSeries Integration for Windows Server products the above information takes precedence over other information published by IBM regarding Windows or VERITAS Backup Exec.

The above information is provided AS IS without warranty of any kind.

 
 
Trademark information
 
See the Trademark information page for information on IBM and other company trademarks.