MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » September 2014

RE: SYSSAV(Option 21) Media Options



fixed

I not understand very well, but you can do GO SAVE, OPTION 22 every month, restore these save in sungard, create vpn crypt communication with a simple internet modems, and create journals receivers and journals and attach to a data, and send data whit remote journal, like mimix or nomax, and create simple like mimix/nomax homemade software, for simple PF data can work well, if you have 6.1 you can add more objects, and best if the information its no so BIGEST you can do fine, an a sugestion better expend money, 1k or 2k its more better than lose all operation




La felicidad es frecuente, no pasa un día en que no estemos un instante en el Paraíso.

To: midrange-l@xxxxxxxxxxxx
Subject: Re: SYSSAV(Option 21) Media Options
From: rob@xxxxxxxxx
Date: Tue, 2 Sep 2014 07:08:03 -0400

I, too, would think Sunguard would be bonded. However, after having had
Iron Mountain deliver a tape to a wrong location I can share some of your
bosses concerns.

Then you might want to look at tape encryption. This will require you to
look up some information and to develop effective communication skills to
convince your management.

Another alternative, still using encryption, would be a Virtual Tape
Library or VTL. I'm really surprised no one else has made that
suggestion. One unit local, which replicates (with encryption) to
Sunguard.

Another option is to save to a virtual tape image catalog. You should use
encryption on that. If you choose not to use encryption then you might
want to zip that up with encryption and a password before transferring it
off to Sunguard. However, the zipping will increase the time and disk
consumption considerably. And think about just how you would recover from
that.

The end in mind is "How would you restore in a DR situation with any
backup strategy you select?". Test your new strategy at Sunguard.


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: "Laine, Rogers" <Rogers.Laine@xxxxxxxxxxxxxxx>
To: "'Midrange-L'" <midrange-l@xxxxxxxxxxxx>
Date: 08/31/2014 03:00 PM
Subject: SYSSAV(Option 21) Media Options
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Hello,

We are running V6.1.0 and have been backing up our system using Option #21
to physical tape media.
The tape is sent offsite each day for use at our remote disaster recovery
site(Sungard).
This tape is used to recovery our full system at Sungard when a disaster
is declared.
Now management has decided that they no longer want to send this tape
offsite for recovery.
One reason is this backup tape has customer data from the application.

Here are options I think may be possible...
Option #1
Continue my daily option#21 but direct my backup to a Windows Server path
on our network. If this is possible?
At remote site recover system reading the backup from the Windows Server.
May need to FTP backup file to remote site before starting recovery. If
this is possible?
Option#2
Modify option#21 to not include any application data that has customer
information.
Run backup directing it to either tape or DVD if it will fit.
This backup would go off site just once until changes to AS400 are made
and would be used to recovery base system.
Along with the backup we would backup the security information daily using
a Save File and FTP to remote site to be restored after the base restore
is finished. This should provide a working system with all updates as it
is being done now.

So what are the Pros/Cons for each option and are they doable?
Any other suggestions without spending money for hardware or software?

Thanks,
Rogers




************************************************
This E-Mail transmission (and/or the documents accompanying it)
may contain information belonging to the sender which is confidential,
privileged and/or exempt from disclosure under applicable law. The
information is intended only for the use of the individual(s) or entity
named above. If you are not the intended recipient, you are hereby
notified that any disclosure, copying, distribution or the taking of any
action in reliance on the contents of this information is strictly
prohibited. If you have received this E-Mail transmission in error,
please immediately notify us by return E-Mail or telephone to arrange
for return of its contents including any documents.
--
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.






Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact