DB2 Backups Strategy on z/OS

Frederic Lavoie

DB2 Backups Strategy on z/OS
Hello,

We would like to know if any documentation is written about DB2
Backups Strategies on z/OS?

Something to guide us with :
- hot or cold backups, when and why? Pros and cons?
- full or incremental, when and why? Pros and cons?
- RETPD to use
- daily, weekly, monthly backups? Pros and cons?
- etc...

We have to create some kind of documentation about best practices.

Here we have more tant 100 different DB2 databases in production and
we are talking about 1 or 2 dba per databases and we would like to
create guide lines to have something more consistent regarding the
backups. At the moment every DB has their own way to do backups....

So if something is already written, I will not have to start from
scracth.

Thank you.

Fred Lavoie
DB Common Group
*613-954-9286

The IDUG DB2-L Listserv is only part of your membership in IDUG. DB2-L list archives, the FAQ, and delivery preferences are at http://www.idug.org/lsidug under the Listserv tab. While at the site, you can also access the IDUG Online Learning Center, Tech Library and Code Place, see the latest IDUG conference information, and much more. If you have not yet signed up for Basic Membership in IDUG, available at no cost, click on Member Services at http://www.idug.org/lsms

Mike Bell

Re: DB2 Backups Strategy on z/OS
(in response to Frederic Lavoie)
Judy Ruby-Brown is one of the experts - she did some presentations at tech
conference and idug some years back.

Note - there is normal backup and then there is the magic flashcopy dual
copy stuff where the remote system gets an io everytime you update the base
tablespace.

Even if you have dual dasd setup, you still need a plan for application
recovery. Not me thankfully but there have been posts to the listserv about
having a bad software update and then backup to last known good table and
then running fix programs. If you are running bad software - 2 copies of
the same wrong data are not worth much.

Mike

-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email] On Behalf
Of Lavoie, Frederic
Sent: Wednesday, January 09, 2008 3:09 PM
To: [login to unmask email]
Subject: [DB2-L] DB2 Backups Strategy on z/OS

Hello,

We would like to know if any documentation is written about DB2
Backups Strategies on z/OS?

Something to guide us with :
- hot or cold backups, when and why? Pros and cons?
- full or incremental, when and why? Pros and cons?
- RETPD to use
- daily, weekly, monthly backups? Pros and cons?
- etc...

We have to create some kind of documentation about best practices.

Here we have more tant 100 different DB2 databases in production and
we are talking about 1 or 2 dba per databases and we would like to
create guide lines to have something more consistent regarding the
backups. At the moment every DB has their own way to do backups....

So if something is already written, I will not have to start from
scracth.

Thank you.

Fred Lavoie
DB Common Group
*613-954-9286

The IDUG DB2-L Listserv is only part of your membership in IDUG. DB2-L list
archives, the FAQ, and delivery preferences are at
http://www.idug.org/lsidug under the Listserv tab. While at the site, you
can also access the IDUG Online Learning Center, Tech Library and Code
Place, see the latest IDUG conference information, and much more. If you
have not yet signed up for Basic Membership in IDUG, available at no cost,
click on Member Services at http://www.idug.org/lsms

The IDUG DB2-L Listserv is only part of your membership in IDUG. DB2-L list archives, the FAQ, and delivery preferences are at http://www.idug.org/lsidug under the Listserv tab. While at the site, you can also access the IDUG Online Learning Center, Tech Library and Code Place, see the latest IDUG conference information, and much more. If you have not yet signed up for Basic Membership in IDUG, available at no cost, click on Member Services at http://www.idug.org/lsms

Lockwood Lyon

Re: DB2 Backups Strategy on z/OS
(in response to Mike Bell)
Fred,

As I have expounded in multiple articles and IDUG presentations, most
shops go about this backwards. They keep asking about "Backup"
strategies. There are no such: there are only "backup tactics" that
support a Recovery Strategy.

I recommend you review your Tablespace/Index recovery requirements. If
applications have SLAs regarding downtime during a recovery, then what
combination of backup strategies do you need to meet those recovery
requirements?

