-at-a-time.
From:
Clark, Margaret MClark at SDDPC.ORG
To:
ADSM-L at VM.MARIST.EDU
Date:
08/25/2010 02:50 PM
Subject:
Re: [ADSM-L] Expiration question
Sent by:
ADSM: Dist Stor Manager ADSM-L at VM.MARIST.EDU
A bit late, but I don't recall any previous responses to this... It will
do
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Zoltan
Forray/AC/VCU
Sent: Monday, August 23, 2010 7:32 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Expiration question
I have 2-issues with expiration processing.
First, on my 5.5.4.2 server - we
02:50 PM
Subject:
Re: [ADSM-L] Expiration question
Sent by:
ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU
A bit late, but I don't recall any previous responses to this... It will
do no good to cancel a running expiration process. When you start again,
expiration picks up exactly where it left off
There is Cancel Expiration,
and then there is Cancel Process on that process number, to different effect.
;-)
I have 2-issues with expiration processing.
First, on my 5.5.4.2 server - we stopped expiration for more than a week,
to perform recovery of a large SAN failure.
Now, expiration has been running since 08/17 and still running. Expired
over 24M objects out of 29M examined. Didn't know if I
Hello,
TSM: 5.1.6.4 w/DRM enabled
AIX: 4.3.3.10
I having been looking at the completion of my expiration processes for
the last 15 days and I see, for example, the following:
07/27/03 15:15:01 ANR2017I Administrator ADMIN issued command:
EXPIRE
INVENTORY
...
The process is completing successfully, but as you can see no DB backup
volumes or recovery plans are expired. I have an admin schedule that
has the following command in it: delete volhistory todate=today-30
type=all, which I do not think would affect the expiration of DB and
recovery plan
command.
-Original Message-
From: Mahesh Tailor [mailto:[EMAIL PROTECTED]
Sent: Monday, July 28, 2003 7:43 AM
To: [EMAIL PROTECTED]
Subject: Expiration Question on 5.1.6.4
Hello,
TSM: 5.1.6.4 w/DRM enabled
AIX: 4.3.3.10
I having been looking at the completion of my expiration processes
the
automatic expiration of DRM database backup volumes is by using
the SET
DRMDBBACKUPEXPIREDAYS command.
-Original Message-
From: Mahesh Tailor [mailto:[EMAIL PROTECTED]
Sent: Monday, July 28, 2003 7:43 AM
To: [EMAIL PROTECTED]
Subject: Expiration Question on 5.1.6.4
Hello,
TSM: 5.1.6.4 w
Environment:
TSM 5.1.1.6 on AIX 4.3.3
TSM Client 5.1.5.15 on Netware 6
On one of my Netware nodes someone deleted directory say
vol1:\home\jdoe\dir\0301 with files underneath on 03/04. That night backups
ran inactivated the directory all files. Now the next day the person
recreated the
You should have at least one inactive copy of all the files for however long
your retainonly version is set for.
Make sure you're viewing active/inactive.
Kamp, Bruce wrote:
Environment:
TSM 5.1.1.6 on AIX 4.3.3
TSM Client 5.1.5.15 on Netware 6
On one of my Netware nodes someone deleted
Does anyone know the particulars on how expiration works.
Normally we are run expiration with a time limit or 6 hours. When we ran it
without the time limit it ran for 15 hours and never finished.
Does expiration start reviewing the db from the beginning or is there some sort
of flag set on
to:
|
| Subject: Another Expiration question
Does anyone know the particulars on how expiration works.
There's information in the Admin Guide, and under the EXPIre Inventory
entry in http://people.bu.edu/rbs/ADSM.QuickFacts . The process was
recently discussed on ADSM-L, relative to Cancel Process vs. Cancel
Expiration - also noted in
Bruce,
When doing a full backup, Data Protection for Exchange will inactivate
any previous incrementals that exist.
I would guess that your policy settings are set up in such a way that
those incrementals are still being retained.
From the policy section in the User's Guide:
-
Incremental
System
E: [EMAIL PROTECTED]
P: (954) 987-2020 x4597
F: (954) 985-1404
---
-Original Message-
From: Del Hoobler [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 13, 2003 8:39 AM
To: [EMAIL PROTECTED]
Subject: Re: Exchange Restore/Expiration Question
Bruce,
Are both log backups and full backups going to this same
management class? If so, that explains it.
Since logs are uniquely named, once DP for Exchange
marks them inactive, they abide by the
Retain Only Version rule... which you show below as 120 days.
So that means they will stay around
Exchange 5.5 SP4 on Win2k SP3
TDP v5.1.5.0
TSM 5.1.1.6 on AIX 4.3.3
Went to do an Restore of 1 of my Exchnage servers when I looked to see how
far back the backups go I see a full ran on 1/26 but I also see a lot of
incrimentals before that. The thing I don't understand is that there is no
full
Richard Sims [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED]
16.01.2003 14:25
Please respond to ADSM: Dist Stor Manager
To: [EMAIL PROTECTED]
cc:
Subject:Re: Quick expiration question
Just a quickie. When an inremental backup runs, some
So is there no way to keep a nodes data (both active and inactive) from
expiring??
-Original Message-
From: Seay, Paul [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 16, 2003 5:29 PM
To: [EMAIL PROTECTED]
Subject: Re: Quick expiration question
Files that do not have an active
Hi TSMers
Just a quickie. When an inremental backup runs, some files get expired.
Does this mean that they are 'marked' for expiration, but only get deleted
from the database when the Expire Inventory job is run?
Thanks
Farren Minns - John Wiley Sons Ltd
On Thu, Jan 16, 2003 at 09:03:09AM +, Farren Minns wrote:
Just a quickie. When an inremental backup runs, some files get expired.
Does this mean that they are 'marked' for expiration, but only get deleted
from the database when the Expire Inventory job is run?
yes.
--
bx
Seize the
-Original Message-
From: Richard Sims [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 16, 2003 6:26 AM
To: [EMAIL PROTECTED]
Subject: Re: Quick expiration question
Just a quickie. When an inremental backup runs, some files get expired.
Does this mean that they are 'marked' for expiration
) [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 16, 2003 12:38 PM
To: [EMAIL PROTECTED]
Subject: Re: Quick expiration question
In light of this, what would be the best way to protect a node's data from
expiring at all?? To keep from both active and inactive versions expiring??
If we rename
All-
Please help me understand this issue. The issue is expiration takes place
,but how
do I confirm its working ok.
I see files get marked in backup schedule and gets deleted as per parameters
,but
still how to verify all goes well?
One of the node has more tapes occupied than other even if
: Wednesday, July 10, 2002 3:38 PM
To: [EMAIL PROTECTED]
Subject: Re: Expiration question.
A quick way is to monitor expiration while it is running with q process.
You can see that objects are being deleted. If it runs during the night
then the next day do a q actlog begind=-1 sea=expiration and see
A quick way is to monitor expiration while it is running with q process.
You can see that objects are being deleted. If it runs during the night
then the next day do a q actlog begind=-1 sea=expiration and see
the summary when it finishes as to how much was deleted.
(Note: The number of objects
Hello,
I have a problem that I am hoping you can help me with. Some of our
Novell servers got hit by a virus because Norton was not up to date. The
network engineers updated Norton to the latest version then ran a full scan
on the servers. Norton apparently touches the files when doing a
backups where ll_name like
'%PART_OF_A_FILENAME%' and
node_name='NOVELLNODEVICTIM'
-Original Message-
From: Alan Davenport [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 24, 2002 2:16 PM
To: [EMAIL PROTECTED]
Subject: File Expiration question.
Hello,
I have a problem that I am
PROTECTED]
To: [EMAIL PROTECTED]
cc:
Subject:File Expiration question.
Hello,
I have a problem that I am hoping you can help me with. Some of our
Novell servers got hit by a virus because Norton was not up to date. The
network engineers updated Norton to the latest version
Expiration is not designed to just delete one file. It runs through entire database
each time and deletes any and all files that meet criteria, for all storage pools and
files. It will do this unless there is a time limit set on it or it terminates
abnormally.
Then reclamation will reclaim
Hello,
I have one primary tape pool and (I won't get into it) and two copy tape
pools.
Example:
I have three copies of a file. The file in the primary pool WILL be
expired.
when expiration processing gets to it.
Does expiration remove AT THE SAME TIME the copies or does expiration
have go
32 matches
Mail list logo
