Project

General

Profile

Task #9098

Gather task list of Enstore tasks done by CMS

Added by Gerard Bernabeu Altayo over 4 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
Normal
Start date:
06/10/2015
Due date:
06/12/2015
% Done:

100%

Estimated time:
2.00 h
Spent time:
Duration: 3

Description

I would like to gather and document in this ticket a list of Enstore tasks done by CMS.

I believe this revolves around migration and squeezing tasks. Chih-Hao also helps with cloning issues with CMS tapes. I am not aware of any other task.

It will be helpful to have details of current responsibilities and plans, issues if any, and estimates of the effort required.

This is precursor of task 8917.


Related issues

Precedes (1 day) Tape Operation - Task #8917: Upgrade cmssrv147 and cmssrv148 to SL6Closed06/15/201506/15/2015

History

#1 Updated by Gerard Bernabeu Altayo over 4 years ago

  • Precedes Task #8917: Upgrade cmssrv147 and cmssrv148 to SL6 added

#2 Updated by Chih-Hao Huang over 4 years ago

  • % Done changed from 0 to 50

This is from my goal:

Enstore Support:
[1] Continue to be the department’s liaison to the Enstore development team.
[2] Work with the Enstore team to mitigate, reduce and recover in situations having media errors.
[3] Test and evaluate software new releases of Enstore.
[4] Provide plots and statistics on accessible web pages as requested by management.
[5] Handle requests for file family additions.
[6] Lead the CMS media management efforts using standard Enstore migration methods:
(a) Continue squeezing of current underused volumes to reclaim tapes that have mostly deleted files
(b) Deal with error handling and recovery

Effort: 5%

#3 Updated by Chih-Hao Huang over 4 years ago

  • % Done changed from 50 to 80
Enstore Support:
[1] Continue to be the department’s liaison to the Enstore development team.
    -- on enstore-admin@fnal.gov mailing list, know what's happening there
    -- occasionally (rarely), helped out for Enstore problems
       -- this only happened a handful times when Enstore developers went into wrong directions
       -- doing this for mutual benefit (and good relationship)
[2] Work with the Enstore team to mitigate, reduce and recover in situations having media errors.
    -- on going task
[3] Test and evaluate software new releases of Enstore.
    -- on demand -- for major releases and necessary patches
[4] Provide plots and statistics on accessible web pages as requested by management.
    -- on going and on demand
[5] Handle requests for file family additions.
    -- the task is delegated to Dave M.
    -- only monitoring role in this for now -- spot the mistakes and help to correct them
[6] Lead the CMS media management efforts using standard Enstore migration methods:
    (a) Continue squeezing of current underused volumes to reclaim tapes that have mostly deleted files
        -- this involves
           (i)   selecting volumes to squeeze
                 -- this is the bulk part of the work
                 -- there are some decisions to make -- does depend on the knowledge of data and requirement
           (ii)  schedule and watch squeezing
                 -- this is actually the least effort part since we have facilities in place
                    -- those facilities, though still working as-is, need to be upgraded to SL6
                       -- up to today, Enstore is still running on SL5, but it doesn't really matter
                 -- monitoring/reporting of the squeezing is in place
           (iii) scanning destination tapes and make sure every file is readable as a user
                 -- part of migration/squeezing process
                 -- similar to (ii), just schedule and watch
           (iv)  file ticket for SSA to recycle the source tapes
                 -- this means permanent destroy of data
                 -- this has to be singed off by data owner (CMS)
    (b) Deal with error handling and recovery
        -- this is another bulk part of the task
        -- things happen
        -- require knowledge in enstore, migration, dcache, data and history
           -- one new historical event was the tape and disk separation happened in 2014

This should account for 5% of my total effort.

#4 Updated by Chih-Hao Huang about 4 years ago

  • Status changed from New to Resolved
  • % Done changed from 80 to 100

This is no longer of interest.



Also available in: Atom PDF