If you use BRMS, no problem you'll still be able to recover since BRMS will
manage the expiration of tapes etc.
If your nightly saves are change only then dropping the weekly is going to
cause you to keep quite a few more tapes around for recovery and I'm
doubtful that a recovery test would be successful. At some point during the
week you'll need a full save, which can still be save while active, but a
full as opposed to an incremental.
The restricted state save, meaning including IBM i LIC and OS is only really
needed after applying PTF groups/cumulative. I would argue that an *IBM
save should be done at least once a month, and always after an individual
PTF or groups are applied, but I've seen customers where the frequency needs
to be shorter since they change parameters on various LPPs during the month.
Bottom line is design your recovery process, then build the back up to
Chief Technical Architect
Agile Technology Architects
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Gqcy
Sent: Thursday, April 24, 2014 2:15 PM
Subject: comfort level in not performing TAPE backups...
I have re-composed this email several times now...
it kept winding up as a pro - con list...
Our IT shop (mostly windows servers, with a small IBM i) has been working
away from tape for some time.
3 years ago we stopped our nightly IBM i backups to physical tape, and went
to a product that exported save files to SAN. we did physical tape spins on
we are now in a full HA/DR protection scenario, and are progressing to
performing our nightly backups on the DR box, NOT the source box...
I am ok with this...
Now, I am being tasked to stop the weekend tape spins now as well, except
for a "month end" full system save tape to be done on Source system.
I need to ask....
Am I going too far down the trail getting away from tape on the IBM i?
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,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l