Take the list of what talks to your array from the array and the switch, not the diagram

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 Every server, from the array

   Your answer, and where it is written down (with the date) The servers (hosts) the array gives storage to, taken from the array's own host list, not the diagram.

   Your answer

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

   How to raise it

   Where to find it:

   The array's management screen: the list of hosts or host mappings. Copy it as it stands today.

   To get it to a 2:

   A list pulled from the array itself, with the date you pulled it.

   What this does not prove:

   A host on the list does not prove it is still in use. Ask its owner before anything is removed.

2. 2 Every switch in the path

   Your answer, and where it is written down (with the date) Each switch between the servers and the array (the network that links servers to storage), with the firmware (the switch's built-in software) it runs.

   Your answer

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

   How to raise it

   Where to find it:

   Each switch's own list of connected devices and its version screen. The array's ports show which switch ports it uses.

   To get it to a 2:

   Every switch in the path on the list, with its firmware read from the switch itself and a date.

3. 3 The backup system, with its version

   Your answer, and where it is written down (with the date) What reads from the array to make backups or copies, and the version it runs today.

   Your answer

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

   How to raise it

   Where to find it:

   The backup console's about or version screen, and the job list that names the array.

   To get it to a 2:

   The product and exact version written down, read from the console, with a date.

   What this does not prove:

   A backup console lists what it was set up to read. It does not show a copy someone made by hand.

4. 4 Everything else

   Your answer, and where it is written down (with the date) Tape, a copy kept on a second array, scripts, and any server that touches the array only at month end or year end.

   Your answer

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

   How to raise it

   Where to find it:

   Change records, the job scheduler, and the people who run month-end and year-end work. Ask them directly.

   To get it to a 2:

   A dated line for each item, or "none, checked on a date".

   What this does not prove:

   A quiet month does not prove there is no year-end job. Ask the people who run it.

5. 5 Dated, and matched to the diagram

   Your answer, and where it is written down (with the date) The date at the top of the list, and every device that is on the diagram but not on the array's lists, or the other way round, named.

   Your answer

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

   How to raise it

   Where to find it:

   Put the diagram next to the lists from rows 1 to 4 and mark each difference. The date is the day you pulled the lists.

   To get it to a 2:

   A date at the top, and every difference between the diagram and the lists explained in a line.

   What this does not prove:

   A list that matches the diagram does not prove both are complete. Both can miss the same device.