Hi,
Unfortunately, full and incremental cycles are managed dissociated on exchange
backups
On exchange backups, fulls can expired while incrementals are still active.
So, we have the same management class for the full and incremental
Best Regards,
Yann MEUNIER
Ingénierie - Système Stockage
Informatique CDC - Etablissement DPI
Office : +33 1 58 50 53 01
Mobile : +33 6 62 47 88 56
-----Message d'origine-----
De : ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] De la part de
Gee, Norman
Envoyé : vendredi 27 juin 2014 08:00
À : ADSM-L AT VM.MARIST DOT EDU
Objet : Re: [ADSM-L] Exchange Incremental Expiry
So the question becomes "When is the incremental backup marked inactive?" Does
it even make sense for an incremental to have a different retention to a full?
When the next full is done. No it does not make sense to be different.
For example
My full backups will expire x days after the next full backups is started. All
of the incrementals that depends on the previous full expires x day after the
next full have completed. At the time the next full completes, all of the
previous incremental backups are mark inactive.
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Steven Harris
Sent: Thursday, June 26, 2014 10:31 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Exchange Incremental Expiry
Hi Again
Further to my last, the customer for which I am designing exchange backups has
until now been a Domino shop. Previously we have taken a Weekly
selective/daily incremental for the databases (remembering that an incremental
on Domino only backs up new databases and those that aren't logged) plus daily
or more frequent log backups. The database management class keeps for 18
months. The logs are kept for 100 days.
I'm now supposed to implement this in Exchange. I can do a weekly full/daily
incremental with no problem and put them to different management classes as I
do for Domino, however the TDP for Exchange manual states
Incremental object names are always unique. These names contain qualifiers
whose values make them unique. Incremental object names are generated at the
time of the backup and therefore are not predictable and cannot be specified.
So the question becomes "When is the incremental backup marked inactive?" Does
it even make sense for an incremental to have a different retention to a full?
IIRC the same applies with MSSQL and the client deletes the logs when the full
on which they depend is no longer on the server. If that is the case for
exchange then there is no point in a different retention for incrementals.
Please chime in if you know
Thanks
Steve.
Steven Harris
TSM Admin
Canberra Australia.
Ce message et toutes les pièces jointes (ci-après le « message ») sont
confidentiels et établis à l’intention exclusive de ses destinataires. Toute
utilisation de ce message non conforme à sa destination, toute diffusion ou
toute publication, totale ou partielle, est interdite, sauf autorisation
expresse. Si vous recevez ce message par erreur, merci de le détruire sans en
conserver de copie et d’en avertir immédiatement l’expéditeur. Internet ne
permettant pas de garantir l’intégrité de ce message, la Caisse des Dépôts et
Consignations décline toute responsabilité au titre de ce message s’il a été
modifié, altéré, déformé ou falsifié. Par ailleurs et malgré toutes les
précautions prises pour éviter la présence de virus dans nos envois, nous vous
recommandons de prendre, de votre côté, les mesures permettant d'assurer la
non-introduction de virus dans votre système informatique.
This email message and any attachments (“the email”) are confidential and
intended only for the recipient(s) indicated. If you are not an intented
recipient, please be advised that any use, dissemination, forwarding or copying
of this email whatsoever is prohibited without Caisse des Depots et
Consignations's prior written consent. If you have received this email in
error, please delete it without saving a copy and notify the sender
immediately. Internet emails are not necessarily secured, and declines
responsibility for any changes that may have been made to this email after it
was sent. While we take all reasonable precautions to ensure that viruses are
not transmitted via emails, we recommend that you take your own measures to
prevent viruses from entering your computer system.
|
