Yes you may create a snapshot schedule for a dedicated virtual disk, and even automapping the snapshots taken by the schedule with LUNs.
Before taking a snapshot you'll need to assign a snapshot space for the virtual disk to keep the snapshots. After the snapshot space is assigned, you may simply choose the "take snapshot" option from the virtual disk options, or alternatively in the snapshot management page, select "take a snapshot" for any snapshot ready virtual disk. 
A snapshot is more like a image taken at a dedicated point of time, recording the complete status of data inside a virtual disk. 
If the two systems are the same model and using the same firmware version, then roaming the RG between the two systems is possible. If however the two systems are different models or using different firmware versions, consult Qsan support team for the possibility.
Volume restoration is NOT supported for a thin-provisioned RG.
The volume restoration does not guarantee the contents on the VDs can be completely restored. This special feature only helps to restore the RAID and volume configurations. Therefore it is possible that some data appear to be inconsistent when the RG/VD is restored from a deleted/failed status.
The volume restoration feature requires all the member disks in the historical time point to be present for restoring the RG/VD status. If any of the member disk is missing then it's not possible to restore the configurations. For further details about this restriciton and limiation please consult Qsan technical support team. 
No, the volume restoration only helps to restore the RAID/volume conifgurations, without modifying or impacting any block level contents inside. 
The volume restoration feature is a RAID and volume configuration status recovery utility. The feature helps to restore a RG and VDs on the RG to choosen historical points recorded in a volume coniguration records list.
If users have a missing features problem, please help to update the Qcentral firmware to the latest version. If the problem still remains after upgrading firmware, please contact with Qsan CS for the Qcentral feature request.