:
Sent by: ADSM: Subject: Re: progressive backup vs.
full + incremental
Dist Stor Manager
:
Sent by: ADSM: Subject: Re: progressive backup vs.
full + incremental
Dist Stor Manager
:
NOLOGIE.FR Subject: Re: progressive backup vs.
full + incremental
Sent by: ADSM:
Dist Stor Manager
:
NOLOGIE.FR Subject: Re: progressive backup vs.
full + incremental
Sent by: ADSM
]
[EMAIL PROTECTED]cc:
NOLOGIE.FR Subject: Re: progressive
backup vs. full + incremental
Sent by: ADSM:
Dist Stor Manager
[EMAIL PROTECTED]
EDU
Roger Deschner
[EMAIL PROTECTED] To: [EMAIL PROTECTED]
Sent by: ADSM: cc:
Dist StorSubject: Re: progressive backup vs.
full + incremental
Manager
:[EMAIL PROTECTED]
Sent: Friday, March 07, 2003 12:31 PM
To: [EMAIL PROTECTED]
Subject: Re: progressive backup vs. full + incremental
My question to you would be, could you do a restore, say 3 months ago, or 9
months ago? How do you keep files longer than the versions on the active
database. Our
To: [EMAIL PROTECTED]
Subject: Re: progressive backup vs. full + incremental
I am going to stick my foot in my mouth but here goes. I do not feel that
3
months ago, 9 months ago, or 7 years ago are backups. These are archives.
We have the problem here that the higher ups tend to think
I am going to stick my foot in my mouth but here goes. I do not feel that 3
months ago, 9 months ago, or 7 years ago are backups. These are archives.
Or perhaps, waybackups, to coin a phrase to maintain delineation between
TSM Backups and Archives. :-)
Richard
Richard,
Should proper credit go to 'Mr. Peabody' for that one?
Richard Sims wrote:
I am going to stick my foot in my mouth but here goes. I do not feel that 3
months ago, 9 months ago, or 7 years ago are backups. These are archives.
Or perhaps, waybackups, to coin a phrase to maintain
cc:
Sent by: ADSM: Subject: Re: progressive backup vs.
full + incremental
Dist Stor Manager
:
NOLOGIE.FR Subject: Re: progressive backup vs.
full + incremental
Sent by: ADSM
:
Sent by: ADSM: Subject: Re: progressive backup vs.
full + incremental
Dist Stor Manager
[EMAIL PROTECTED]To: [EMAIL PROTECTED]
E.ID.US cc:
Sent by: ADSM: Subject: Re: progressive backup vs.
full + incremental
Dist Stor
Manager
of Contract Employees
(P.A.C.E. -- www.pacepros.com)
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
William Rosette
Sent: Wednesday, March 05, 2003 7:22 AM
To: [EMAIL PROTECTED]
Subject: Re: progressive backup vs. full + incremental
This progressive
: Re: progressive backup vs.
full + incremental
Dist Stor
Manager
[EMAIL PROTECTED]
.EDU
03/06/2003 03:09
PM
Please respond
To (briefly?) summarize... (the first two bullets address your original query):
- With TSM, all the active AND inactive versions are (a) always in the silo, (b) only
sent across the network ONCE (if you use the progressive-incremental the way it was
intended)... extra copies of the same version
Old style Full+Incr (as it was some 15-20 years ago...)
Say you run weekend full with weekday incrementals.
Say on Friday, your environment goes down
You restore from your weekend full
You restore from your Mon incr (all the data on the tapes)
You restore from your Tue incr
Progressive incremental backs up only new or changed files. during the
initial backup the client backs up all eligible files of course(full
backup). Subsequently, files are backed up again only if they are new or
have changed since the last backup. In TSMs case, a pointer to each version
of
TSM can give very quick restores, but beware fragmentation in uncollocated
tape pools. We had to rebuild a small (350GB) unix server last year that
required upward of 300 tape mounts, and finding a single file in the middle
of each tape. It took days.
Since then I have gotten funding to buy
what is the difference between
full+incremental , incremental and partial incremental ?
also when I do
dsmc incr
which incremental backup procedure is applied ?
do I need to always specify subdir=yes to backup all changed (data)
files , directories since last incr backup or dsmc incr
21 matches
Mail list logo
