SD GUI will basically duplicate the whole LUN from snapshot, so yes, observed behavior is normal.
If you want to do full volume revert to previous snapshot you can do it using SD command line utility (sdcli.exe). Do not forget that reverting volume will irrecoverably delete all snapshots after the one you revert to.
I was trying to revert to a snapshot from a command line by executing the command:
sdcli snap restore -d z -s SnapShotName
but the situation remains the same
Here is some Syslog:
Severity Event Triggerred Message info wafl.volume.snap.autoDelete Tue Apr 26 13:32:48 CEST Deleting snapshot '26-04-2011_HOUR_13_00' in volume 'HyperV_SQL' to recover storage info wafl.volume.snap.autoDelete Tue Apr 26 13:32:33 CEST Deleting snapshot '26-04-2011_HOUR_12_39' in volume 'HyperV_SQL' to recover storage info app.log.info Tue Apr 26 13:30:27 CEST R710NODE1: SnapDrive 6.2: (198) Snapshot Copy event: For the description of this event please check the application event log on the host system. info lun.clone.split.started Tue Apr 26 13:30:20 CEST Clone split was started on LUN /vol/HyperV_SQL/HyperV_SQL. notice lun.snaprestore.notice Tue Apr 26 13:30:10 CEST [74577978, 3369100, 61491606] snap restore: Clone/Restore could not set space reservations on restored LUN notice wafl.vol.full Tue Apr 26 13:30:10 CEST file system on volume HyperV_SQL is full notice lun.snaprestore.notice Tue Apr 26 13:30:10 CEST [74577978, 3369100, 61491606] snap restore: started
A also posted screenshot from my system manager representing this lun configuration (Screen3.jpg)
Why is that one snapshot is so big ?
What command should I use to avoid such situation ?
Assumming of course that I have one Lun per Volume. But what if I would have several luns on the same volume and I want to recover only one lun not entire volume, then should I use "sdcli snap restore"?