User's Manual
l The virtual disk name can contain only alphanumeric characters as well as spaces, dashes and underscores. The maximum name length depends on the
controller. In most cases, the maximum length is 15 characters. The name cannot start with a space, end with a space, or be left blank.
To rename a virtual disk:
1. Type the new name in the text box.
2. Click Rename. If you want to exit without renaming the virtual disk, click Go Back To Virtual Disk Page.
To locate this task in Storage Management:
1. Expand the Storage tree object to display the controller objects.
2. Expand a controller object.
3. Select the Virtual Disks object.
4. Select Rename from the Available Tasks drop-down menu.
5. Click Execute.
Virtual Disk Task: Change Policy
Does my controller support this feature? See "Supported Features."
Use the Change Policy task to change a virtual disk's read, write, or cache policy. See "RAID Controller Read, Write, Cache, and Disk Cache Policy" for more
information.
To change a virtual disk's read, write, or disk cache policy:
1. Select the new policy from the Read Policy, Write Policy, and Disk Cache Policy drop-down menus.
2. Click Apply Changes. If you want to exit without changing the virtual disk policy, click Go Back To Virtual Disk Page.
To locate this task in Storage Management:
1. Expand the Storage tree object to display the controller objects.
2. Expand a controller object.
3. Select the Virtual Disks object.
4. Select Change Policy from the Available Tasks drop-down menu.
5. Click Execute.
Split Mirror
Does my controller support this feature? See "Supported Features."
Use the Split Mirror task to separate mirrored data originally configured as a RAID 1, RAID 1-concatenated, or RAID 10 virtual disk. Splitting a RAID 1 or RAID 1-
concatenated mirror creates two concatenated nonredundant virtual disks. Splitting a RAID 10 mirror creates two RAID 0 (striped) nonredundant virtual disks.
Data is not lost during this operation.
NOTE: The Rename task is not available for concatenated virtual disks on a CERC SATA1.5/2s controller.
NOTE: In cluster mode, the PERC 3/DC controller only allows write-through caching.