[THIN] Re: File & Print Server Outages
- From: "Braebaum, Neil" <Neil.Braebaum@xxxxxxxxxxxxxxxxx>
- To: "'thin@xxxxxxxxxxxxx'" <thin@xxxxxxxxxxxxx>
- Date: Thu, 26 Jun 2003 14:26:03 +0100
Um, I use EMC SAN solutions as the back-end to my MSCS clusters (among other
machines).
We also use StorageTek silos for the backup (enterprise) software.
Whilst this fits an enterprise type rationale, it does have a bearing or
cost, on complexity.
It wasn't all plain sailing is all I'll say.
For clustering (MSCS) ideally (if you want any decent support) that the
*entire* solution is on the cluster HCL.
Neil
> -----Original Message-----
> From: Lucas Boyken [mailto:lboyken@xxxxxxxxx]
> Sent: 26 June 2003 14:16
> To: thin@xxxxxxxxxxxxx
> Subject: [THIN] Re: File & Print Server Outages
>
> If you want to get even more extreme...check out EMC2 SAN
> solutions. Clustering servers through a SAN, especially
> EMC's, would give you uptime like you wouldn't believe.
> However, you'll pay for it. The last installation that
> served over 9,000 users was over a million dollars I believe.
> However, that also came with EMC's huge tape storage unit.
> That stuff is unbelievable. =20
>
> -----Original Message-----
> From: Ron Oglesby [mailto:roglesby@xxxxxxxxxxxx]=20
> Sent: Thursday, June 26, 2003 8:05 AM
> To: thin@xxxxxxxxxxxxx
> Subject: [THIN] Re: File & Print Server Outages
>
>
> Like Neil, in a high availability scenario I would say
> Cluster it. The trick is that you have to define what an
> acceptable amount of down time is for the services. So a out
> of commission File server that hosts home dirs, data etc, may
> have a SLA of 4 hours of down time. (tough to recover if you
> loose a mother board and don't have spares, fast backups
> etc.) But if is not so important and you can accept a day
> then so be it.
>
> Or if it is 24x7 type system with requirements for 4 9's I
> would go with a cluster or at least replicate the home dirs.
> Replication can be done on the cheap if you cant get budget
> for clustering. I mean replicate the data to a secondary
> server, then set the home dirs via login script as the user
> logs on. You can put some logic in the script to check for
> the primary server and if it failed set the home dir to the
> secondary server. This is not perfect of course but gets you
> to the 4 hour SLA. (I prefer clustering but not every one has
> the budget right away)
>
> Ron Oglesby
> Senior Technical Architect
> =3D20
> RapidApp
> Office 312.372.7188
> Mobile 815.325.7618
> email roglesby@xxxxxxxxxxxx
> =3D20
>
> -----Original Message-----
> From: Braebaum, Neil [mailto:Neil.Braebaum@xxxxxxxxxxxxxxxxx]=3D20
> Sent: Thursday, June 26, 2003 4:39 AM
> To: 'thin@xxxxxxxxxxxxx'
> Subject: [THIN] Re: File & Print Server Outages
>
> I put profiles (mandatory) and home directories on MSCS
> clustered file shares (same for printers, as it happens).
>
> Not totally flawless, but generally very robust, and quickly
> resolvable for most failures.
>
> I might add, the reason for using MSCS, isn't purely for
> terminal server environments.
>
> Neil
>
> > -----Original Message-----
> > From: Richard Wykes [mailto:richard@xxxxxxxxx]=3D20
> > Sent: 26 June 2003 10:32
> > To: thin@xxxxxxxxxxxxx
> > Subject: [THIN] File & Print Server Outages
> >=3D20
> >=3D20
> > Hi,
> >=3D20
> > After having a problem with one of our two File & Print=3D20
> >server=20 today =3D3D that brought down half of our Citrix
> users=3D20
> >because =
> they=20
> >had no home drive, I wondered if anyone could=3D20 share their =
> thoughts=20
> >on how they have their =3D3D systems setup=3D20 to avoid outages
> >like=20 this. =3D20 Thanks
> >=3D20
> > Richard
***********************************************************************
This e-mail and its attachments are confidential and are intended for
the above named recipient only. If this has come to you in error,
please notify the sender immediately and delete this email from your
system. You must take no action based on this, nor must you copy or
disclose it or any part of its contents to any person or organisation.
Statements and opinions contained in this email may not necessarily
represent those of Littlewoods. Please note that email communications
may be monitored.
The registered office of Littlewoods Limited and its subsidiaries
is 100 Old Hall Street, Liverpool, L70 1AB.
Registered number of Littlewoods Limited is 262152
***********************************************************************
********************************************************
This weeks sponsor - RTOSoft TScale
Complaints about applications response time - DO SOMETHING ABOUT IT!
TScale 2.0 improves applications response time and increases terminal
server capacity. Really get MORE from your existing servers! Free eval:
http://www.rtosoft.com/enter.asp?id=130
**********************************************************
Useful Thin Client Computing Links are available at:
http://thethin.net/links.cfm
For Archives, to Unsubscribe, Subscribe or
set Digest or Vacation mode use the below link:
http://thethin.net/citrixlist.cfm
Other related posts:
