Re: Semi-OT: Vsphere shutdown

[Richard Stovall]

I say, "oof" (TM, -sc)

Thanks for the good wishes, and believe me when I tell you that I haven't
forgotten for a moment that MBS is headquartered about 70 miles from where
I sit.  :)


On Fri, Mar 1, 2013 at 1:45 PM, Webster  wrote:

>  “The procedure itself seems straightforward enough, but those spindles
> have been going for about 4.5 years and it could mean a lot of restore time
> if more than two in any disk group decide that they don't want to spin up
> again.”
>
> ** **
>
> Actually had this happen at a hospital’s data center back in early 2010.
> Someone went work in the data center and decided it was too cold for them
> in the room.  So they went over to the “DO NOT TOUCH OR ADJUST THIS
> THERMOSTAT” labeled box and turned OFF the entire A/C system.  They left
> and forgot to turn the A/C back on.  A few hours later alarms were going
> off everywhere (it was 5 below zero F outside) and by the time we got there
> all the servers, UPS units, SANS, NASes and just about everything else had
> powered off.
>
> ** **
>
> No one knew what happened but the building super opened the roof vent to
> let the extreme cold air from outside into the data center.  By the time
> they figured out what had happened, the rooftop HVAC units had frozen.
> When they got all that figured out, the customer realized they had no idea
> what needed to be powered on in what order because they had never shutdown
> before.  They just started powering up servers, storage, firewalls,
> switches, you name it in random order since a non-random order was unknown.
> 
>
> ** **
>
> Two of their SANs came up with multiple drive failures and then there were
> those mysterious Unix servers that no one knew about.  No one knew the
> passwords to get in to start the services and software.  They had to place
> an emergency call in to HP since it was HP Unix servers and HP SANs.  I was
> there at the beginning discovery phase of an AD assessment because two
> hospitals were merging and they needed to know what to plan for in merging
> the two Ads.  All this happened on a Friday.  I was sent home early since
> no one was now available to work with me.
>
> ** **
>
> I do hope you don’t any mysterious servers or systems waiting to bite you
> in the butt when you power up. J  If so, MBS and ASB are available at
> excellent emergency rates! LOL  I’m not available, I start a 35,000 seat
> XenDesktop project on Monday.
>
> ** **
>
> Thanks
>
> ** **
>
> ** **
>
> Webster
>
> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~
> ~   ~
>
> ---
> To manage subscriptions click here:
> http://lyris.sunbelt-software.com/read/my_forums/
> or send an email to listmana...@lyris.sunbeltsoftware.com
> with the body: unsubscribe ntsysadmin
>

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

Re: Semi-OT: Vsphere shutdown

[Steven Peck]

