Something like this.
<paste here>
Back to the original question concerning "Merely a Marginally
Manipulatable Manifestation of Mail Messages" (or, "The M: Drive")...

The free space shown is tied to the exchange install point, not a
particular information store - the "Root" of the ExIFS.  Since you can
have multiple stores spread across multiple drives, "free space" is
really more complex than can be represented by that one file system API
(getfreespace).  "Free Space" could be seen as the amount of space on
the drive with your EDB and STM files, but they could be on different
drives and there could be more than one of each, so how would you
calculate it?  "Free Space" could be seen as the amount of space on the
log drive since you can't process more transactions than that even if
there is a big drive for the EDB and STM. But there could be more than
one log drive as well if you have multiple storage groups.  The ExIFS
driver is a single point of access to the entire set of storage groups
and stores on the system, so the used and available drive space can be
spread across multiple volumes.  There might be an argument for adding
it all up and showing it that way.  On the other hand there is an
argument for showing the smallest available since that will be the
bottleneck.  The problem is, since this is held to the rules of file
systems, there are fewer choices available than one might be able to
imagine.

In Windows 2000 I can attach my CDROM drive (or any other drive for that
matter) to a subdirectory of my C: drive.  That doesn't make the size of
the
C: drive change by 600MB though just because there's 600MB more space in
the file tree.  Nor does that space factor into free space display for
the C: drive.  In the other direction, I can map a drive, say H:, to my
home directory on the file server, which happens to have a quota on it.
The free space displayed for the H: drive, therefore, is not a
representation of how much space is really "available".

With Exchange, you must understand the way physical storage is used to
correctly manage your system.  Physical storage is used by several
different "files" which make up an Exchange "store".  No plain
representation of the available physical storage will really tell you
the space available to the entire store.  So, since one wouldn't
typically ask a physical disk drive how much space an Exchange Store
has, there's no need to require an accurate answer.

It's a bit like asking a real estate agent to compute how much furniture
someone could own based on the size of a piece of land (i.e. a lot).  A
lot may be 30'x100', but that doesn't tell you anything about furniture.
The person in question may have a Storage Unit somewhere else.  They may
have another house, or several.  However, if you want to get a list of
all the furniture, the lot (or rather the front door of the house) is a
decent place to start.  Once there you can ask the person who answers
the door (file system driver) to see their containers (rooms) and items
(sofas and chairs). All you need is an address.  "M:" will probably do.


=======================================================
Andy Webb            [EMAIL PROTECTED]      www.swinc.com
Simpler-Webb, Inc.   Austin, TX            512-322-0071
-- Way to go USPS Cycling Team and Lance Armstrong!! --
======================================================= 

-----Original Message-----
From: Kevin Miller [mailto:[EMAIL PROTECTED]] 
Sent: Tuesday, November 20, 2001 10:13 AM
To: Exchange Discussions
Subject: RE: E2K M Drive (moving it)


WOW! That was an amazing explanation.. Thank you Andy

Kevinm M WLKMMAS, UCC+WCA, CKWSE


-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Webb, Andy
Sent: Tuesday, November 20, 2001 8:10 AM
To: Exchange Discussions
Cc: '[EMAIL PROTECTED]'
Subject: RE: E2K M Drive (moving it)


The M drive is merely a manifestation[1] of mail messages.

You can read quite a bit more on Windows Installable File System drivers
on MSDN.  A file system is really just a collection of APIs that allow
you to navigate a set of data in a logical fashion - containers
(folders) and items (files).  It shouldn't be too hard to see how one
might view mail data as containers (folders) and items (messages). [3] 

So, the ExIFS driver, which is installed with Exchange 2000 is the
"Exchange Installable File System driver."  It allows a certain set of
well known APIs [2]to view the containers and items.  It just so happens
that if you give a file system supporting those APIs a drive letter, you
can see it through Explorer or a CMD window, or any of the other
standard Windows file dialog boxes...because they use the file system
APIs to access data.

