240 likes | 381 Views
iSeries Rocks. Table of Contents. Information Lifecycle Management Information Lifecycle Management Diagram Overview Incoming Data and Systems I-Series Center of the Universe for Data I-Series Center of the Universe for Hardware Primary Storage and Hardware Level Replication
E N D
Table of Contents • Information Lifecycle Management • Information Lifecycle Management Diagram • Overview Incoming Data and Systems • I-Series Center of the Universe for Data • I-Series Center of the Universe for Hardware • Primary Storage and Hardware Level Replication • Primary Storage and Software Level Replication • Network Attached Storage • Content Attached Storage - Worm Disk • Juke Boxes • Tape Libraries • Virtual Tape Libraries • Overview Outgoing Data and Systems • Outgoing Feeder Systems • Network Attached Storage - Multi System • Other
Information Lifecycle • The most visible negative effect of the vast and mushrooming amount of content is cost – of hardware and software and the personnel needed to support it-a problem exacerbated by the common practice of treating all information as “mission-critical” and therefore to be support by the best, highly performing, most reliable technology. • ILM promises to align a company’s information storage infrastructure with it Business Needs • LEVELS • Creation of Data • Extremely Active • Very Active • Active • Semi-Active • Semi-Inactive • Inactive • Off-line • Destruction of Data
End Part One • The squeaky wheel may get the grease, but it is also the first one to get replaced.
End Part Two • Everyone seems normal until you get to know them.
Other • SMP • Multiple Processors working on one JOB • Rebuild large logical after major system failure • Process long running nightly jobs • QQRYDEGREE Parallel processing degree • *NONE • *IO • *OPTIMIZE • *MAX • CHGQRYA • *NONE • *IO • *OPTIMIZE • *MAX • Number of task • O/S400 Maximum Capacities
Other • SMAPP -- EDTRCYAP Command • System access path recovery time . . . 150 *SYSDFT, *NONE, *MIN, *OFF, Recovery time • System access path recovEstimated system access path recovery time . . . : 133 Minutes • Total not eligible recovery time . . . . . . . . : 0 Minutes • Total disk storage used . . . . . . . . . . . . . : 5608.943 MB • % of disk storage used . . . . . . . . . . . . . : .088 ery time • Under SMAPP, the system looks at all access paths to determine how it can meet the specified target times for recovering access paths. It may not choose to protect an access path that you consider critical. • When the system determines how to meet the target times for recovering access paths, it considers only access paths that are not explicitly journaled.
END • We must Believe in luck how else can be explain the success of those we do not like