Connect via ip/name to ESXi host you know the DC is on.
Log in with local credentials (or root since it's what most do)
Right click -> power on.

Power on vCenter environment

Stop messing with systems on the host directly since it annoys vCenter
Connect to vCenter, power on the rest.

Steven Peck
http://www.blkmtn.org


On Fri, Mar 1, 2013 at 10:28 AM, Webster  wrote:

> If I don't have a physical DC, how can I boot it first? :)
>
> Thanks
>
>
> Webster
>
> > -Original Message-
> > From: John Cook [mailto:john.c...@pfsf.org]
> > Sent: Friday, March 01, 2013 12:16 PM
> > To: NT System Admin Issues
> > Subject: RE: Semi-OT: Vsphere shutdown
> >
> > One more thing - If you don't have a physical DC in that location boot
> that
> > first
>
>
> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~
> ~   ~
>
> ---
> To manage subscriptions click here:
> http://lyris.sunbelt-software.com/read/my_forums/
> or send an email to listmana...@lyris.sunbeltsoftware.com
> with the body: unsubscribe ntsysadmin
>
>

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

Re: Semi-OT: Vsphere shutdown

[Steven Peck]

We're all HP blade and SAN here.
It's not that bad.  We've survived on purpose scheduled power downs, ups
maintenance battery exploded wtf power downs.  The whole thing is pretty
resilient.  This is not to say due diligence isn't a good thing.  :)

We have all physical vCenter Servers now because of our size and the
irritation of virtual ones during the above scenario's but

some notes from the unexpected ones
Most servers came up just fine.  Sometimes you needed to bounce a
SQL and/or an app box or two to get things started in order.

For the expected ones we knew where all the DCs / Name resolution
servers were and started those up through direct connect to the ESXi host,
then the VC server stuff, then SQL and the rest.

For one environment we have several set up as vApps which dictates startup
order.



On Fri, Mar 1, 2013 at 10:23 AM, Richard Stovall  wrote:

> Thanks, Steven.  We're a small shop and the team is one other person and
> me.  We had our meeting to go through everything yesterday.
>
> I've already created the plan of attack and written out configs for
> devices to my PC and a USB stick.  The SQL DBA says his db backups are OK
> and he's ready.  The only parts I'm deeply worried about are our HP blade
> chassis and EVA SAN.  There shouldn't be any issues, but they were
> installed during a period when I did not work at the company and I have
> never gone through the shutdown procedure for them.  The procedure itself
> seems straightforward enough, but those spindles have been going for about
> 4.5 years and it could mean a lot of restore time if more than two in any
> disk group decide that they don't want to spin up again.
>
> Cheers,
> Richard
>
>
> On Fri, Mar 1, 2013 at 12:57 PM, Stringham, Steven wrote:
>
>> Get your order dependence list down. Make a list of all the
>> services/servers and decide what order they should be shut down in and what
>> order they can come back up.  I did this recently (moved my datacenter to
>> another location) and it made all the difference to have hashed that out
>> and have a full list to check box as things went down and came back up.
>> Provide this list to your team, and walk through the list multiple times
>> with them as you go.
>>
>> Don't forget to add switches/routers/fibrechannel
>> switches/firewalls/SANs/NASs/managed power strips/etc. to the list.
>> Everything matters. Get a config backup of these on a external device
>> (thumbdrive/laptop) and do a write mem on them before powering them down.
>>
>> Make a note of where the SQL servers are in that list - as well as the
>> vcenter server. Is it hosting it's own database is or is it elsewhere.
>> Also, make a note of which physical host that the vcenter server was on so
>> you can connect to it directly to bring it back up.
>>
>> Make sure you have whatever config cables available to connect directly
>> to the switches/routers etc. in case of trouble on powering back up.
>>
>> Good luck.
>>
>> Steven Stringham
>>
>>
>> -Original Message-
>> From: Kurt Buff [mailto:kurt.b...@gmail.com]
>> Sent: Friday, March 01, 2013 10:25 AM
>> To: NT System Admin Issues
>> Subject: Re: Semi-OT: Vsphere shutdown
>>
>> On Fri, Mar 1, 2013 at 8:52 AM, Richard Stovall 
>> wrote:
>> > In a few days time I will have to completely shutdown my datacenter
>> > for some electrical maintenance.  (Yes, I'm nervous.  It's been online
>> > non-stop for
>> > 6.5 years.)
>> >
>> > I have 3 Vsphere ESX 4.1 hosts that I need to shutdown along with
>> > everything else.  My vcenter server is virtualized.  Two questions:
>> >
>> > 1) Do I need to put the hosts into maintenance mode before powering
>> > them off?  All of the VMs will already be powered off.
>> >
>> > 1) I can poweroff two of the hosts using the vcenter client, but after
>> > I shutdown the vcenter VM how should I poweroff the final host?  Just
>> > connect the client directly to the host and shut it down that way?  I
>> > can't think why this wouldn't work.
>> >
>> > Thanks in advance,
>> > RS
>>
>> One more thing...
>>
>> If you have a multi-site environment, and your connectivity to the other
>> sites will be affected, then when bringing things back up, make sure you
>> have connectivity to the other sites before bringing up your DC - so
>> firewall/router/VPN connections before the DC, in this case.
>> Then, make sure your DC is communicating with DCs in other sites before
>> bringing up the rest of the infrastructure.
>>
>> It's not that I think that anything *bad* will happen if you do it out of
>> order - but it gave me much more peace of mind when I did that.
>>
>> Kurt
>>
>> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <
>> http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~
>>
>> ---
>> To manage subscriptions click here:
>> http://lyris.sunbelt-software.com/read/my_forums/
>> or send an email to listmana...@lyris.sunbeltsoftware.com
>> with the body: unsubscribe ntsysadmin
>>
>>
>> --
>> For 

RE: Semi-OT: Vsphere shutdown

[Webster]

“The procedure itself seems straightforward enough, but those spindles have 
been going for about 4.5 years and it could mean a lot of restore time if more 
than two in any disk group decide that they don't want to spin up again.”

Actually had this happen at a hospital’s data center back in early 2010.  
Someone went work in the data center and decided it was too cold for them in 
the room.  So they went over to the “DO NOT TOUCH OR ADJUST THIS THERMOSTAT” 
labeled box and turned OFF the entire A/C system.  They left and forgot to turn 
the A/C back on.  A few hours later alarms were going off everywhere (it was 5 
below zero F outside) and by the time we got there all the servers, UPS units, 
SANS, NASes and just about everything else had powered off.

No one knew what happened but the building super opened the roof vent to let 
the extreme cold air from outside into the data center.  By the time they 
figured out what had happened, the rooftop HVAC units had frozen.  When they 
got all that figured out, the customer realized they had no idea what needed to 
be powered on in what order because they had never shutdown before.  They just 
started powering up servers, storage, firewalls, switches, you name it in 
random order since a non-random order was unknown.

Two of their SANs came up with multiple drive failures and then there were 
those mysterious Unix servers that no one knew about.  No one knew the 
passwords to get in to start the services and software.  They had to place an 
emergency call in to HP since it was HP Unix servers and HP SANs.  I was there 
at the beginning discovery phase of an AD assessment because two hospitals were 
merging and they needed to know what to plan for in merging the two Ads.  All 
this happened on a Friday.  I was sent home early since no one was now 
available to work with me.

I do hope you don’t any mysterious servers or systems waiting to bite you in 
the butt when you power up. ☺  If so, MBS and ASB are available at excellent 
emergency rates! LOL  I’m not available, I start a 35,000 seat XenDesktop 
project on Monday.

Thanks


Webster

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

Re: Semi-OT: Vsphere shutdown

[Kurt Buff]

Probably a good idea to have the DC with the FSMO roles be the last
one down and the first one up.

Kurt

