I am looking to use Opensolaris/ZFS to create an iscsi SAN to provide storage
for a collection of virtual systems and replicate to an offiste device.
While testing the environment I was surprised to see the size of the
incremental snapshots, which I need to send/receive over a WAN connection,
On Sep 30, 2009, at 5:48 AM, Brian Hubbleday wrote:
I am looking to use Opensolaris/ZFS to create an iscsi SAN to
provide storage for a collection of virtual systems and replicate to
an offiste device.
While testing the environment I was surprised to see the size of the
incremental
On Sep 30, 2009, at 5:48 AM, Brian Hubbleday wrote:
I am looking to use Opensolaris/ZFS to create an iscsi SAN to
provide storage for a collection of virtual systems and replicate to
an offiste device.
While testing the environment I was surprised to see the size of the
incremental
I took binary dumps of the snapshots taken in between the edits and this showed
that there was actually very little change in the block structure, however the
incremental snapshots were very large. So the conclusion I draw from this is
that the snapshot simply contains every written block since
Just realised I missed a rather important word out there, that could confuse.
So the conclusion I draw from this is that the --incremental-- snapshot simply
contains every written block since the last snapshot regardless of whether the
data in the block has changed or not.
--
This message
I had a 50mb zfs volume that was an iscsi target. This was mounted into a
Windows system (ntfs) and shared on the network. I used notepad.exe on a remote
system to add/remove a few bytes at the end of a 25mb file.
--
This message posted from opensolaris.org
On Sep 30, 2009, at 10:40 AM, Brian Hubbleday b...@delcam.com wrote:
Just realised I missed a rather important word out there, that could
confuse.
So the conclusion I draw from this is that the --incremental--
snapshot simply contains every written block since the last snapshot
It is more cost, but a WAN Accelerator (Cisco WAAS, Riverbed, etc.) would be a
big help.
Scott
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
Depending on the data content that you're dealing you can compress the
snapshots inline with the send/receive operations by piping the data
through gzip. Given that we've been talking about 500Mb text files,
this seems to be a very likely solution. There was some mention in the
Kernel
On 30-Sep-09, at 10:48 AM, Brian Hubbleday wrote:
I had a 50mb zfs volume that was an iscsi target. This was mounted
into a Windows system (ntfs) and shared on the network. I used
notepad.exe on a remote system to add/remove a few bytes at the end
of a 25mb file.
I'm astonished that's
Ross Walker wrote:
On Sep 30, 2009, at 10:40 AM, Brian Hubbleday b...@delcam.com wrote:
Just realised I missed a rather important word out there, that could
confuse.
So the conclusion I draw from this is that the --incremental--
snapshot simply contains every written block since the last
11 matches
Mail list logo
