<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title>Frank&apos;s Activity Log</title>
    <link rel="alternate" type="text/html" href="http://fcs.blog.uvm.edu/" />
    <link rel="self" type="application/atom+xml" href="http://fcs.blog.uvm.edu/atom.xml" />
   <id>tag:fcs.blog.uvm.edu,2009://1</id>
    <link rel="service.post" type="application/atom+xml" href="https://fcs.blog.uvm.edu/mt/mt-atom.cgi/weblog/blog_id=1" title="Frank's Activity Log" />
    <updated>2009-09-22T18:41:50Z</updated>
    <subtitle>Purportedly the highlights of my work day...</subtitle>
    <generator uri="http://www.sixapart.com/movabletype/">Movable Type 3.34</generator>
 
<entry>
    <title>22. September 2009 -- Dienstag</title>
    <link rel="alternate" type="text/html" href="http://fcs.blog.uvm.edu/2009/09/22_september_2009_dienstag.html" />
    <link rel="service.edit" type="application/atom+xml" href="https://fcs.blog.uvm.edu/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=680" title="22. September 2009 -- Dienstag" />
    <id>tag:fcs.blog.uvm.edu,2009://1.680</id>
    
    <published>2009-09-22T12:11:47Z</published>
    <updated>2009-09-22T18:41:50Z</updated>
    
    <summary>Admin</summary>
    <author>
        <name></name>
        
    </author>
            <category term="Activity Log" />
    
    <content type="html" xml:lang="en" xml:base="http://fcs.blog.uvm.edu/">
        <![CDATA[<h4>Admin</h4>
<dl>
<dt>LDAP</dt>
<dd><ul compact>
<li>Join errors -- 1 of 2 fixed.  Banner being down I think is preventing the second from being delivered to LDAP.</li>
<li>Privacy flags</li>
</ul></dd>
<dt>Backup</dt>
<dd><ul compact>
<li>Examine save group failures</li>
<li>Recycle expired tapes</li>
</ul></dd>
<dt>Footprints</dt>
<dd><ul compact>
<li>129287: email notifications of new requests being sent to former agents.  Resolved -- Footprints stores this list in the MRprojects file and does <b>not</b> clean it up when you remove an agent.</li>
</ul></dd>
</dl>]]>
        
    </content>
</entry>
<entry>
    <title>18. September 2009 -- Freitag</title>
    <link rel="alternate" type="text/html" href="http://fcs.blog.uvm.edu/2009/09/18_september_2009_freitag.html" />
    <link rel="service.edit" type="application/atom+xml" href="https://fcs.blog.uvm.edu/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=679" title="18. September 2009 -- Freitag" />
    <id>tag:fcs.blog.uvm.edu,2009://1.679</id>
    
    <published>2009-09-18T12:04:17Z</published>
    <updated>2009-09-18T19:54:53Z</updated>
    
    <summary>Admin</summary>
    <author>
        <name></name>
        
    </author>
            <category term="Activity Log" />
    
    <content type="html" xml:lang="en" xml:base="http://fcs.blog.uvm.edu/">
        <![CDATA[<h4>Admin</h4>
<dl>
<dt>LDAP</dt>
<dd><ul compact>
<li>Fix join errors from this morning</li>
<li>Rant at openldap developers for calling 2.4 stable with all the issues still floating around on 2.4.18.</li>
</ul></dd>
<dt>Backup</dt>
<dd><ul compact>
<li>Oops... too many clients defined... who was supposed to keep count this week.... hmm, looks like it was my turn. Darn!</li>
<li>EMC 31051592 -- Yes, I am really running 7.4sp5 and I really do still have nsrck's that hang (well, I did before I re-defined the 94 clients that had been deleted).</li>
<li>Test environment.... romulus and remus are back and they have a VTL this time.</li>
</dl>]]>
        
    </content>
