text: <html>
          <head> <meta charset="UTF-8">
          <style>
          table, th, td {
              border: 1px solid black;
              font-size: 10px;
          }
          </style> </head>
          <body>
          <table frame="hsides" rules="groups" width="100%%">
              [html]<thead><tr><tdcolspan="2">In the Migration Policy Slorage Level Lethniton window (+ gure >- Z2 on page 124 ), you provide the following information for the new policy storage level :</td></tr></thead><tbody><tr><td>•</td><td>Level identifier : This field distinguishes the different storage levels within the migration policy. The value must be unique within the storage levels of the migration policy. ASM uses the level identifier to delermme the current leve</td></tr><tr><td>•</td><td>Disabled : Specifying this option causes ASM to skip this level in the storage hierarchy. The Disabled option can be used in a situation where an optical unit is added to the system later, but the administrator wants to add an optical policy l</td></tr><tr><td>This option can also be used when migration to a policy level is discontinued, such as a tape unit. A policy level cannot be removed if data is archived to it, but it can be disabled so that no more data is migrated to that level.</td><td>•</td></tr><tr><td>Description of the policy level : Use this field to provide a description of the policy level.</td><td>•</td></tr><tr><td>Primary medial system. The lysten from which you can choose are copital, tape, disk, or expire. If you select expire as the last policy tever, when data neaches this level in the migraphise experce. It is removed from the acclive suverem eve</td><td>•</td></tr><tr><td>Duration at this level : In this field, you specify either no maximum or a specified number of days before ASM moves the data to the next level in the migration sequence.</td><td>•</td></tr><tr><td>Primary storage group : Select the storage group that you want to use to store the data at this level.</td><td>•</td></tr><tr><td>Create backup copy and backup storage group : You select these options if you want AEM to create a backup copy of the data when it moves to this policy level. The backup storage group must be created with a media type of backup.</td><td>•</td></tr><tr><td>Stage to disk when data is retrieved from tape and the duration on disk in days : Choose these options to cache data that is returned from tape to disk for the number of days that are specified.</td><td>In nursescenario, we created as policy evaluated that stomes data for 100 days on disk by using the disk poor stronger group that is assigned to auxiliary stronger point. The also created a policy event that stome based on spotsal stronge ma</td></tr><tr><tdcolspan="2">Figure 5 - 23 on page 126 shows the final migration policy structure.</td></tr><tr><tdcolspan="2"</tr></tbody>
          </table> </body> </html>