D-Link DSN-6110 User Manual for DSN-6110 & DSN-6110 with DSN-610 - Page 87

Rollback, Snapshot constraint

Get D-Link DSN-6110 PDF manuals and user guides View all D-Link DSN-6110 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 87 highlights

5.4.3 Rollback The data in snapshot VD can rollback to original VD. Please follow the procedures. 1. Select "/ Volume configuration / Snapshot". 2. Check the gray button next to the Snap VD number which user wants to rollback the data; click "Rollback". 3. Done, the data in snapshot VD is rollback to original VD. Caution Before executing rollback, it is better to dismount file system for flushing data from cache to disks in OS first. System sends pop-up message when user executes rollback function. 5.4.4 Snapshot constraint D-LINK snapshot function applies Copy-on-Write technique on UDV/VD and provides a quick and efficient backup methodology. When taking a snapshot, it does not copy any data at first time until a request of data modification comes in. The snapshot copies the original data to snapshot space and then overwrites the original data with new changes. With this technique, snapshot only copies the changed data instead of copying whole data. It will save a lot of disk space. • Create a data-consistent snapshot Before using snapshot, user has to know why sometimes the data corrupts after rollback of snapshot. Please refer to the following diagram. When user modifies the data from host, the data will pass through file system and memory of the host (write caching). Then the host will flush the data from memory to physical disks, no matter the disk is local disk (IDE or SATA), DAS (SCSI or SAS), or SAN (fibre or iSCSI). From the viewpoint of storage device, it can not control the behavior of host side. This case maybe happens. If user takes a snapshot, some data is still in memory and not flush to disk. Then the snapshot may have an incomplete image of original data. The problem does not belong to the storage device. To avoid this data inconsistent issue between snapshot and original data, user has to make the operating system flush the data from memory of host (write caching) into disk before taking snapshot. 87

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
87
5.4.3
Rollback
The data in snapshot VD can rollback to original VD. Please follow the procedures.
1.
Select
“/ Volume configuration / Snapshot”
.
2.
Check the gray button next to the Snap VD number which user wants to rollback the
data; click
“Rollback”
.
3.
Done, the data in snapshot VD is rollback to original VD.
Caution
Before executing rollback, it is better to dismount file system for flushing
data from cache to disks in OS first. System sends pop-up message when
user executes rollback function.
5.4.4
Snapshot constraint
D-LINK
snapshot function applies Copy-on-Write technique on UDV/VD and provides a
quick and efficient backup methodology. When taking a snapshot, it does not copy any
data at first time until a request of data modification comes in. The snapshot copies the
original data to snapshot space and then overwrites the original data with new changes.
With this technique, snapshot only copies the changed data instead of copying whole data.
It will save a lot of disk space.
•
Create a data-consistent snapshot
Before using snapshot, user has to know why sometimes the data corrupts after rollback
of snapshot. Please refer to the following diagram.
When user modifies the data from host, the data will pass through file system and
memory of the host (write caching). Then the host will flush the data from memory to
physical disks, no matter the disk is local disk (IDE or SATA), DAS (SCSI or SAS), or SAN
(fibre or iSCSI). From the viewpoint of storage device, it can not control the behavior of
host side. This case maybe happens. If user takes a snapshot, some data is still in
memory and not flush to disk. Then the snapshot may have an incomplete image of
original data. The problem does not belong to the storage device. To avoid this data
inconsistent issue between snapshot and original data, user has to make the operating
system flush the data from memory of host (write caching) into disk before taking
snapshot.