ViPR 2.2 - Ingest Unmanaged File Systems into ViPR
Table of Contents
Once under ViPR management, the ingested storage resources can be managed by provisioning users in the same way as if they had been created using ViPR, allowing them to be exported to hosts, expanded, protected using snapshot and copy techniques, etc.
Any file system that is brought under ViPR management must be assigned to a file virtual pool. So, before you can ingest volumes, you must ensure that a virtual pool exists whose criteria match those of the file systems to be ingested.
The discovery process finds file systems on a specified array and matches them with file virtual pools. When you use the ingest service, only file systems that were previously discovered to belong to a specified file virtual pool are ingested.Back to Top
- Discover all unmanaged file systems on an array.
- Ingest discovered block volumes.
Before you begin
This operation requires the System Administrator role in ViPR.
The virtual array and virtual pool into which you want to ingest the storage pools must exist when the discovery is performed.
The discovery process finds storage pools on a selected storage system and identifies the virtual array and virtual pool that discovered each file system matches with.
File systems will only be discovered on file storage system that have been added to ViPR as physical assets.
- Select the physical file storage systems from which you want to discover unmanaged file systems. You can select more than one file storage system.
The orders page is displayed and shows the progress of the request. If the order is successfully fulfilled, you can use the Ingest Unmanaged File Systems to bring them under management by ViPR.
Before you begin
- Only System Administrators can ingest unmanaged file systems.
To be ingested, the unmanged file systems must be in physical pools which are already associated with a ViPR virtual storage pool.
- The Discover Unmanaged File Systems service must have been run on the file storage system.
- Rerun the Discover Unmanaged File Systems service if the virtual array or virtual pools have been modified since the last time the Discover Unmanaged File Systems service was run.
- Ingested file systems will be assigned to a project. You must belong to the selected project and have write-permission on the project.
- To ingest an
Isilon unmanaged file systems:
- The virtual pool must have been configured with the Provisioning Type set to Thin. Isilon file systems are thinly provisioned. Thin resources can only be created in "thin" vpools.
- The Isilon file system exports must be in either /ifs/sos or /ifs/vipr. File systems exported to other locations will not be ingested by ViPR.
- Select the storage system from which you want to ingest file systems.
- Select the virtual array whose virtual pools contain the storage system physical pools that host the file systems you want to import. The storage system might contribute physical storage pools to a number of virtual pools. If you want to ingest to all virtual pools, you will need to run the service again for the other virtual pools.
It is possible that not all of the storage system physical pools are included in the virtual array that forms part of your virtual data center. For that reason, you don't want to ingest all unmanged file systems on the storage system, just those in physical storage pools that meet the criteria of your virtual pools.
- Select the virtual pool that the unmanaged volumes are in.
- Select the project that you want the unmanaged file systems to be assigned to.
The orders page is displayed showing the progress of the request. If the order is successfully fulfilled, you can look at thepage to see the imported file systems.