On Fri, Mar 1, 2013 at 10:30 AM, Richard Stovall  wrote:
> I've got two physical DCs and one virtual at this site.  The physical ones
> are one traditional rack server and one blade.  The blade doesn't use any
> SAN storage, but I don't plan to bring it back up until the SAN is
> completely online.
>
>
> On Fri, Mar 1, 2013 at 1:15 PM, John Cook  wrote:
>>
>> One more thing - If you don't have a physical DC in that location boot
>> that first - it'll save you loads of suffering. I keep a physical and
>> virtual DC for this very reason.
>>
>>  John W. Cook
>> Network Operations Manager
>> Partnership For Strong Families
>> 5950 NW 1st Place
>> Gainesville, Fl 32607
>> Office (352) 244-1610
>> Cell (352) 215-6944
>> MCSE, MCP+I, MCTS, CompTIA A+, N+, VSP4, VTSP4
>>
>> -Original Message-
>> From: Stringham, Steven [mailto:sstri...@lrlaw.com]
>> Sent: Friday, March 01, 2013 12:57 PM
>> To: NT System Admin Issues
>> Subject: RE: Semi-OT: Vsphere shutdown
>>
>> Get your order dependence list down. Make a list of all the
>> services/servers and decide what order they should be shut down in and what
>> order they can come back up.  I did this recently (moved my datacenter to
>> another location) and it made all the difference to have hashed that out and
>> have a full list to check box as things went down and came back up. Provide
>> this list to your team, and walk through the list multiple times with them
>> as you go.
>>
>> Don't forget to add switches/routers/fibrechannel
>> switches/firewalls/SANs/NASs/managed power strips/etc. to the list.
>> Everything matters. Get a config backup of these on a external device
>> (thumbdrive/laptop) and do a write mem on them before powering them down.
>>
>> Make a note of where the SQL servers are in that list - as well as the
>> vcenter server. Is it hosting it's own database is or is it elsewhere. Also,
>> make a note of which physical host that the vcenter server was on so you can
>> connect to it directly to bring it back up.
>>
>> Make sure you have whatever config cables available to connect directly to
>> the switches/routers etc. in case of trouble on powering back up.
>>
>> Good luck.
>>
>> Steven Stringham
>>
>>
>> -Original Message-
>> From: Kurt Buff [mailto:kurt.b...@gmail.com]
>> Sent: Friday, March 01, 2013 10:25 AM
>> To: NT System Admin Issues
>> Subject: Re: Semi-OT: Vsphere shutdown
>>
>> On Fri, Mar 1, 2013 at 8:52 AM, Richard Stovall  wrote:
>> > In a few days time I will have to completely shutdown my datacenter
>> > for some electrical maintenance.  (Yes, I'm nervous.  It's been online
>> > non-stop for
>> > 6.5 years.)
>> >
>> > I have 3 Vsphere ESX 4.1 hosts that I need to shutdown along with
>> > everything else.  My vcenter server is virtualized.  Two questions:
>> >
>> > 1) Do I need to put the hosts into maintenance mode before powering
>> > them off?  All of the VMs will already be powered off.
>> >
>> > 1) I can poweroff two of the hosts using the vcenter client, but after
>> > I shutdown the vcenter VM how should I poweroff the final host?  Just
>> > connect the client directly to the host and shut it down that way?  I
>> > can't think why this wouldn't work.
>> >
>> > Thanks in advance,
>> > RS
>>
>> One more thing...
>>
>> If you have a multi-site environment, and your connectivity to the other
>> sites will be affected, then when bringing things back up, make sure you
>> have connectivity to the other sites before bringing up your DC - so
>> firewall/router/VPN connections before the DC, in this case.
>> Then, make sure your DC is communicating with DCs in other sites before
>> bringing up the rest of the infrastructure.
>>
>> It's not that I think that anything *bad* will happen if you do it out of
>> order - but it gave me much more peace of mind when I did that.
>>
>> Kurt
>>
>> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~
>>   ~
>>
>> ---
>> To manage subscriptions click here:
>> http://lyris.sunbelt-software.com/read/my_forums/
>> or send an email to listmana...@lyris.sunbeltsoftware.com
>> with the body: unsubscribe ntsysadmin
>>
>>
>> --
>> For more information about Lewis and Roca LLP, please go to
>> www.lewisandroca.com.
>>
>> Phoenix (602)262-5311   Reno (775)823-2900
>> Tucson (520)622-2090Albuquerque (505)764-5400
>> Las Vegas (702)949-8200 Silicon Valley (650)391-1380
>>
>>   This message is intended only for the use of the individual or entity to
>> which it is addressed. If the reader of this message is not the intended
>> recipient, or the employee or agent responsible for delivering the message
>> to the intended recipient, you are hereby notified that any dissemination,
>> distribution or copying of this message is strictly 

Re: Semi-OT: Vsphere shutdown

[Richard Stovall]

I've got two physical DCs and one virtual at this site.  The physical ones
are one traditional rack server and one blade.  The blade doesn't use any
SAN storage, but I don't plan to bring it back up until the SAN is
completely online.


On Fri, Mar 1, 2013 at 1:15 PM, John Cook  wrote:

