• A-Z
  • Directory
  • myUVM
  • Loading search...

Frank's Activity Log

19. Juli 2018: Donnerstag

Posted: July 20th, 2018 by fcs

Today’s Activities:

  • Backups:
    • YAY – no unexpected failures last night!
    • Added 40 tapes to the Scratch pool.
  • LDAP/Accounts:
    • No updates require human intervention.
    • Prototyping password scrambling.
    • One more (last?) tweak to the AD update notifications.
  • FootPrints 12:
    • No response from BMC, sigh.
    • Should I figure this out myself, or wait for them???
  • General: Suggest two ways to match IPv6 VPN addresses in firewalls.

18. Juli 2018: Mitwoch

Posted: July 19th, 2018 by fcs

Today’s Activities:

  • Backups:
    • Confirmed and updated daily jbod check on bujbod2
      to deal with yesterday’s disk replacement.
    • that client change from Monday is still not correct.
      Doh! I missed the need to update ozzie’s firewall.
      Fixed it now.
    • Tape Vaulting: 40 & 40.
    • Team turns off several RHEL5 systems – disable enmasse.
    • TAPE clones completed at 18:34 (5,082 GB).
    • DISK clones completed at 22:11 (14,622 GB).
  • LDAP/Accounts:
    • No updates require human intervention.
    • More tweaking of the notifications about AD updates.
    • VPN adjustment per request.
    • Preliminary discussions of compromised/misused accounts.
  • FootPrints (000544924):
    • LOG requests, and config requests and I’m dealing
      with a shotgun of interesting questions that are
      seemingly not relevant.

17. Juli 2018: Dienstag

Posted: July 18th, 2018 by fcs

Today’s Activities:

  • Backups:
    • bujbod2: /c0/e8/s1 (ST4000NM0023/Z1Z34RGT) SMART failure:
      Installed ST4000NM0125/ZC147K30.
      CopyBack initiated at 06:27.
      CopyBack complete at 21:16.
    • Clones started for this week.
    • COMIS clones completed at 07:14 (17 GB).
    • client was changed yesterday differently than I was told.
      Necessary changes made to definitions.
  • LDAP/Accounts:
    • No updates require human intervention.
    • Tweak AD update process to be slightly more tolerant.
  • Footprints:
    • With the changes made subsequent to being informed of
      KB Article 000148291 (installing on RHEL7),
      the install claims to have worked, but it won’t run.
    • Hello, BMC…

16. Juli 2018: Montag

Posted: July 17th, 2018 by fcs

Today’s Activities:

  • Backups:
    • bujbod2: /c0/e8/s1 (ST4000NM0023/Z1Z34RGT) SMART failure:
      Initiated replacement.
      Rebuild onto Hotspare completed at 16:48.
    • Reclaimed two tapes for the vaults.
  • LDAP/Accounts:
    • No updates require human intervention.
    • VPN change per request.
    • More work on the CLICK feed to support UUID.
    • input from AD for AD update was late,
      manually ran the update after alumnus work completed.
  • Footprints:
    • Configuration change made to fix escalation issue described in
      https://communities.bmc.com/docs/DOC-69784
    • 00544924 – another round of 20 questions.

13. Juli 2018: Freitag

Posted: July 16th, 2018 by fcs

Today’s Activities:

  • Backups:
    • Qualstar RMA #51053
      • installed new drive.
      • SN 1310209179 replaces 1310215928 in H1 (*71*).
      • SN2 does not see the new drive.
      • SN2 had to be rebooted to see the new drive.
    • Added forty tapes to the Scratch pool.
    • Updated backup system’s wiki page.
  • LDAP/Accounts:
    • Four updates require human intervention. Found, fixed.
    • Push back on IAM – their discovered duplicate is
      really a duplication from PeopleSoft – have to fix
      it in PS not in LDAP.
    • New retiree feed file from HR.
    • Meeting about CLICK feed changes.

11. Juli 2018: Mittwoch

Posted: July 13th, 2018 by fcs

Today’s Activities:

  • Backups:
    • Qualstar – Converted to Qualstar WWN setting.
      • Had to reboot almost all of the drives
      • One of them, of course, failed to reboot
      • It is actually failing to power on.
        Drive 1310215928 reported to Qualstar.
      • The drives on stornode10 which had appeared
        to reconnect, needed to be rebooted too.
      • Qualstar confirmed bad drive, issued
        RMA #51053 to replace 1310215928.
    • Client powered off yesterday, disable it today.
  • LDAP/Accounts:
    • preferred name set per request.
    • One update requires human intervention – found, fixed.
  • General:
    • IPv6 VPN firewall rules.

10. Juli 2018: Dienstag

Posted: July 13th, 2018 by fcs

Today’s Activities:

  • Backups:
    • Qualstar RMA #51046:
      Replaced SN2 *b9ded 1310286258 with *34b38 1310119697
      Oops.. *34b38 has been here before.
      Have to destroy the library and create a new one.
    • ABORT issued for DISK, FSGen3 and TAPE clones.
    • Tape Vaulting: 40 & 40.
    • DISK clones aborted at 08:34.
    • FSGen3 clones aborted at 13:26.
    • TAPE clones aborted at 15:57.
  • LDAP/Accounts:
    • No updates require human intervention.
    • Updating LDAP entries per requests.

9. Juli 2018: Montag

Posted: July 10th, 2018 by fcs

Today’s Activities:

  • Backups:
    • Multiple full saves from the weekend continue to slog along.
    • Reclaimed one tape for the vaults.
    • SN2’s *b9ded (ST1) drive – RMA #51046 – drive arrives.
    • COMIS clones completed at 12:47 (420 GB).
  • LDAP/Accounts:
    • No updates require human intervention.
    • One piece of fallout from Friday’s double update.
      The account in question wound up LOCKED for purging.
      Corrected that error this morning.
    • VPN Group change per request.
  • Footprints:
    • Discovered that although the IBM JAVA was installed, the
      system was still using the OpenJDK version – and it does
      not work (at least it can’t run JAVA code…).
      Used the alternatives selector to move the the IBM JAVA
      version, and java is working now. Perhaps that will make
      things work better with the installation?
    • Their install script still blows up with being unable to
      find the class javax/servlet/Filter.
    • Install process is failing to pull .jar files from
      /usr/share/tomcat/lib (/usr/share/tomcat is the tomcat_home)
      at the critical point – it uses that path earlier in the
      process.
    • Updated case 00544924 notes – requested BMC call.
    • Same BMC support tech that I told I wanted the issue escalated
      last week called today.
      I do not seem to be able to communicate the problem to them.
    • Emailed the support manager, requesting the case be re-assigned
      to someone else.

6. Juli 2018: Freitag

Posted: July 9th, 2018 by fcs

Today’s Activities:

  • Backups:
    • The usual clients continue to fail.
    • SN2’s *b9ded (ST1) drive marks five (5) tapes as unlabeled.
      • nsrjb -I process fixed the five (5) tapes.
      • itdt dump… passes — would it do anything else?
      • itdt test… passes too. Erhm!
      • dump sent to Qualstar for analysis.
      • RMA #51046 issued to replace the drive.
    • DISK clones completed at 15:41 (36,692 GB).
  • LDAP/Accounts:
    • One update required human intervention, found, fixed.
    • Tweak cleanup routines.
  • Footprints:
    • Request sample PostgreSQL JDBC test routine on issue 544924.
      • No test program exists – so typical!
      • Escalated issue — no further update from BMC.
    • More research on alternatives.
  • CFEngine – work on semodule -l issues. This is much like
    beating one’s head against a brick wall.

5. Juli 2018: Donnerstag

Posted: July 6th, 2018 by fcs

Today’s Activities:

  • Backups:
    • FSGen3 clone completed at 03:38 (24,003 GB).
    • COMIS MED9300 groups continue to fail – contact again.
    • Added 40 tapes to the Scratch pool.
    • Tape Vaulting: 40 & 40.
  • LDAP/Accounts:
    • No updates require human intervention.
    • CLICK feed, allow completely duplicate SALARY records.
  • Footprints:
    • Modified daily backup script to reduce error count.
    • Pushing BMC to call me today about issue 544924.
    • Instead of calling, BMC now says that postgres is the problem.
    • BMC Support Manager called (about the other issue)…
      will look at 544924 and have someone call me.
Contact Us ©2010 The University of Vermont – Burlington, VT 05405 – (802) 656-3131
Skip to toolbar