<?php
   if ( ereg("^(128\.101\.102|160\.94\.145|134\.84\.210)", $_SERVER[REMOTE_ADDR]) ) {
?>
<?xml version="1.0" encoding="utf-8"?>
    <rss version="2.0">
        <channel>
            <title>JaWS Software Admin News</title>
            <link>http://blog.lib.umn.edu/jaws/swadm/</link>
            <description></description>
            <language>en</language>
            <copyright>Copyright 2013</copyright>
            <lastBuildDate>Sun, 10 Feb 2013 12:25:26 -0600</lastBuildDate>
            <generator>http://www.sixapart.com/movabletype/</generator>
            <docs>http://www.rssboard.org/rss-specification</docs>
    
            <item>
                <title>test2</title>
                <description>Testing again! </description>
                <link>http://blog.lib.umn.edu/jaws/swadm/2013/02/test2.php</link>
                <guid>http://blog.lib.umn.edu/jaws/swadm/2013/02/test2.php</guid>
        
        
                <pubDate>Sun, 10 Feb 2013 12:25:26 -0600</pubDate>
            </item>
    
            <item>
                <title>Test</title>
                <description>Just testing some functionality. </description>
                <link>http://blog.lib.umn.edu/jaws/swadm/2013/02/test.php</link>
                <guid>http://blog.lib.umn.edu/jaws/swadm/2013/02/test.php</guid>
        
        
                <pubDate>Sun, 10 Feb 2013 10:14:28 -0600</pubDate>
            </item>
    
            <item>
                <title>Overhead Cabling moves, part 1</title>
                <description><![CDATA[As part of WBOB's move from underfloor to overhead cabling for the entire WBOB data center the ethernet for JaWS Servers will need to be swapped to overhead routed cables that are already in place. Each move will result in a brief 1 minute interruption in network connectivity while the cables are swapped. The applications residing on the affected servers will be restarted if necesary, it should only be required for applications with persistent connections to external databases or NFS mounts.<br /><br />Production servers will be recabled in multiple batches, one this Sunday (8/8) between 7:00a - 10:00a and another one next Sunday (8/15) between 7:00a - 10:00a. The 8/8 batch swadm responsibilities will be handled by Ben Larson, the 8/15 batch will be handled by Chris Ament. <br /><br />Non production servers will be done during the week of 8/9 on Tuesday 8/10 7:00 - 9:00a with Ben Larson coordinating with OIA and on Wednesday 8/11 8:00a - 10:00a with Garrett Kuchta coordinating with OIA.<br /><br />To determine when a server is slated to be moved please refer to the Google Doc viewable <a href="http://spreadsheets.google.com/a/umn.edu/pub?key=t-BOOHrELTnmRzJX8aZCjxQ&amp;output=html">here</a>. NOTE: all times after 8/15 are considered tentative pending CAB approval!<br /><br />There are approved 'urgent' changes in Service Center for two of these production windows currently, the 8/8 window is change&nbsp; C67894 and the 8/15 window is change C67897 .<br />]]></description>
                <link>http://blog.lib.umn.edu/jaws/swadm/2010/08/overhead-cabling-moves-part-1.php</link>
                <guid>http://blog.lib.umn.edu/jaws/swadm/2010/08/overhead-cabling-moves-part-1.php</guid>
        
        
                    <category domain="http://www.sixapart.com/ns/types#tag">Production</category>
        
                    <category domain="http://www.sixapart.com/ns/types#tag">WBOB</category>
        
                <pubDate>Thu, 05 Aug 2010 15:18:18 -0600</pubDate>
            </item>
    
            <item>
                <title>VPN hardware upgrade on March 23rd</title>
                <description><![CDATA[NTS will be upgrading the VPN hardware on March 23rd.&nbsp; Details of the announcement are below.<br /><br /><blockquote><font style="font-size: 0.8em;"><i>
On March 23, 2010, the existing VPN hardware and software will be<br />
upgraded. A new Cisco VPN client will also be introduced for use with the<br />
upgraded hardware and software. Depending on your needs and what OS you<br />
currently run, you may need to upgrade your VPN client:<br /><br />
If you run on a 64 bit version of Windows, and/or you are using IPv6, you<br />
will need to upgrade to the new Cisco VPN client (called AnyConnect). The<br />
current VPN client software is referred to as EasyConnect.<br /><br />
NTS is running a test system now if you would like to try out the new VPN<br />
client. The test hardware for both the AnyConnect and EasyConnect clients<br />
is: <a href="http://anyconnect-cluster-test.vpn.umn.edu/" target="_blank">anyconnect-cluster-test.vpn.<wbr>umn.edu</a><br /><br />
L2TP is also an option for connecting to the UofMvpn workgroup. The<br />
advantage of using L2TP is that it is native to Windows, Mac and Linux and<br />
thus you don't need to install any additional software.<br />
L2TP as implemented only supports UofMvpn workgroup. To use other<br />
workgroups, you will need to use the AnyConnect or the EasyConnect client.<br />
The L2TP client does not work behind firewalled desktop networks.<br />
The test hardware for L2TP is: <a href="http://nct.vpn.umn.edu/" target="_blank">nct.vpn.umn.edu</a><br /><br />
Only use the UofMvpn VPN workgroup for testing with any of the clients for<br />
now.<br /><br />
VPN workgroups are also called instances or tunnel groups.<br /><br />
Draft documentation and client software is available at:<br /><a href="https://netfiles.umn.edu/users/peiffer/" target="_blank">https://netfiles.umn.edu/<wbr>users/peiffer/</a><br /><br />
Please let me know if I can provide further information via <a href="mailto:oialinux@umn.edu" target="_blank">oialinux@umn.edu</a>.</i></font><br /></blockquote>









 ]]></description>
                <link>http://blog.lib.umn.edu/jaws/swadm/2010/03/vpn-hardware-upgrade-on-march-23rd.php</link>
                <guid>http://blog.lib.umn.edu/jaws/swadm/2010/03/vpn-hardware-upgrade-on-march-23rd.php</guid>
        
        
                    <category domain="http://www.sixapart.com/ns/types#tag">VPN</category>
        
                <pubDate>Mon, 08 Mar 2010 09:54:13 -0600</pubDate>
            </item>
    
            <item>
                <title>Web Hotel Maintenance on Sunday, March 7th, 7:00-7:30AM</title>
                <description><![CDATA[OIA will be performing maintenance on the Web Hotel server (warrior) on Sunday, March 7th, from 7-7:30AM.&nbsp; The work will include:<br /><br />- Additional network interface/VLAN to support migration from tank to warrior<br />- Operating system patches<br /><br />The outage is expected to last less than 5 minutes if work goes as planned.&nbsp; Please inform customers who are sensitive to downtime during this time period.<br /><br />In preparation for this work, ultraman and pursuit will have operating system patches applied and be rebooted on Wednesday, March 3rd at 8:30AM.<br /><br /> ]]></description>
                <link>http://blog.lib.umn.edu/jaws/swadm/2010/02/web-hotel-maintenance-on-sunday-march-7th-700-730am.php</link>
                <guid>http://blog.lib.umn.edu/jaws/swadm/2010/02/web-hotel-maintenance-on-sunday-march-7th-700-730am.php</guid>
        
        
                    <category domain="http://www.sixapart.com/ns/types#tag">Hotel</category>
        
                    <category domain="http://www.sixapart.com/ns/types#tag">Production</category>
        
                <pubDate>Fri, 19 Feb 2010 11:00:16 -0600</pubDate>
            </item>
    
            <item>
                <title>Filenet hotel sites to be decommissioned</title>
                <description><![CDATA[
The following sites are set to be decommissioned 2:00p Tuesday February
2nd. They all live on the old filenet hotel (zoar/nebula) and the
cnames either point off to other web servers or they merely serve
redirects now. If you have questions or concerns about this please
contact swadm.<br />

<br />

<a class="moz-txt-link-abbreviated" href="http://www.hhh.umn.edu/">www.hhh.umn.edu</a><br />

<a class="moz-txt-link-abbreviated" href="http://www.cdes.umn.edu/">www.cdes.umn.edu</a><br />

<a class="moz-txt-link-abbreviated" href="http://www.academic.umn.edu/">www.academic.umn.edu</a><br />

stpaulcareers.umn.edu<br />

ssw.cehd.umn.edu<br />

fsos.cehd.umn.edu<br />

fscn-old.cfans.umn.edu<br />

dha.cdes.umn.edu<br /><br />Added 2-2-2010:<br />goldstein.cdes.umn.edu<br />rjp.umn.edu<br /><br />Added 2-3-2010:<br />www.che.umn.edu<br />]]></description>
                <link>http://blog.lib.umn.edu/jaws/swadm/2010/01/filenet-hotel-sites-to-be-decommissioned.php</link>
                <guid>http://blog.lib.umn.edu/jaws/swadm/2010/01/filenet-hotel-sites-to-be-decommissioned.php</guid>
        
                    <category domain="http://www.sixapart.com/ns/types#category">Public</category>
        
        
                    <category domain="http://www.sixapart.com/ns/types#tag">Hotel</category>
        
                    <category domain="http://www.sixapart.com/ns/types#tag">Production</category>
        
                <pubDate>Thu, 28 Jan 2010 16:27:39 -0600</pubDate>
            </item>
    
            <item>
                <title>Changes to IPSca (free-but-valid) certs</title>
                <description><![CDATA[The IPSca root CA under which all the IPSca free-but-valid .edu certificates issued to date have been created, and is widely supported in current browsers, expires 12-29-2009. The <a href="http://certs.ipsca.com/support/emailrenovacionca_apache_in.htm">solution</a> outlined by IPSca is to renew all IPSca issued certificates to utilize their newly issued CA's. I have submitted all current IPSca certs for renewal and begun installing the new certificates and certificate chain files to use their new CA's.<br /><br />However, the new CA's are not recognized in the majority of browsers currently, meaning that these certs will flag as untrusted in most browsers. As of today the only two browsers that are supporting IPSca's new CA's are Internet Explorer and Chrome on Windows for users who have applied the optional windows updates since November 2009. Firefox is <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=529286">working</a> on getting it included with no ETC.<br /><br />If you have a site on the list below and need a valid cert for it then please write to certificates@software.umn.edu and request a Thawte. (Note that a new Thawte will cost $144 .)<br /><br />List of sites with IPSca certs as of 12-23-09:<br /><br />*.software.umn.edu<br />
leaf.oit.umn.edu<br />
motel-test.software.umn.edu<br />
templates.umsurvey.umn.edu<br />
timber.software.umn.edu<br />
*.test-hotel.software.umn.edu<br />
*.dev-hotel.software.umn.edu<br />
test-status.umn.edu<br />
wiki-test.software.umn.edu<br />
mnscupachy-test.software.umn.edu<br />
pachyderm.umn.edu<br />
pachyderm-test.umn.edu<br />
sphpachy.umn.edu<br />
mnscupachy.umn.edu<br />
sphpachy-test.umn.edu<br />
test-hotel.software.umn.edu<br />
sysstatdev.software.umn.edu<br />
dev-status.umn.edu<br /> ]]></description>
                <link>http://blog.lib.umn.edu/jaws/swadm/2009/12/changes-to-ipsca-free-but-valid-certs.php</link>
                <guid>http://blog.lib.umn.edu/jaws/swadm/2009/12/changes-to-ipsca-free-but-valid-certs.php</guid>
        
        
                    <category domain="http://www.sixapart.com/ns/types#tag">Certificates</category>
        
                    <category domain="http://www.sixapart.com/ns/types#tag">Hotel</category>
        
                <pubDate>Wed, 23 Dec 2009 12:51:58 -0600</pubDate>
            </item>
    
            <item>
                <title>Web Hotel failback complete</title>
                <description><![CDATA[The transition of the Web &amp; MySQL Hotel back to their respective production environments was completed at 7AM this morning.&nbsp; Please let us know if you notice any problems.<br /> ]]></description>
                <link>http://blog.lib.umn.edu/jaws/swadm/2009/10/web-hotel-failback-complete.php</link>
                <guid>http://blog.lib.umn.edu/jaws/swadm/2009/10/web-hotel-failback-complete.php</guid>
        
        
                    <category domain="http://www.sixapart.com/ns/types#tag">Hotel</category>
        
                    <category domain="http://www.sixapart.com/ns/types#tag">MySQL</category>
        
                <pubDate>Mon, 26 Oct 2009 09:25:43 -0600</pubDate>
            </item>
    
            <item>
                <title>Web Hotel failover complete</title>
                <description><![CDATA[The Web Hotel failover scheduled for 5AM this morning was completed at 5:30AM.&nbsp; Pong is was promoted to production web hotel server; badlands production MySQL hotel ]]></description>
                <link>http://blog.lib.umn.edu/jaws/swadm/2009/10/web-hotel-failover-complete.php</link>
                <guid>http://blog.lib.umn.edu/jaws/swadm/2009/10/web-hotel-failover-complete.php</guid>
        
        
                    <category domain="http://www.sixapart.com/ns/types#tag">Hotel</category>
        
                <pubDate>Fri, 23 Oct 2009 07:25:13 -0600</pubDate>
            </item>
    
            <item>
                <title>IPF Change to production Solaris Hosts</title>
                <description><![CDATA[OIA will be altering the IPF config on assassin, assault, kram, kengo, and stargate Thursday (10-15) morning at 9:00 am. This update to the firewall will allow the OITsec's scan appliance to ping the host but block full scans from happening. This will allow them to take our hosts off the exception list but should prevent our hosts from getting DoS'd as has happened several times in the past.<br /><br />Please report any odd behavior from these hosts right away to support@software .<br /> ]]></description>
                <link>http://blog.lib.umn.edu/jaws/swadm/2009/10/ipf-change-to-production-solaris-hosts.php</link>
                <guid>http://blog.lib.umn.edu/jaws/swadm/2009/10/ipf-change-to-production-solaris-hosts.php</guid>
        
                    <category domain="http://www.sixapart.com/ns/types#category">Public</category>
        
        
                    <category domain="http://www.sixapart.com/ns/types#tag">Hotel</category>
        
                    <category domain="http://www.sixapart.com/ns/types#tag">Production</category>
        
                    <category domain="http://www.sixapart.com/ns/types#tag">UMContent</category>
        
                    <category domain="http://www.sixapart.com/ns/types#tag">WebVista</category>
        
                <pubDate>Wed, 14 Oct 2009 16:07:34 -0600</pubDate>
            </item>
    
            <item>
                <title>NAS storage maintenance this Sunday, Sept 27, 6:30AM</title>
                <description><![CDATA[There will be a third (and final) planned <b>NAS outage this Sunday beginning at 6:30am and lasting for approximately 2 hours</b>.&nbsp; NFS mounted home directories will be unavailable during this time, and any login sessions may be disrupted.&nbsp; Please log out before you leave on Friday.<br /><br /><b>Affected mount points are:</b><br />adcs_stellent_nfs_04<br />DR_oia_linux_nfs_09<br />DR_LIB_NFS_01<br />jaws_backup<br />jaws_homedir_02<br />jaws_moodle_nfs_02<br />oia_webhost_nfs_06, 07,.08<br />UMWiki_NFS_02<br /><br />]]></description>
                <link>http://blog.lib.umn.edu/jaws/swadm/2009/09/nas-storage-maintenance-this-sunday-sept-27-630am.php</link>
                <guid>http://blog.lib.umn.edu/jaws/swadm/2009/09/nas-storage-maintenance-this-sunday-sept-27-630am.php</guid>
        
        
                    <category domain="http://www.sixapart.com/ns/types#tag">NAS</category>
        
                <pubDate>Wed, 23 Sep 2009 16:56:11 -0600</pubDate>
            </item>
    
            <item>
                <title>MySQL Hotel upgrade, Bastion Hosts, and Server provisioning</title>
                <description><![CDATA[There are some server infrastructure changes coming (or already here) that will affect everyone in one way or another.&nbsp; Details are on the wiki - I'll summarize them here and you can decide which parts are relevant to your work.&nbsp; Please come to the All-staff meeting on Monday with questions or concerns.<br /><br /><b>MySQL Hotel Upgrade:</b><br />We're upgrading our MySQL Hotel (venus) to new hardware with a master/slave configuration.&nbsp; The upgrade will occur on Sunday, October 11th, between 8-10AM.&nbsp; See <a href="https://wiki.umn.edu/view/Swadm/WebHotel#MySQL_Database">https://wiki.umn.edu/view/Swadm/WebHotel#MySQL_Database</a> for details including migration options.<br /><br /><b>Bastion Hosts:</b><br />SSH access to all OIT servers is restricted to either the OIT VPN or selected bastion hosts.&nbsp; We will be consolidating this infrastructure, effectively retiring the original JaWS bastions (frogger &amp; naomi) in favor of the OIA bastions (ale01, ale02, and ale03).&nbsp; Access to the OIA bastions requires 2FA -- use of SSH keys is allowed and encouraged.&nbsp; There is no date set, but we are targeting having this completed before the end of the year. See <a href="https://wiki.umn.edu/view/Swadm/BastionHost">https://wiki.umn.edu/view/Swadm/BastionHost</a> for specifics.<br /><br /><b>Server Provisioning: </b><br />All new server installations (physical or virtual) are based on a new RHEL image that has some significant differences compared to the traditional JaWS image.&nbsp; Access and security policies are more restrictive.&nbsp; See <a href="https://wiki.umn.edu/view/Swadm/ServerConfig">https://wiki.umn.edu/view/Swadm/ServerConfig</a> for additional detail and an inventory of differences.<br /><br /> ]]></description>
                <link>http://blog.lib.umn.edu/jaws/swadm/2009/09/mysql-hotel-upgrade-bastion-hosts-and-server-provisioning.php</link>
                <guid>http://blog.lib.umn.edu/jaws/swadm/2009/09/mysql-hotel-upgrade-bastion-hosts-and-server-provisioning.php</guid>
        
        
                    <category domain="http://www.sixapart.com/ns/types#tag">Hotel</category>
        
                    <category domain="http://www.sixapart.com/ns/types#tag">MySQL</category>
        
                    <category domain="http://www.sixapart.com/ns/types#tag">Production</category>
        
                <pubDate>Thu, 17 Sep 2009 12:36:14 -0600</pubDate>
            </item>
    
            <item>
                <title>Additional details on the upcoming WBOB outage from OIA</title>
                <description><![CDATA[This has also been added to the wiki.<br /><a href="https://wiki.umn.edu/view/Swadm/WbobOutage10242009">https://wiki.umn.edu/view/Swadm/WbobOutage10242009</a><br /><br />-------- Original Message --------<br />Subject: [OITDCTENANTS] IT Outage on Saturday, October 24, 2009<br />Date: Wed, 16 Sep 2009 08:13:15 -0500<br />From: Joe Zanmiller &lt;jpz@umn.edu&gt;<br />Reply-To: OITDC Tenants &lt;OITDCTENANTS@LISTS.UMN.EDU&gt;<br />To: OITDCTENANTS@LISTS.UMN.EDU<br /><br />Beginning at 2:00 a.m. on Saturday, October 24, 2009, all University of <br />Minnesota IT systems and applications will be unavailable for use. <br />Beginning at 2:00 a.m., University of Minnesota IT staff from the Office <br />of Information Technology (OIT) and from departments with servers in the <br />WBOB Data Center will begin bringing down their applications with a goal <br />that systems and applications will be unavailable for use by 4:45 a.m. <br />The Data Center will powered off at 7 a.m. and will be available for <br />staff to restart applications on Sunday, October 25 at approximately1:00 <br />a.m. All applications supported by OIT are expected to be restored to <br />service by 7:00 a.m. on October 25 and will become available on their <br />normal schedule.<br /><br />OIT has created a Web site that will be continuously updated as we plan <br />for and execute this outage: <br />https://systemstatus.umn.edu/view/Main/OutageInfo.<br /><br />PLANNED OUTAGE<br />The Office of Information Technology (OIT) has been planning for this <br />outage and communicating regularly with collegiate IT Directors. It is <br />absolutely necessary that we perform this work, as it will decrease the <br />risk of an unplanned outage to the University's IT applications during a <br />critical time, such as student registration or final exams.<br /><br />OIT acknowledges that this is a very difficult time, and we recognize <br />the importance of the University's core systems. However, we ask you to <br />understand the need for us to perform this critical work, and we ask you <br />to help us by sharing this information with your students, staff, <br />faculty, and customers who will need to adjust their schedules to <br />accommodate this critical work.<br /><br />TECHNICAL DETAILS<br />This outage is being scheduled so that OIT can increase the amount of <br />utility and emergency power to its primary data center, which is located <br />in the West Bank Office Building (WBOB). This will allow OIT to increase <br />the reliability, availability, and capacity of this data center.<br /><br />All Enterprise and University-wide applications supported by OIT run on <br />servers and disk in the WBOB Data Center. In addition, servers and disk <br />for OIT Hosting Services are located in the WBOB Data Center. Finally, <br />several University departments are tenants in the WBOB Data Center and <br />have critical servers and storage there.<br /><br />If we have an event causing the loss of all power (i.e., both utility <br />and generator backup power) in the WBOB Data Center, we currently do not <br />have the capability to provide uninterrupted availability of Enterprise <br />and University-wide Applications and many Departmental Applications. <br />Last summer, we had two catastrophic power-loss events in the WBOB Data <br />Center that caused applications to not be available for several hours By <br />upgrading the power system in this data center, OIT will be better able <br />to support the applications and systems that reside there with decreased <br />risk for unscheduled interruption to service. If we do not perform this <br />necessary work, the University will continue to be at considerably <br />greater risk for unplanned outages to Enterprise and University-wide <br />applications similar to the two outages in July and August 2008.<br /><br />SHUTDOWN SCHEDULE FOR SATURDAY, OCTOBER 24<br />* No later than 4:45 a.m. All OIT Hosting customers and Data Center <br />tenants must have their applications and databases shut down.<br /><br />* Beginning at 4:45 a.m.: Tenant staff will be given access to the Data <br />Center, if necessary, to power-off their equipment.<br /><br />* No later than 5:45a.m.: All tenant equipment in the Primary Data <br />Center must be powered-off.<br /><br />* Beginning at 5:45 a.m.: OIA will finish powering-off all of our <br />servers and the SAN.<br /><br />* 7:00 a.m.: The Data Center will be turned over to the construction <br />engineers and contractor, and all power to the Primary Data Center will <br />be turned off. (Note: power should remain available in the WBOB building <br />during construction activities, except for 6th floor.)<br /><br />RESTART SCHEDULE FOR SUNDAY, OCTOBER 25<br />* 1:00 a.m.: After OIT has restarted the network and the SAN, the Data <br />Center will be open for tenants to begin restarting their systems. At <br />this time, OIT will begin starting servers for our hosting customers and <br />for Enterprise Applications.<br /><br />* Beginning at 3 a.m.: Servers will be available for Hosting Services <br />customers to restart their databases and applications. OIT engineers <br />will verify the functionality of all OIT-supported databases and <br />applications by 7:00 a.m. Applications will be available to customers <br />per the normal schedule on Sunday.<br /><br />EARLY FINISH<br />OIT will make every effort to reduce the timeframe of this outage. If we <br />finish construction early, OIT staff will immediately begin the process <br />to restart, beginning with the network, SAN, and servers. If tenants and <br />Hosting Services customers have requested, OIT engineers will call <br />tenants when the SAN becomes available so they can restart their <br />servers, and OIT engineers will call Hosting Service customers when the <br />servers are ready for them to restart their databases and applications. <br />If you would like to receive this notification, reply to this e-mail and <br />provide a contact phone number and e-mail address that can be used the <br />day of the event.<br /><br />COMMUNICATIONS DURING THE EVENT<br />During the outage, you can visit <br />https://systemstatus.umn.edu/view/Main/OutageInfo for up-to-date <br />information about the progress of the construction and system restart <br />activities. In addition, the System Status page will be updated <br />throughout the weekend to reflect the status of individual applications: <br />http://systemstatus.umn.edu/view/Main.<br /><br />Please share this information with any staff or faculty that will need <br />to plan for this event.<br /><br />Al Pierce<br />Senior Manager<br />Operations, Infrastructure, and Architecture Data Center Operations<br />Office of Information Technology<br /><br /><div><br /></div>]]></description>
                <link>http://blog.lib.umn.edu/jaws/swadm/2009/09/additional-details-on-the-upcoming-wbob-outage-from-oia.php</link>
                <guid>http://blog.lib.umn.edu/jaws/swadm/2009/09/additional-details-on-the-upcoming-wbob-outage-from-oia.php</guid>
        
        
                    <category domain="http://www.sixapart.com/ns/types#tag">Production</category>
        
                    <category domain="http://www.sixapart.com/ns/types#tag">WBOB</category>
        
                <pubDate>Wed, 16 Sep 2009 09:34:30 -0600</pubDate>
            </item>
    
            <item>
                <title>WBOB Data Center Outage on Saturday, October 24th</title>
                <description><![CDATA[We've been getting an number of questions regarding the planned outage for the WBOB data center on <b>Saturday, October 24th</b>.&nbsp; The backup generator for the data center is being replaced with a larger unit that can handle the current and expected future demands on that facility.&nbsp; We don't have specifics on exact times at this point, but the expectation is that the entire facility will be shutdown for most of the day on Saturday, with service being restored as late as Sunday morning.&nbsp; We'll have more specific times in the coming weeks.<br /><br />We're using this event as an opportunity to test our DR readiness for a number of services.&nbsp; High availability, redundancy, and recover-ability are on the minds of many of us and our customers.&nbsp; In some cases the necessary infrastructure is already in place.&nbsp; In others (read: most), we're not there yet, and we're working with application custodians and OIA to assess our options and prioritize work towards that end.<br /><br />At the end of the day, many services will simply be unavailable during the outage.&nbsp; Our goal is to test what we have, fix what we can, and get insights into expectations and the scope of the work ahead for the others.<br /><br /><font style="font-size: 1em;"><b><font style="font-size: 1.25em;">Additional</font> <font style="font-size: 1.25em;">Information will be posted on the wiki as it becomes available:</font></b></font><br /><a href="https//wiki.umn.edu/view/Swadm/WbobOutage10242009">https://wiki.umn.edu/view/Swadm/WbobOutage10242009</a><br /><br /> ]]></description>
                <link>http://blog.lib.umn.edu/jaws/swadm/2009/09/wbob-data-center-outage-on-saturday-october-24th.php</link>
                <guid>http://blog.lib.umn.edu/jaws/swadm/2009/09/wbob-data-center-outage-on-saturday-october-24th.php</guid>
        
        
                    <category domain="http://www.sixapart.com/ns/types#tag">Development</category>
        
                    <category domain="http://www.sixapart.com/ns/types#tag">Production</category>
        
                    <category domain="http://www.sixapart.com/ns/types#tag">WBOB</category>
        
                <pubDate>Thu, 10 Sep 2009 11:38:38 -0600</pubDate>
            </item>
    
            <item>
                <title>NAS Maintenance this Sunday, Sept 13, 6-10AM</title>
                <description><![CDATA[The storage group is performing maintenance on NAS infrastructure that will affect the NFS mounted home directories on many JAWS servers.&nbsp; <b>Please close any open terminal sessions/logins no later than 11pm on Saturday evening to avoid data loss from open files. </b>]]></description>
                <link>http://blog.lib.umn.edu/jaws/swadm/2009/09/nas-maintenance-this-sunday-sept-13-6-10am.php</link>
                <guid>http://blog.lib.umn.edu/jaws/swadm/2009/09/nas-maintenance-this-sunday-sept-13-6-10am.php</guid>
        
        
                    <category domain="http://www.sixapart.com/ns/types#tag">NAS</category>
        
                <pubDate>Tue, 08 Sep 2009 10:20:08 -0600</pubDate>
            </item>
    
        </channel>
    </rss>
<$php
}
$>
