Backup DB into selected volumes

[p.winiarczyk]

Hi,

I'd like to ask you about database backups. After reading manual and few articles I've decided to make daily incremental database backups and full backup once a week. For my small system it is enough. Problem is in volumes where i want to store them.

I think that good idea is to keep database backups in selected volumes . Thats why I invoke following db command:

backup db devc=tape type=inc scratch=no vol=GS6118L3,GS6119L3

Problem is that after scheduling it, only two backups were invoke, and when I try make another, TSM responces that this volumes are in use and skips them.

So, my question is how to force TSM server to store database backups (active and past) in this two volumes (LTO3) ?

In volume history I have notices that full backup was send into GS6118L3, and incremental into GS6119L3.

Some actlog:

08/19/2010 02:00:12      ANR2017I Administrator TSMADMIN issued command: BACKUP DB
 AM                       devc=tape type=inc scratch=no vol=GS6118L3,GS6119L3
                          (SESSION: 2772)
08/19/2010 02:00:12      ANR4559I Backup DB is in progress. (SESSION: 2772)
 AM
08/19/2010 02:00:12      ANR0984I Process 9 for DATABASE BACKUP started in the
 AM                       BACKGROUND at 02:00:12 AM. (SESSION: 2772, PROCESS: 9)
08/19/2010 02:00:12      ANR2281I Incremental database backup started as process 9.
 AM                       (SESSION: 2772, PROCESS: 9)
08/19/2010 02:00:12      ANR2753I (BACKUPSDB):ANR2281I Incremental database backup
 AM                       started as process 9.  (SESSION: 2772)
08/19/2010 02:00:12      ANR2756I Scheduled command BACKUPSDB started successfully.
 AM                       (SESSION: 2772, PROCESS: 9)
08/19/2010 02:00:12      ANR0406I Session 2773 started for node $$_TSMDBMGR_$$
 AM                       (DB2/LINUXX8664) (Tcp/Ip localhost(59914)). (SESSION:
                          2773)
08/19/2010 02:00:12      ANR1409W Volume GS6118L3 already in use - skipped.
 AM                       (SESSION: 2773)
08/19/2010 02:00:12      ANR1409W Volume GS6119L3 already in use - skipped.
 AM                       (SESSION: 2773)
08/19/2010 02:00:12      ANR4521E The number of volumes specified in the BACK DB
 AM                       command is not sufficient Backup failed. (SESSION: 2773)
08/19/2010 02:00:13      ANR4583E Database backup terminated - output media full
 AM                       and scratch media could not be mounted. (SESSION: 2773)

Is it possible to append database backup to perviously used tape ?
I was wondering also if such often mount of tapes may damage them ?

Thanks for your help

 

[axisminden]

TSM use one Tape per DB Backup. you can not use again.

regards
michael

 

[ChrisRees]

Hi

Just let TSM use scratch tapes for DB backups, much easier and it works fine.

Cheers

 

[p.winiarczyk]

Thanks for your reply,

so it sad for me that TSM use one db backup per one tape. In my testing environment I have only two scratch tapes.

So the solution is to have more scratch tapes and or manipulate retention time for db backups. But it isn't health for tape to month and unmount her very often.

Have you tried to store db backups in FILE device class ?

 

[chris_magic]

Hi,

Yes, you can backup your TSM DB on a devclass FILE.
I did this operation everyday in more than backup on tape.

Regards,

 

[Jacob_6]

You could try doing your incrementals to disk and your fulls to tape. I did all my backups to disk, after a server that I was getting ready to retire lost all its connections to the physical library and management didn't want to pay for new fddi cards for a system that was going to be going out of service in a month or so.

It would mean changing you db retention to one, so you could cycle the tapes through or just add a third scratch tape to your rotation.

 

[p.winiarczyk]

Thank you for your advices. I will try make db backups on FILE device class and store them into storage array. I think it will be efficient and safe.

Regards