Tape Replacement

Replacing tape- and virtual tape-based systems

Model9 replaces existing tape hardware and software without changing daily operations and data management processes.

Reduce backup costs by:

  • Offloading backups, archives and space management processing to zIIPs, IFLs and open systems
  • Replacing physical and virtual tape hardware (such as VTS, VTL and ATL) with any storage system or Cloud storage
  • Consolidating existing backup, tape management, encryption and reporting software products into a single software solution

Cloud Backup

Cloud storage as primary storage

The server supports data backup storage and archives as well as direct data restore and recall from Cloud object storage. Model9 encrypts all data before being moved to the Cloud and supports leading Cloud providers such as Microsoft Azure, Amazon S3 and Glacier, Google Cloud Storage and more.

Cloud storage as a secondary storage tier

Data is first written to onsite storage for best performance. Later, according to a predefined policy, cold data is archived in the Cloud. Data is indexed and organized for fast retrieval to onsite storage or directly to the mainframe.

Cloud storage as the target for storage replication

All data written to the server storage, whether onsite or in the Cloud, may be replicated as a secondary copy in the Cloud. Multiple Cloud storage targets for replication are also supported.

z/OS UNIX Backup

Model9 supports z/OS UNIX file-level incremental backup and restore, which saves backup space and shortens backup windows. It only backs up changed files in the z/OS UNIX file system, as opposed to backing up the complete HFS/ZFS data set every time a UNIX file is changed. During restore, only the specific UNIX file is restored directly to the UNIX file system, without having to restore the entire HFS/ZFS data set first.

This leads to greater productivity – allowing fast restore by anyone, without requiring systems support.

Disaster Recovery

The server and storage media may be located at a remote site and function as an in-house vault backup for disaster recovery. In bare-metal recovery situations, a stand-alone restore program is IPLed, over network, directly from the server (using the HMC “Load from removable media or server” action). A standalone restore program is used to restore volumes and data sets without requiring the agent to be running in z/OS.


Automatic recovery tests

Model9 automatically tests the data management infrastructure and verifies that all backups are recoverable and all archived data is instantly available. Backups and archives are tested according to a predefined policy, or randomly, to ensure successful restores. A detailed report is sent to the storage administrator after every test, including a record of the test and alerts resulting from restore failures. This feature eliminates the need for periodic manual recovery tests.

IFL/HiperSocket utilization on z/Linux

When running the backup server on z/Linux with IFLs, the server and agent communicate via HiperSockets. With HiperSockets, data is transferred in memory and never leaves the mainframe host. The use of high-speed HiperSockets as a communications link allows for shorter backup windows. Since the data does not leave the mainframe host, in-motion data encryption may not be required, thus freeing up additional CPU resources. TCP/IP processing in z/OS for sending data over HiperSockets is zIIP-eligible.

Running the server on z/Linux provides the flexibility to use any storage system, including MF DASD, SAN, NAS and Cloud storage.

and get a complimentary assessment report within 48 hours