solutions for common z/os storage management problems and

66
Solutions For Common z/OS Storage Management Problems And Issues Mark Jula and Todd Lipp Rocket Software November 2020 Session 6BD

Upload: others

Post on 01-Oct-2021

1 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Solutions For Common z/OS Storage Management Problems And

Solutions For Common z/OS Storage Management Problems And Issues

Mark Jula and Todd Lipp

Rocket Software

November 2020

Session 6BD

Page 2: Solutions For Common z/OS Storage Management Problems And

How Does Storage Management Affect Organizations?

• Storage affects many key

operational aspects of your

organization

• Application performance,

throughput, and availability

• Effective and efficient storage

device utilization

• CPU utilization & batch

processing

• DR planning: Backup &

Recovery, Data loss, Regulatory

compliance

Page 3: Solutions For Common z/OS Storage Management Problems And

How Does Storage Management Affect Organizations?

• Effects of Storage Issues can be easily masked or overlooked

• Performance impacts related to storage issues

• Growing requirements for CPU, storage devices and media: “cost of doing business”

• Planned outages (e.g. ICF Catalog maintenance) are a “necessary evil”

• Hidden problems that can cause unplanned outages or application failures

• Data Integrity - Failing/struggling DR exercises

Page 4: Solutions For Common z/OS Storage Management Problems And

How Does Storage Management Affect Organizations?

• Storage Administration Staff Stretched to Keep up

• Monitoring daily/weekly/monthly activity

• Device management

• “Process of elimination” problem resolution

• Wasted time on repetitive tasks

• Lack of time to research what’s going on in the

system

• Labor intensive activities such as backup & recovery

• Learning Curve

Page 5: Solutions For Common z/OS Storage Management Problems And

Common HSM Problems Part1 HSM Issues And Problems – The Importance of HSM Auditing and Reporting Tools

Page 6: Solutions For Common z/OS Storage Management Problems And

How Is My HSM Environment Running?

• How did last nights HSM processing go?

• Are repetitive migration failures

affecting performance daily?

• Are HSM migration policies in tune

with the current business

environment, or are they draining

CPU resources and wasting DASD?

Page 7: Solutions For Common z/OS Storage Management Problems And

Why Are HSM Tools Important?

➢Report on the success rate (and cost) in migrating and backing up what is expected daily✓Why? Not knowing the failures will lead to higher disk occupancy (and disk costs) and missing

backup (with business risks)

➢Make sure that all the tapes that HSM has been using over the last xx years are still present ✓Why? HSM and the tape Management System are isolated z/OS subsystems with no tight

integration and thus a high risk for inconsistencies

➢Have the best guarantee that all the controlling information for managing the migration and backups is still valid✓Why? When problems are unknown, invalid controlling information will only be visible when a

recall or a recover fails for a production user

➢Identify data sets that are constantly transported between disk and tape✓Why? “Thrashed data” can be a serious waste of resources inside HSM

Page 8: Solutions For Common z/OS Storage Management Problems And

Why Are HSM Tools Important?

➢Be sure that the daily time windows for migration and backup are sufficient to handle all DASD volumes✓Why? Unhandled volumes will probably not be handled tomorrow as well, read: data sets on

these volumes will never be migrated or backed up

➢Do not maintain migrated or backed up data that is no longer really required for business reasons✓Why? A large percentage of unneeded aged data makes the management by HSM much heavier

than can be justified by business reasons

➢Establish a quick and easy recovery procedure in case you ever lost an HSM migration tape or backup tape✓Why? As long as the tape has not been overridden, the controlling information for HSM can be

reconstructed but it is a very time consuming process with standard HSM tools

➢Reorganize the HSM control data sets when needed (= now), not at the end of the month✓Why? Standard reorganization processes lead to an application interruption

Page 9: Solutions For Common z/OS Storage Management Problems And

IBM Advanced Audit for DFSMShsm Overview

• All Audits Are Comprehensive and Fast➢Eliminates the need to execute

multiple audit commands for a single control data set

• Automated User-Selected Fixes➢Select fixes from a provided list or

create your own ➢Errors and fixes are organized by

error type in an ISPF panel

• Fix JCL and Commands are Automatically Generated➢Apply fixes to one, some, or all data

sets in a problem class

