Re: Actual save time in BRMS?

[Kirk Goins <kirkgoins@xxxxxxxxx>]

What is showing in the History Log. Typically there is a message posted
there for each library saved.  I don't know what system you are running but
stepping up to a LTO2-4 using the LVD interface should speed things up too.

On Tue, May 18, 2010 at 6:28 AM, Loyd Goodbar <loyd@xxxxxxxxxxxxxx> wrote:

> In BRMS, is there a way to determine the actual time it took to save a
> library?
>
> In our daily backup, we perform a full save of four main libraries to tape.
> They all start within a couple of minutes, and end 90 minutes later. Here
> is
> a partial list of the media information report (entries before and after
> these five are excluded):
>
>  Saved       Save     Item     Save     Save     Expire  Objects
> Item        Type     Type     Date     Time      Date   Saved
> VNGDBDTA    *FULL    *LIB    5/18/10  3:08:17  6/08/10    6398
> VNGCUSDTA   *FULL    *LIB    5/18/10  3:10:23  6/08/10      35
> PROD_MOD    *FULL    *LIB    5/18/10  3:10:24  6/08/10    2266
> PROD_DTA    *FULL    *LIB    5/18/10  3:11:15  6/08/10     117
> QGPL        *FULL    *LIST   5/18/10  4:40:02  6/08/10      68
>
> The tape drive is single LTO1 (3581). We are V5R4. (Unfortunately, we have
> vendor software issues - sitll! - that prevent us from moving to 6.1.)
>
> Our current save strategy is to save the enitre system on Sunday, then save
> specific libraries (full save) during the week. In the event of a disaster,
> we only need a Sunday tape and the most recent daily tape. Other libraries
> not saved daily were determined to be of low risk.
>
> We are looking to reduce our current backup window.
>
> Thanks in advance,
> Loyd
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.