It's no different than a network drive or a RAM drive or a flash memory
card or a zip drive or ... It is merely a manifestation of data in the
form of folders and files.  The thing to remember is that since it is
just a view of the mail messages presented by the file system APIs, it's
not necessarily the most feature rich way to manipulate that data.  The
manipulation via the ExIFS (M: drive) is limited by the set of file
system APIs [2].  On the other hand, the ability to manipulate the data
through a mail client like Outlook has a very rich set of APIs for
dealing with mail data - much beyond the simple functions for finding
and displaying files. The messaging APIs that are native to the Exchange
store allow things like getrecipients, addattachment, resolvenames, etc.

So, the M: drive can be seen as an (abbreviated) acronym for "Marginally
Manipulatable Manifestation of Mail Messages."

regards [4]
Andy

[1] to make evident or certain by showing or displaying
[2] readfile, writefile, movefile, deletefile, renamefile, openfile,
closefile, findfile, etc. [3] it's slightly more complex than this
because a mail message is actually a container as well. it contains a
header and a body and perhaps one or more attachments, which themselves
can be messages (containers).  it also can contain multiple bodies (e.g
mime multipart alternative content) that display based on the best
capabilities of the client. [4] hope this didn't make it worse
=======================================================
Andy Webb            [EMAIL PROTECTED]      www.swinc.com
Simpler-Webb, Inc.   Austin, TX            512-322-0071
-- Way to go USPS Cycling Team and Lance Armstrong!! --
======================================================= 

_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Archives:               http://www.swynk.com/sitesearch/search.asp
To unsubscribe:         mailto:[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]

Kevinm M WLKMMAS, UCC+WCA, CKWSE CKST


-----Original Message-----
From: Martin Blackstone [mailto:[EMAIL PROTECTED]] 
Sent: Sunday, December 02, 2001 12:01 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange partition getting huge over the weekend... : found
o ut!!!


There is no M: drive

-----Original Message-----
From: Kevin Miller [mailto:[EMAIL PROTECTED]] 
Sent: Sunday, December 02, 2001 11:55 AM
To: MS-Exchange Admin Issues
Subject: RE: Exchange partition getting huge over the weekend... : found
out!!!


Please tell me you did not run a file level scanner on the server.

Kevinm M WLKMMAS, UCC+WCA, CKWSE CKST


-----Original Message-----
From: Eric Mailloux [mailto:[EMAIL PROTECTED]] 
Sent: Sunday, December 02, 2001 11:41 AM
To: MS-Exchange Admin Issues
Subject: RE: Exchange partition getting huge over the weekend... : found
out!!!


Antivirus software

        I have a planned virus scan on sunday midnight.... That's the
reason for the unusual amount of log files...


Bye,

Eric

-----Message d'origine-----
De : Eric Mailloux 
Envoy� : 2 d�cembre, 2001 14:02
� : MS-Exchange Admin Issues
Objet : Exchange partition getting huge over the weekend...


Hello!

    Exchange 2000 SP1.

    The Exchange partition (M:\ drive) gets huge overly fast during the
weekend  : from 2.1GB on friday PM to almost 9.0GB on monday AM. No one
is at the office during that time. I only have about 50 mailboxes on the
server. What causes the log files to get this numerous this fast, over
the weekand when it is not the case during the week? Is there a way or a
tool that would allow me to view all the activity that went on on the
mail server???

    Could it be that I am being used as a relay???


Thank you! 


Eric Mailloux
Administrateur r�seau
Groupe TelPlus Inc.
(418) 524-9455, poste 109
 
************************
L'information que contient ce courriel est confidentielle et peut
contenir des informations privil�gi�es sur le plan technique et/ou
juridique. Si vous avez re�u ce courriel par erreur, veuillez nous en
aviser imm�diatement par courriel. Veuillez �galement supprimer ce
courriel de votre syst�me, vous abstenir de le copier ou de l'utiliser
pour quelque raison, ni en divulguer le contenu � quiconque.
 
The information in this email is confidential and may be legally and/or
technically privileged. If you have received this e-mail in error,
please reply immediately by e-mail and then delete this message from
your system. Please do not copy or use this email for any purposes, or
disclose its contents to any other person.
************************

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm


List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm



List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm



List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm

Reply via email to