• Quickly Verifies the Integrity of DFSMShsm Metadata➢ The ability to recall data➢ The ability to recover data

• The ability to recycle tapeAuditsfor the MCDS, BCDS and OCDS➢Verifies contents➢Identifies inconsistencies and errors ➢Compares contents to catalogs and

tape management inventory➢ s➢ Identifies out-of-sync conditions

with other metadata

Page 10: Solutions For Common z/OS Storage Management Problems And

IBM Advanced HSM Reporter Overview

• HSM Control Data Set (CDS) Reporting • Visualize record contents in the CDSs• Filter and sort by:

• Size • Migration status• Backup versions • Other …

• Customized criteria• Identify data sets by creation date• Identify by migration date• Identify by last used date• Identify by size• Identify by recall thrashing• Other …

• HSM Health Reports• Reports status of HSM automatic functions

(volume oriented)

• HSM LOGX/Y Reporting • Report on HSM activity performed since

the last SWAPLOG and found in the LOGY dataset

• A SWAPLOG is usually performed daily or when log is full

• An exact copy of the LOGY file is required• Many LOGY datasets can be concatenated for

analysis

• Report on historical information• Migration / recall activities• Backup / recovery activities• Other

• Planning and trending reporting

• Volume Dump Reporting• Reports HSM Full Volume Dump

Information• Ability to recover volume or single data set

Page 11: Solutions For Common z/OS Storage Management Problems And

Common HSM Problems Part2 I Have Way Too Many HSM Tapes In My Data Center

Page 12: Solutions For Common z/OS Storage Management Problems And

IBM Advanced Archive for DFSMShsm

Archiving Aging HSM Data to the Cloud and reducing costs and HSM clutter• Enables new storage tier in the ILM hierarchy which is

not directly managed by DFSMShsm

• Archived data will be cataloged and removed from MCDS• Optionally remove associated BCDS entries• OCDS entries will also be cleaned up as data is

moved from DFSMShsm managed tape

• Directly processes the DFSMShsm control datasets and ML2 tapes, no additional DFSMShsm overhead is incurred

• Coordinates file movement to the cloud based on batch job parameters

• Automatically pulls the requested file back from the object store and writes it to a DFSMShsm ML2 tape

• Updates MCDS and OCDS on recall from cloud

• Initiates a standard DFSMShsm recall for the file

• Benefits:

• Reduce the TCO of DFSMShsm by:• Reducing DFSMShsm managed inventory• Reducing cost of storage

• Allows less frequent DFSMShsm processing saving CPU cycles

• Consolidates Archive Tapes that are underutilized

• No DASD H/W vendor requirement – it’s software

zPrimary

(ML0)

ML1

ML2

Page 13: Solutions For Common z/OS Storage Management Problems And

DFSMShsm

• Aged data moves between active disk to other levels

• ML1 compressed data on disk

• ML2 compressed data on tape

• Compressed data reduces space --> less cost

• Tape is less expensive than disk, but what is happening with all that ML2 data?

Flash

Disk

Tape/VTL

zPrimaryStorage

(ML0)

ML1

ML2

Page 14: Solutions For Common z/OS Storage Management Problems And

How much data remains in DFSMShsm

76%

58%

43%

34%

26%

1yr+ 2yr+ 3yr+ 4yr+ 5yr+

Case 1

78%

69%

60%55%

37%

1yr+ 2yr+ 3yr+ 4yr+ 5yr+

Case 2

Page 15: Solutions For Common z/OS Storage Management Problems And

Archiving Aging HSM Data to the Cloud

• Create an ML3 level of archive data

• Where the SLA is right for you• Public

• Private

• Hybrid

Flash

Disk

Tape/VTL

Cloud

zPrimaryStorage

(ML0)

ML1

ML2

(ML3)

Page 16: Solutions For Common z/OS Storage Management Problems And

Advanced Archive Now Supports Archive From L0

• Archive selection can now include non HSM managed data on disk

• Allows for the introduction of an archive strategy for any system application or workload

• Still allows for automatic recall

• New parameter required to designate archive selection

Page 17: Solutions For Common z/OS Storage Management Problems And

Archive Selection

Batch task executed on an as needed basisOn initial implementation this would be frequent to get the backlog of eligible data archivedOn going processing would be scheduled based on the amount of new data created

Reads the DFSMShsm Migration Control Data Set (MCDS) to identify the migrated data sets that are eligible based on the selection criteria

Data can be selected based onDays since last reference as an extension of DFSMS Management Class PoliciesUser specified selection criteria

Supports Multiple Criteria for selectionDays since creation, since last used, since migration, until expirationData set name and Management Class patterns

Page 18: Solutions For Common z/OS Storage Management Problems And

Archive Selection using Management Class

Archive Days policy is defined for selected Management Classes

Archive Group is defined to identify the Cloud Definition that will be used or colocation of the data on Archive tapes

Page 19: Solutions For Common z/OS Storage Management Problems And

Archive Selection using CRITERIA DDSupported criteria

DSN=pattern, XDSN=pattern, DSN>ddname, XDSN>ddname

MGMTCLAS=pattern, XMGMTCLAS=pattern, MGMTCLAS>ddname, XMGMTCLAS>ddname

#DAYS_SINCE_CREATE=0-999

#DAYS_SINCE_LASTUSED=0-999

#DAYS_SINCE_MIGRATED=0-999

#DAYS_UNTIL_EXPIRATION=0-999

MIGRATION_DATE=YYYY.DDD-YYYY.DDD or MM/DD/YYYY-MM/DD/YYYY

EXPIRATION_DATE=YYYY.DDD-YYYY.DDD or MM/DD/YYYY-MM/DD/YYY

Page 20: Solutions For Common z/OS Storage Management Problems And

Archive Processing

Reads the MCDS and ML2 tape data for the file and writes to Archive media

Deletes corresponding entries from DFSMShsm

Changes the MIGRAT ICF catalog entry to RCHIVE

Updates the Advanced Archive DB

Optionally deletes DFSMShsm backup versions

Also supports archival to tape

Cloud Storage options supported• IBM Cloud Object Storage• SOFTLAYER• Amazon S3• HDS HCP• FTP

Page 21: Solutions For Common z/OS Storage Management Problems And

Advanced Archive Restore

Initiated by

Attempt to access the data

Batch restore processing

Basically just a reverse of the Archive process.

Archived data is copied to a new ML2 tape HSM CDS is updated with the information about the restored file MIGRAT ICF catalog entry is restored For batch restore, Recall processing is optionally initiated.

PARM=SIM is your friend

Simulates processing for

• Archive (PGM=AXQRCHIV)

• Restore (PGM=AXQRESTR)

• Recycle (PGM=AXQRCYCL)

• Cleanup (PGM=AXQCLNUP)

Page 22: Solutions For Common z/OS Storage Management Problems And

Archive Reporting• ISPF interface to display

archived files and related information

• Batch reporting of

archived files and related information

• Batch reporting of Archive DB update

log records

Page 23: Solutions For Common z/OS Storage Management Problems And

Tape Issues In GeneralMy VTS is filling up and we may have to upgrade costing us $$$$

Page 24: Solutions For Common z/OS Storage Management Problems And

IBM Cloud Tape Connector for z/OS

• For mainframe static archival or point-in-time backup data

• Captures tape or disk data stream to disk cache; handles data blocking for object storage; pushes data to cloud

• Also allows movement of data directly from disk to cloud

• Connects to• CLS - Cleversafe• FTP - File transfer protocol• HCP - Hitachi Content Platform• S3 - Amazon Simple Storage Service• SFT - IBM SoftLayer

• Can be public, private or hybrid cloud implementation

GDPS

Grid

DS8K

DF

SM

S

LocalRemote

HSM

CDS

TS7700

IBM Cloud Tape Connector for z/OS

Amazon

Page 25: Solutions For Common z/OS Storage Management Problems And

IBM Cloud Tape Connector• Allows z/OS to Read and Write Data to Object Storage Environments, using a Started Task CUZCLOUD

• Clones Tape and DASD I/O and Manages Cloud Data Transfer in the Background

• Controls allow for SMS Storage Class, Esoteric Unit and DSN filtering

• Can Process Existing Tape or DASD Data

• Data processed from disk must be sequential format

• Retention of Cloud Based Data Managed Within the Product

• Software Solution: No Hardware or Additional Software Requirements

• zIIP enabled (can be disabled)

• Support for encryption of data in flight

• Support for z/EDC compression

• AT-TLS enabled