> One more thing - If you don't have a physical DC in that location boot
> that first - it'll save you loads of suffering. I keep a physical and
> virtual DC for this very reason.
>
>  John W. Cook
> Network Operations Manager
> Partnership For Strong Families
> 5950 NW 1st Place
> Gainesville, Fl 32607
> Office (352) 244-1610
> Cell (352) 215-6944
> MCSE, MCP+I, MCTS, CompTIA A+, N+, VSP4, VTSP4
>
> -Original Message-
> From: Stringham, Steven [mailto:sstri...@lrlaw.com]
> Sent: Friday, March 01, 2013 12:57 PM
> To: NT System Admin Issues
> Subject: RE: Semi-OT: Vsphere shutdown
>
> Get your order dependence list down. Make a list of all the
> services/servers and decide what order they should be shut down in and what
> order they can come back up.  I did this recently (moved my datacenter to
> another location) and it made all the difference to have hashed that out
> and have a full list to check box as things went down and came back up.
> Provide this list to your team, and walk through the list multiple times
> with them as you go.
>
> Don't forget to add switches/routers/fibrechannel
> switches/firewalls/SANs/NASs/managed power strips/etc. to the list.
> Everything matters. Get a config backup of these on a external device
> (thumbdrive/laptop) and do a write mem on them before powering them down.
>
> Make a note of where the SQL servers are in that list - as well as the
> vcenter server. Is it hosting it's own database is or is it elsewhere.
> Also, make a note of which physical host that the vcenter server was on so
> you can connect to it directly to bring it back up.
>
> Make sure you have whatever config cables available to connect directly to
> the switches/routers etc. in case of trouble on powering back up.
>
> Good luck.
>
> Steven Stringham
>
>
> -Original Message-
> From: Kurt Buff [mailto:kurt.b...@gmail.com]
> Sent: Friday, March 01, 2013 10:25 AM
> To: NT System Admin Issues
> Subject: Re: Semi-OT: Vsphere shutdown
>
> On Fri, Mar 1, 2013 at 8:52 AM, Richard Stovall  wrote:
> > In a few days time I will have to completely shutdown my datacenter
> > for some electrical maintenance.  (Yes, I'm nervous.  It's been online
> > non-stop for
> > 6.5 years.)
> >
> > I have 3 Vsphere ESX 4.1 hosts that I need to shutdown along with
> > everything else.  My vcenter server is virtualized.  Two questions:
> >
> > 1) Do I need to put the hosts into maintenance mode before powering
> > them off?  All of the VMs will already be powered off.
> >
> > 1) I can poweroff two of the hosts using the vcenter client, but after
> > I shutdown the vcenter VM how should I poweroff the final host?  Just
> > connect the client directly to the host and shut it down that way?  I
> > can't think why this wouldn't work.
> >
> > Thanks in advance,
> > RS
>
> One more thing...
>
> If you have a multi-site environment, and your connectivity to the other
> sites will be affected, then when bringing things back up, make sure you
> have connectivity to the other sites before bringing up your DC - so
> firewall/router/VPN connections before the DC, in this case.
> Then, make sure your DC is communicating with DCs in other sites before
> bringing up the rest of the infrastructure.
>
> It's not that I think that anything *bad* will happen if you do it out of
> order - but it gave me much more peace of mind when I did that.
>
> Kurt
>
> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <
> http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~
>
> ---
> To manage subscriptions click here:
> http://lyris.sunbelt-software.com/read/my_forums/
> or send an email to listmana...@lyris.sunbeltsoftware.com
> with the body: unsubscribe ntsysadmin
>
>
> --
> For more information about Lewis and Roca LLP, please go to
> www.lewisandroca.com.
>
> Phoenix (602)262-5311   Reno (775)823-2900
> Tucson (520)622-2090Albuquerque (505)764-5400
> Las Vegas (702)949-8200 Silicon Valley (650)391-1380
>
>   This message is intended only for the use of the individual or entity to
> which it is addressed. If the reader of this message is not the intended
> recipient, or the employee or agent responsible for delivering the message
> to the intended recipient, you are hereby notified that any dissemination,
> distribution or copying of this message is strictly prohibited. If you have
> received this communication in error, please notify us immediately by
> replying to the sender of this E-Mail by return E-Mail or by telephone.
>   In accordance with Internal Revenue Service Circular 230, we advise you
> that if this email contains any tax 

RE: Semi-OT: Vsphere shutdown

[Webster]

If I don't have a physical DC, how can I boot it first? :)

Thanks


Webster

> -Original Message-
> From: John Cook [mailto:john.c...@pfsf.org]
> Sent: Friday, March 01, 2013 12:16 PM
> To: NT System Admin Issues
> Subject: RE: Semi-OT: Vsphere shutdown
> 
> One more thing - If you don't have a physical DC in that location boot that
> first


~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

Re: Semi-OT: Vsphere shutdown

[Richard Stovall]

Thanks, Steven.  We're a small shop and the team is one other person and
me.  We had our meeting to go through everything yesterday.

I've already created the plan of attack and written out configs for devices
to my PC and a USB stick.  The SQL DBA says his db backups are OK and he's
ready.  The only parts I'm deeply worried about are our HP blade chassis
and EVA SAN.  There shouldn't be any issues, but they were installed during
a period when I did not work at the company and I have never gone through
the shutdown procedure for them.  The procedure itself seems
straightforward enough, but those spindles have been going for about 4.5
years and it could mean a lot of restore time if more than two in any disk
group decide that they don't want to spin up again.

Cheers,
Richard


On Fri, Mar 1, 2013 at 12:57 PM, Stringham, Steven wrote:

> Get your order dependence list down. Make a list of all the
> services/servers and decide what order they should be shut down in and what
> order they can come back up.  I did this recently (moved my datacenter to
> another location) and it made all the difference to have hashed that out
> and have a full list to check box as things went down and came back up.
> Provide this list to your team, and walk through the list multiple times
> with them as you go.
>
> Don't forget to add switches/routers/fibrechannel
> switches/firewalls/SANs/NASs/managed power strips/etc. to the list.
> Everything matters. Get a config backup of these on a external device
> (thumbdrive/laptop) and do a write mem on them before powering them down.
>
> Make a note of where the SQL servers are in that list - as well as the
> vcenter server. Is it hosting it's own database is or is it elsewhere.
> Also, make a note of which physical host that the vcenter server was on so
> you can connect to it directly to bring it back up.
>
> Make sure you have whatever config cables available to connect directly to
> the switches/routers etc. in case of trouble on powering back up.
>
> Good luck.
>
> Steven Stringham
>
>
> -Original Message-
> From: Kurt Buff [mailto:kurt.b...@gmail.com]
> Sent: Friday, March 01, 2013 10:25 AM
> To: NT System Admin Issues
> Subject: Re: Semi-OT: Vsphere shutdown
>
> On Fri, Mar 1, 2013 at 8:52 AM, Richard Stovall  wrote:
> > In a few days time I will have to completely shutdown my datacenter
> > for some electrical maintenance.  (Yes, I'm nervous.  It's been online
> > non-stop for
> > 6.5 years.)
> >
> > I have 3 Vsphere ESX 4.1 hosts that I need to shutdown along with
> > everything else.  My vcenter server is virtualized.  Two questions:
> >
> > 1) Do I need to put the hosts into maintenance mode before powering
> > them off?  All of the VMs will already be powered off.
> >
> > 1) I can poweroff two of the hosts using the vcenter client, but after
> > I shutdown the vcenter VM how should I poweroff the final host?  Just
> > connect the client directly to the host and shut it down that way?  I
> > can't think why this wouldn't work.
> >
> > Thanks in advance,
> > RS
>
> One more thing...
>
> If you have a multi-site environment, and your connectivity to the other
> sites will be affected, then when bringing things back up, make sure you
> have connectivity to the other sites before bringing up your DC - so
> firewall/router/VPN connections before the DC, in this case.
> Then, make sure your DC is communicating with DCs in other sites before
> bringing up the rest of the infrastructure.
>
> It's not that I think that anything *bad* will happen if you do it out of
> order - but it gave me much more peace of mind when I did that.
>
> Kurt
>
> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <
> http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~
>
> ---
> To manage subscriptions click here:
> http://lyris.sunbelt-software.com/read/my_forums/
> or send an email to listmana...@lyris.sunbeltsoftware.com
> with the body: unsubscribe ntsysadmin
>
>
> --
> For more information about Lewis and Roca LLP, please go to
> www.lewisandroca.com.
>
> Phoenix (602)262-5311   Reno (775)823-2900
> Tucson (520)622-2090Albuquerque (505)764-5400
> Las Vegas (702)949-8200 Silicon Valley (650)391-1380
>
>   This message is intended only for the use of the individual or entity to
> which it is addressed. If the reader of this message is not the intended
> recipient, or the employee or agent responsible for delivering the message
> to the intended recipient, you are hereby notified that any dissemination,
> distribution or copying of this message is strictly prohibited. If you have
> received this communication in error, please notify us immediately by
> replying to the sender of this E-Mail by return E-Mail or by telephone.
>   In accordance with Internal Revenue Service Circular 230, we advise you
> that if this email contains any tax advice, such tax advice was not
> intended

RE: Semi-OT: Vsphere shutdown

[John Cook]

One more thing - If you don't have a physical DC in that location boot that 
first - it'll save you loads of suffering. I keep a physical and virtual DC for 
this very reason.

 John W. Cook
Network Operations Manager
Partnership For Strong Families
5950 NW 1st Place
Gainesville, Fl 32607
Office (352) 244-1610
Cell (352) 215-6944
MCSE, MCP+I, MCTS, CompTIA A+, N+, VSP4, VTSP4

-Original Message-
From: Stringham, Steven [mailto:sstri...@lrlaw.com]
Sent: Friday, March 01, 2013 12:57 PM
To: NT System Admin Issues
Subject: RE: Semi-OT: Vsphere shutdown

Get your order dependence list down. Make a list of all the services/servers 
and decide what order they should be shut down in and what order they can come 
back up.  I did this recently (moved my datacenter to another location) and it 
made all the difference to have hashed that out and have a full list to check 
box as things went down and came back up. Provide this list to your team, and 
walk through the list multiple times with them as you go.

Don't forget to add switches/routers/fibrechannel 
switches/firewalls/SANs/NASs/managed power strips/etc. to the list. Everything 
matters. Get a config backup of these on a external device (thumbdrive/laptop) 
and do a write mem on them before powering them down.

Make a note of where the SQL servers are in that list - as well as the vcenter 
server. Is it hosting it's own database is or is it elsewhere. Also, make a 
note of which physical host that the vcenter server was on so you can connect 
to it directly to bring it back up.

Make sure you have whatever config cables available to connect directly to the 
switches/routers etc. in case of trouble on powering back up.

Good luck.

Steven Stringham


-Original Message-
From: Kurt Buff [mailto:kurt.b...@gmail.com]
Sent: Friday, March 01, 2013 10:25 AM
To: NT System Admin Issues
Subject: Re: Semi-OT: Vsphere shutdown

On Fri, Mar 1, 2013 at 8:52 AM, Richard Stovall  wrote:
> In a few days time I will have to completely shutdown my datacenter
> for some electrical maintenance.  (Yes, I'm nervous.  It's been online
> non-stop for
> 6.5 years.)
>
> I have 3 Vsphere ESX 4.1 hosts that I need to shutdown along with
> everything else.  My vcenter server is virtualized.  Two questions:
>
> 1) Do I need to put the hosts into maintenance mode before powering
> them off?  All of the VMs will already be powered off.
>
> 1) I can poweroff two of the hosts using the vcenter client, but after
> I shutdown the vcenter VM how should I poweroff the final host?  Just
> connect the client directly to the host and shut it down that way?  I
> can't think why this wouldn't work.
>
> Thanks in advance,
> RS

One more thing...

If you have a multi-site environment, and your connectivity to the other sites 
will be affected, then when bringing things back up, make sure you have 
connectivity to the other sites before bringing up your DC - so 
firewall/router/VPN connections before the DC, in this case.
Then, make sure your DC is communicating with DCs in other sites before 
bringing up the rest of the infrastructure.

It's not that I think that anything *bad* will happen if you do it out of order 
- but it gave me much more peace of mind when I did that.

Kurt

~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ 
  ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin


--
For more information about Lewis and Roca LLP, please go to 
www.lewisandroca.com.

Phoenix (602)262-5311   Reno (775)823-2900
Tucson (520)622-2090Albuquerque (505)764-5400
Las Vegas (702)949-8200 Silicon Valley (650)391-1380

  This message is intended only for the use of the individual or entity to 
which it is addressed. If the reader of this message is not the intended 
recipient, or the employee or agent responsible for delivering the message to 
the intended recipient, you are hereby notified that any dissemination, 
distribution or copying of this message is strictly prohibited. If you have 
received this communication in error, please notify us immediately by replying 
to the sender of this E-Mail by return E-Mail or by telephone.
  In accordance with Internal Revenue Service Circular 230, we advise you that 
if this email contains any tax advice, such tax advice was not intended or 
written to be used, and it cannot be used, by any taxpayer for the purpose of 
avoiding penalties that may be imposed on the taxpayer

~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ 
  ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com

RE: Semi-OT: Vsphere shutdown

[Stringham, Steven]

Get your order dependence list down. Make a list of all the services/servers 
and decide what order they should be shut down in and what order they can come 
back up.  I did this recently (moved my datacenter to another location) and it 
made all the difference to have hashed that out and have a full list to check 
box as things went down and came back up. Provide this list to your team, and 
walk through the list multiple times with them as you go.

Don't forget to add switches/routers/fibrechannel 
switches/firewalls/SANs/NASs/managed power strips/etc. to the list. Everything 
matters. Get a config backup of these on a external device (thumbdrive/laptop) 
and do a write mem on them before powering them down.

Make a note of where the SQL servers are in that list - as well as the vcenter 
server. Is it hosting it's own database is or is it elsewhere. Also, make a 
note of which physical host that the vcenter server was on so you can connect 
to it directly to bring it back up.

Make sure you have whatever config cables available to connect directly to the 
switches/routers etc. in case of trouble on powering back up.

Good luck.

Steven Stringham


-Original Message-
From: Kurt Buff [mailto:kurt.b...@gmail.com]
Sent: Friday, March 01, 2013 10:25 AM
To: NT System Admin Issues
Subject: Re: Semi-OT: Vsphere shutdown

On Fri, Mar 1, 2013 at 8:52 AM, Richard Stovall  wrote:
> In a few days time I will have to completely shutdown my datacenter
> for some electrical maintenance.  (Yes, I'm nervous.  It's been online
> non-stop for
> 6.5 years.)
>
> I have 3 Vsphere ESX 4.1 hosts that I need to shutdown along with
> everything else.  My vcenter server is virtualized.  Two questions:
>
> 1) Do I need to put the hosts into maintenance mode before powering
> them off?  All of the VMs will already be powered off.
>
> 1) I can poweroff two of the hosts using the vcenter client, but after
> I shutdown the vcenter VM how should I poweroff the final host?  Just
> connect the client directly to the host and shut it down that way?  I
> can't think why this wouldn't work.
>
> Thanks in advance,
> RS

One more thing...

If you have a multi-site environment, and your connectivity to the other sites 
will be affected, then when bringing things back up, make sure you have 
connectivity to the other sites before bringing up your DC - so 
firewall/router/VPN connections before the DC, in this case.
Then, make sure your DC is communicating with DCs in other sites before 
bringing up the rest of the infrastructure.

It's not that I think that anything *bad* will happen if you do it out of order 
- but it gave me much more peace of mind when I did that.

Kurt

~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ 
  ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin


--
For more information about Lewis and Roca LLP, please go to 
www.lewisandroca.com.

Phoenix (602)262-5311   Reno (775)823-2900
Tucson (520)622-2090Albuquerque (505)764-5400
Las Vegas (702)949-8200 Silicon Valley (650)391-1380

  This message is intended only for the use of the individual or entity to 
which it is addressed. If the reader of this message is not the intended 
recipient, or the employee or agent responsible for delivering the message to 
the intended recipient, you are hereby notified that any dissemination, 
distribution or copying of this message is strictly prohibited. If you have 
received this communication in error, please notify us immediately by replying 
to the sender of this E-Mail by return E-Mail or by telephone.
  In accordance with Internal Revenue Service Circular 230, we advise you that 
if this email contains any tax advice, such tax advice was not intended or 
written to be used, and it cannot be used, by any taxpayer for the purpose of 
avoiding penalties that may be imposed on the taxpayer

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

Java 0 day again...

[Ziots, Edward]

And the Java 0-days just keep on coming
  http://isc.sans.edu/diary.html?n&storyid=15310

Edward E. Ziots, CISSP, CISA, Security +, Network +
Security Engineer
Lifespan Organization
ezi...@lifespan.org

This electronic message and any attachments may be privileged and confidential 
and protected from disclosure. If you are reading this message, but are not the 
intended recipient, nor an employee or agent responsible for delivering this 
message to the intended recipient, you are hereby notified that you are 
strictly prohibited from copying, printing, forwarding or otherwise 
disseminating this communication. If you have received this communication in 
error, please immediately notify the sender by replying to the message. Then, 
delete the message from your computer. Thank you.





~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

Re: Semi-OT: Vsphere shutdown

[Richard Stovall]

Thanks John, Robert and Kurt.  I've got a full plan for how to go about the
shutdown and restart.  One physical DC will be the last to shutdown and the
first to power up.  Putting that plan together was long overdue and a good
exercise in really understanding dependencies.

Now pray for the disk drive gods to be merciful, and the resume won't need
to be touched...

Thanks again,
RS


On Fri, Mar 1, 2013 at 12:25 PM, Kurt Buff  wrote:

> On Fri, Mar 1, 2013 at 8:52 AM, Richard Stovall  wrote:
> > In a few days time I will have to completely shutdown my datacenter for
> some
> > electrical maintenance.  (Yes, I'm nervous.  It's been online non-stop
> for
> > 6.5 years.)
> >
> > I have 3 Vsphere ESX 4.1 hosts that I need to shutdown along with
> everything
> > else.  My vcenter server is virtualized.  Two questions:
> >
> > 1) Do I need to put the hosts into maintenance mode before powering them
> > off?  All of the VMs will already be powered off.
> >
> > 1) I can poweroff two of the hosts using the vcenter client, but after I
> > shutdown the vcenter VM how should I poweroff the final host?  Just
> connect
> > the client directly to the host and shut it down that way?  I can't think
> > why this wouldn't work.
> >
> > Thanks in advance,
> > RS
>
> One more thing...
>
> If you have a multi-site environment, and your connectivity to the
> other sites will be affected, then when bringing things back up, make
> sure you have connectivity to the other sites before bringing up your
> DC - so firewall/router/VPN connections before the DC, in this case.
> Then, make sure your DC is communicating with DCs in other sites
> before bringing up the rest of the infrastructure.
>
> It's not that I think that anything *bad* will happen if you do it out
> of order - but it gave me much more peace of mind when I did that.
>
> Kurt
>
> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~
> ~   ~
>
> ---
> To manage subscriptions click here:
> http://lyris.sunbelt-software.com/read/my_forums/
> or send an email to listmana...@lyris.sunbeltsoftware.com
> with the body: unsubscribe ntsysadmin
>

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

Re: Semi-OT: Vsphere shutdown

[Kurt Buff]

On Fri, Mar 1, 2013 at 8:52 AM, Richard Stovall  wrote:
> In a few days time I will have to completely shutdown my datacenter for some
> electrical maintenance.  (Yes, I'm nervous.  It's been online non-stop for
> 6.5 years.)
>
> I have 3 Vsphere ESX 4.1 hosts that I need to shutdown along with everything
> else.  My vcenter server is virtualized.  Two questions:
>
> 1) Do I need to put the hosts into maintenance mode before powering them
> off?  All of the VMs will already be powered off.
>
> 1) I can poweroff two of the hosts using the vcenter client, but after I
> shutdown the vcenter VM how should I poweroff the final host?  Just connect
> the client directly to the host and shut it down that way?  I can't think
> why this wouldn't work.
>
> Thanks in advance,
> RS

One more thing...

If you have a multi-site environment, and your connectivity to the
other sites will be affected, then when bringing things back up, make
sure you have connectivity to the other sites before bringing up your
DC - so firewall/router/VPN connections before the DC, in this case.
Then, make sure your DC is communicating with DCs in other sites
before bringing up the rest of the infrastructure.

It's not that I think that anything *bad* will happen if you do it out
of order - but it gave me much more peace of mind when I did that.

Kurt

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

Re: Semi-OT: Vsphere shutdown

[Kurt Buff]

And the way to do that is to set your VMs not to autoboot at power up
of the hosts...

Kurt

On Fri, Mar 1, 2013 at 8:59 AM, John Cook  wrote:
> That’s perfectly fine. I’d make sure your VCenter is set to be the first VM
> to come up at reboot.
>
>
>
>  John W. Cook
>
> Network Operations Manager
>
> Partnership For Strong Families
>
> 5950 NW 1st Place
>
> Gainesville, Fl 32607
>
> Office (352) 244-1610
>
> Cell (352) 215-6944
>
> MCSE, MCP+I, MCTS, CompTIA A+, N+, VSP4, VTSP4
>
>
>
> From: Richard Stovall [mailto:rich...@gmail.com]
> Sent: Friday, March 01, 2013 11:53 AM
> To: NT System Admin Issues
> Subject: Semi-OT: Vsphere shutdown
>
>
>
> In a few days time I will have to completely shutdown my datacenter for some
> electrical maintenance.  (Yes, I'm nervous.  It's been online non-stop for
> 6.5 years.)
>
>
>
> I have 3 Vsphere ESX 4.1 hosts that I need to shutdown along with everything
> else.  My vcenter server is virtualized.  Two questions:
>
>
>
> 1) Do I need to put the hosts into maintenance mode before powering them
> off?  All of the VMs will already be powered off.
>
>
>
> 1) I can poweroff two of the hosts using the vcenter client, but after I
> shutdown the vcenter VM how should I poweroff the final host?  Just connect
> the client directly to the host and shut it down that way?  I can't think
> why this wouldn't work.
>
>
>
> Thanks in advance,
>
> RS
>
> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~
> ~   ~
>
> ---
> To manage subscriptions click here:
> http://lyris.sunbelt-software.com/read/my_forums/
> or send an email to listmana...@lyris.sunbeltsoftware.com
> with the body: unsubscribe ntsysadmin
>
>
> 
>
> CONFIDENTIALITY STATEMENT: The information transmitted, or contained or
> attached to or with this Notice is intended only for the person or entity to
> which it is addressed and may contain Protected Health Information (PHI),
> confidential and/or privileged material. Any review, transmission,
> dissemination, or other use of, and taking any action in reliance upon this
> information by persons or entities other than the intended recipient without
> the express written consent of the sender are prohibited. This information
> may be protected by the Health Insurance Portability and Accountability Act
> of 1996 (HIPAA), and other Federal and Florida laws. Improper or
> unauthorized use or disclosure of this information could result in civil
> and/or criminal penalties.
> Consider the environment. Please don't print this e-mail unless you really
> need to.
>
> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~
> ~   ~
>
> ---
> To manage subscriptions click here:
> http://lyris.sunbelt-software.com/read/my_forums/
> or send an email to listmana...@lyris.sunbeltsoftware.com
> with the body: unsubscribe ntsysadmin

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

Re: Semi-OT: Vsphere shutdown

[Kurt Buff]

On Fri, Mar 1, 2013 at 8:52 AM, Richard Stovall  wrote:
> In a few days time I will have to completely shutdown my datacenter for some
> electrical maintenance.  (Yes, I'm nervous.  It's been online non-stop for
> 6.5 years.)
>
> I have 3 Vsphere ESX 4.1 hosts that I need to shutdown along with everything
> else.  My vcenter server is virtualized.  Two questions:
>
> 1) Do I need to put the hosts into maintenance mode before powering them
> off?  All of the VMs will already be powered off.
>
> 1) I can poweroff two of the hosts using the vcenter client, but after I
> shutdown the vcenter VM how should I poweroff the final host?  Just connect
> the client directly to the host and shut it down that way?  I can't think
> why this wouldn't work.
>
> Thanks in advance,

o- If you have a physical DC with DNS, power off that last, and power
it up first.
o- Make sure that VMs aren't set to boot at power on.

Otherwise, that looks really good - not that I'm an expert, but I've
already had to do this once for exactly the same reason.

Kurt

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

Re: Semi-OT: Vsphere shutdown

[Robert Cato]

I would not put the hosts in maintenance mode.

You are correct, connect to the last host with the client directly. You
should keep track of which host has the VC and start that host up first,
connect using the client directly so you can start the VC.

Update your resume :)

On Fri, Mar 1, 2013 at 11:52 AM, Richard Stovall  wrote:

> In a few days time I will have to completely shutdown my datacenter for
> some electrical maintenance.  (Yes, I'm nervous.  It's been online non-stop
> for 6.5 years.)
>
> I have 3 Vsphere ESX 4.1 hosts that I need to shutdown along with
> everything else.  My vcenter server is virtualized.  Two questions:
>
> 1) Do I need to put the hosts into maintenance mode before powering them
> off?  All of the VMs will already be powered off.
>
> 1) I can poweroff two of the hosts using the vcenter client, but after I
> shutdown the vcenter VM how should I poweroff the final host?  Just connect
> the client directly to the host and shut it down that way?  I can't think
> why this wouldn't work.
>
> Thanks in advance,
> RS
>
> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~
> ~   ~
>
> ---
> To manage subscriptions click here:
> http://lyris.sunbelt-software.com/read/my_forums/
> or send an email to listmana...@lyris.sunbeltsoftware.com
> with the body: unsubscribe ntsysadmin
>

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

RE: Semi-OT: Vsphere shutdown

[John Cook]

That’s perfectly fine. I’d make sure your VCenter is set to be the first VM to 
come up at reboot.

 John W. Cook
Network Operations Manager
Partnership For Strong Families
5950 NW 1st Place
Gainesville, Fl 32607
Office (352) 244-1610
Cell (352) 215-6944
MCSE, MCP+I, MCTS, CompTIA A+, N+, VSP4, VTSP4

From: Richard Stovall [mailto:rich...@gmail.com]
Sent: Friday, March 01, 2013 11:53 AM
To: NT System Admin Issues
Subject: Semi-OT: Vsphere shutdown

In a few days time I will have to completely shutdown my datacenter for some 
electrical maintenance.  (Yes, I'm nervous.  It's been online non-stop for 6.5 
years.)

I have 3 Vsphere ESX 4.1 hosts that I need to shutdown along with everything 
else.  My vcenter server is virtualized.  Two questions:

1) Do I need to put the hosts into maintenance mode before powering them off?  
All of the VMs will already be powered off.

1) I can poweroff two of the hosts using the vcenter client, but after I 
shutdown the vcenter VM how should I poweroff the final host?  Just connect the 
client directly to the host and shut it down that way?  I can't think why this 
wouldn't work.

Thanks in advance,
RS

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin



CONFIDENTIALITY STATEMENT: The information transmitted, or contained or 
attached to or with this Notice is intended only for the person or entity to 
which it is addressed and may contain Protected Health Information (PHI), 
confidential and/or privileged material. Any review, transmission, 
dissemination, or other use of, and taking any action in reliance upon this 
information by persons or entities other than the intended recipient without 
the express written consent of the sender are prohibited. This information may 
be protected by the Health Insurance Portability and Accountability Act of 1996 
(HIPAA), and other Federal and Florida laws. Improper or unauthorized use or 
disclosure of this information could result in civil and/or criminal penalties.
Consider the environment. Please don't print this e-mail unless you really need 
to.

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin