This is what we used to do with our Domino backups (hope to have all Domino
servers shutdown by years end - the university moved to GMail). Daily
incrementals and weekly selective/full.
Do note that if your Domino admin does a reorg, that resets the DBIID which
causes a full/selective backup. Our admin used to do that every couple of
weeks.
On Wed, Aug 26, 2015 at 5:14 AM, Loon, EJ van (ITOPT3) - KLM <
Eric-van.Loon AT klm DOT com> wrote:
> Hi Frank!
> Thank you very much for your correction, I will advise my customer to use
> selectives with once a week an incremental.
> Kind regards,
> Eric van Loon
> AF/KLM Storage Engineering
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of
> Frank Ramke
> Sent: dinsdag 25 augustus 2015 16:50
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: Data Protection for IBM Domino
>
> Eric
>
> After further study with circular logging, it turns out I didn't give good
> advise.
>
> With circular logging, incremental backup will not backup the database
> unless the database's DBIID changes (a rare occurrence). Selective backups
> to backup the changes along with occasional incremental, to inactivate
> deleted databases is the right way to go.
>
>
> "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 08/21/2015
> 10:30:05 AM:
>
> > From: "Loon, EJ van (ITOPT3) - KLM" <Eric-van.Loon AT KLM DOT COM>
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Date: 08/21/2015 10:33 AM
> > Subject: Re: Data Protection for IBM Domino Sent by: "ADSM: Dist Stor
> > Manager" <ADSM-L AT VM.MARIST DOT EDU>
> >
> > Hi Frank!
> > I indeed read that part of the manual, but it's all about transaction
> > logs and the 'logged databases' whatever that means.
> > Nothing about what your backup strategy should be when circular
> > logging is used.
> > So thank you very much for your reply, it's really appreciated! I will
> > advise my customer to switch to incremental backups.
> > Kind regards,
> > Eric van Loon
> > AF/KLM Storage Engineering
> >
> > -----Original Message-----
> > From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> > Of Frank Ramke
> > Sent: vrijdag 21 augustus 2015 15:43
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: Re: Data Protection for IBM Domino
> >
> > Eric,
> >
> > Just noticed your question was about circular logging....
> >
> > "The customer uses circular logging only for all Domino instances."
> >
> > With circular logging, we cannot backup transaction logs!
> >
> > Anyway YES, Daily incrementals instead of Daily selectives with
> > occasional incremental is fine. New and changed nsf files will be
> > backed up, deleted ones will be inactivated...
> >
> >
>
> ======================================================================================================
>
> >
> >
> > This topic is found under "Backup Strategies" in the book.
> > http://www-01.ibm.com/support/knowledgecenter/SSGSG7_7.1.0/
> > com.ibm.itsm.mail.dom.win.doc/concept_domcbup3.html
> >
> > Sample Strategies
> > ...
> >
> > Full backup plus transaction log archives
> > It is often not practical to back up entire databases with each
> > regular backup for large Domino installations. Archival logging
> > captures changes to all logged databases in the archived transaction
> > log files. Full database backups are run less frequently, reducing
> > burdens on network and storage resources. To implement this strategy:
> > - Run regular log archives by running the archivelog command. The log
> > file does not fill and it captures changes to logged databases.
> > - Run regular Incremental backups, which back up logged databases with
> > unchanged DBIIDs.
> > - Run occasional Selective backups of all logged databases. The number
> > of transaction log files to be processed during a restore is
> reduced.
> > - Issue the inarchivelog command (following Selective backups) to
> > allow nonessential transaction log files to expire.
> >
> > The archivelog command captures changes to all logged databases in
> > between full backups of selected databases. To restore a database to
> > its most recent state, restore the most recent database backup and
> > specify /applylogs. All the necessary archived transaction log files
> > are restored so that updates for the database can be applied
> >
> >
> >
> > From: "Loon, EJ van (ITOPT3) - KLM" <Eric-van.Loon AT KLM DOT COM>
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Date: 08/21/2015 09:00 AM
> > Subject: Data Protection for IBM Domino
> > Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> >
> >
> >
> > Hi guys!
> > One of my customers uses Data Protection for IBM Domino for a few
> > years now. All mail instances are backed up daily with the domdsmc
> > selective command. I recently discovered that old deleted databases
> > were never removed from TSM, which seems to be caused by the fact that
> > we do selectives only. Only an occasional domdsmc incremental seems to
> > remove them.
> > So I recommended the customer to implement an incremental backup once
> > a week. He now asks me "What if I run daily incrementals instead of
> > the selectives?" I don't know if that will work, nor can I find the
> > answer in the manuals...
> > The customer uses circular logging only for all Domino instances.
> > Thank you very much for your help in advance!
> > Kind regards,
> > Eric van Loon
> > AF/KLM Storage Engineering
> > ********************************************************
> > For information, services and offers, please visit our web site:
> > http://www.klm.com. This e-mail and any attachment may contain
> > confidential and privileged material intended for the addressee only.
> > If you are not the addressee, you are notified that no part of the
> > e-mail or any attachment may be disclosed, copied or distributed, and
> > that any other action related to this e-mail or attachment is strictly
> > prohibited, and may be unlawful.
> > If you have received this e-mail by error, please notify the sender
> > immediately by return e-mail, and delete this message.
> >
> > Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/ or
> > its employees shall not be liable for the incorrect or incomplete
> > transmission of this e-mail or any attachments, nor responsible for
> > any delay in receipt.
> > Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal
> > Dutch
> > Airlines) is registered in Amstelveen, The Netherlands, with
> > registered number 33014286
> > ********************************************************
> >
> > ********************************************************
> > For information, services and offers, please visit our web site:
> > http://www.klm.com. This e-mail and any attachment may contain
> > confidential and privileged material intended for the addressee only.
> > If you are not the addressee, you are notified that no part of the
> > e-mail or any attachment may be disclosed, copied or distributed, and
> > that any other action related to this e-mail or attachment is strictly
> > prohibited, and may be unlawful. If you have received this e-mail by
> > error, please notify the sender immediately by return e-mail, and
> > delete this message.
> >
> > Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/ or
> > its employees shall not be liable for the incorrect or incomplete
> > transmission of this e-mail or any attachments, nor responsible for
> > any delay in receipt.
> > Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal
> > Dutch Airlines) is registered in Amstelveen, The Netherlands, with
> > registered number 33014286
> > ********************************************************
> >
> >
> ********************************************************
> For information, services and offers, please visit our web site:
> http://www.klm.com. This e-mail and any attachment may contain
> confidential and privileged material intended for the addressee only. If
> you are not the addressee, you are notified that no part of the e-mail or
> any attachment may be disclosed, copied or distributed, and that any other
> action related to this e-mail or attachment is strictly prohibited, and may
> be unlawful. If you have received this e-mail by error, please notify the
> sender immediately by return e-mail, and delete this message.
>
> Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its
> employees shall not be liable for the incorrect or incomplete transmission
> of this e-mail or any attachments, nor responsible for any delay in receipt.
> Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch
> Airlines) is registered in Amstelveen, The Netherlands, with registered
> number 33014286
> ********************************************************
>
>
--
*Zoltan Forray*
TSM Software & Hardware Administrator
Xymon Monitor Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
www.ucc.vcu.edu
zforray AT vcu DOT edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will
never use email to request that you reply with your password, social
security number or confidential personal information. For more details
visit http://infosecurity.vcu.edu/phishing.html
|