Example: a 100GB table with a 50 GB partitioning index. The application
(a financial one) requires that any outage be no more than 30 minutes.
In our case, while it might have been possible to recover the tablespace
from multiple partition backups, the REBUILD of the Index took several
hours. Hence, we had to consider: (a) Index Image Copies; (b) DASD
mirroring; (c) "Shadow" tables; and, (d) other backup methods.

Lock Lyon
Fifth Third Bancorp


-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email] On
Behalf Of Lavoie, Frederic
Sent: Wednesday, January 09, 2008 4:09 PM
To: [login to unmask email]
Subject: [DB2-L] DB2 Backups Strategy on z/OS

Hello,

We would like to know if any documentation is written about DB2
Backups Strategies on z/OS?

Something to guide us with :
- hot or cold backups, when and why? Pros and cons?
- full or incremental, when and why? Pros and cons?
- RETPD to use
- daily, weekly, monthly backups? Pros and cons?
- etc...

We have to create some kind of documentation about best practices.

Here we have more tant 100 different DB2 databases in production and
we are talking about 1 or 2 dba per databases and we would like to
create guide lines to have something more consistent regarding the
backups. At the moment every DB has their own way to do backups....

So if something is already written, I will not have to start from
scracth.

Thank you.

Fred Lavoie
DB Common Group
*613-954-9286

This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated.

The IDUG DB2-L Listserv is only part of your membership in IDUG. DB2-L list archives, the FAQ, and delivery preferences are at http://www.idug.org/lsidug under the Listserv tab. While at the site, you can also access the IDUG Online Learning Center, Tech Library and Code Place, see the latest IDUG conference information, and much more. If you have not yet signed up for Basic Membership in IDUG, available at no cost, click on Member Services at http://www.idug.org/lsms

Frederic Lavoie

Re: DB2 Backups Strategy on z/OS
(in response to Lockwood Lyon)
Do you know where I can find the presentation?

Thank you


Fred Lavoie
DB Common Group
*613-954-9286
-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email] On
Behalf Of Mike Bell
Sent: January 9, 2008 4:41 PM
To: [login to unmask email]
Subject: Re: [DB2-L] DB2 Backups Strategy on z/OS

Judy Ruby-Brown is one of the experts - she did some presentations at
tech
conference and idug some years back.

Note - there is normal backup and then there is the magic flashcopy dual
copy stuff where the remote system gets an io everytime you update the
base
tablespace.

Even if you have dual dasd setup, you still need a plan for application
recovery. Not me thankfully but there have been posts to the listserv
about
having a bad software update and then backup to last known good table
and
then running fix programs. If you are running bad software - 2 copies
of
the same wrong data are not worth much.

Mike

-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email] On
Behalf
Of Lavoie, Frederic
Sent: Wednesday, January 09, 2008 3:09 PM
To: [login to unmask email]
Subject: [DB2-L] DB2 Backups Strategy on z/OS

Hello,

We would like to know if any documentation is written about DB2
Backups Strategies on z/OS?

Something to guide us with :
- hot or cold backups, when and why? Pros and cons?
- full or incremental, when and why? Pros and cons?
- RETPD to use
- daily, weekly, monthly backups? Pros and cons?
- etc...

We have to create some kind of documentation about best practices.

Here we have more tant 100 different DB2 databases in production and
we are talking about 1 or 2 dba per databases and we would like to
create guide lines to have something more consistent regarding the
backups. At the moment every DB has their own way to do backups....

So if something is already written, I will not have to start from
scracth.

Thank you.

Fred Lavoie
DB Common Group
*613-954-9286

The IDUG DB2-L Listserv is only part of your membership in IDUG. DB2-L
list
archives, the FAQ, and delivery preferences are at
http://www.idug.org/lsidug under the Listserv tab. While at the site,
you
can also access the IDUG Online Learning Center, Tech Library and Code
Place, see the latest IDUG conference information, and much more. If
you
have not yet signed up for Basic Membership in IDUG, available at no
cost,
click on Member Services at http://www.idug.org/lsms

