Professional Documents
Culture Documents
220 Os 400 Backup N Restore
220 Os 400 Backup N Restore
220 Os 400 Backup N Restore
Backup/Recovery
Strategies Update
for AS/400 and iSeries 400
IBM server iSeries
Selwyn Dickey
1
Backup and Recovery Strategies Update
IBM server iSeries
AGENDA
Ensuring a Complete Backup Strategy
Domino Servers
Windows Servers
Linux in a Partition
Independent ASPs
Logical Partitioned Systems
2
Ensuring a Complete Backup Strategy
IBM server iSeries
3
Backing Up Domino Server
IBM server iSeries
Information stored by Domino appears in several different directories
on the system:
/QSYS.LIB/QNOTES.LIB: Licensed program information that does not change.
Saved with SAVLIB *IBM or SAVLIB *NONSYS.
/QSYS.LIB/QNOTESAPI.LIB: C APIs that do not change. Saved with SAVLIB
*IBM or SAVLIB *NONSYS.
/QSYS.LIB/QNOTESCPP.LIB: C++ APIs that do not change. Saved with
SAVLIB *IBM or SAVLIB *NONSYS.
/QSYS.LIB/QNOTESHTST.LIB: HiTest APIS that do not change. Saved with
SAVLIB *IBM or SAVLIB *NONSYS.
/QSYS.LIB/QNOTESLSKT.LIB: LotusScript Extensions that do not change.
Saved with SAVLIB *IBM or SAVLIB *NONSYS.
/QSYS.LIB/QUSRNOTES.LIB: Customization Information that may change.
Saved with SAVLIB *ALLUSR or SAVLIB *NONSYS.
4
Backing Up Domino Server
IBM server iSeries
Majority of information for Domino is in the Integrated File System.
/QIBM/ProdData/Lotus/Notes: Static product information. Saved with SAV
command.
/QIBM/UserData/Lotus/Notes: Customization files for the product. Saved with
SAV command.
Pathname specified when you configure the server: Path for the databases on
the server. Saved with SAV command.
5
Backing Up the Domino Product
IBM server iSeries
6
Backing Up the Domino Server
IBM server iSeries
When saving a Domino server, you typically save all the information
that is changing associated with the server.
You must save:
All the databases
Users' mail databases
Names and address book for the server
When you configure a Domino server, specify the directory for that
server such as /NOTES/DATA. By default, all the databases for the
server are in that path. Typically, end users cannot create Domino
databases in any location except the default path for the server. If
you are responsible for backing up a Domino server, develop a
backup strategy that matches your policy of where you keep
information. The two main approaches for this are:
Limit the location of Domino databases.
Save everything.
7
Backing Up the Domino Server Example
IBM server iSeries
8
Backing Up the Domino Server Example
IBM server iSeries
Saving everything for Domino Databases: If your Domino databases
are not confined to a specific directory path, use any of the following
options:
Save your entire system (option 21 from the Save menu)
Save all user data (option 23 from the Save menu)
Use the SAV command to save everything except the QSYS.LIB and QDLS file
system:
9
Backing Up OS/400 Integration for Windows Server
IBM server iSeries
Windows Server new in V4R5 enables you to run a truly integrated
version of Windows NT or Windows 2000 server on your iSeries 400.
10
Backing Up Windows Server
IBM server iSeries
For full backup save the /QFPNWSSTG directory. You must also
vary off the Integrated Netfinity/x-Series Server(NWSD).
11
Backing Up Windows Server
IBM server iSeries
When you save, the system attempts to save the directories within
the QNTC directory or the directories within the QFPNWSSTG
directory.
If network server description varied on - Save contains /QNTC directories
associated with Integrated Netfinity/x-Series Server (NWSD).
/QNTC requires working TCP/IP internal LAN connection.
If network server description varied off - Save contains directories within the
/QFPNWSSTG directory. Individual files and directories cannot be restored
from a saved copy of a directory within the /QFPNWSSTG directory.
Time to save /QFPNWSSTG SIGNIFICANTLY less than saving /QNTC, to take
advantage of this, consider the following:
Option 21 or 23 Save, vary off the Integrated Netfinity/x-Series Server(NWSD).
Put objects that change frequently, such as files, in one or two subdirectories in
/QNTC. Save changes with the Integrated Netfinity/x-Series Server(NWSD) varied
on.
12
Backing Up Linux in a Partition
IBM server iSeries
Data on Linux can be stored two ways:
Stored on "virtual disks" (NWSSTG) owned by OS/400
Stored on real disk devices owned by Linux
13
Backing Up Linux in a Partition
IBM server iSeries
"Real" disk devices must be backed up using Linux commands
Linux can write to Virtual or Direct Attached Tape Drives
Requires Standard Linux Commands
Allows for file-level backup and recovery
Virtual disks can also be backed up to real or virtual tapes using standard
Linux commands
14
Backing Up Independent ASPs
IBM server iSeries
Independent ASPs (Disk Pools 33-255) Used for Switched Disks &
Clustering
Support for Libraries in IASPS in V5R2
Save/Restore Individual ASPs or Entire System with IASPs
ASPDEV parameter on SAVxxx and RSTxxx Commands
Independent ASPs Require Active State for Save
Save-While-Active Strategy for 24 X 7 Up Time
Restricted State Save - Option 21 (Entire System)
Clustering Fail Over
Switches ASPs to Another System
To Include Independent ASP Data - Option 21
End Cluster Resource Group
Ensure Independent ASPs are in an Active State
15
Recovering Independent ASPs
IBM server iSeries
Independent ASP Configuration Not Saved
ASP Configuration Must be Created During System Recovery
System Recovery Requires
Restore of System and User Data (May or May Not Include
Independent ASP Data)
IPL of System
Configure Independent ASPs through Ops Navigator
Restore of Independent ASP Data
16
Backup/Recovery for Logical Partitions
IBM server iSeries
Backup / Recovery for Logical Partitioned Systems
Each Partition Needs to Be Backed Up - Multiple Tape Drives to Back up
Partitions Concurrently
Recovering Primary Partition - Requires all Partitions to be Ended
Recovery of Secondary Partitions Initiated from Primary (Manual D-IPL)
Logical Partition Configuration Maintained on Primary - Not Saved
17
Recovering Logical Partitions
IBM server iSeries
IBM Business Recovery Services
LPAR Contract to Recover LPAR'd Systems
May Contract for LPAR to Recover Multiple Systems
18
Reducing Your Backup and Recovery Windows
IBM server iSeries
12
11 1
10 2
9 3
8 4
7 5
6
19
Latest Tape Technologies
IBM server iSeries
20
3590E Tape Device
IBM server iSeries
256 Track versus 128 Track.
21
Improved 3590E Save Rates
IBM server iSeries
Up to 114 GB per Hour on New 8xx Hardware
Single Drive
Very Large Files
3:1 Compaction
22
3590E Fibre Channel
IBM server iSeries
Available on iSeries 400 models only
23
3590E Fibre Channel
IBM server iSeries
- Available V5R1
24
Future 3590 Tape Enhancements
IBM server iSeries
- New 3590 Hardware
Doubles Tape Capacity
May Upgrade B and E Tape Drives
Same Existing Performance
SCSI and Fibre Channel Support
Tape Capability
Reuses Current 3590 Cartridges
Reads B and E Formatted Tapes
25
Future 3494 Tape Library Enhancements
IBM server iSeries
3494
Media
Library
26
358x Tape Devices
New LTO (Linear Tape Open) Technology IBM server iSeries
Started shipping on 12/01/2000 (V4R4 or later)
Wide offering, single drive to very large tape library
High performance, high capacity - 384 track
Lower cost than 3590
100GB per cartridge, >300GB with 3:1 compaction
New LTO cartridge with density of *ULTRIUM1
INFO APAR II12621
Compatibility
No compatibility with existing tape devices
Full Interchange with 358x family (IBM and OEM)
HVD (High Voltage Differential) support only on AS/400 and iSeries
Supports Optimum Block - Can DUPTAP to tape device supporting 256K or
higher optimum block size
27
358x Tape Devices
IBM server iSeries
Better performance on iSeries 400
15 MB/s without compaction, 27 MB/s with compaction or 97 GB/hr
Attached via 2749 IOP (iSeries 400)
13 MB/s with compaction or 47 GB/hr
Attached via 2729 IOP (AS/400e)
17 MB/s with compaction or 60 GB/hr
Attached via 6501/6534 IOP (AS/400e)
28
358x Tape Devices
IBM server iSeries
3580 Model H11
- Single host, low cost tape device
- Single drive, single cartridge
29
358x Tape Devices
IBM server iSeries
3583 Models L18/L36/L72
Note: Even though the 3583 can hold 6 drives, only one
host can attach to the media library.
30
358x Fibre Channel
IBM server iSeries
3584 Fibre Channel
- Available V5R1
- No Upgrade, Brand New Drives
- Better Performance
- Same as 3590E Fibre Channel
- Up to 136GB per hour
- Available 7/01/2001
- No Upgrade, New Tape Drives
- LVD Adapters inside Library
31
358x Tape Devices
IBM server iSeries
Word of Caution...
32
Alternate Installation Device
IBM server iSeries
Alternate Installation Device Support
Allows setup of Alternate Installation Device for Alternate IPL Device
REQUIRED for NEW FIBRE CHANNEL TAPE DRIVES!
Define through DST options.
IMPORTANT: If Alternate Installation Device is setup, PID Install CD is
REQUIRED for installs and recoveries from tape.
33
Future Save/Restore for Optical Storage
IBM server iSeries
34
Save-While-Active
IBM server iSeries
35
Save-While-Active
IBM server iSeries
Save-While-Active Restrictions Removed (V4R1)
Once checkpoint reached, locks for most objects dropped.
More applications can restart after checkpoint message CPI3712 sent.
36
Save-While-Active Enhancements
IBM server iSeries
Faster Save-While-Active Checkpoint (V5R1)
Database Changes to Achieve Faster Checkpoint
37
Concurrent Saves
IBM server iSeries
38
Concurrent Saves
IBM server iSeries
Multiple Concurrent Saves Against Single Library (V4R1)
SAVOBJ, SAVCHGOBJ, and QSRSAVO API can now run concurrently against
same library.
No longer receive message that library cannot be allocated.
Break Up Large Libraries to save Concurrently/Multiple Tape Drives
SAVCHGOBJ OBJ(A* B* C* ...L*) LIB(NAME)
SAVCHGOBJ OBJ(M* N* O* ...Z*) LIB(NAME)
39
Concurrent Saves
IBM server iSeries
Generic Values on OMITLIB (V4R1)
SAVLIB/SAVCHGOBJ now support generic values on OMITLIB parameter.
Possible uses:
Omit groups of libraries: OMITLIB(TEMP*).
SAVLIB LIB(*ALLUSR) using 2 tape drives concurrently:
SAVLIB LIB(*ALLUSR) OMITLIB(#LIBRARY A* B* ...L*)
SAVLIB LIB(*ALLUSR) OMITLIB(M* N* ...Z*)
40
Omit Parameter
IBM server iSeries
Omit Parameter on SAVSYS (V4R1)
SAVSYS has new OMIT parameter to omit SAVCFG and/or SAVSECDTA.
OMIT (*CFG)
OMIT (*SECDTA)
OMIT (*CFG *SECDTA)
41
Concurrent Save/Restore using BRMS/400
IBM server iSeries
Run Multiple BRMS Backup Control Groups Concurrently
Reduces Save and Restore Times using Multiple Tape Devices
Submit Multiple Save/Restore Jobs to Multiple Tape Devices
User Must Balance the Control Group Data so Jobs end at Same Time
42
Parallel Saves and Restores
IBM server iSeries
43
Parallel Save / Restore
IBM server iSeries
Parallel Save / Restore (V4R4)
Save a large library, a large object or a list of large objects to multiple tape
drives in parallel - "Spreads data across tapes"
Improves Save Performance for Very Large Objects - not designed for small
objects
End User Interface through BRMS/400 - also supports list of libraries
No special values (*NONSYS, *IBM, *ALLUSR) yet...
Same Number of Drives on Save not "required" for restore
44
Parallel Save/Restore
IBM server iSeries
New for V5R1
Special values *ALLPROD, *ALLTEST, *ALLUSR, *IBM,
*ASP01–*ASP32, and Generics now supported
Objects “spread” at the full library level
Restores for objects saved in parallel using special values are
in serial restore mode (One Tape Device)
List of Libraries - BRMS determines best "spreading" (object or full library level)
45
Online Backup of Lotus Servers
IBM server iSeries
46
Online Backup of Lotus Servers
IBM server iSeries
Save Domino Server While Active
V4R4 BRMS PTF SF65062
Domino 5.02c
No Need to Reach Checkpoint - True Online Backup
No need to End Server or Replicate to another Server for Backup
BRMS/400 handles Recovery Process
Allows 24X7 up time of Domino Server
47
Online Incremental Backup of Lotus Servers
IBM server iSeries
Incremental Backups - Domino Servers
V4R4/V4R5 BRMS PTF SF65708
Domino 5.08.01
V5R1 BRMS PTF SI01742
BRMS/400 handles Recovery Process
Allows Point in Time Restores
48
More Good Stuff!!
IBM server iSeries
49
Good PTFs to Know About
IBM server iSeries
Restore Performance Improvement for Lots and Lots of IFS Objects
(objects in directories)
V4R4M0 - SF65355
V4R5M0 - SF65133
50
Backup and Recovery Book
IBM server iSeries
Backup and Recovery Book (V4R1)
Basic and Advanced Backup and Recovery books combined into ONE book.
Hardcopy Book no longer shipped free.
Fee charged for book.
Hardcopy critical for DASD Configuration and System Recoveries.
Ensure yes on Configuration for Hardcopy Book.
51
Backup and Recovery Information
IBM server iSeries
Read the book EVERY time a new release comes out?
You MUST use the correct version of the book with each new release!
52
New Backup and Recovery Information
V4R5 Backup and Recovery Book IBM server iSeries
New Step by Step Restore Instructions when Recovering Entire System to the same
system - See Appendix G.
New Steps for Moving Previous Release User Data to a System at a Higher Release -
See Chapter 15.
New steps also available on Supportline Knowledge database
http://as400service.rochester.ibm.com/supporthome.nsf/Document/10000051
53
Save/Restore Limits - V5R1
IBM server iSeries
Save/Restore Limits - Enhancements
Number of Private Authorities that can be Saved for a User Profile
Number of User Profiles that can be Saved (previous limit 116,500)
Restore User Profiles (RSTUSRPRF) no longer requires Restricted State
unless restoring all User Profiles
Restore User Profiles (RSTUSRPRF) and Restore Authority (RSTAUT) support
300 values on USRPRF parameter (previous limit 50)
Increased number of Unrelated Files that can be saved from a Single Library to
360,000 (previous limit 55,000)
Save/Restore Displays, Printouts and Outfiles Handle Object Sizes Larger than
2 GB
Maximum Size of Savefile Increased to 1 TB (previous limit 256 GB)
54
V5R1 BRMS Enhancements
IBM server iSeries
Entire System Default Backup Control Group - *SYSTEM
Green Screen and GUI
Option 21 Backup Entire System on Green Screen
55
BRMS Network Feature Supports TCP/IP
IBM server iSeries
Available for V5R1
PTF SI01742 to Enable TCP/IP Networking on V5R1 System
PTF SF65708 on V4R4/V4R5 System Communicating with V5R1 System
Enabled for
TCP/IP Networking
PTF SI01742 on any V5R1 System using SNA to Communicate with V5R1
System
Enabled for TCP/IP Networking
http://www-1.ibm.com/servers/eserver/iseries/service/brms/brmstcpip.htm
56
V5R1 BRMS Enhancements
IBM server iSeries
BRMS Goes GUI!
- Ops Navigator Interface
- Easy to Use
- Wizards
- Equivalent Backup Capability - Save Menu Options 21, 22,23
- Tape Inventory Management
- Full System Recovery Report
- Complete BRMS Function in Future Releases
- Spooled File Backup
- Media Library Support
- Media Movement
- Time to Switch if Still Using:
- Save Menu Options
- CL Command Programs
- Operational Assistant Backup
- Ops Navigator Backup
57
BRMS OpsNav Capabilities - V5R1
IBM server iSeries
58
BRMS OpsNav Future Release Enhancements
IBM server iSeries
59
BRMS Future Release Enhancements
IBM server iSeries
60
Recovery Enhancements
IBM server iSeries
61
Recovery Enhancements - V5R1
IBM server iSeries
ALWOBJDIF(*FILELVL) on RSTLIB and RSTOBJ Commands
Allows restore of a physical file that has file level differences
Eliminates renaming of files on restore (e.g. File0001, File0002)
Use when trying to restore over existing files with file/member level difference
62
Disaster Recovery
IBM server iSeries
63
Disaster Recovery
IBM server iSeries
Recovering Your Business Depends on:
Recovery
Plans
Network
Connectivity
64
World Trade Center Tragedy
IBM server iSeries
September 11, 2001 - Largest Tragedy in U.S.
History
No Warning - Immediate Red Alert
Primary Recovery Site Utilized was Sterling Forest, NY
40 miles north of New York City
Highly Equipped and Staffed
65
World Trade Center Tragedy
IBM server iSeries
Major Data Centers not Located in Financial
District
Big Loss was Office Equipment and Office Space
IBM Helped
Restore Networks
Found Temporary Office Space
Provided Phones, Laptops & Workstations
Brought in Servers to Handle Increased Website
Traffic
66
Lessons Learned from WTC Tragedy
IBM server iSeries
Major Transportation Mode Crippled
67
Rapid Recovery for iSeries and AS/400 Replication
IBM server iSeries
68
iSeries and AS/400 Replication
IBM server iSeries
IBM Site
Hotsite
Customer
Customer
69
iSeries and AS/400 Replication Options
IBM server iSeries
70
Remember.....Test Your Recovery!!!
IBM server iSeries
71
Topic 19: Reference Material
IBM server iSeries
l
ia
er
at
M
ce
en
er
ef
R
72
Reference Material
IBM server iSeries
Backup and Recovery; SC41-5304-02(V4R3)
Backup and Recovery; SC41-5304-03(V4R4)
Backup and Recovery; SC41-5304-04(V4R5)
Backup and Recovery; SC41-5304-05(V5R1)
Automated Tape Library Planning & Management;
SC41-5309(Version 4)
Integrated File System Introduction; SC41-4711
CL Reference; SC41-4722
ADSTAR Distributed Storage Manager General
Information;GH35-0114
The System Administrator's Companion to AS/400 Availability and
Recovery Redbook; SG24-2161(V4R2)
Backup Recovery and Media Services/400; SC41-4345-01
A Practical Approach to Managing Backup Recovery and Media
Services/400 Redbook; SG24-4840-00
73
Trademarks and Disclaimers
8 Copyright International Business Machines Corporation 2001 IBM server iSeries
References in this document to IBM products or services do not imply that IBM intends to make them available in every country.
The following terms are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both:
Lotus, Lotus Domino, Lotus Quickplace, Freelance, and Word Pro are trademarks of Lotus Development Corporation in the United States, other countries, or both.
Tivoli and NetView are trademarks of Tivoli Systems Inc. in the United States, other countries, or both.
C-bus is a trademark of Corollary, Inc. in the United States, other countries, or both.
Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.
PC Direct is a trademark of Ziff Communications Company in the United States, other countries, or both and is used by IBM Corporation under license.
ActionMedia, LANDesk, MMX, Pentium and ProShare are trademarks of Intel Corporation in the United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other countries.
SET and the SET Logo are trademarks owned by SET Secure Electronic Transaction LLC.
Other company, product and service names may be trademarks or service marks of others.
All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual environmental costs and
performance characteristics may vary by customer.
Information in this presentation concerning non-IBM products was obtained from a supplier of these products, published announcement material, or other publicly available sources and
does not constitute an endorsement of such products by IBM. Sources for non-IBM list prices and performance numbers are taken from publicly available information, including vendor
announcements and vendor worldwide homepages. IBM has not tested these products and cannot confirm the accuracy of performance, capability, or any other claims related to non-IBM
products. Questions on the capability of non-IBM products should be addressed to the supplier of those products.
All statements regarding IBM future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. Contact your local IBM office or IBM
authorized reseller for the full text of the specific Statement of Direction.
Some information in this presentation addresses anticipated future capabilities. Such information is not intended as a definitive statement of a commitment to specific levels of
performance, function or delivery schedules with respect to any future products. Such commitments are only made in IBM product announcements. The information is presented here to
communicate IBM's current investment and development activities as a good faith effort to help with our customers' future planning.
Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will experience
will vary depending upon considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed.
Therefore, no assurance can be given that an individual user will achieve throughput or performance improvements equivalent to the ratios stated here.
Photographs shown are of engineering prototypes. Changes may be incorporated in production models.
74