This answers a lot of questions for me, thank you so much!
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Mark
Haye
Sent: Wednesday, February 22, 2012 6:37 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] What if (NDMP)
"Package deal" ... I'm
"Package deal" ... I'm going to use that. :)
You are correct. Objects that are expired but not yet deleted won't be
visible and therefore can't be selected for restore.
The same concepts apply to normal backup files. For example, the behavior
of NDMP backup versions is identical to that of ada
This matches what I see in our environment - q nasbackup doesn't show the full
backup that the differentials depend upon, once the full backup ages out. We
have successfully restored volumes using a recent differential with its older
associated full backup so it does work. However, your use of
I'm not directly familiar with the NDMP backup expiration scenario, but
what you're describing makes sense to me. If the full is older than what
the copy group is set to, then it seems reasonable that you can only
restore, in it's own right, the backups which have not yet been expired -
ie. a diff
A full backup that has a dependent differential can be expired, but will
not be deleted. This means that a full backup that is beyond the retention
criteria will not be visible, but will be available for restoring
differentials. As others have noted, fulls and differentials are managed
by the sam
On 22 feb. 2012, at 14:20, Ehresman,David E. wrote:
> What if there were a
>
> 1) storage pool with retonly=15 and retextra=15
>
> 2) it received data from a backup node (NDMP) process
>
> 3) the NDMP runs a full backup once every six months
>
> 4) the NDMP run an increment
Hi,
I had such a kind of problem on a fresh install of TSM 6.2.3 (on Linux) :
ANR0171I dbiconn.c(1952): Error detected on 0:1, database in evaluation mode.
When doing the dsmserv format in order to create the DB, the db2sysc tried to
make a lookup to the LDAP server for the instance owner. As t
I'm thinking since they are indeed DIFFs not incrementals, I'll end up with one
Full and one Diff most months, and just a Full on the month I do a full.
David
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Prather, Wanda
Sent: Wednesday, Febr
Yes, but I'm still looking for the answer to your original question.
If the diffs are tied to the fulls as a set/same object, doesn't that mean if
you do one full and then do diffs for 6 months, that you end up with 6 months
of diffs in storage, no matter what the retextra/retonly setting?
Same management class is used for both full and incremental
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Christian Svensson
Sent: Wednesday, February 22, 2012 10:27 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] SV: What if
Hi,
The Full Backu
I'm glad David asked this question, because I have the same one, as I have been
digging around in the backups table trying to figure out what goes on.
The question is, if retextra is 15 and retonly is 15, and you take one full
NDMP backup followed by 20 diffs, does anything roll off?
How many fu
Hi,
The Full Backup and Inc Backup are the same object for TSM.
That mean if you backup the Full Backup with Managment Class A then backup
Incremental with MG Class B, TSM will then change the FULL backup to MG Class B.
Best Regards
Christian Svensson
Cell: +46-70-325 1577
E-mail: christian.sve
What if there were a
1) storage pool with retonly=15 and retextra=15
2) it received data from a backup node (NDMP) process
3) the NDMP runs a full backup once every six months
4) the NDMP run an incremental monthly on the months a full is not run
What data does TSM actually
Hi,
Any info in db2diag.log?
https://www-304.ibm.com/support/docview.wss?uid=swg21383716
Kind regards,
Karel
-Oorspronkelijk bericht-
Van: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] Namens Killam,
Perpetua
Verzonden: woensdag 22 februari 2012 10:40
Aan: ADSM-L@VM.MARIST.EDU
ANYONE HAD ISSUES AFTER UPGRADING TO TSM6.3 FROM 6.2.1 on aix 6.1
Didn't have problems with another upgrade
Opened a ticket with IBM , WILL SEE WHAT THEY SAY
ANR7801I Subsystem process ID is 5112088.
15 matches
Mail list logo