</entry>
<entry>
    <title>17. September 2009 -- Donnerstag</title>
    <link rel="alternate" type="text/html" href="http://fcs.blog.uvm.edu/2009/09/17_september_2009_donnerstag.html" />
    <link rel="service.edit" type="application/atom+xml" href="https://fcs.blog.uvm.edu/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=678" title="17. September 2009 -- Donnerstag" />
    <id>tag:fcs.blog.uvm.edu,2009://1.678</id>
    
    <published>2009-09-17T12:04:44Z</published>
    <updated>2009-09-17T13:38:16Z</updated>
    
    <summary>Admin</summary>
    <author>
        <name></name>
        
    </author>
            <category term="Activity Log" />
    
    <content type="html" xml:lang="en" xml:base="http://fcs.blog.uvm.edu/">
        <![CDATA[<h4>Admin</h4>
<dl>
<dt>LDAP</dt>
<dd><ul compact>
<li>Fix join failures from yesterday</li>
<li>Privacy flag requests</li>
<li>Fix join failures from today</li>
</ul></dd>
<dt>Backup</dt>
<dd><ul compact>
<li>EMC 31359116 -- savegrp core -- message back from the SME indicates that they got the core without the binary to examine.  That's strange because I packaged the core and the savegrp binary in the zip file that I uploaded.  I have verified that the file present on powerlink has the core and the binary inside it (downloaded and unpacked it here).  Still, they looked at something because the SME believes this is LGTsc32510 and LGTsc32658.  I have requested that my support tech provide me the descriptions of LGTsc32510 and LGTsc32658.</li>
</ul></dd>
</dl>
]]>
        
    </content>
</entry>
<entry>
    <title>8. September 2009 -- Dienstag</title>
    <link rel="alternate" type="text/html" href="http://fcs.blog.uvm.edu/2009/09/8_september_2009_dienstag.html" />
    <link rel="service.edit" type="application/atom+xml" href="https://fcs.blog.uvm.edu/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=677" title="8. September 2009 -- Dienstag" />
    <id>tag:fcs.blog.uvm.edu,2009://1.677</id>
    
    <published>2009-09-08T15:51:39Z</published>
    <updated>2009-09-08T16:58:51Z</updated>
    
    <summary>Admin</summary>
    <author>
        <name></name>
        
    </author>
            <category term="Activity Log" />
    
    <content type="html" xml:lang="en" xml:base="http://fcs.blog.uvm.edu/">
        <![CDATA[<h4>Admin</h4>
<dl>
<dt>Backup</dt>
<dd><ul compact>
<li>EMC 31192910 -- Continuing to work on the sev 1 issue -- Windows server 2008 DR doesn't work.</li>
<li>EMC 31051592 -- Reopen -- get LGTsc30901 facts -- created June 27th, hot fix available August 4th -- but EMC support people I dealt with didn't know of it, couldn't find it when I called in the issue on August 21 and it is still not listed in the powerstink knowledgebase</li>
</ul></dd>
<dt>LDAP</dt>
<dd><ul compact>
<li>Nightly update failures from Saturday dealt with</li>
</ul></dd>
</dl>]]>
        
    </content>
</entry>
<entry>
    <title>27. August 2009 -- Donnerstag</title>
    <link rel="alternate" type="text/html" href="http://fcs.blog.uvm.edu/2009/08/27_august_2009_donnerstag.html" />
    <link rel="service.edit" type="application/atom+xml" href="https://fcs.blog.uvm.edu/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=676" title="27. August 2009 -- Donnerstag" />
    <id>tag:fcs.blog.uvm.edu,2009://1.676</id>
    
    <published>2009-08-27T23:50:48Z</published>
    <updated>2009-08-27T23:58:39Z</updated>
    
    <summary>Admin</summary>
    <author>
        <name></name>
        
    </author>
            <category term="Activity Log" />
    
    <content type="html" xml:lang="en" xml:base="http://fcs.blog.uvm.edu/">
        <![CDATA[<h4>Admin</h4>
<dl>
<dt>Backup</dt>
<dd><ul compact>
<li>EMC 31051592: no nsrck's hung this morning.</li>
<li>EMC 31099632: no word from EMC -- have to refresh their memory tomorrow.</li>
<li>Scouting for word on whether 7.4sp5 is safe or not -- appears it is good</li>
<li>Tapes and Disks picked up by SecurShred for destruction.</li>
<li>Start to lay out design for scripted staging.</li>
<li>Investigations into why backups on reindeer are so much slower than they should be.</li>
<li>Replaced batteries in tape fire safes.</li>
</ul></dd>
<dt>LDAP</dt>
<dd><ul compact>
<li>Privacy flags</li>
<li>Thoughts about how to separate the SOR and WP information</li>
<li>Research how students find out their id number</li>
</ul></dd>
</dl>]]>
        
    </content>
</entry>
<entry>
    <title>26. August 2009 -- Mittwoch</title>
    <link rel="alternate" type="text/html" href="http://fcs.blog.uvm.edu/2009/08/26_august_2009_mittwoch.html" />
    <link rel="service.edit" type="application/atom+xml" href="https://fcs.blog.uvm.edu/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=675" title="26. August 2009 -- Mittwoch" />
    <id>tag:fcs.blog.uvm.edu,2009://1.675</id>
    
    <published>2009-08-26T23:47:27Z</published>
    <updated>2009-08-27T23:50:44Z</updated>
    
    <summary>Admin -- More EMC Bashing</summary>
    <author>
        <name></name>
        
    </author>
            <category term="Activity Log" />
    
    <content type="html" xml:lang="en" xml:base="http://fcs.blog.uvm.edu/">
        <![CDATA[<h4>Admin</h4>
<dl>
<dt>Backup</dt>
<dd><ul compact>
<li>EMC 31051592: Forced to level 1 to get call back, two hours on the phone with support, re-defined 42 clients that had been removed over the course of the last 15 years, nsrim -X now runs without causing nsrck to hang.  Acid test will be whether there is a hung nsrck or not tomorrow morning.</li>
<li>EMC 31099632: Support thinks it may be an SQL sp3 hotfix -- which COMIS is leary of because they are not seeing any indications that they are having this issue.  I agree.  Sent support searching for why the VSS backup is ignoring the directive to skip .mdf files.</li>
</ul></dd>
</dl>]]>
        
    </content>
</entry>
<entry>
    <title>25. August 2009 -- Dienstag</title>
    <link rel="alternate" type="text/html" href="http://fcs.blog.uvm.edu/2009/08/25_august_2009_dienstag.html" />
    <link rel="service.edit" type="application/atom+xml" href="https://fcs.blog.uvm.edu/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=674" title="25. August 2009 -- Dienstag" />
    <id>tag:fcs.blog.uvm.edu,2009://1.674</id>
    
    <published>2009-08-25T14:38:05Z</published>
    <updated>2009-08-25T14:43:08Z</updated>
    
    <summary>Admin (EMC Bashing)</summary>
    <author>
        <name></name>
        
    </author>
            <category term="Activity Log" />
    
    <content type="html" xml:lang="en" xml:base="http://fcs.blog.uvm.edu/">
        <![CDATA[<h4>Admin</h4>
<dl>
<dt>Backup</dt>
<dd><ul compact>
<li>Manually clean tape drive, EMC 23189374... still broken since 14. April 2008!</li>
<li>EMC 31051592: <ul compact>
    <li>kill off the nsrck that started and hung at midnight.</li>
    <li>Discover the "undef" volume problem is a side effect of this daily process not working.</li>
    <li>Continue manual nsrck -L6's against all clients in /nsr/index</li>
</ul></li>
<li>EMC 31099632 -- open, sev 2 -- med104 failing VSS SYSTEM SERVICES:\ backup due to SQL</li>
<li>Weekly cloning script finished.  So, once the nightly backups finally finish, I'll be able to recycle networker on the server to see if that clears up the issue with 31051592.</li>
</ul></dd>
</dl>]]>
        
    </content>
</entry>
<entry>
    <title>24. August 2009 -- Montag</title>
    <link rel="alternate" type="text/html" href="http://fcs.blog.uvm.edu/2009/08/24_august_2009_montag.html" />
    <link rel="service.edit" type="application/atom+xml" href="https://fcs.blog.uvm.edu/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=673" title="24. August 2009 -- Montag" />
    <id>tag:fcs.blog.uvm.edu,2009://1.673</id>
    
    <published>2009-08-24T14:14:49Z</published>
    <updated>2009-08-24T19:53:13Z</updated>
    
    <summary>Admin</summary>
    <author>
        <name></name>
        
    </author>
            <category term="Activity Log" />
    
    <content type="html" xml:lang="en" xml:base="http://fcs.blog.uvm.edu/">
        <![CDATA[<h4>Admin</h4>
<dl>
<dt>Backup</dt>
<dd><ul compact>
<li>EMC 31051592: worked for an hour on the phone with Wallace on Friday and ran commands on Sunday afternoon.  The "nsrck -m" ran without error.  However, the "nsrim -X" appears to have hung up trying to work on a client that was removed in March of 2008.  Will spend more time working with EMC this morning.  Much work on this issue today, no resolution.</li>
<li>Tape/Drive destruction assembly</li>
</ul></dd>
<dt>LDAP</dt>
<dd><ul compact>
<li>Alumni email-for-life additions</li>
</ul></dd>
</dl>
]]>
        
    </content>
</entry>
<entry>
    <title>21. August 2009 -- Freitag</title>
    <link rel="alternate" type="text/html" href="http://fcs.blog.uvm.edu/2009/08/21_august_2009_freitag.html" />
    <link rel="service.edit" type="application/atom+xml" href="https://fcs.blog.uvm.edu/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=672" title="21. August 2009 -- Freitag" />
    <id>tag:fcs.blog.uvm.edu,2009://1.672</id>
    
    <published>2009-08-21T15:10:05Z</published>
    <updated>2009-08-21T19:18:50Z</updated>
    
    <summary>Admin</summary>
    <author>
        <name></name>
        
    </author>
            <category term="Activity Log" />
    
    <content type="html" xml:lang="en" xml:base="http://fcs.blog.uvm.edu/">
        <![CDATA[<h4>Admin</h4>
<dl>
<dt>Backup</dt>
<dd><ul compact>
<li>31051592: Sev 2 -- nightly nsrim/nsrck pair starts up (nsrim forks and starts nsrck) but nsrck never finishes... one was running for 17 days.  Does not use any cpu time, just sits there.... EMC is trying to force me to upgrade to the brand new 7.4.5 release.</li>
<li>Volumes going "undef" instead of "expired" -- 5 more this morning, recycled them manually</li>
<li>Replace broken handle on fire safe.</li>
</ul></dd>
<dt>LDAP</dt>
<dd><ul compact>
<li>Privacy Flags</li>
</ul></dd>
</dl>]]>
        
    </content>
</entry>
<entry>
    <title>18. August 2009 -- Dienstag</title>
    <link rel="alternate" type="text/html" href="http://fcs.blog.uvm.edu/2009/08/18_august_2009_dienstag.html" />
    <link rel="service.edit" type="application/atom+xml" href="https://fcs.blog.uvm.edu/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=671" title="18. August 2009 -- Dienstag" />
    <id>tag:fcs.blog.uvm.edu,2009://1.671</id>
    
    <published>2009-08-18T16:04:46Z</published>
    <updated>2009-08-18T19:44:38Z</updated>
    
    <summary>Admin</summary>
    <author>
        <name></name>
        
    </author>
            <category term="Activity Log" />
    
    <content type="html" xml:lang="en" xml:base="http://fcs.blog.uvm.edu/">
        <![CDATA[<h4>Admin</h4>
<dl>
<dt>Backup</dt>
<dd><ul compact>
<li>EMC SR 30744500: Discovered man nsrck -MXv (long string of client names) running yesterday when I shutdown networker for monthly maintenance.  Could those (some running from as far back as August 1, be related to the ongoing corruption problems in daemon.raw?</li>
<li>Found more tapes that have volretent value of "undef" instead of "expired".  These appear to be tapes that had previously had the volretent set to the ssretent value instead of the clretent value.  At least I will assume that until I find one that was never on that list of tapes.  Opened issue for tracking in sharepoint -- issue #104</li>
<li>EMC SR 30964166: Working with Greg using norton1 as our guinea pig to verify that ASR recovery with AFTD's involved is bad news -- discovered that storage node ordering is critical to having it actually work.</li>
<li>Notify Cambridge that I would like info about the "dual power" option for the Qualstar XLS</li>
</ul></dd>
<dt>LDAP</dt>
<dd><ul compact>
<li>Privacy Flags</li>
<li>Alumni Email-For-Life updates</li>
<li>Double check that backup of data directory is working</li>
</ul></dd>
</dl>]]>
        
    </content>
</entry>
<entry>
    <title>17. August 2009 -- Montag</title>
    <link rel="alternate" type="text/html" href="http://fcs.blog.uvm.edu/2009/08/17_august_2009_montag.html" />
    <link rel="service.edit" type="application/atom+xml" href="https://fcs.blog.uvm.edu/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=670" title="17. August 2009 -- Montag" />
    <id>tag:fcs.blog.uvm.edu,2009://1.670</id>
    
    <published>2009-08-17T23:30:00Z</published>
    <updated>2009-08-18T16:04:21Z</updated>
    
    <summary>Admin -- Backup Maintenance</summary>
    <author>
        <name></name>
        
    </author>
            <category term="Activity Log" />
    
    <content type="html" xml:lang="en" xml:base="http://fcs.blog.uvm.edu/">
        <![CDATA[<h4>Admin</h4>
<dl>
<dt>Backup</dt>
<dd>Monthly Backup Maintenance
<ul compact>
<li>Qualstar XLS: Upgraded firmware from version 2 to version 3.  Process took 7 hours.</li>
<li>AFTD: fsck'd /disk1 on storage nodes 5, 7, and 8.</li>
<li>LTO4 drives: Upgraded firmware to 94D0 to address a code "A" issue with rewinds.</li>
<li>Rebooted all storage nodes and NSR Server.</li>
</ul></dd>
<dt>LDAP</dt>
<dd>Privacy flags</dd>
<dt>Accounts</dt>
<dd>Automated Purge Process test (dry) run.</dd>
</dl>]]>
        
    </content>
</entry>
<entry>
    <title>15. August 2009 -- Samstag</title>
    <link rel="alternate" type="text/html" href="http://fcs.blog.uvm.edu/2009/08/15_august_2009_samstag.html" />
    <link rel="service.edit" type="application/atom+xml" href="https://fcs.blog.uvm.edu/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=669" title="15. August 2009 -- Samstag" />
    <id>tag:fcs.blog.uvm.edu,2009://1.669</id>
    
    <published>2009-08-15T12:10:38Z</published>
    <updated>2009-08-15T13:13:44Z</updated>
    
    <summary>Admin</summary>
    <author>
        <name></name>
        
    </author>
            <category term="Activity Log" />
    
    <content type="html" xml:lang="en" xml:base="http://fcs.blog.uvm.edu/">
        <![CDATA[<h4>Admin</h4>
<dl>
<dt>Calendar</dt>
<dd>OS Maintenance applied and Calendar database maintenance run</dd>
<dt>Backup</dt>
<dd><ul compact>
<li>rebooted gnu - read-only file system error -- more fallout from the Day of Disaster!</li>
<li>Changed nsrports range on rh4-build.  Discovered the real problem in NW7.5 is that some piece of nsrexecd is hard coded to open port 7937 -- so if 7937 is in the range of ports nsrexecd is allowed to use some other piece of nsrexecd is 60% likely to get it before the piece that was written incorrectly. -- Amazing!!!  Tell the client code it can not use port 7937 and it still does use it.... and this pile of sh*t passed quality assurance testing!  wow!!!</li>
<li>Restart of 'UVM Fullsave 2' for above two issues</li>
</ul>
</dl>]]>
        
    </content>
</entry>
<entry>
    <title>14. August 2009 -- Freitag</title>
    <link rel="alternate" type="text/html" href="http://fcs.blog.uvm.edu/2009/08/14_august_2009_freitag.html" />
    <link rel="service.edit" type="application/atom+xml" href="https://fcs.blog.uvm.edu/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=668" title="14. August 2009 -- Freitag" />
    <id>tag:fcs.blog.uvm.edu,2009://1.668</id>
    
    <published>2009-08-14T20:00:00Z</published>
    <updated>2009-08-15T12:10:29Z</updated>
    
    <summary>Admin -- Disaster Day</summary>
    <author>
        <name></name>
        
    </author>
            <category term="Activity Log" />
    
    <content type="html" xml:lang="en" xml:base="http://fcs.blog.uvm.edu/">
        <![CDATA[<h4>Admin</h4>
<dl>
<dt>Disaster Day</dt>
<dd>The postmortem remains to be done and will require the assistance of IBM and EMC (VMWare), but we've had a fun day of it.  It started on Thursday (while I was out) when working with IBM about an issue that had caused the replication connection between two SAN systems to break.  IBM determined that there was an Efix specifically for this condition.  It was tested on the target SAN with a VMWare cluster connected to it without incident during the day.  Therefore, somewhere between 9 and 10 PM Thursday evening, the first part of the Efix was applied to the source SAN.  Well, the production VMWare cluster got really pissed and several guest systems lost access to their disks.  I am not sure, but I suspect that all guests saw some interruption to their activities.  Not only did these systems lose their disks, but VMWare appeared to have lost access to the files that represented their disks.  I'm not sure of what things were tried in the next 3.5 hours, but I was paged at 1:30 am Friday morning to deal with recovering our primary LDAP server from backups (essentially to perform a bare metal restoration).  We spent a couple of hours during which time we discovered that our support contract with EMC/VMWare had expired -- guarantees from the sales people that we'd be sent an automatic renewal notice to the contrary, we had no support contract.  It took time to convince the support structure that we were not bums and would be contacting sales to negotiate a renewal and finally VMWare was working to help resolve the issue.  

<p>At about 2:30 I started the bare metal recovery of the LDAP server (create a new VMWare guest and recover all the files from the NetWorker backup system) and I was amazed that it had completed in less than two hours.  It wasn't perfect, because the backup had been done before the previous day's batch update and it was missing some information that was needed.  I retrieved the LDAP database from one of the replica servers and got the LDAP server back up and running.  I didn't realize that I was missing the previous day's batch run data until after I'd manually kicked off the days batch run, which had lots of errors because it was comparing today's authoritative feed data to that from two days ago instead of just yesterdays.  To correct this, I've updated the nightly batch script so it issues a NetWorker save of the batch update data directory when the nightly batch process is complete.  So, as long as the batch process runs to completion, the backup system will have the information.</p>

<p>VMWare did come through eventually, with not one but two filesystem dd patches to correct the corruption and the files that were unavailable were all eventually able to be seen and their guests could be started again.  Which was good.</p>

<p>Sadly, the incident was not free of problems.  We discovered that the ASR recovery process on the Windows 2003 printer server tripped over a bug in NetWorker.  An issue is open with NetWorker about that -- it was opened as a Sev 1, but has been lowered because VMWare was able to get the VMFS corruption fixed and we were able to get the printers server running again before the 1 hour call back time on the Sev 1 had expired.  We will built a test Windows system that we will do an ASR recovery on and work through this problem with EMC/NetWorker.  In short, the problem is that in our environment we send Full saves to one set of disk and incrementals to another set of disk.  Those different sets of disk are mounted on different backup servers (storage nodes).  NetWorker's ASR recovery process is reading the information from the full save and then demanding that the incremental disk be removed from the storage node it is attached to and moved to the same storage node the full save disk is attached to.  That's just not physically possible with direct attached disk.</p>

<p>The final notice that all was recovered was sent out by Geoff at 3:50pm Friday afternoon.<br />
</dd></dl></p>]]>
        
    </content>
</entry>
<entry>
    <title>27. Juli 2009 -- Montag</title>
    <link rel="alternate" type="text/html" href="http://fcs.blog.uvm.edu/2009/07/27_juli_2009_montag.html" />
    <link rel="service.edit" type="application/atom+xml" href="https://fcs.blog.uvm.edu/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=667" title="27. Juli 2009 -- Montag" />
    <id>tag:fcs.blog.uvm.edu,2009://1.667</id>
    
    <published>2009-07-27T14:46:24Z</published>
    <updated>2009-07-27T14:47:39Z</updated>
    
    <summary>Admin</summary>
    <author>
        <name></name>
        
    </author>
            <category term="Activity Log" />
    
    <content type="html" xml:lang="en" xml:base="http://fcs.blog.uvm.edu/">
        <![CDATA[<h4>Admin</h4>
<dl>
<dt>LDAP:</dt>
<dd><ul compact>
<li>Update delEntry routine to remember the PeopleSoft emplid value</li>
</ul></dd>
</dl>]]>
        
    </content>
</entry>
<entry>
    <title>20. Juli 2009 -- Montag</title>
    <link rel="alternate" type="text/html" href="http://fcs.blog.uvm.edu/2009/07/20_juli_2009_montag.html" />
    <link rel="service.edit" type="application/atom+xml" href="https://fcs.blog.uvm.edu/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=666" title="20. Juli 2009 -- Montag" />
    <id>tag:fcs.blog.uvm.edu,2009://1.666</id>
    
    <published>2009-07-20T15:14:39Z</published>
    <updated>2009-07-20T20:49:07Z</updated>
    
    <summary>Admin -- backup maintenance</summary>
    <author>
        <name></name>
        
    </author>
            <category term="Activity Log" />
    
    <content type="html" xml:lang="en" xml:base="http://fcs.blog.uvm.edu/">
        <![CDATA[<h4>Admin</h4>
<dl>
<dt>Backup:</dt>
<dd><ul compact>
<li>Monthly maintenance day:
<ol compact>
<li>Qualstar XLS832700 firmware update -- FAILED
<ul compact>
<li>X-Y board is original and needs to be replaced to be certain it will work with the new firmware.  Qualstar is researching replacement options (maintenance agreement coverage)</li>
</ul>
<li>NetWorker updated to 7.4.4.6 to fix several open issues</li>
<li>OS Maintenance applied to server and dedicated storage nodes</li>
<li>DD460's replaced with DD690</li>
</ol></li>
<li>Several 09xxxxL4 tapes returned to the scratch pool.</li>
<li>Replaced worn out LTO cleaning tape with a new one.</li>
</ul></dd>
</dl>
]]>
        
    </content>
</entry>

</feed> 

