Hi
I'm sorry, I'm still slightly confused. The problem is that under
incremental backup I am not often seeing the databases backed up. I now
know that if the db is compacted that will change the dbiid and thus it
will be backed up, but is this enough.
My position is this. We do a full backup each weekend, so I'm happy with
this. Each day we do an incremental which apparently doesn't back any
databases up, but we do then back up the transaction logs. So I'm happy
that we can restore from the weekly and then roll forward without too much
trouble.
So can I be happy that things are working as necessary, or should the
database dbiids be changing under other circumstances as well and thus
being backed up during the week also?
I apologise if I'm just being dumb here :-(
Many thanks again
Farren Minns
Solaris System Admin / Oracle DBA
IT - Hosting Services
John Wiley & Sons, Ltd.
The Atrium,
Southern Gate,
Chichester,
West Sussex PO19 8SQ.
Tel: +44 (0) 1243 770406
Fax: +44 (0) 1243 775878
|-----------------------------+-------------------------------------------|
| Del Hoobler | |
| <hoobler AT US.IBM DOT COM> |
|
| Sent by: "ADSM: Dist Stor | To|
| Manager" | [email protected]|
| <ADSM-L AT VM.MARIST DOT EDU> | DU
|
| | cc|
| 03/11/2005 12:48 | |
| | Subject|
| Please respond to | Re: [ADSM-L] Re |
| "ADSM: Dist Stor | TDP for Lotus |
| Manager" | Domino (again) |
| <ADSM-L AT VM.MARIST DOT EDU> |
|
| | |
| | |
| | |
| | |
| | |
|-----------------------------+-------------------------------------------|
Hi Farren,
The transaction logs are not backed up during a
"domdsmc incremental" command. The transaction logs
are backed up with the "domdsmc archivelog" command.
You are correct that many customers do a "domdsmc selective"
command once a week (or more often, depending on the
amount of log data generated) so that when a
database is recovered, not as many transaction logs
need to be replayed against the restored database.
DBIIDs can change under different circumstances
such as database compaction.
Thanks,
Del
----------------------------------------------------
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 11/03/2005
06:40:48 AM:
> Hi all
>
> I'm still having some problems (re email below), understanding under
what
> conditions the Domino dbs are backed up.
>
> Can I assume that I am right on the following:-
>
> If the dbs are logged and transaction logs are being created and backed
up,
> only the transaction logs will be backed up during an incremental which
is
> why we would need to do selective backups of the entire dbs each week to
> cut down on the amount of rolling forward to be done?
>
> But, in this case, will the DBIIDs of the logged databases ever change?
>
> Thanks
>
>
> Farren Minns
> Solaris System Admin / Oracle DBA
> IT - Hosting Services
>
>
> >>>Hi Farren,
>
> >>>From the Users Guide:
>
> >>>Incremental Backup
> >>>An incremental backup provides a conditional backup function
> >>>that performs a full online backup of Domino databases
> >>>under the following conditions:
> >>>The database is within the Domino data path or symbolically
> >>>linked to the Domino data path by directory or database links.
> >>>The database is not excluded from backup by exclude statements
> >>>within the Tivoli Storage Manager options file.
> >>>If the database is logged, the DBIID has changed.
> >>>If the database is not logged, it has been modified since
> >>>the last backup occurred (data and non-data modification
> >>>dates are checked).
> >>>The database is new or newly included in the backup.
>
> >>>Thanks,
>
> >>>Del
>
>
> ######################################################################
> The information contained in this e-mail and any subsequent
> correspondence is private and confidential and intended solely
> for the named recipient(s). If you are not a named recipient,
> you must not copy, distribute, or disseminate the information,
> open any attachment, or take any action in reliance on it. If you
> have received the e-mail in error, please notify the sender and delete
> the e-mail.
>
> Any views or opinions expressed in this e-mail are those of the
> individual sender, unless otherwise stated. Although this e-mail has
> been scanned for viruses you should rely on your own virus check, as
> the sender accepts no liability for any damage arising out of any bug
> or virus infection.
> ######################################################################
######################################################################
The information contained in this e-mail and any subsequent
correspondence is private and confidential and intended solely
for the named recipient(s). If you are not a named recipient,
you must not copy, distribute, or disseminate the information,
open any attachment, or take any action in reliance on it. If you
have received the e-mail in error, please notify the sender and delete
the e-mail.
Any views or opinions expressed in this e-mail are those of the
individual sender, unless otherwise stated. Although this e-mail has
been scanned for viruses you should rely on your own virus check, as
the sender accepts no liability for any damage arising out of any bug
or virus infection.
######################################################################
|
