The days it takes to copy everything off your old array are on no screen

Yes 2

Written down, with a date (a log, a screen, a document), and it meets your own plan.

Partly 1

Remembered, but not written down, or the record shows you missed your plan.

No 0

Nobody knows, or it was never done. A blank is a finding.

"None, checked on a date" counts as a record. No plan or target written down? Write your guess first, then measure: the guess is your plan.

Tap No, Partly or Yes for each question. Your score adds up as you go. Nothing you tap is saved or sent.

Five questions about your own setup

1. 1 Days to copy off

   Your answer, and where it is written down (with the date) How many days would copying everything off the old array take? Write used space (TB) ___ divided by copy speed (TB per hour) ___ = hours ___, divided by 24 = days ___.

   Your answer

   No 0Partly 1Yes 2
   Score 0, 1 or 2This quarterNext quarter

   How to raise it

   Where to find it:

   Rows 2 and 3 give the two figures. Divide used space by copy speed to get hours, then divide the hours by 24. Write the days next to the date in row 4.

   To get it to a 2:

   The days are written down from rows 2 and 3, dated, and sit next to the support end date.

   What this does not prove:

   The answer counts copying alone, at full speed. It is the least the move will take, not the length of the project.

2. 2 Used space on the old array

   Your answer, and where it is written down (with the date) How much data does the old array hold today? Write the terabytes (TB) used, not the total size, and the date you read it.

   Your answer

   No 0Partly 1Yes 2
   Score 0, 1 or 2This quarterNext quarter

   How to raise it

   Where to find it:

   The capacity screen on the old array. It usually shows used space per pool (a group of disks managed together). Add the pools up.

   To get it to a 2:

   A dated reading of used space, added up across every pool.

   What this does not prove:

   Used space grows. A reading from last year does not show what the array holds today.

3. 3 A copy speed you have timed

   Your answer, and where it is written down (with the date) How fast did the last large copy you ran go? Write the terabytes moved divided by the hours it took, in TB per hour.

   Your answer

   No 0Partly 1Yes 2
   Score 0, 1 or 2This quarterNext quarter

   How to raise it

   Where to find it:

   The job log of one large copy you already run, such as a volume move or a restore. It shows how much moved and how long it took. Do not use a number from a spec sheet.

   To get it to a 2:

   A dated job log entry for a large copy, with the speed worked out from it.

   What this does not prove:

   The speed you timed is not the speed of the real move. The new array, the network and whatever else is running change it.

4. 4 The support end date

   Your answer, and where it is written down (with the date) On what date does the maker stop supporting the old array? Write it here, and the days from row 1 beside it.

   Your answer

   No 0Partly 1Yes 2
   Score 0, 1 or 2This quarterNext quarter

   How to raise it

   Where to find it:

   Your support contract, or the maker's own page for that model, or your partner. Write where you found it.

   To get it to a 2:

   A date taken from the contract or the maker's page, written next to the days of copying.

5. 5 The day the move must start

   Your answer, and where it is written down (with the date) Is a start date for the move on the calendar, at least the days in row 1 before the support end date, and who owns it?

   Your answer

   No 0Partly 1Yes 2
   Score 0, 1 or 2This quarterNext quarter

   How to raise it

   Where to find it:

   Your team calendar or change schedule. Count back from the support end date by the days in row 1, and more for everything the division leaves out.

   To get it to a 2:

   A start date on the calendar at least the days in row 1 before support ends, with a named person. A date that leaves fewer days than row 1 scores 1.