• ICSF required to do certain hashing that is necessary for S3 and Cleversafe API requests

• Parmlib members can be Encrypted

• The Cloud Connector Repository is a z/OS VSAM Keyed Sequential data set (KSDS)

• Maintains Its Own Cloud Based Backup to Facilitate Alternate Site Recovery

• Sysplex enabled: CTC employs ENQ/DEQ logic to keep Repository update integrity across the LPARs

Page 26: Solutions For Common z/OS Storage Management Problems And

IBM Cloud Tape Connector• Inventory and Data Recovery

• Product maintains its own inventory which is completely independent of the source data

• Customer is free to delete uploaded disk and tape data and release those assets for current workload

• Product inventory can be easily reviewed via the ISPF interface %CUZVP11

• Data set restore can be initiated from the ISPF interface, one file at a time or groups of files at a time

• ISPF driven restores can direct the cloud file to disk or tape regardless of where it was captured

• Large block tape datasets ( > 32k ) cannot be directed to disk

• ISPF interface is highly customizable (CSETUP command)

• SAF authority is verified upon restore

• A Tape Compare Utility batch utility is provided

Page 27: Solutions For Common z/OS Storage Management Problems And

IBM Cloud Tape Connector Key Uses

• Offload of Cool/Cold Data

• Hot transactional data is NOT suitable for object storage• Majority of data growth is long lived, unstructured data• Backups, archives, etc.

• Disaster Recovery

• Clients can eliminate physical transportation costs of tapes• Clients can reduce on site redundant storage costs for replication• Clients can reduce network costs

• Tape Elimination

• This can be challenging unless the customer is ready to significantly change their operational procedures• A good companion product to consider is Virtual Tape Emulation (VTE aka VTFM)

Page 28: Solutions For Common z/OS Storage Management Problems And

ISPF Interface: Main Menu

Page 29: Solutions For Common z/OS Storage Management Problems And

ISPF Interface: Defining Cloud Servers

Page 30: Solutions For Common z/OS Storage Management Problems And

CTC Staging is in Effect

Page 31: Solutions For Common z/OS Storage Management Problems And

Backup Filter Criteria

Page 32: Solutions For Common z/OS Storage Management Problems And

Dataset Status Before & After Backup with Cloud Tape Connector

Page 33: Solutions For Common z/OS Storage Management Problems And

Catalog Issues and Problems How can I keep my catalogs available 24/7?

Page 34: Solutions For Common z/OS Storage Management Problems And

Advanced CatalogManagement

➢Backup and Recovery

➢BCS Reorganization

➢ICF Catalog Diagnosis and Repair

➢Disaster Recovery Support

➢Catalog and VSAM Data Set Management

➢Splitting and Merging Catalogs

➢Maintenance and Repair Features

➢Tivoli Enterprise Portal Integration

34

Page 35: Solutions For Common z/OS Storage Management Problems And

Recognize Your Risks

ICF Catalogs Are Extremely Critical

to z/OS

All current and migrated data is

cataloged

Cataloged data is not accessible if the catalog is not available

What Makes This Critical? You

Probably Have:

A very high number of data

sets

A very low number of catalogs

35

43

1712

8 85

0

10

20

30

40

50

1 2 3 4 5 6-20

Catalog Data Distribution

➢ You have hundreds of thousands of data sets

➢ They are cataloged across 20-50 catalogs

➢ Yet the majority of your data sets could be cataloged in as few as 2-3 catalogs

➢ An unplanned outage or catastrophic failure of one catalog could result in significant downtime for critical business applications

Page 36: Solutions For Common z/OS Storage Management Problems And

Move Entries While Data Sets Are in Use

➢Processes an alias level where data sets are open to move them non-disruptively from one catalog to another

➢One alias level can be processed at a time

➢Communications with all systems in a sysplex sharing access to the catalog whose entries are to be moved must be established

➢A communications started task within ACM is required to be running on all systems sharing the catalogs

➢Complete integrity is maintained for all data sets

➢Restart capability supported for WHILE-OPEN processing

➢Simulation capability allows advance testing and error correction

MERGECAT WHILE-OPEN

Command

36

Page 37: Solutions For Common z/OS Storage Management Problems And

Catalog Problems

Things Go Bump in the Night …

➢Volumes crash and have to be restored

