Instead of doing a SELECTIVE backup on a periodic basis, which won't update the
last backup date/time of the filespace, use the
MODE=ABSOLUTE of the backup copygroup. In your domain, make a copy of the
active policy set and change all the management class
backup copygroups to MODE=ABSOLUTE instead of the default of MODIFIED. Then on
your "occasional" timeframe, run an admin schedule to
activate this policy set, do your backups which are incremental and then the
next day run another admin schedule to activate your
MODE=MODIFIED policyset. This way your schedules don't change and as far as the
client is concerned you just ran a unqualified
INCREMENTAL backup and the filespaces are updated. Since the active policyset
will have ABSOLUTS, you'll get a copy of every file
whether it's changed or not.
I've been doing TSM not for over 8-years and this is the first time I've ever
thought of a way to use multiple policyset definitions
in a domain.
Bill Boyer
"Backup my harddrive? How do I put it in reverse?" - ??
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Paul Dudley
Sent: Saturday, May 26, 2007 8:59 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Point in time restore problem
>From what I read the standard incremental backup is restricted in that it only
>backs up new or changed files since the last
incremental backup.
However I have been told that we need to run "absolute" incremental backups on
a periodic basis - these incremental backups backup
all files whether they have changed or not, so that the "Last Incr Date" is
updated, so that "Point in time" restores don't have to
traverse through a huge transaction log and spend long periods of time
restoring files that were later deleted.
I quote from the dsmc help option for incremental backups:
Mode:
Permits you to back up only files that changed since the last backup
(modified). Also permits you to back up the files whether they
changed or not (absolute).
What I want to know is if you can run an absolute backup from the command line
on the client server.
The end result I want to achieve from all of this, is to run full backups on a
periodic basis so that when I have to perform a
"Point in time" restore it does it quickly and does not have to traverse a huge
transaction log and restore files that were later
deleted.
Regards
Paul
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of Richard Sims
> Sent: Saturday, 26 May 2007 11:57 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] Point in time restore problem
>
> On May 26, 2007, at 9:34 AM, Paul Dudley wrote:
>
> > OK - can I perform an absolute/unqualified incremental backup from
the
> > command line using the dsmc command?
> >
> > If so then how? I cannot see the correct option to use under dsmc
> > incr.
>
> There is no option... That's the whole point - it's unqualified: you
are
> in no way restricting the incremental backup, which proceeds on the
> basis of inventory comparison with prior backups.
> This is the most basic TSM backup, as described in the client manual:
>
> Full and partial incremental backup
> If you select entire file systems, you are performing a full
> incremental
> backup. If you select a directory tree or individual files, you are
> performing a partial incremental backup.
>
> Read through the "Backing up your data" section of the client manual.
> The TSM Concepts redbook also helps explain the differences.
>
> Richard Sims
ANL - CELEBRATING 50 YEARS
ANL DISCLAIMER
This e-mail and any file attached is confidential, and intended solely to the
named addressees. Any unauthorised dissemination or
use is strictly prohibited. If you received this e-mail in error, please
immediately notify the sender by return e-mail from your
system. Please do not copy, use or make reference to it for any purpose, or
disclose its contents to any person.
|
