ETI-NET z/OS

BackHome Modernization Guide

Backup and RestoreFiles and DatasetsUNIX and Windows

BackHome is a backup and restore product by ETI-NET. Explore technical details, modernization strategies, and migration paths below.

Product Overview

BackHome provides data transfer and backup capabilities between HP NonStop (Tandem) systems and z/OS environments.

The solution uses FTP and proprietary protocols for data transfer, ensuring efficient and reliable data movement. Key components include: * **NonStop Agent:** Resides on the HP NonStop system. * **z/OS Server:** Runs on the z/OS platform. * **Central Management Console:** Provides a unified interface for managing and monitoring data transfers. BackHome supports authentication via RACF, ACF2, and Top Secret on z/OS.

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 is the primary function of BackHome?

BackHome facilitates data transfer from HP NonStop systems to z/OS environments. It supports both tape and disk storage on z/OS.

How are data transfers configured in BackHome?

BackHome uses configuration files to define transfer parameters, including source and destination details, file mappings, and scheduling options. These files are typically managed through a command-line interface.

What protocols does BackHome use for data transfer?

BackHome supports standard FTP for data transfer between HP NonStop and z/OS. It also uses proprietary protocols for optimized performance and data integrity.

What kind of logging is available in BackHome?

BackHome provides detailed logging capabilities, capturing information about transfer status, errors, and performance metrics. These logs can be used for monitoring and troubleshooting.

Technical

What are the main system components of BackHome?

The core components include the NonStop Agent, the z/OS Server, and the Central Management Console. The NonStop Agent resides on the HP NonStop system, while the z/OS Server runs on the z/OS platform. The Central Management Console provides a unified interface for managing and monitoring data transfers.

How do the components communicate with each other?

BackHome uses FTP and proprietary protocols for communication between the NonStop Agent and the z/OS Server. The Central Management Console communicates with both components via secure TCP/IP connections.

What storage mechanisms are used by BackHome?

BackHome supports various tape formats on z/OS, including standard IBM tape formats. For disk storage, it supports VSAM and sequential datasets.

What administrative interfaces are available?

BackHome uses a command-line interface (CLI) for most administrative tasks. Configuration files are used to define transfer parameters and scheduling options.

Business Value

How does BackHome contribute to business continuity?

BackHome ensures business continuity by providing reliable data transfer and backup capabilities between HP NonStop and z/OS. This minimizes downtime and ensures data availability.

How does BackHome improve operational efficiency?

BackHome optimizes data transfer performance, reducing the time required for backups and restores. This improves operational efficiency and reduces costs.

Does BackHome support automation?

BackHome supports automation of data transfer tasks, reducing manual intervention and the risk of errors. This improves reliability and reduces operational overhead.

Security

What authentication methods are supported by BackHome?

BackHome supports authentication via RACF, ACF2, and Top Secret on z/OS. It also supports user authentication on the HP NonStop platform.

What access control model is used by BackHome?

BackHome uses an access control list (ACL) model to manage user permissions and access to data transfer resources.

What encryption is used and where?

BackHome uses encryption during data transfer to protect sensitive information. The specific encryption algorithms used depend on the configuration and protocols selected.

What audit/logging capabilities exist?

BackHome provides comprehensive audit logging, capturing information about user access, data transfers, and security events. These logs can be used for security monitoring and compliance reporting.

Operations

What administrative interfaces are available for BackHome?

BackHome provides a command-line interface (CLI) for administrative tasks, including configuration, monitoring, and troubleshooting. The CLI can be accessed via a terminal or scripting.

How is user management handled in BackHome?

BackHome supports centralized user management through integration with z/OS security systems such as RACF, ACF2, and Top Secret. User permissions are managed through access control lists (ACLs).

What are the main configuration parameters for BackHome?

Key configuration parameters include source and destination details, file mappings, scheduling options, and security settings. These parameters are defined in configuration files.

What monitoring/logging capabilities exist in BackHome?

BackHome provides detailed logging and monitoring capabilities, capturing information about transfer status, errors, and performance metrics. These logs can be used for troubleshooting and performance analysis.

Ready to Start Your Migration?

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

Calculate ROI