Broadcom z/OS

CREWS Modernization Guide

Backup and RestoreDiskTools and UtilitiesAdministrationData Management

CREWS is a backup and restore product by Broadcom. Explore technical details, modernization strategies, and migration paths below.

Product Overview

CREWS (Catalog Recovery and Early Warning System) is a tool designed to manage and protect z/OS catalogs.

The tool is deployed on-premise and requires technical expertise to configure and manage.

Modernization Strategies

Rehost

Timeline:
6-12 months

Lift-and-shift to cloud infrastructure with minimal code changes. Fast migration with lower risk.

Refactor (Recommended)

Timeline:
18-24 months

Optimize application architecture for cloud while preserving business logic. Best ROI long-term.

Replatform

Timeline:
3-5 years

Complete rewrite to cloud-native architecture with microservices and modern tech stack.

Frequently Asked Questions

General

What does CREWS do?

CREWS is a catalog backup and recovery tool for z/OS. It provides capabilities for catalog backup, restore, forward recovery from SMF records, catalog checkup and reorganization, and master catalog alias synchronization. It helps ensure the integrity and availability of critical catalog data.

Is this a system, application, or tool?

CREWS is a tool set designed to manage and protect z/OS catalogs. It provides a range of utilities for backup, recovery, and maintenance, ensuring catalog data integrity and availability.

What types of organizations use this?

Organizations that rely on z/OS mainframe systems and require robust catalog management capabilities use CREWS. This includes enterprises in industries such as banking, finance, insurance, and government.

When should we consider CREWS?

A company should consider using CREWS when they need a reliable solution for backing up, restoring, and maintaining their z/OS catalogs. This is especially important when dealing with large volumes of data and critical business applications.

What are the alternatives to CREWS?

Alternatives to CREWS include Mainstar Catalog Recovery Plus, Tivoli Advanced Catalog Management, and Catalog Information Manager. These products offer similar catalog management capabilities for z/OS environments.

Technical

For mainframe products: Does this run in an LPAR?

CREWS runs on the z/OS platform and requires access to SMF records for forward recovery. It operates within an LPAR and integrates with existing z/OS subsystems.

How is CREWS typically deployed?

CREWS is deployed on-premise within the z/OS environment. It requires technical expertise to implement and configure, including knowledge of z/OS systems and catalog management.

Is this a standalone product or does it extend/enhance another product?

CREWS enhances the management of z/OS catalogs by providing backup, recovery, and maintenance capabilities. It operates as a standalone product but integrates with existing z/OS infrastructure.

What other products or components must be present for this to work?

CREWS requires z/OS and access to SMF records. It may also require specific security configurations and access to system datasets.

Business Value

How does CREWS provide business value?

CREWS ensures business continuity by providing reliable catalog backup and recovery. It minimizes downtime and data loss in the event of a catalog failure, ensuring critical applications remain available.

What would happen if an organization did NOT use this product?

Without CREWS, organizations face the risk of catalog corruption or loss, leading to application outages and data unavailability. Manual recovery processes are time-consuming and error-prone.

How does CREWS help with compliance?

CREWS helps organizations meet compliance requirements by ensuring the integrity and availability of catalog data. It provides audit trails and reporting capabilities to demonstrate compliance with industry regulations.

Security

What authentication methods are supported?

CREWS supports standard z/OS authentication methods, such as RACF, ACF2, and Top Secret. It integrates with existing security systems to control access to catalog data and functions.

What access control model is used?

CREWS uses an access control model based on z/OS security systems (RACF, ACF2, Top Secret). It allows administrators to define granular access permissions for users and groups.

What audit/logging capabilities exist?

CREWS provides audit logging capabilities to track user activity and system events. These logs can be used to monitor security and identify potential threats.

Operations

What ongoing operational requirements exist?

Ongoing operational requirements for CREWS include monitoring catalog backups, performing regular maintenance, and ensuring the system is properly configured. Staff with z/OS experience are needed to manage the product.

What administrative interfaces are available?

CREWS provides a command-line interface (CLI) and potentially a GUI for administration. User management is handled through z/OS security systems (RACF, ACF2, Top Secret).

What are common implementation challenges?

Common implementation challenges include configuring CREWS to work with existing z/OS security systems, ensuring proper access to SMF records, and scheduling backups to minimize impact on system performance.

Ready to Start Your Migration?

Download our comprehensive migration guide for CREWS or calculate your ROI.

Calculate ROI