Re: Backup to DISK using BRMS

[DrFranken <midrange@xxxxxxxxxxxx>]

> I thought the VTL volumes were "pre-initialized" similar to when you
> CRTNWSSTG. Or is this not the case?

In the early days some vendors DID allocate all needed space. This was, 
um, 'a problem.' :-)  None of them do that any longer that I am aware of.

        - Larry "DrFranken" Bolhuis

www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.

On 7/21/2016 8:44 AM, Steinmetz, Paul wrote:
> Jim,
>
> If I'm interpreting you correctly, there will never be any "wasted space" on a VTL volume, correct.
>
> Paul
>
> -----Original Message-----
> From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Oberholtzer
> Sent: Thursday, July 21, 2016 8:20 AM
> To: 'Midrange Systems Technical Discussion'
> Subject: RE: Backup to DISK using BRMS
>
> Paul:
>
> On most of the VTLs I've used you set the size of the tape image to the size of the physical tape you might export to (as a maximum)  in order to maintain compatibility with the physical tape volume.  The VTL will only use the amount of space it needs for the save even if it's set with a large maximum.
>
> --
> Jim Oberholtzer
> Agile Technology Architects
>
>
> -----Original Message-----
> From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Steinmetz, Paul
> Sent: Thursday, July 21, 2016 7:14 AM
> To: 'Midrange Systems Technical Discussion'
> Subject: RE: Backup to DISK using BRMS
>
> 1) What size do you create your VTL volumes?
> Just large enough to include one nights entire save Or Do you go with a standard size, nTB.
>
> 2) We keep 180 days of BRMS log data. Never have to use a native restore.
>
>                      Start Maintenance for BRM (STRMNTBRM)
>
>
>
> Type choices, press Enter.
>
>
>
> Label  . . . . . . . . . . . . .
>
> Expire media . . . . . . . . . .   *YES          *YES, *NO
>
> Expire media set volumes . . . . > *YES          *NO, *YES
>
> Remove media information:
>
>   Media contents . . . . . . . .   *EXP          *EXP, *NONE, *REUSE
>
>   Object level detail  . . . . .   *MEDCON       1-9999, *MEDCON
>
> Remove migration information . .   180           1-9999, *NONE
>
> Run media movement . . . . . . .   *NO           *NO, *YES
>
> Remove log entries:
>
>   Type . . . . . . . . . . . . . > *ALL          *ALL, *NONE, *ARC, *BKU,
> *M...
>   From date  . . . . . . . . . . > *BEGIN        Date, *BEGIN, *CURRENT,
> nnnnn
>   To date  . . . . . . . . . . . > 180           Date, *END, *CURRENT, nnnnn
>
> Run cleanup operations . . . . .   *YES          *YES, *NO
>
> Retrieve volume statistics . . .   *YES          *YES, *NO
>
> Audit system media . . . . . . .   *NONE
>
>                + for more values
>
>
> More...
>
> Paul
>
> -----Original Message-----
> From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rob Berendt
> Sent: Thursday, July 21, 2016 7:50 AM
> To: Midrange Systems Technical Discussion
> Subject: RE: Backup to DISK using BRMS
>
> Using VTL instead of manual tape is opening up some options for us.
> Especially with the though of a remote data center.
>
> Remember when I told you that we have two data centers?  One in Garrett and one in Kendallville.  Both in Indiana and only 17 miles apart.  So we have a third VTL at US Signal in Grand Rapids MI.  That only replicates the mtrees and not the individual volumes.
>
> Well, our Garrett building data center, while newer, is a glorified closet.
> Even so, it's getting so crowded there they are eyeing that space.
>
> The thought process is this.
> 1 - Forget about the third vtl in Grand Rapids.
> 2 - Move all equipment currently in our Kendallville data center to Grand Rapids.
> 3 - Move all Power 8 and other server racks from Garrett to Kendallville.
> 4 - Move remaining Garrett telco equipment to a room across the hall with some noisy UPS that no one will ever tolerate as an office (at least since my boss moved out of it).
>
> We can easily consolidate the equipment moving from Kendallville to Grand Rapids in a single rack.  Before we do so we're checking with US Signal if we use our rack or theirs.
> Sure there will be a lot to make sure of but this ain't my first data center move.
>
> With the third vtl we've been testing the comm between us and Grand Rapids and we're happy.
>
>
> Rob Berendt
> --
> IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail
> to:  2505 Dekko Drive
>           Garrett, IN 46738
> Ship to:  Dock 108
>           6928N 400E
>           Kendallville, IN 46755
> http://www.dekko.com
>
> --
> 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.
>
> Please contact support@xxxxxxxxxxxx for any subscription related questions.
> --
> 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.
>
> Please contact support@xxxxxxxxxxxx for any subscription related questions.
>
> --
> 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.
>
> Please contact support@xxxxxxxxxxxx for any subscription related questions.