You can move the diagnostic/trace logging to another drive, this typically fills up with hundreds of MBs even a few GBs, so its a good idea to have this on a separate partition. This is usually the main culprit for running out of drive space. The setting is in central admin Operations --> Diagnostic logging, or http://yourcentraladmin:1234/_admin/metrics.aspx
Sezai. On Wed, Jun 3, 2009 at 11:06 AM, Michael Nemtsev < [email protected]> wrote: > Hello, > > I would avoid such shenanigans, because SharePoint doesn't support > installation of core files on other drives. Even installation package ask > you where to install, it keeps 12Hive folder on C drive. > Just move DB to other drive and that's all > > Even there are some ways to move all files from C I expect you get number > of unpredictable issues with updates, components and other stuff which has > encoded C:\ drive. > > I believe that SharePoint 2010 will fix this, especially around the feature > storage (should be isolated storage, not file directory) > > > Michael Nemtsev > Readify | Microsoft MVP > http://msmvps.org/blogs/laflour > T: 0424 184 978 | E: [email protected] > ________________________________________ > From: [email protected] [[email protected]] On Behalf Of Paul Noone [ > [email protected]] > Sent: Wednesday, 3 June 2009 11:20 AM > To: [email protected] > Subject: SharePoint ate my hard drive > > Hi all, > > Does anyone know if SharePoint can be installed on a partition other than > C? > > We’ve run into major disk space issues with our VMS (they were only ever > allocated a 20GB drive). As a result I’ve uninstalled non-essential > software, reduced diagnostic log retention and trace log levels. I’m even > looking at creating a new partition for all servers and relocating any log > files that can be moved. > > I still don’t see this as a long term solution though because its Windows > (and SharePoint) Updates that are the real culprits. > > The way I see it we either get some third party software and resize all the > C partitions (unsupported?) or rebuild all the servers with greater disk > capacity and attempt MOSS/WSS installation on a partition that can be > resized. > > Would be very interested in hearing if other people have run into this, > what the solutions were, and what general base requirements you’d suggest > for disk size. > > Regards, > > Paul > Online Developer, ICT > CEO Sydney > ________________________________ > Support procedure: https://www.codify.com/lists/support > List address: [email protected] > Subscribe: [email protected] > Unsubscribe: [email protected] > List FAQ: http://www.codify.com/lists/ozmoss > Other lists you might want to join: http://www.codify.com/lists > > -------------------------------------------------------------------------------- > Support procedure: http://www.codify.com/lists/support > List address: [email protected] > Subscribe: [email protected] > Unsubscribe: [email protected] > List FAQ: http://www.codify.com/lists/ozmoss > Other lists you might want to join: http://www.codify.com/lists > > -------------------------------------------------------------------------------- Support procedure: http://www.codify.com/lists/support List address: [email protected] Subscribe: [email protected] Unsubscribe: [email protected] List FAQ: http://www.codify.com/lists/ozmoss Other lists you might want to join: http://www.codify.com/lists
