Ensure you are familiar with the terminology differences between the Oracle VM and the Oracle FS System interfaces
| Oracle VM terms | Oracle FS System terms | Notes |
|---|---|---|
| Access group | SAN hosts |   |
| Clone | Active Clone LUN | These are read and write clones that can be mapped to SAN hosts (access groups). These clones remain active throughout their lives. |
| Physical disk | LUN |   |
| Present and unpresent | Map and unmap | |
| Snap clone* | Active Clone LUN of an inactive Clone LUN (Snapshot) | Snap clones are always created from inactive clones. They are read and writable versions of the inactive clone (snapshot). As such, they look like normal clones. |
| Snapshot* | Inactive Clone LUN whose name is prefixed with OSCSNAP- | Making the clone inactive makes the clone read-only. These clones remain inactive throughout their lives. The plug-in automatically prefixes the name with OSCSNAP- to identify the clone physical disk as an Oracle Storage Connect snapshot. The prefix is not visible in the Oracle VM GUI because the Oracle VM Storage Connect Plug-In for Oracle Flash Storage Systems removes the prefix before returning the name to Oracle VM. |
| Split clone | None | Oracle FS System clones cannot be separated from their parent and still retain the same ID. Split clones are not supported. |
| Storage array | Oracle FS System SAN systems | Oracle VM Manager version 3.1 and later refers to storage arrays as SAN servers. |
| Storage element | Storage objects such as LUN, Clone LUN, or filesystems |   |