Just for clarification...
Yann said this:
"Furthermore, it seems as if the integrity check is not made,
Exchange will not purge its logs."
This is not accurate. Exchange will purge its logs when a
FULL or INCREMENTAL backup completes successfully
(and when the logs have been shipped and committed to
any replicas.) The integrity check does not need to run
for the logs to be truncated.
Thank you,
Del
----------------------------------------------------
"ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu> wrote on 06/27/2014
08:06:39 AM:
> From: "Meunier, Yann" <yann.meunier AT CAISSEDESDEPOTS DOT FR>
> To: ADSM-L AT vm.marist DOT edu
> Date: 06/27/2014 08:07 AM
> Subject: Re: Exchange and client compression
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu>
>
> Hi,
>
> I was confronted him about.
> What is crucial is well oversizing and separate disks logs of
disksdatabases.
> For my part, discs newspapers are between 76G and 100G.
>
> Beyond, you will not be able to backup in a reasonable time.
> I make a full weekly backup and incremental daily.
> Be careful though, versioning is managed separately between the
> full backups and incremental backups.
> If you perform incremental backups regularly, the time of check
> integrity are not huge (about 15 minutes to 300 G).
> And therefore, full weekly backup should not be a problem.
> Furthermore, it seems as if the integrity check is not made,
> Exchange will not purge its logs.
>
> 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 Steven Harris
> Envoyé : vendredi 27 juin 2014 13:25
> À : ADSM-L AT VM.MARIST DOT EDU
> Objet : Re: [ADSM-L] Exchange and client compression
>
> Hi Hans Chr.
>
> Thanks for your reply
>
> As I understand it if the DAG has more than two replicas and two of
> those are healthy the integrity check can be skipped. This Exchange
> design has only two replicas so I'm forced into the check on every
backup.
>
> Regards
>
> Steve
>
> On 27/06/2014 7:51 PM, Hans Christian Riksheim wrote:
> > I also wonder about the integrity checker. With DAG isn't the
> > integrity guranteed if replication is working fine and thus integrity
> > check in TSM can be skipped?
> >
> > Regards,
> >
> > Hans Chr.
> >
> >
> > On Fri, Jun 27, 2014 at 7:08 AM, Steven Harris
> > <steve AT stevenharris DOT info>
> > wrote:
> >
> >> Hi All
> >>
> >> I'm working on a backup design for Exchange 2013. Unfortunately I
> >> pretty much have to take what I've been given and make it work.
> >>
> >> There are two sites and there will be two DAGs with two replicas in
> >> each DAG and 10x1TB databases per DAG.
> >>
> >> Since there are only two replicas the backup will be throttled by the
> >> integrity checker. Drives are TS1120 at one site and TS1140 at the
> >> other, and I've been directed to take a full backup every weekend. I
> >> wanted to stagger them through the week but was overruled on that.
> >> Of course disk space is tight, but I will need to use a file pool
> >> because I can't have all my drives busy with Exchange to the
> >> exclusion of all else as the data drips through the integrity
checker.
> >>
> >> I was wondering if client compression might be useful here. The
> >> databases will normally be all active at one site and all passive at
> >> the other for each DAG, so if I'm backing up the passive copy the
> >> additional CPU usage should not be a problem. With the exchange
> >> delayed deletion features, redundant database copies, modern disk
> >> arrays etc I don't anticipate these backups will ever be restored for
> >> anything other than audit or discovery purposes, and so impact of
> >> compression on restore won't be an issue.
> >>
> >> Is anyone using client compression on Exchange (2007 or later) and
> >> if so what sort of compression rate and cpu impact are you seeing? Is
> >> there any impact on throughput?
> >>
> >> 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.
>
|