The IDUG DB2-L Listserv is only part of your membership in IDUG. DB2-L
list archives, the FAQ, and delivery preferences are at
http://www.idug.org/lsidug under the Listserv tab. While at the site,
you can also access the IDUG Online Learning Center, Tech Library and
Code Place, see the latest IDUG conference information, and much more.
If you have not yet signed up for Basic Membership in IDUG, available at
no cost, click on Member Services at http://www.idug.org/lsms

The IDUG DB2-L Listserv is only part of your membership in IDUG. DB2-L list archives, the FAQ, and delivery preferences are at http://www.idug.org/lsidug under the Listserv tab. While at the site, you can also access the IDUG Online Learning Center, Tech Library and Code Place, see the latest IDUG conference information, and much more. If you have not yet signed up for Basic Membership in IDUG, available at no cost, click on Member Services at http://www.idug.org/lsms

Mike Turner

Re: DB2 Backups Strategy on z/OS
(in response to Frederic Lavoie)
Hi Fred

There is a Redbook on Disaster Recovery that you may find helpful:

http://www.redbooks.ibm.com/abstracts/sg246370.html?Open

Regards
Mike Turner
Email: [login to unmask email]
Tel: +44 (0)1565 873702
web: www.michael-turner.ltd.uk
----------------------------------------------------------------------------
------------
Michael Turner Ltd. Registered in England and Wales No. 1433722. Registered
Office: 131 King Street, Knutsford, Cheshire, WA16 6EJ. VAT Reg. No. GB 338
4159 44.