➢Catalogs (BCSs and VVDSs) become corrupted and have to be restored

➢Data sets become uncataloged, don’t ever get cataloged, or are cataloged to the wrong catalog

➢Data sets are cataloged, but don’t exist

➢CAS or caching problems

37

Page 38: Solutions For Common z/OS Storage Management Problems And

BCS Forward Recovery

➢Forward Recovery of a BCS

38

VVDSBCS

VOL001

Volume at time

of last backup

All

SMF

Data

VVDS

VOL001

Volume after

recovery

BCS

ACM RECOVER

Command

BCS

P.I.T.

Copy

RECOVER BCS(UCAT.TST1) –

INFILE(BACKUPDD) –

FORWARD(SMFFILE(SMFDD))

Page 39: Solutions For Common z/OS Storage Management Problems And

39

Reorganize While Open

Why/When Do I Need This?

➢Catalogs with a 24x7 availability requirement

➢Catalogs with index/data structural problems

➢Creeping key problem in the BCS

➢Major volatility in the BCS (caused by lots of data set deletes and defines)

➢Catalogs that have IMBED/REPLICATE specified, and scheduling downtime to remove them is difficult

Page 40: Solutions For Common z/OS Storage Management Problems And

Advanced Catalog Management and TEP

Provides an Overview of Key Catalog Information

40

Drill Down to Get Details When a Problem Occurs

Page 41: Solutions For Common z/OS Storage Management Problems And

Allocation Issues Prevent Space Abends and deal with invalid or outdated JCL references

Page 42: Solutions For Common z/OS Storage Management Problems And

Tivoli Advanced Allocation Management -Overview

Tivoli Advanced Allocation Management (TAAM) avoids and recovers from x37 type ABENDs that are caused by:

➢Insufficient disk space allocations

➢Unavailable DASD extents

➢Out-of-space conditions

Provides enhanced allocation management (EAM) features to provide centralized control of DASD volume usage and standardized allocation attributes

Provides the option of advanced volume selection (AVS) for a non-SMS managed data set at initial allocation time to enforce standards

Provides volume group support that enables you to define DASD groups from which to select additional volumes as needed

Features

Space Related Abends Sx37

➢Are a very common situation in batch processing

➢Have a very disruptive impact for Service Level Agreements and deadlines

Some Typical Error Situations:

➢Requested Amount of Primary Space is not available

➢Secondary Space is needed but not defined

➢Requested Amount of Secondary Space is not available

➢The current volume is out-of-space and more volumes are needed

➢Set rules for the allocation of space on the additional volumes

➢Duplicate Catalog Entry

Tivoli Advanced Allocation Management (TAAM) works with a rule-based mechamism:

➢Set the default handling rules for the enabled error situations

➢Define up to 30+ filters for datasets to be intercepted by TAAM

➢With individual handling rules and overrides of the defaults

Page 43: Solutions For Common z/OS Storage Management Problems And

Advanced Allocation Manager

➢ Avoid and recover from X37 type abends and NOTCAT2 situations

➢ Handles all DASD data sets, both SMS and non SMS-managed

➢ Maximizes use of the current volume before attempting to allocate additional volumes

➢ Limits fragmentation

➢ Greater control with SMS and non-SMS

➢ Non-SMS volume group definition

➢ Re-direction of unit type➢ Allocation based on variety of

variables

➢ Non-SMS placement based on resource metrics

➢ Set or override over 50 allocation attributes

Make DATACLAS, override JCL

43

43

1712

8 85

0

10

20

30

40

50

1 2 3 4 5 6-20

Catalog Data Distribution

TEP integration and take-action makes it easy to see issues and

intervene

Page 44: Solutions For Common z/OS Storage Management Problems And

TAAM Architecture

TAAM runs as a started task

TAAM sets intercepts (aka

hooks ☺) into z/OS allocation and end-

of-volume logic during TAAM initialization

Basic product-control options are specified in a PDS control member

called an OPTIONS member

“Which situations to intercept" and “Which objects to

intercept" are specified in a PDS control member

called a RULEDEFS member

The user can communicate with product through the supplied ISPF dialog or through

operator commands

Overview statistics can be viewed via

the dialog

Detailed statistics can be obtained and reported by requesting SMF recording and

reporting on them using a supplied reporting utility

