I used 'delete volh' but sometimes it take effect and sometimes it doesn't
delete any volume as following depict :
tsm: FGVNGHIATD_SERVER1>q volh type=dbbackup
Date/Time: 04/07/2005 17:14:47
Volume Type: BACKUPFULL
Backup Series: 21
Backup Operation: 0
Volume Seq: 1
Device Class: FILEDEV3
Volume Name: D:\TSMDATA\SERVER1\12868887.DBB
Volume Location:
Command:
Date/Time: 04/07/2005 17:15:14
Volume Type: BACKUPFULL
Backup Series: 22
Backup Operation: 0
Volume Seq: 1
Device Class: FILEDEV3
Volume Name: D:\TSMDATA\SERVER1\12868914.DBB
Volume Location:
Command:
Date/Time: 04/08/2005 10:31:44
Volume Type: BACKUPFULL
Backup Series: 23
Backup Operation: 0
Volume Seq: 1
Device Class: FILEDEV3
Volume Name: D:\TSMDATA\SERVER1\12931104.DBB
Volume Location:
Command:
Date/Time: 04/08/2005 10:53:24
Volume Type: BACKUPFULL
Backup Series: 24
Backup Operation: 0
Volume Seq: 1
Device Class: FILEDEV3
Volume Name: D:\TSMDATA\SERVER1\12932404.DBB
Volume Location:
Command:
tsm: FGVNGHIATD_SERVER1>del volh tod=today tot=now type=dbb
Do you wish to proceed? (Yes (Y)/No (N)) Y
ANR2467I DELETE VOLHISTORY: 0 sequential volume history entries were
successfully deleted.
Although, I also set two following option in DRM, I can't not delete DB backup.
Primary Storage Pools: DISKPOOL FILEPOOL
Process FILE Device Type?: Yes
----- Original Message -----
From: "Daniel Sparrman" <Daniel.Sparrman AT EXIST DOT SE>
To: <ADSM-L AT VM.MARIST DOT EDU>
Sent: Wednesday, April 06, 2005 5:10 PM
Subject: Re: Backup TSM database
No, that command only takes effect when it is combined with database
volumes handled by the Disaster Recovery Manager expiration procedure.
Best Regards
Daniel Sparrman
-----------------------------------
Daniel Sparrman
Chef Utveckling & Drift
Exist i Stockholm AB
Propellervägen 6B
183 62 TÄBY
Växel: 08 - 754 98 00
Mobil: 070 - 399 27 51
nghiatd <nghiatd2 AT FPT.COM DOT VN>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
2005-04-15 12:19
Please respond to
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To
ADSM-L AT VM.MARIST DOT EDU
cc
Subject
Re: Backup TSM database
So that command only take effect if I use backup to tape ?
----- Original Message -----
From: "Daniel Sparrman" <Daniel.Sparrman AT EXIST DOT SE>
To: <ADSM-L AT VM.MARIST DOT EDU>
Sent: Wednesday, April 06, 2005 5:01 PM
Subject: Re: Backup TSM database
That command will not have the same effect. The drmbackupexpiredays only
sets the option for the DRM and not for expiration.
You cannot do this without using the delete volhist command.
Best Regards
Daniel Sparrman
-----------------------------------
Daniel Sparrman
Chef Utveckling & Drift
Exist i Stockholm AB
Propellervdgen 6B
183 62 TDBY
Vdxel: 08 - 754 98 00
Mobil: 070 - 399 27 51
nghiatd <nghiatd2 AT FPT.COM DOT VN>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
2005-04-15 12:06
Please respond to
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To
ADSM-L AT VM.MARIST DOT EDU
cc
Subject
Re: Backup TSM database
I use command : "Set drmdbbackupexpiredays 7" and it is not effective.
----- Original Message -----
From: "John Naylor" <John.Naylor AT SCOTTISH-SOUTHERN.CO DOT UK>
To: <ADSM-L AT VM.MARIST DOT EDU>
Sent: Wednesday, April 06, 2005 4:29 PM
Subject: Re: Backup TSM database
> this will delete all your database backups except the latest
> del volh tod=today tot=now type=dbb
>
> this will delete all your database backups except the last 7 days worth
> del volh tod=today-7 type=dbb
>
>
>
>
>
>
>
> nghiatd <nghiatd2 AT fpt.com DOT vn>
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu>
> 15/04/2005 10:08
> Please respond to
> "ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu>
>
>
> To
> ADSM-L AT vm.marist DOT edu
> cc
>
> Subject
> Re: Backup TSM database
>
>
>
>
>
>
> I set schedule to backup TSM database daily with command "backup db
> type=full devclass=filedev1". So I have a lot DB backup version.
>
>
> ----- Original Message -----
> From: "Daniel Sparrman" <Daniel.Sparrman AT EXIST DOT SE>
> To: <ADSM-L AT VM.MARIST DOT EDU>
> Sent: Wednesday, April 06, 2005 3:48 PM
> Subject: Re: Backup TSM database
>
>
> I would guess that you only have one database backup left on that
device?
>
> The last database backup on a specific device cannot be expired.
>
> Best Regards
>
> Daniel Sparrman
> -----------------------------------
> Daniel Sparrman
> Chef Utveckling & Drift
> Exist i Stockholm AB
> Propellervdgen 6B
> 183 62 TDBY
> Vdxel: 08 - 754 98 00
> Mobil: 070 - 399 27 51
>
>
>
> nghiatd <nghiatd2 AT FPT.COM DOT VN>
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> 2005-04-15 10:55
> Please respond to
> "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
>
> To
> ADSM-L AT VM.MARIST DOT EDU
> cc
>
> Subject
> Re: Backup TSM database
>
>
>
>
>
>
> I used use FILE type volumes to backup TSM database. But I can not
delete
> database backup volume with "expire inventory".
> ANR0812I Inventory file expiration process 3 completed:
> examined 2125 objects, deleting 10 backup objects, 0
> archive
> objects, 0 DB backup volumes, and 0 recovery plan
files.
> 0 errors were encountered.
>
> Do you have any idea ?
>
> Nghiatd,
>
>
> ----- Original Message -----
> From: "Richard Sims" <rbs AT BU DOT EDU>
> To: <ADSM-L AT VM.MARIST DOT EDU>
> Sent: Monday, April 04, 2005 7:06 PM
> Subject: Re: Backup TSM database
>
>
> > On Apr 19, 2005, at 7:28 AM, nghiatd wrote:
> >
> > > Can I use private tape if I incremental backup db. Not support
backup
> > > db to
> > > one tape is too waste
> >
> > One dbbackup per volume. See definitive statement in IBM TechNote
> > 1153782.
> >
> > TSM database backups are critical resources, and the intention is that
> > each tape be immediately securable by removing from the library and
> > securing in a vault or like safe place. And you don't want to have to
> > deal with partial expiration and reclamation issues.
> >
> > Where small libraries are an issue, the developers have provided the
> > ability to use FILE type volumes. (You could even have an SATA drive
> > running inside a safe as the destination of such backups.)
> >
> > Richard Sims
> >
>
>
>
> **********************************************************************
> The information in this E-Mail is confidential and may be legally
> privileged. It may not represent the views of Scottish and Southern
> Energy Group.
> It is intended solely for the addressees. Access to this E-Mail by
> anyone else is unauthorised. If you are not the intended recipient,
> any disclosure, copying, distribution or any action taken or omitted
> to be taken in reliance on it, is prohibited and may be unlawful.
> Any unauthorised recipient should advise the sender immediately of
> the error in transmission. Unless specifically stated otherwise, this
email (or any attachments to it) is not an offer capable of acceptance or
acceptance of an offer and it does not form part of a binding contractual
agreement.
>
>
> Scottish Hydro-Electric, Southern Electric, SWALEC, S+S and SSE Power
Distribution are trading names of the Scottish and Southern Energy Group.
> **********************************************************************
>
|
