Re: IFS support in ACS - 1.6.1.1 -- MIDRANGE-L

Subject: Re: IFS support in ACS - 1.6.1.1
From: Rob Berendt <rob@xxxxxxxxx>
Date: Tue, 6 Dec 2016 10:14:02 -0500
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

There is an API used by some saves. In which blocks of data are
processed. One example of it's use is the special command SAVRST. So
they grab a chunk of data, and they do not save it to media or save files.
They take that chunk and actually start the restore on the target
machine. There are a few benefits to this:
- The save/transfer/restore are all running at the same time in parallel.
Instead of save, transfer, restore.
- No save file on both the source and target eating up space, even if only
temporarily.
This API is publicly available.

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: IFS support in ACS - 1.6.1.1 , Vernon Hamberg

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.