• Please help support our sponsors by considering their products and services.
    Our sponsors enable us to serve you with this high-speed Internet connection and fast webservers you are currently using at ADSM.ORG.
    They support this free flow of information and knowledge exchange service at no cost to you.

    Please welcome our latest sponsor Tectrade . We can show our appreciation by learning more about Tectrade Solutions
  • Community Tip: Please Give Thanks to Those Sharing Their Knowledge.

    If you receive helpful answer on this forum, please show thanks to the poster by clicking "LIKE" link for the answer that you found helpful.

  • Community Tip: Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING)

    Click the link above to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This notice will disappear after you have made at least 3 posts.

Backing up DB2 logs to disk

dank

ADSM.ORG Member
Joined
Mar 9, 2007
Messages
13
Reaction score
0
Points
0
Hi all,

I've had a nagging problem for ages now, which I think I've just worked out. Firstly, can someone tell me if I'm talking absolute rubbish, and secondly, if I'm not, can someone help me find a resolution.

Here's the scenario.

We have 2 DB2 systems, a test and a production. The test goes over the LAN, and the Production goes LAN Free.

The test system goes straight to the diskpool, which then gets migrated to tape at 05:00 every morning. Obviously being LAN Free, production goes straight to tape.

The main issue we've been having, is the incremental backups which run every night and every lunchtime. The production box picks up a tape, and happily goes on its way. The test system writes about 8 gig to disk (which is to be expected). Here's where the fun starts. In the last 5 minutes or so of its backup, the test system decides that it needs a tape, and pre-empts the mount point that the production server is using. This cancels the session for the production server, and the backup fails.

My thinking is - the bulk of the backup for the test system goes to disk, but when it gets to the "Include logs" part of the backup, its trying to put those straight to tape.

I think I have gotten round this by increasing the number of mount points that the test system can use (I will have to wait until tomorrow to check if this actually makes a difference.), so in theory it will mount a second tape if the production box is using the first. However, if this does work, I'd still like to get it writing solely to disk, otherwise I might as well just write the whole lot straight to tape anyway.

Any thoughts?
 

moon-buddy

ADSM.ORG Moderator
Joined
Aug 24, 2005
Messages
7,033
Reaction score
405
Points
0
Location
Somewhere in the US
How many tape drives do you have?

If you have more than 1 tape drive, then the test system should just mount another tape on another drive unless it was specified that DB2 backups will have to use a particular tape volume.
 

dank

ADSM.ORG Member
Joined
Mar 9, 2007
Messages
13
Reaction score
0
Points
0
We have 3 drives, which would be fine for lunchtimes, as they're the only backups running, but it gets a bit busy overnight, as there's a couple of other LAN Free backups running, so I'd like to keep the test system away from the drives if I can.
 

cheffern

ADSM.ORG Senior Member
Joined
Mar 9, 2005
Messages
1,006
Reaction score
7
Points
0
Location
Massachusetts, USA
Website
Visit site
Where are you running these jobs from - the TSM server as a scheduled backup? If so - what is the priority with which you run the job -
because -
In the last 5 minutes or so of its backup, the test system decides that it needs a tape, and pre-empts the mount point that the production server is using. This cancels the session for the production server, and the backup fails.
-
that should not be kicking any tape out -
it should be waiting in turn for a drive...

-Chef.
 

dank

ADSM.ORG Member
Joined
Mar 9, 2007
Messages
13
Reaction score
0
Points
0
No, the backups are scheduled from in DB2.
 

nbs03

ADSM.ORG Senior Member
Joined
Mar 24, 2004
Messages
263
Reaction score
3
Points
0
Location
Baltimore, Md
Website
Visit site
Dank,
Your DB should be going to the backup pool and logs should be using the archive pool storage defined in the management class. Check the destination of these and make sure that you don't have a maximum size threshold set.
cheers,
Neil
 

dank

ADSM.ORG Member
Joined
Mar 9, 2007
Messages
13
Reaction score
0
Points
0
Just checked the settings for the only management class in that domain - both the backups and the archive settings are set to go to the same disk pool.

The maximum size threshold is set to No Limit.
 
Last edited:

Advertise at ADSM.ORG

If you are reading this, so are your potential customer. Advertise at ADSM.ORG right now.

DigitalOcean $100 Credit

Support ADSM.ORG and get DigitalOcean FREE credit. DigitalOcean currently offer a $100, 60-day Free Credit for new accounts. Sign-up here:

DigitalOcean Referral Badge

The Spectrum Protect TLA (Three-Letter Acronym): ISP or something else?

  • Every product needs a TLA, Let's call it ISP (IBM Spectrum Protect).

    Votes: 20 18.7%
  • Keep using TSM for Spectrum Protect.

    Votes: 65 60.7%
  • Let's be formal and just say Spectrum Protect

    Votes: 13 12.1%
  • Other (please comement)

    Votes: 9 8.4%

Forum statistics

Threads
31,885
Messages
135,936
Members
21,783
Latest member
london
Top