-----Original Message-----
From: [login to unmask email]
[mailto:[login to unmask email]On Behalf Of Lavoie, Frederic
Sent: Wednesday, 09 January 2008 21:09
To: [login to unmask email]
Subject: [DB2-L] DB2 Backups Strategy on z/OS



Hello,

We would like to know if any documentation is written about DB2
Backups Strategies on z/OS?

Something to guide us with :
- hot or cold backups, when and why? Pros and cons?
- full or incremental, when and why? Pros and cons?
- RETPD to use
- daily, weekly, monthly backups? Pros and cons?
- etc...

We have to create some kind of documentation about best practices.

Here we have more tant 100 different DB2 databases in production and
we are talking about 1 or 2 dba per databases and we would like to
create guide lines to have something more consistent regarding the
backups. At the moment every DB has their own way to do backups....

So if something is already written, I will not have to start from
scracth.

Thank you.

Fred Lavoie
DB Common Group
*613-954-9286

The IDUG DB2-L Listserv is only part of your membership in IDUG. DB2-L list
archives, the FAQ, and delivery preferences are at
http://www.idug.org/lsidug under the Listserv tab. While at the site, you
can also access the IDUG Online Learning Center, Tech Library and Code
Place, see the latest IDUG conference information, and much more. If you
have not yet signed up for Basic Membership in IDUG, available at no cost,
click on Member Services at http://www.idug.org/lsms

The IDUG DB2-L Listserv is only part of your membership in IDUG. DB2-L list archives, the FAQ, and delivery preferences are at http://www.idug.org/lsidug under the Listserv tab. While at the site, you can also access the IDUG Online Learning Center, Tech Library and Code Place, see the latest IDUG conference information, and much more. If you have not yet signed up for Basic Membership in IDUG, available at no cost, click on Member Services at http://www.idug.org/lsms

William Favero

Re: DB2 Backups Strategy on z/OS
(in response to Mike Turner)
Just go to DB2' support web page...

http://www.ibm.com/software/data/db2/support/db2zos/

and search on Judy Ruby-Brown.

Lots of good stuff will show up

Willie



Lavoie, Frederic wrote:
> Do you know where I can find the presentation?
>
> Thank you
>
>
> Fred Lavoie
> DB Common Group
> *613-954-9286
> -----Original Message-----
> From: DB2 Data Base Discussion List [mailto:[login to unmask email] On
> Behalf Of Mike Bell
> Sent: January 9, 2008 4:41 PM
> To: [login to unmask email]
> Subject: Re: [DB2-L] DB2 Backups Strategy on z/OS
>
> Judy Ruby-Brown is one of the experts - she did some presentations at
> tech
> conference and idug some years back.
>
> Note - there is normal backup and then there is the magic flashcopy dual
> copy stuff where the remote system gets an io everytime you update the
> base
> tablespace.
>
> Even if you have dual dasd setup, you still need a plan for application
> recovery. Not me thankfully but there have been posts to the listserv
> about
> having a bad software update and then backup to last known good table
> and
> then running fix programs. If you are running bad software - 2 copies
> of
> the same wrong data are not worth much.
>
> Mike
>
> -----Original Message-----
> From: DB2 Data Base Discussion List [mailto:[login to unmask email] On
> Behalf
> Of Lavoie, Frederic
> Sent: Wednesday, January 09, 2008 3:09 PM
> To: [login to unmask email]
> Subject: [DB2-L] DB2 Backups Strategy on z/OS
>
> Hello,
>
> We would like to know if any documentation is written about DB2
> Backups Strategies on z/OS?
>
> Something to guide us with :
> - hot or cold backups, when and why? Pros and cons?
> - full or incremental, when and why? Pros and cons?
> - RETPD to use
> - daily, weekly, monthly backups? Pros and cons?
> - etc...
>
> We have to create some kind of documentation about best practices.
>
> Here we have more tant 100 different DB2 databases in production and
> we are talking about 1 or 2 dba per databases and we would like to
> create guide lines to have something more consistent regarding the
> backups. At the moment every DB has their own way to do backups....
>
> So if something is already written, I will not have to start from
> scracth.
>
> Thank you.
>
> Fred Lavoie
> DB Common Group
> *613-954-9286
>
> The IDUG DB2-L Listserv is only part of your membership in IDUG. DB2-L
> list
> archives, the FAQ, and delivery preferences are at
> http://www.idug.org/lsidug under the Listserv tab. While at the site,
> you
> can also access the IDUG Online Learning Center, Tech Library and Code
> Place, see the latest IDUG conference information, and much more. If
> you
> have not yet signed up for Basic Membership in IDUG, available at no
> cost,
> click on Member Services at http://www.idug.org/lsms
>
> The IDUG DB2-L Listserv is only part of your membership in IDUG. DB2-L
> list archives, the FAQ, and delivery preferences are at
> http://www.idug.org/lsidug under the Listserv tab. While at the site,
> you can also access the IDUG Online Learning Center, Tech Library and
> Code Place, see the latest IDUG conference information, and much more.
> If you have not yet signed up for Basic Membership in IDUG, available at
> no cost, click on Member Services at http://www.idug.org/lsms
>
> The IDUG DB2-L Listserv is only part of your membership in IDUG. DB2-L list archives, the FAQ, and delivery preferences are at http://www.idug.org/lsidug under the Listserv tab. While at the site, you can also access the IDUG Online Learning Center, Tech Library and Code Place, see the latest IDUG conference information, and much more. If you have not yet signed up for Basic Membership in IDUG, available at no cost, click on Member Services at http://www.idug.org/lsms
>
>
>

--
Willie
My DB2 blog --> http://blogs.ittoolbox.com/database/db2zos
Houston, TX, USA

The IDUG DB2-L Listserv is only part of your membership in IDUG. DB2-L list archives, the FAQ, and delivery preferences are at http://www.idug.org/lsidug under the Listserv tab. While at the site, you can also access the IDUG Online Learning Center, Tech Library and Code Place, see the latest IDUG conference information, and much more. If you have not yet signed up for Basic Membership in IDUG, available at no cost, click on Member Services at http://www.idug.org/lsms

Max Scarpa

Re: DB2 Backups Strategy on z/OS
(in response to William Favero)

I agree with Lyon. In many shops I saw there's no a 'approved' strategy as
it depends on SLAs (if any), on type of business the company does, down to
the single DBA's ideas about backups.
And a given strategy change over the time: for example moving from a
IC-based DR to a DASD-replication DR. So don't consider a chosen strategy
a 'strategy forever', nothing is forever (even love. If it is, probably
you're a candidate for elections in US).

Among the many things, consider that a IC-based backup strategy is 'your',
in the sense that you can manage it by your own, while a DASD-based stategy
(actually it's used for DR purposes) is somewhat 'system-wide' and has a
more limited field of use. And you've to ask for help to your best friends
DASD managers.

As I said some years ago (when I thought things were all white or or all
black) you have to detect the 'heartbeat' (or wavelength as I call it) of
main applications (ie a meaningful period of applications activity). When
heartbeat is known, your IC strategy become quite clear.

For instance, historical tables usually have a long-period heartbeat
(weekly monthly, yearly...) ie they are not updated so frequently. ZIP
tables (or something similar) are updated not so often.
Orders tables are updated every second. Some bank table$ are updated a lot
during some periods (say Xmas). Some others are updated randomly. And all
of the are updated batch, online or both.

The only hint I can give to you is: it's better to have one IC in excess
than one IC missing. This is your real goal.

Max Scarpa

Certified DB2 Jedi Knight
Star join wars department
Obi-wan-Kenobi Ltd
Tatooine







"Lyon, Lockwood"
<[login to unmask email]
.COM> To
Sent by: DB2 Data [login to unmask email]
Base Discussion cc
List
<[login to unmask email] Subject
ORG> Re: [DB2-L] DB2 Backups Strategy on
z/OS

09/01/2008 23.48


Please respond to
DB2 Database
Discussion list
at IDUG
<[login to unmask email]
2-l.org>






Fred,

As I have expounded in multiple articles and IDUG presentations, most
shops go about this backwards. They keep asking about "Backup"
strategies. There are no such: there are only "backup tactics" that
support a Recovery Strategy.

I recommend you review your Tablespace/Index recovery requirements. If
applications have SLAs regarding downtime during a recovery, then what
combination of backup strategies do you need to meet those recovery
requirements?

Example: a 100GB table with a 50 GB partitioning index. The application
(a financial one) requires that any outage be no more than 30 minutes.
In our case, while it might have been possible to recover the tablespace
from multiple partition backups, the REBUILD of the Index took several
hours. Hence, we had to consider: (a) Index Image Copies; (b) DASD
mirroring; (c) "Shadow" tables; and, (d) other backup methods.

Lock Lyon
Fifth Third Bancorp


-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email] On
Behalf Of Lavoie, Frederic
Sent: Wednesday, January 09, 2008 4:09 PM
To: [login to unmask email]
Subject: [DB2-L] DB2 Backups Strategy on z/OS

Hello,

We would like to know if any documentation is written about DB2
Backups Strategies on z/OS?

Something to guide us with :
- hot or cold backups, when and why? Pros and cons?
- full or incremental, when and why? Pros and cons?
- RETPD to use
- daily, weekly, monthly backups? Pros and cons?
- etc...

We have to create some kind of documentation about best practices.

Here we have more tant 100 different DB2 databases in production and
we are talking about 1 or 2 dba per databases and we would like to
create guide lines to have something more consistent regarding the
backups. At the moment every DB has their own way to do backups....

So if something is already written, I will not have to start from
scracth.

Thank you.

Fred Lavoie
DB Common Group
*613-954-9286

This e-mail transmission contains information that is confidential and may
be privileged. It is intended only for the addressee(s) named above. If
you receive this e-mail in error, please do not read, copy or disseminate
it in any manner. If you are not the intended recipient, any disclosure,
copying, distribution or use of the contents of this information is
prohibited. Please reply to the message immediately by informing the sender
that the message was misdirected. After replying, please erase it from your
computer system. Your assistance in correcting this error is appreciated.

The IDUG DB2-L Listserv is only part of your membership in IDUG. DB2-L
list archives, the FAQ, and delivery preferences are at
http://www.idug.org/lsidug under the Listserv tab. While at the site, you
can also access the IDUG Online Learning Center, Tech Library and Code
Place, see the latest IDUG conference information, and much more. If you
have not yet signed up for Basic Membership in IDUG, available at no cost,
click on Member Services at http://www.idug.org/lsms

The IDUG DB2-L Listserv is only part of your membership in IDUG. DB2-L list archives, the FAQ, and delivery preferences are at http://www.idug.org/lsidug under the Listserv tab. While at the site, you can also access the IDUG Online Learning Center, Tech Library and Code Place, see the latest IDUG conference information, and much more. If you have not yet signed up for Basic Membership in IDUG, available at no cost, click on Member Services at http://www.idug.org/lsms

Avram Friedman

Re: DB2 Backups Strategy on z/OS
(in response to Max Scarpa)
Max and Lyon
There is an additional wrinkle to this backup recovery issue.

In a single shop there can be many groups with diffrerent but over lapping
stakes in the Business Continuity world. For example

The storage Management team may have the responsibility for getting
PRODUCTION and SYSTEM DASD back ... These are often to copy restores in
DB2 terms and the backups are taken quite independently of what DB2 might
or might not be doing at the moment.

The Systems Programmers / System DBA's Here the backup / recovery tends
to be very bookish ... we will restrore the DB2 subsystem to current where
current is defined as to the latest logs available at DR. We will provide the
intrastructure support (Software and logs) to allow application areas to
recover there objects to 'current'

Applications. From my own perspective this is where things get a bit weird.
It is not uncommon for an application group to arugue
PIT recoveries only and then we will simply rerun the updating applications.
or
The primary key of our big objects is date related so we know what parts
have changed and what parts have not. Why back up (Image copy parts)
that have not changed for years

What tends to happen is things get bumped up the chain, An application
recovery failure results in they claiming the SysProgs SysDBAs should of been
better prepared. A DB2 system recovery failure is usually the fault of Storage
Management, A Storage management failure gets blamed on the operating
system group. Operating system problems usually gets blamed on the Business
Continuity plan etc etc etc

The problem is each of these groups has diffrent procedures and objectives.
As a result when procedures get more and more diffrent groups take actions
to CYA (Cover Your Ass) For example many storage management groups will
back up DB2 database volumes no matter how lould people screem WE HAVE
IMAGE COPIES.

From a DB2 Systems standpoint CYA calls for coping things when the last
copy in SYSCOPY approaches or exceeds the log archive rentenion period.
Typically an attempt should be made to charge a lot for this service.
Municipalities will often shovel the snow for lazy homeowners and levy a Big
FEE its the same idea.

The CYA requirements tend to be reduced in shops that have consistant
policies. When application groups have expected and monitored deliverables
for copies there is less CYA work for the SysProgs.

By the way I don't whant people to think I am picking on application people,
everyone sees the world through there own glasses and mine are those of an
old time SysProg.

Regards
Avram Friedman


On Fri, 11 Jan 2008 09:16:07 +0100, [login to unmask email] wrote:

>
>I agree with Lyon. In many shops I saw there's no a 'approved' strategy as
>it depends on SLAs (if any), on type of business the company does, down to
>the single DBA's ideas about backups.
>And a given strategy change over the time: for example moving from a
>IC-based DR to a DASD-replication DR. So don't consider a chosen strategy
>a 'strategy forever', nothing is forever (even love. If it is, probably
>you're a candidate for elections in US).
>
>Among the many things, consider that a IC-based backup strategy is 'your',
>in the sense that you can manage it by your own, while a DASD-based
stategy
>(actually it's used for DR purposes) is somewhat 'system-wide' and has a
>more limited field of use. And you've to ask for help to your best friends
>DASD managers.
>
>As I said some years ago (when I thought things were all white or or all
>black) you have to detect the 'heartbeat' (or wavelength as I call it) of
>main applications (ie a meaningful period of applications activity). When
>heartbeat is known, your IC strategy become quite clear.
>
>For instance, historical tables usually have a long-period heartbeat
>(weekly monthly, yearly...) ie they are not updated so frequently. ZIP
>tables (or something similar) are updated not so often.
>Orders tables are updated every second. Some bank table$ are updated a lot
>during some periods (say Xmas). Some others are updated randomly. And all
>of the are updated batch, online or both.
>
>The only hint I can give to you is: it's better to have one IC in excess
>than one IC missing. This is your real goal.
>
>Max Scarpa
>
>Certified DB2 Jedi Knight
>Star join wars department
>Obi-wan-Kenobi Ltd
>Tatooine
>
>
>
>
>
>
>
> "Lyon, Lockwood"
> <[login to unmask email]
> .COM> To
> Sent by: DB2 Data [login to unmask email]
> Base Discussion cc
> List
> <[login to unmask email] Subject
> ORG> Re: [DB2-L] DB2 Backups Strategy on
> z/OS
>
> 09/01/2008 23.48
>
>
> Please respond to
> DB2 Database
> Discussion list
> at IDUG
> <[login to unmask email]
> 2-l.org>
>
>
>
>
>
>
>Fred,
>
>As I have expounded in multiple articles and IDUG presentations, most
>shops go about this backwards. They keep asking about "Backup"
>strategies. There are no such: there are only "backup tactics" that
>support a Recovery Strategy.
>
>I recommend you review your Tablespace/Index recovery requirements. If
>applications have SLAs regarding downtime during a recovery, then what
>combination of backup strategies do you need to meet those recovery
>requirements?
>
>Example: a 100GB table with a 50 GB partitioning index. The application
>(a financial one) requires that any outage be no more than 30 minutes.
>In our case, while it might have been possible to recover the tablespace
>from multiple partition backups, the REBUILD of the Index took several
>hours. Hence, we had to consider: (a) Index Image Copies; (b) DASD
>mirroring; (c) "Shadow" tables; and, (d) other backup methods.
>
>Lock Lyon
>Fifth Third Bancorp
>

The IDUG DB2-L Listserv is only part of your membership in IDUG. DB2-L list archives, the FAQ, and delivery preferences are at http://www.idug.org/lsidug under the Listserv tab. While at the site, you can also access the IDUG Online Learning Center, Tech Library and Code Place, see the latest IDUG conference information, and much more. If you have not yet signed up for Basic Membership in IDUG, available at no cost, click on Member Services at http://www.idug.org/lsms

Max Scarpa

Re: DB2 Backups Strategy on z/OS
(in response to Avram Friedman)


Avram

It is what (probably I missed my goal) I tried to point out. I prefere a
full IC-based strategy but I know that there are companies using DASD-based
strategy to 'fill holes' in IC-strategy, holes that shouldn't

exists. It they are present, your strategy could (in my opinion is) wrong
as if something goes wrong and you're not able to restore some data, worl
war III will start in your company.

What I want to say is that now a IC strategy is more complicated than some
years ago.

Max Scarpa



The IDUG DB2-L Listserv is only part of your membership in IDUG. DB2-L list archives, the FAQ, and delivery preferences are at http://www.idug.org/lsidug under the Listserv tab. While at the site, you can also access the IDUG Online Learning Center, Tech Library and Code Place, see the latest IDUG conference information, and much more. If you have not yet signed up for Basic Membership in IDUG, available at no cost, click on Member Services at http://www.idug.org/lsms

Frederic Lavoie

Re: DB2 Backups Strategy on z/OS
(in response to Max Scarpa)
Hello,

I would like to thank everybody that responds to me. That was
useful.

Fred Lavoie
DB Common Group
*613-954-9286

The IDUG DB2-L Listserv is only part of your membership in IDUG. DB2-L list archives, the FAQ, and delivery preferences are at http://www.idug.org/lsidug under the Listserv tab. While at the site, you can also access the IDUG Online Learning Center, Tech Library and Code Place, see the latest IDUG conference information, and much more. If you have not yet signed up for Basic Membership in IDUG, available at no cost, click on Member Services at http://www.idug.org/lsms