Jump to content

Recommended Posts

Posted

Good morning all!

 

I know it's the weekend but here at Sun (Oracle) we never stop working.... unless it's football or beer of course - or is that just me?

 

Anyway, for all you S7000 users please see below....

 

A new 2009.Q3 micro release has been posted to the Sun Download Centre.

 

All users are encouraged to upgrade, especially those using Active Directory. As always, you can find the list of Sun Storage 7000 software releases at:

 

Software Updates - Fishworks - wikis.sun.com

 

The release notes for this particular release can be found at:

 

ak-2009.09.01.4.1 Release Notes - Fishworks - wikis.sun.com

 

Hope you all have a great weekend.

 

Warmest regards,

 

Phil

  • Thanks 2
Posted

Hey all,

 

Could someone remind me what the best-practice is for doing upgrades with regards to skipping releases or doing each one in turn?

 

I'm currently on 2009.09.01.2.0,1-1.6 (Q3.2.0), which leaves me with this following to do:

 

2009.Q3.3.0

2009.Q3.4.0

2009.Q3.4.1

 

Should I do each one in order with a reboot in between each, or should I go straight to Q3.4.1? I don't mind doing either, it's half term next week so I can afford a couple of hours of downtime. I normally like to stay one release behind (Q3.2 has been rock solid for me) but it's hard to justify not getting the latest release as there are known fixes...

 

Many thanks,

Chris

Posted

I believe you normally just need to run the latest update - it includes all previous upgrades. I think the only exception was if you were running <2.5 prior to updating to 3.0 or later when you had to update to a 2.5 or later release first.

 

Planning on running this update myself next week :)

  • Thanks 2
Posted

Thanks guys, that's what I figured. I guess the only thing that crossed my mind is that most of the testing would be from one version to the next, and that there's a disk firmware upgrade in one of those releases, but we shall see how it goes! :)

 

Chris

Posted (edited)

Just done the update and it's now going through offlining each disk. I've received no errors or alerts and it seems to be working fine. I assume this is the disk firmware update automatically happening?

 

EDIT: Just had a spare disk triggered as a replacement to a disk failure. :(

Edited by Duke

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...