Page 45: Solutions For Common z/OS Storage Management Problems And

Tivoli Advanced Allocation Management STC Tape

Tivoli Advanced Allocation Management -Architecture

Page 46: Solutions For Common z/OS Storage Management Problems And

Other Storage Features available in TAAM

System related functions

➢Trace and diagnose the logic that leads to the applied rule

➢Configure message handling

➢Check syntax of rules before their activation

➢ISPF interface

➢Enables/Disables TAAM

➢Activation of new rules

➢RACF integration

➢View Statistics

➢SMF logging of TAAM actions

➢SMF detailed reporting

➢Console commands

Reduce the size of the secondary extent to the largest available extent on the volume

Write an End-Of-File marker on newly allocated datasets

Release unused space when closing a dataset

Dynamically increase number of Directory Blocks for a PDS

Alter JCL allocation attributes on selected data sets during allocation

Page 47: Solutions For Common z/OS Storage Management Problems And

Backup and Recovery Are you confident that you are backing up all critical data sets?

Are you concerned that you are wasting resources on redundant backups?

Page 48: Solutions For Common z/OS Storage Management Problems And

Tivoli Advanced Backup and Recovery

ACDI

• Identifies the data used by the application

• Produces the list of critical data sets to be backed up

ABARS Manager

• Performs and manages ABARS application backup and recovery

Incremental ABARS

• Reduces both the size and elapsed time of ABARS backups

• Manages application cycle behavior

CBTI

• Tracks all backups; provides recovery JCL

• Provides reporting to ensure critical data sets are backed up

Fast Replication Services

• Exploits storage subsystem fast replication functions

• Instantaneous application backup and recovery

Page 49: Solutions For Common z/OS Storage Management Problems And

ACDI Overview

Setup and Configuration Parameters

• Use default values or customize for specific applications

• Build critical data set list

• Formats include: DFDSS, FDR, CA-DISK, ABARS or LIST

• ALL input data is classified as critical by default

• Specify using scheduler system, such as CA7

• Specify using ISPF

Levels of Filtering

• Universal filters used by all applications

• Global filters used by multiple applications

• Local Filters used by specific application

• Job names

• Data set names

• Device types (UNITs)

• Volume serials

• System IDs (LPARs)

Data Set Names List is Generated

Page 50: Solutions For Common z/OS Storage Management Problems And

Application Data Set Usage Tracking

• Information collected from start to end of application cycle

• Started task captures application specific data set usage

• Inspects application job JCL when executed

• Updates ACDI database

• All referenced data set names

• Data set usage based on SMF records

• Input, output, delete, rename, etc.

Data set usage is automatically tracked and

recorded for each application’s batch

cycle

• Automatic tracking and recording of data sets used during each application’s batch cycle

• Unique setup and configuration parameters can be specified for individual applications

• Application defined by registering application job names

• Application critical data set filtering

• Automatic generation of the current list of application data sets for backup

Critical Data Discovery

Page 51: Solutions For Common z/OS Storage Management Problems And

CBTI Overview

➢ Complete tracking of all backups created in the z/OS environment regardless of the data mover used

➢ DFSMShsm incremental backup/automatic dump, ARCINBAK, ABARS

➢ DFSMSdss, IEBGENER, IEBCOPY, IDCAMS,FDR, SORT, CA-DISK, etc…

➢ Reports to compare the current application critical data set list to the backup inventory

➢ Reports that show multiple backup copies of the same data set (perhaps redundant)

➢ Locate and restore any data set in the backup inventory

➢ Reporting for applications, auditors and others who are inquiring about backup information

➢ Updates the inventory database with results

➢ Displays all recorded backups

➢ BackupEnd Feature reports backup status for all application critical data sets

➢ Dynamically builds restore job➢ Restore any data set or groups of data sets

➢ Restore data for application to specific application cycle points (current, -1, -2, ..)

➢ Automatically build the required JCL and control cards

➢ Easily rename restored data sets

➢ ISPF interface for ease-of-use

Page 52: Solutions For Common z/OS Storage Management Problems And

ABARS Manager Overview

Manages DFSMShsm ABARS backup and recovery

Provides ABARS functional enhancements and reporting

A utility for all application data backup and recovery

All application data is stacked together on the output media

Single or multiple data sets can be recovered/renamed

Entire application can be recovered at a specific synch point

Recovery can be “tiered” - most important applications first

Features provide for both onsite recovery and D/R recovery

Page 53: Solutions For Common z/OS Storage Management Problems And

ABARS Manager Overview

ABARS Backup uses the Critical Data Set List in

the SDS generated at

the end of each application

cycle by ACDI

An ABARS Manager batch job is used to perform the

ABARS backup

The ABACKUP Results are

Viewable via the ABARS

Manager ISPF Interface

Recovery is possible at the

data set level or at the

aggregate level

Minimal DFSMShsm

environment required at the

D/R site

ABARS Activity Reporting is

Available

Page 54: Solutions For Common z/OS Storage Management Problems And

Incremental ABARS Overview

➢Reduces the elapsed time of the nightly backup, by backing up changed data sets only

➢Application data set change activity monitors data set usage information in real time using SMF records

➢Uses a base + incremental methodology

➢Automatically recovers the application cycle data from the base to the most current incremental

➢Can be overridden if necessary to recover base + x number of days

➢Recovers only the most current copy of each data set

➢Prevents “back-leveling” data from an older copy

Page 55: Solutions For Common z/OS Storage Management Problems And

Fast Replication Services Overview

➢Storage-aware backup and recovery solution➢ Integrates storage processor fast-replication

facilities

➢Performs instantaneous backups

➢Reduces recovery time

➢Simplifies disaster recovery procedures

➢Uses less CPU, I/O and storage resources

➢Invoked and managed using TABR ➢ACDI critical data set discovery

➢Fast Replication backup and optional offload

➢CBTI backup inventory management

➢Fast Replication and offload restore

➢ Using Fast Replication Services➢ Define the backup profiles➢ Use SDS created by ACDI or create a

new SDS ➢ Select desired backup profile

➢ Backup only – no offload permitted➢ Backup with offload required➢ Offload attributes

➢ Submit backup job➢ Backup results recorded in FRZ

repository and TABR inventory database

➢ Optionally offload Fast Replication backup to tape

➢ Restore from Fast Replication backup or offload

Page 56: Solutions For Common z/OS Storage Management Problems And

So … What about Monitoring?

56

Space – What’s available at the

Group, Volume and Dataset levels?

Performance –Where are the slowdowns?

Cache - Is it being utilized effectively?

Shared DASD –Who is impacting

this volume’s response time?

Applications – Are throughput

problems related to DASD?

I/O Subsystem –Can balancing be

improved?

Tape devices – How many slots are in use in the ATL?

DFHSM – Which user is generating

recalls?

RAID - Which logical volumes

share physical disk media?

Productivity - How can routine storage

tasks be automated?

What are yours?

Page 57: Solutions For Common z/OS Storage Management Problems And

OMEGAMON for Storage on z/OS➢ Real-time and historical mainframe STORAGE

monitoring

➢ Powerful alerting and “Take Action” capability

➢ Daily Storage management capability and functions

➢ Full GUI and E3270UI user interfaces

➢ A wide breadth of mainframe storage information:

➢ Space and Performance management (storage groups all the

way down to data set groups, define your own for reporting)

➢ Tape / VTS

➢ Channels (FICON), Control Units, CACHE

➢ DFSMShsm (View and administer your active HSM queues,

control Datasets, etc. )

➢ DFSMShsm / DFSMSdss / ICKDSF / IDCAMS online toolkit

➢ Batch JCL creation from toolkit – any JCL

➢ SMS constructs

➢ z/OS Copy Services monitoring

➢ DASD & Tape drive physical device support

➢ Ability to see all logical volumes on a physical disk

➢ Powerful applications view

➢ Powerful real time dataset view and action capability

➢ Integration capabilities from TEP interface to

➢ Dynamic Workspace Linking to:➢ IBM Advanced Reporting & Management for

DFSMShsm (ITARD)

➢ IBM Advanced Audit for DFSMShsm (ITAAD)

➢ IBM Tivoli Advanced Catalog Management (ITACM)

➢ IBM Tivoli Advanced Backup and Recovery (ITABR)

➢ IBM Tivoli Advanced Allocation Manager (ITAAM)

➢ IBM Tivoli Tape Optmizer (ITTO)

➢ IBM Tivoli Automated Tape Allocation Manager (ATAM)

➢ DFSMSrmm reporting and toolkit functions

Cornerstone for every zStorage

management Tool box!

Page 58: Solutions For Common z/OS Storage Management Problems And

Customer benefits:

➢Monitor and manage z/OS storage availability, performance, and workload views

➢Toolkit maximizes efficiency of your daily z/OS storage management functions

➢Sophisticated alerting of DASD, Tape and subsystem software e.g. DFSMShsm, RMM, etc.

➢Help meet application SLA’s: Reduce Outages, Quicker Problem Resolution

➢Improve productivity of resources and staff (take action & Toolkit)

➢Improve z/OS operational performance e.g hardware and software

➢Reduce ISV SW costs (including cost of multi-vendors) (OPEX)

➢Reduce or defer CPU and Storage Hardware cost (CAPEX)

OM Storage benefits

Page 59: Solutions For Common z/OS Storage Management Problems And

59

E3270UI (Enhanced 3270 UI)

➢ Enhanced 3270 UI for subject matter experts ➢ Advanced navigation methods➢ Advanced usage capabilities, e.g. Find, linking,

context sensitive, scrolling, etc.➢ Ability to create intelligent alerts using

conditional logic ➢ Ability to create and see a situations➢ Integration with other OMEGAMONs➢ Real-time and near term history➢ Consistent interface across all OMEGAMON

products➢ Resides on z/OS

Page 60: Solutions For Common z/OS Storage Management Problems And

60

Tivoli Enterprise Portal (TEP)

➢ Browser-based access to monitoring data ➢ Ability to create intelligent alerts using

conditional logic ➢ Ability to see an alert and information related

to it from the same interface➢ Reflex automation capabilities➢ Procedural/resolution information can be

provided through Expert Advice➢ Built-in TN3270 to quickly navigate to console,

TSO➢ Built-in Web Browser➢ Real-time, near term and long term history➢ Consistent interface across all OMEGAMON

products➢ TEP GUI interface enabled for all products in

the IBM Advanced Storage Management Suite and Advanced Backup and Recovery Manager

Page 61: Solutions For Common z/OS Storage Management Problems And

Dataset Metrics Web UI – Using Zowe!!!

Part of OM Storage V5.5

Currently allows for full access to all data set data.

Definition of dataset attribute groups not necessary.

Users can select, filter and slice and dice their data in the way that makes sense for the scenario.

Ad-hoc queries are most powerful when you are not quite sure of what you need to see

Requirements:

• z/OS Host Requirements

• IBM SDK for Node.js z/OS v6.11 or later

• ZFS directory

• AT-TLS for HTTP encryption

• Authentication via SAF

• Client Requirements

• Chrome v54 or later

• Firefox v44 or later

NEW!

Page 62: Solutions For Common z/OS Storage Management Problems And

New introduced in v5.5.0 – Zowe User Interface

➢Multiple views, including summarization for key attributes.

➢Flexible filtering to quickly build ad-hoc queries.

➢Quickly choose the columns needed.

➢Sorting across the entire result set.

➢Access to ALL data through on-demand pagination.

Page 63: Solutions For Common z/OS Storage Management Problems And

View By Data Set provides access to all data set attributes.

View By [HLQ, Class, Group] provides

summarization across all datasets for the selected attribute.

Drill down into data set list for

summarized row.

Page 64: Solutions For Common z/OS Storage Management Problems And

IBM Advanced Storage Management Suite

64

OMEGAMON Storage

Advanced Reporting & Management HSM

Advanced Catalog

Advanced Audit HSM

Advanced Allocation

Cloud Tape Connector

Advanced Archive HSM

Components Available Separately

Monitor & Report Manage & Protect Archive & Cloud Storage

Page 65: Solutions For Common z/OS Storage Management Problems And

Please submit your session feedback!

• Do it online at http://conferences.gse.org.uk/2020/feedback/6BD

• This session is 6BD

Page 66: Solutions For Common z/OS Storage Management Problems And

GSE UK Conference 2020 Charity

• The GSE UK Region team hope that you find this presentation and others that follow useful and help to expand your knowledge of z Systems.

• Please consider showing your appreciation by kindly donating a small sum to our charity this year, NHS Charities Together. Follow the link below or scan the QR Code:

http://uk.virginmoneygiving.com/GuideShareEuropeUKRegion