om: "Loon, Eric van (ITOPT3) - KLM" <eric-van.l...@klm.com>
> To: ADSM-L@VM.MARIST.EDU
> Date: 06/21/2017 04:28 AM
> Subject: Re: SAP HANA backup expiration
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU>
>
> Hi Del!
> Thank you very
Engineering
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Del
Hoobler
Sent: maandag 19 juni 2017 15:48
To: ADSM-L@VM.MARIST.EDU
Subject: Re: SAP HANA backup expiration
Hi Eric,
Once the backups have been deleted in HANA Studio, then HANA will delay
plan to add support for expiration based on version limit in a
future delivery.
Del
"ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> wrote on 06/19/2017
05:22:33 AM:
> From: "Loon, Eric van (ITOPT3) - KLM" <eric-van.l...@klm.com>
> To: ADSM-L@VM.MAR
Dear Del,
About a year ago you explained why TDP for HANA backup versioning is no longer
working (see your mail down below), do you know if SAP has fixed this issue by
now?
I'm still struggling with this in our environment. The only documentation I can
find on the IBM site about this issue is
We have two TSM 6.2.2.0 servers running under mainframe Linux. Both
report 'DB Backup Series Expiration Days: 3 Day(s)' when I execute
'query drmstat' commands.
One of the systems is configured as a library manager. It performs
a database snapshot and a full database backup daily. These are
@VM.MARIST.EDU
Reply-To: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] DB backup expiration
We have two TSM 6.2.2.0 servers running under mainframe Linux. Both
report 'DB Backup Series Expiration Days: 3 Day(s)' when I execute
'query drmstat' commands.
One of the systems
-
From: Thomas Denier thomas.den...@jeffersonhospital.org
Sender: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU
Date: Mon, 1 Aug 2011 16:01:16
To: ADSM-L@VM.MARIST.EDU
Reply-To: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] DB backup expiration
We have two TSM
Hi to all
I want to keep a backup version for 1 year. How i must define the
management class below:
Policy Domain NameSVCY185_POLICYDOMAIN
Policy Set Name SVCY185_POLICYSET
Mgmt Class Name CY185MGMT
Copy Group Name STANDARD
Versions
Hi,
It depends on what you really want? Keep all versions 1 year, versions =
nolimit. See below.
//Henrik
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Nicolas Savva
Sent: den 9 december 2005 11:09
To: ADSM-L@VM.MARIST.EDU
Subject: Backup
On Mar 28, 2005, at 2:51 AM, Nicolas Savva wrote:
...If i am correct, based on the above mc an inactive file will be
deleted
after 33 days. What about the active backup? for example i am trying to
restore a file that i took backup, and i can't see any of
inactive/active
backup versions of this
anything, at 22-848523.
Yiannakis
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Nicolas Savva
Sent: Monday, March 28, 2005 10:52 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Backup expiration
Hi to all
I have the following management class:
Policy Domain
Hi to all
I have the following management class:
Policy Domain NameSVCY185_POLICYDOMAIN
Policy Set Name SVCY185_POLICYSET
Hi experts,
Can anyone help me out in understanding the series of commands used in
scheduling Tivoli database backup expiration process if we ignore del
volhist command.
Regards
Akash Jain
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On
Behalf Of Akash Jain
Can anyone help me out in understanding the series of commands
used in scheduling Tivoli database backup expiration process
if we ignore del volhist command.
I'm not sure what you mean by ignore, but there are two
Since I installed 4.2.1 I see my expiration of old db backups and the
pending volumes has not been happening automatically. Yesterdays database
snapshot did this:
10/23/01 14:04:44 ANR0984I Process 158 for DATABASE BACKUP started in
the
BACKGROUND at 14:04:44.
15 matches
Mail list logo
