the snapshot (legacy) virtual disk and the snapshot (legacy) repository virtual disk. For example, if youhave a base virtual disk with a name of Engineering Data, the snapshot (legacy) virtual disk can have aname of Engineering Data-S1, and the snapshot (legacy) repository virtual disk can have a name ofEngineeringData- R1.If you do not choose a name for either the snapshot (legacy) virtual disk or the snapshot (legacy)repository virtual disk, the MD storage management software creates a default name by using the basevirtual disk name. An example of the snapshot (legacy) virtual disk name that the RAID controller modulesmight create is, if the base virtual disk name is aaa and does not have a snapshot (legacy) virtual disk, thedefault snapshot (legacy) virtual disk name is aaa – 1. If the base virtual disk already has n – 1 number ofsnapshot (legacy) virtual disks, the default name is aaa – n. An example of the snapshot (legacy)repository virtual disk name that the RAID controller module might create is, if the base virtual disk nameis aaa and does not have a snapshot (legacy) repository virtual disk, the default snapshot (legacy)repository virtual disk name is aaa – R1. If the base virtual disk already has n – 1 number of snapshot(legacy) repository virtual disks, the default name is aaa – Rn.If you do not specify the unconfigured space or free space, the snapshot (legacy) repository virtual disk isplaced in the same disk group as the base virtual disk. If the disk group where the base virtual disk residesdoes not have enough space, this command fails.Enclosure Loss ProtectionWhen you assign the physical disks, if you set the enclosureLossProtect parameter to TRUE and haveselected more than one physical disk from any one enclosure, the storage array returns an error. If youset the enclosureLossProtect parameter to FALSE, the storage array performs operations, but thedisk group that you create might not have enclosure loss protection.When the RAID controller module firmware assigns the physical disks, if you set theenclosureLossProtect parameter to TRUE, the storage array returns an error if the RAID controllermodule firmware cannot provide physical disks that result in the new disk group having enclosure lossprotection. If you set the enclosureLossProtect parameter to FALSE, the storage array performs theoperation even if it means the disk group might not have enclosure loss protection.Scheduling Snapshots (Legacy)You can use the enableSchedule and the schedule parameters to schedule automatic snapshots(legacy). Automatic snapshots (legacy) can be scheduled daily, weekly, or monthly (by day or by date).The enableSchedule parameter turns on or off the ability to schedule snapshots (legacy). When youenable scheduling, you use the schedule parameter to define when you want the snapshots (legacy) tooccur.This list explains how to use the options for the schedule parameter:immediate As soon as you enter the command, a snapshot (legacy) virtual disk is created and acopyon- write operation begins.startDate A specific date on which you want to create a snapshot (legacy) virtual disk andperform a copy-on-write operation. The format for entering the date is MM:DD:YY.If you do not provide a start date, the current date is used. An example of thisoption is startDate=06:27:11.scheduleDay A day of the week on which you want to create a snapshot (legacy) virtual disk andperform a copy-on-write operation. The values that you can enter are: monday,tuesday, wednesday, thursday, friday, saturday, sunday, and all. Forexample: scheduleDay=wednesday.191
