hi mark
surely if a _file_ was being updated within the directory, then the file
would be backed up but not the directory name itself??
we intend investigating the dsmsched.log, when we can find the time!
dave
--
"on a clear disk, you can seek for ever."
"on a clear disk, you can seek for ever."
> ----------
> From: Remeta, Mark[SMTP:MRemeta AT SELIGMANDATA DOT COM]
> Sent: 18 August 2000 15:28
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: ms exchange updating WinNT directory
>
> Hello again Dave, I see what your saying but a directory is just a
> directory, who cares how many versions you keep, they are all the same..
> It's the files in the directory that you should worry about. Do you know
> what file in the WinNT directory that is getting updated on a daily basis.
> It should be in the log if you have it set for verbose.
>
> Mark
>
>
> -----Original Message-----
> From: Frost, Dave [mailto:dave.frost AT TELEVAULTIT DOT COM]
> Sent: Friday, August 18, 2000 10:14 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: ms exchange updating WinNT directory
>
>
> hi mark
>
> the defaults for the server are "keep 7 versions"; however, for exchange,
> we
> keep several weeks of logs. The requirement was to restore -14days. (a
> bit
> inconsistent, but all the other servers on the site use the same mc). We
> were able to restore a recent version of the server (say -6), and then
> restore the required exchange (-14) ok.
>
> the point being that an nt node with exchange seems to update the winnt
> dir
> in some way every day, so the directory (but not the contents) gets backed
> up every day, whereas with an ordinary nt node, winnt rarely gets
> backedup.
>
> dave
> --
> "on a clear disk, you can seek for ever."
>
>
> > ----------
> > From: Remeta, Mark[SMTP:MRemeta AT SELIGMANDATA DOT COM]
> > Sent: 18 August 2000 14:21
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: Re: ms exchange updating WinNT directory
> >
> > Hi Dave, are you saying that the WinNT directory was not restored?
> > As far as using a special dirmc, the WinNT directory should still be
> there
> > as long as it is still on the client.
> >
> > Mark
> >
> >
> > -----Original Message-----
> > From: Frost, Dave [mailto:dave.frost AT TELEVAULTIT DOT COM]
> > Sent: Friday, August 18, 2000 8:11 AM
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: ms exchange updating winnt directory
> >
> >
> > Hi *SMers
> >
> > We were restoring an exchange server to a point-in-time - both the
> server
> > itself and exchange. While we were restoring the server, we found that
> > there were no "winnt" directories for the date we wanted. Investigating
> > this, we have found that if the nt server is NOT running exchange, then
> > the
> > winnt directory rarely gets updated, but if it IS running exchange, then
> > the
> > winnt directory gets updated (and hence backed up and so expired) every
> > day.
> > The files within the directory do not _appear_ change.
> >
> > Has anybody else seen this behaviour? Is there a way round it aside
> from
> > a
> > special dirmc with the same retentions as the exchange node itself?
> >
> > dave
> > --
> > "on a clear disk, you can seek for ever."
> >
> >
> > www.guardianit.com
> > The information contained in this email is confidential and intended
> only
> > for the use of the individual or entity named above. If the reader of
> > this
> > message is not the intended recipient, you are hereby notified that any
> > dissemination, distribution, or copying of this communication is
> strictly
> > prohibited. Guardian iT Group will accept no responsibility or
> liability
> > in
> > respect to this email other than to the addressee. If you have received
> > this communication in error, please notify us immediately via email:
> > postmaster AT guardianit DOT com
> >
> > Confidentiality Note: The information transmitted is intended only for
> the
> > person or entity to whom or which it is addressed and may contain
> > confidential and/or privileged material. Any review, retransmission,
> > dissemination or other use of this information by persons or entities
> > other
> > than the intended recipient is prohibited. If you receive this in error,
> > please delete this material immediately..
> >
>
> www.guardianit.com
> The information contained in this email is confidential and intended only
> for the use of the individual or entity named above. If the reader of
> this
> message is not the intended recipient, you are hereby notified that any
> dissemination, distribution, or copying of this communication is strictly
> prohibited. Guardian iT Group will accept no responsibility or liability
> in
> respect to this email other than to the addressee. If you have received
> this communication in error, please notify us immediately via email:
> postmaster AT guardianit DOT com
>
> Confidentiality Note: The information transmitted is intended only for the
> person or entity to whom or which it is addressed and may contain
> confidential and/or privileged material. Any review, retransmission,
> dissemination or other use of this information by persons or entities
> other
> than the intended recipient is prohibited. If you receive this in error,
> please delete this material immediately..
>
www.guardianit.com The
information contained in this email is confidential and intended only for the
use of the individual or entity named above. If the reader of this message is
not the intended recipient, you are hereby notified that any dissemination,
distribution, or copying of this communication is strictly prohibited.
Guardian iT Group will accept no responsibility or liability in respect to this
email other than to the addressee. If you have received this communication in
error, please notify us immediately via email: postmaster AT guardianit DOT com
|
