|
Yes. It's designed to replicate the volume not the individual object. It
has a command front end so it would be done on a scheduled basis; once a
day or so as you say.
Definitely leaves a window of vulnerability where the images in an optical
volume may not have been replicated. We will be leaving the images on DASD
for a short time period and replicating each image from there.to cover this.
Gord
On Mon, Sep 22, 2014 at 8:06 AM, <rob@xxxxxxxxx> wrote:
Gord,
So if I change one 23 byte text file stored on that virtual optical file
instead of sending that one changed file it sends the whole 200GB (or
whatever size you have allocated for that optical volume) to the remote
system?
Does it do this every time I change that 23 byte text file or just once a
day or so?
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
From: Gord Hutchinson <gordm1@xxxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 09/22/2014 07:53 AM
Subject: Re: image catalogs in library mode and HA
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
Jim,
I'm a little behind you in this process but we will also be replicating
our
virtual optical to an HA site. We use MIMIX to replicate our application
but the virtual optical will be replicated using a Virtual Optical
Replication utility from IBM. The tool unloads the Image Catalog and
saves
the optical volume to a save file and reloads the image catalog. The
saved
file is then FTPed to the target system and restored.
Gord
On Fri, Sep 19, 2014 at 1:50 PM, Jim Franz <franz9000@xxxxxxxxx> wrote:
We use image catalogs in library mode (this is not ptfs or OS stuff, butapplications.
real images stored on disk) and virtual image devices for our
Now looking a cloud based HA (high availability) solution and they arethe
asking questions about the objects related to this.
Is anyone else doing HA and virtual images - need to verify I have all
related components:list
1. IMGCLG01 *IMGCLG QUSRSYS
2. Catalog . . : IMGCLG01 Status . . . : Ready
Type . . . . : Optical Device . . . : OPTVLB01
Directory . : /EKDVIRTUAL/IMGCLG01
3. OPTVLB01 632B Virtual Optical for IMGCLG01 Catalog
4. Directory . . . . : /ekdvirtual/IMGCLG01
Opt Object link
.
..
OAJ015 >>>>> we have 100 catalog entries per catalog (8
catalogs)
OAJ016
QIMGCLG
Object . . . . . . : /ekdvirtual/IMGCLG01/OAJ015
Type . . . . . . . . . . . . . . . . . : STMF
Owner . . . . . . . . . . . . . . . . : GR_WAFEKD
System object is on . . . . . . . . . : Local
Auxiliary storage pool . . . . . . . . : 1
Object overflowed . . . . . . . . . : No
Coded character set ID . . . . . . . . : 37
Hidden file . . . . . . . . . . . . . : No
PC system file . . . . . . . . . . . . : No
Read only . . . . . . . . . . . . . . : No
Need to archive (PC) . . . . . . . . . : Yes
Need to archive (System) . . . . . . . : Yes
Creation date/time . . . . . . . . . . : 06/04/14 07:06:56
Last access date/time . . . . . . . . : 09/19/14 01:13:33
Data change date/time . . . . . . . . : 09/19/14 01:13:33
Attribute change date/time . . . . . . : 09/19/14 01:13:33
Size of object data in bytes . . . . . : 2310567936
Allocated size of object . . . . . . . : 2311323648
File format . . . . . . . . . . . . . : *TYPE2
Size of extended attributes . . . . . : 0
Storage freed . . . . . . . . . . . . : No
Temporary object . . . . . . . . . . . : No
Disk storage option . . . . . . . . . : *DYNAMIC
Main storage option . . . . . . . . . : *DYNAMIC
Auditing value . . . . . . . . . . . . : *NOTAVL
Object domain . . . . . . . . . . . . : *SYSTEM
Number of hard links . . . . . . . . . : 1
Last used date . . . . . . . . . . . . : 09/19/14
Days used count . . . . . . . . . . . : 76
Allow write during save . . . . . . . : No
Can be saved . . . . . . . . . . . . . : No
System use . . . . . . . . . . . . . . : *VRTVOL
Jim Franz
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
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.
--
Gord Hutchinson
TST Overland Express
--
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.
--
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.
As an Amazon Associate we earn from qualifying purchases.
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.