Name: Disk Backup and Restore
Availability: InStock

Question 1

What does Disk Backup and Restore do?

Accepted Answer

Disk Backup and Restore is a software solution designed for z/OS environments. It provides capabilities to back up, restore, and archive datasets, ensuring data protection and availability. The software helps organizations manage their data lifecycle effectively.

Question 2

Is this a system, application, or tool?

Accepted Answer

This is a software application specifically designed for mainframe environments. It provides a set of tools and functions to manage data backup, recovery, and archiving processes. It is not a system-level component but rather an application that runs on z/OS.

Question 3

What types of organizations use this?

Accepted Answer

Organizations that rely on mainframe systems, particularly those running z/OS, and require robust data protection and archiving capabilities use this product. These organizations typically include large enterprises in sectors such as finance, insurance, and government. Any company needing to ensure data integrity and availability on the mainframe can benefit.

Question 4

When should we consider Disk Backup and Restore?

Accepted Answer

A company should consider Disk Backup and Restore when it needs to implement or improve its data backup and recovery strategies on z/OS. This is particularly relevant when dealing with large volumes of critical data that must be protected against loss or corruption. Compliance requirements and the need for efficient data archiving are also key triggers.

Question 5

What are the alternatives to Disk Backup and Restore?

Accepted Answer

Alternatives include BMC AMI Storage FDR, and MaxBack/VSE. These products offer similar functionality for data backup, restore, and archiving in mainframe environments. The choice depends on specific requirements, existing infrastructure, and vendor preferences.

Question 6

For mainframe products: Does this run in an LPAR?

Accepted Answer

Disk Backup and Restore operates within a z/OS LPAR (Logical Partition) on the mainframe. It leverages z/OS system services and requires access to the datasets that need to be backed up or restored. It may also integrate with other z/OS subsystems for enhanced functionality.

Question 7

What configuration files are used?

Accepted Answer

The product typically uses configuration files to define backup schedules, retention policies, and storage locations. These files specify the datasets to be managed and the parameters for backup and restore operations. The specific format and syntax of these files are detailed in the product documentation.

Question 8

What protocols does it use for communication?

Accepted Answer

Disk Backup and Restore likely uses standard mainframe protocols for data transfer and communication. These may include protocols like TCP/IP for network communication and specific mainframe protocols for interacting with storage devices and other z/OS components. The exact protocols used depend on the specific implementation and configuration.

Question 9

What types of APIs does this product expose?

Accepted Answer

The product likely exposes APIs that allow integration with other mainframe applications and systems. These APIs may support functions such as initiating backups, restoring datasets, querying backup status, and managing storage resources. The specific API types and methods are detailed in the product's API documentation.

Question 10

What business problem does it solve?

Accepted Answer

Disk Backup and Restore solves the business problem of data loss and unavailability on mainframe systems. It ensures that critical datasets can be recovered in the event of hardware failures, software errors, or other disasters. Without this product, organizations risk significant data loss, business disruption, and potential compliance violations.

Question 11

How does it help with compliance?

Accepted Answer

The product helps organizations meet compliance requirements by providing a reliable and auditable data backup and recovery solution. It ensures that data is protected and can be restored to meet regulatory obligations. This is particularly important for industries with strict data retention and protection mandates.

Question 12

What is the typical licensing model?

Accepted Answer

The licensing model is likely based on factors such as the size of the mainframe environment, the number of datasets being protected, or the processing capacity of the system. It could be a perpetual license with ongoing maintenance fees or a subscription-based model. The specific terms and conditions are determined by Broadcom.

Question 13

What specific authentication methods are supported?

Accepted Answer

Disk Backup and Restore supports authentication methods compatible with z/OS security standards. This may include integration with RACF (Resource Access Control Facility), ACF2 (Access Control Facility 2), or Top Secret for user authentication and authorization. These systems control access to mainframe resources.

Question 14

What access control model is used?

Accepted Answer

The product likely employs an access control model based on the security features of z/OS. This typically involves using RACF, ACF2, or Top Secret to define user roles and permissions, controlling access to datasets and backup/restore functions. The specific model used depends on the organization's security policies and configuration.

Question 15

What encryption is used and where?

Accepted Answer

Encryption is used to protect data both in transit and at rest. Data is encrypted during backup and restore processes to prevent unauthorized access. The specific encryption algorithms used are detailed in the product's security documentation and may include AES or other industry-standard encryption methods.

Question 16

What audit/logging capabilities exist?

Accepted Answer

The product provides audit and logging capabilities to track backup and restore operations, user access, and system events. These logs can be used to monitor security, detect unauthorized activity, and meet compliance requirements. The logs are typically stored in z/OS system logs or dedicated log files.

Question 17

What level of technical expertise is required to implement it?

Accepted Answer

Implementing Disk Backup and Restore requires expertise in z/OS systems administration and data management. Understanding mainframe security concepts and backup/recovery best practices is also essential. Organizations may need to train existing staff or hire specialized personnel to manage the product effectively.

Question 18

What ongoing operational requirements exist?

Accepted Answer

Ongoing operational requirements include monitoring backup and restore jobs, managing storage resources, and ensuring the integrity of backup data. Regular maintenance tasks, such as updating configuration files and applying software patches, are also necessary. Proactive monitoring and timely intervention are crucial for maintaining data protection.

Question 19

What are common implementation challenges?

Accepted Answer

Common implementation challenges include integrating the product with existing z/OS security systems, configuring backup schedules to minimize performance impact, and ensuring sufficient storage capacity for backup data. Thorough planning, testing, and collaboration with mainframe experts are essential for a successful implementation.

Share Your Product Experience

Disk Backup and Restore

Product Overview

Frequently Asked Questions

What does Disk Backup and Restore do?

Is this a system, application, or tool?

What types of organizations use this?

When should we consider Disk Backup and Restore?

What are the alternatives to Disk Backup and Restore?

For mainframe products: Does this run in an LPAR?

What configuration files are used?

What protocols does it use for communication?

What types of APIs does this product expose?

What business problem does it solve?

How does it help with compliance?

What is the typical licensing model?

What specific authentication methods are supported?

What access control model is used?

What encryption is used and where?

What audit/logging capabilities exist?

What level of technical expertise is required to implement it?

What ongoing operational requirements exist?

What are common implementation challenges?

Related Products

More from Broadcom

AcceleREXX

ACF2

Allocate DASD Space and Placement

Auditor for z/OS

Automation Point

Bind Analyzer for Db2

Similar Products

ABARS/Assist

Adabas Delta Save

Allocate DASD Space and Placement

Allocation Control Center

Application Backup Center

Application Recovery Tool for IMS and DB2

Help Improve This Directory

Share Your Product Experience