Acopia Networks 810-0044-00 Manual de instalación Pagina 376

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 492
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 375
Policy for Balancing Capacity
Draining One or More Shares
12-42 CLI Storage-Management Guide
Disabling Reports
From gbl-ns-vol-plc mode, use no report to prevent the rule from generating a report:
no report
This has no effect after the first (and only) run of the placement rule.
For example, the following command sequence disables reporting for the rule,
“mvTars:”
bstnA6k(gbl)# namespace archives
bstnA6k(gbl-ns[archives])# volume /home
bstnA6k(gbl-ns-vol[archives~/home])# place-rule mvTars
bstnA6k(gbl-ns-vol-plc[archives~/home~mvTars])# no report
bstnA6k(gbl-ns-vol-plc[archives~/home~mvTars])# ...
Retaining Copies of Files on the Share (optional)
Before you enable the rule and start migrating files off of the share, you have the
option to retain copies of those files. From gbl-ns-vol-shr mode, use the
migrate
retain-files
command to put this safeguard in place:
migrate retain-files
The file copies go to a hidden directory, “~acopia_msnap,” at the root of the share. To
restore the files later, you can access the back-end share directly (it is not included in
the volume).
For example, the following command sequence retains all migrated files in the it5
share:
Do not use this command for a share in a share farm. If a share-farm-balancing policy
tries to move files off of this share, this placement rule makes copies of them, thereby
ensuring that the share’s free space never actually changes. The balancing policy will
therefore move files off of the share indefinitely, unnecessarily occupying space on other
shares.
Use this only as a safeguard when draining all files from a share.
Vista de pagina 375
1 2 ... 371 372 373 374 375 376 377 378 379 380 381 ... 491 492

Comentarios a estos manuales

Sin comentarios