[cisco-voip] Question About Hard Drive Partitions for Unity
Pat Hayes
pat-cv at wcyv.com
Tue Feb 10 12:35:46 EST 2009
A larger C: partition isn't likely to directly cause a problem, but it
does mean that your other partition(s) are going to be that much
smaller, and that can certainly lead to problems, if only with
user/message capacity. Maybe not a huge issue if the box is over
spec'd and/or you're not hosting exchange on the same server.
The docs say you should either use the PCD (which will create you a
Cisco approved 12 gig partition) or to install your own OS and use a
12 gig partition. If you stray from that, TAC can tell you you're
running an unsupported config, and ask you to reinstall properly. That
isn't too likely to happen, particularly for issues unrelated to the
OS or partitioning, but it is a risk you open yourself up to.
If the only reason to do this is because 'that's how the server guys
like to do it', is it really worth it? This might be a good time to
have a heart to heart with them.There's going to be all sorts of other
things that they 'like to do' that can have highly negative effects on
your voice servers. Security agents, anti virus, group policy,
changing AD permissions, moving users around, Exchange maintenance,
third party software, etc. You might as well break the ice now :-)
On Mon, Feb 9, 2009 at 2:51 PM, Miller, Steve
<MillerS at dicksteinshapiro.com> wrote:
> Our network team likes to program servers with a C drive equal to 50 gigs.
> This is a standard configuration for all their non-telephony servers and
> they would like to keep setting up the servers this way, including our Unity
> servers. All of our Unity servers are currently set up with 12 gig C drives
> for the operating system and larger sizes for the D drives. Is there any
> reason for us to use 12 gigs instead of 50 gigs? What if we decided that
> going forward we were going to partition all our Unity servers with 50
> gigs of the disk set up for the C drive and the rest for the D drive? Is
> there any specific reason why that would be an issue? Would Cisco TAC have
> a problem with supporting such a configuration? If so, why? Your insight
> is greatly appreciated. Thank you!
>
>
> Steve Miller
> Telecom Engineer
> Dickstein Shapiro LLP
> 1825 Eye Street NW | Washington, DC 20006
> Tel (202) 420-3370| Fax (202) 330-5607
> MillerS at dicksteinshapiro.com
>
>
>
> --------------------------------------------------------
> This e-mail message and any attached files are confidential and are intended
> solely for the use of the addressee(s)
> named above. This communication may contain material protected by
> attorney-client, work product, or other
> privileges. If you are not the intended recipient or person responsible for
> delivering this confidential
> communication to the intended recipient, you have received this
> communication in error, and any review, use,
> dissemination, forwarding, printing, copying, or other distribution of this
> e-mail message and any attached files
> is strictly prohibited. Dickstein Shapiro reserves the right to monitor any
> communication that is created,
> received, or sent on its network. If you have received this confidential
> communication in error, please notify the
> sender immediately by reply e-mail message and permanently delete the
> original message.
>
> To reply to our email administrator directly, send an email to
> postmaster at dicksteinshapiro.com
>
> Dickstein Shapiro LLP
> http://www.DicksteinShapiro.com
>
> ==============================================================================
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
More information about the cisco-voip
mailing list