The problem is that the windows server backup seems to choose dynamic
vhd (which would make sense in most cases) and I dont know if there is a
way to change that. Using ISCSI-volumes wont help in my case since
servers are running on physical hardware.
Am 27.04.2010 01:54, schrieb Brandon
- Tim.Kreis tim.kr...@gmx.de skrev:
The problem is that the windows server backup seems to choose dynamic
vhd (which would make sense in most cases) and I dont know if there is
a
way to change that. Using ISCSI-volumes wont help in my case since
servers are running on physical
Hi Tim,
thanks for sharing your dedup experience. Especially for Virtualization, having
a good pool of experience will help a lot of people.
So you see a dedup ratio of 1.29 for two installations of Windows Server 2008 on
the same ZFS backing store, if I understand you correctly.
What dedup
Hi,
The setting was this:
Fresh installation of 2008 R2 - server backup with the backup feature - move
vhd to zfs - install active directory role - backup again - move vhd to same
share
I am kinda confused over the change of dedup ratio from changing the record
size, since it should dedup
I found the VHD specification here:
http://download.microsoft.com/download/f/f/e/ffef50a5-07dd-4cf8-aaa3-442c0673a029/Virtual%20Hard%20Disk%20Format%20Spec_10_18_06.doc
I am not sure if i understand it right, but it seems like data on disk gets
compressed into the vhd (no empty space), so even
On Mon, Apr 26, 2010 at 8:51 AM, tim Kries tim.kr...@gmx.de wrote:
I am kinda confused over the change of dedup ratio from changing the record
size, since it should dedup 256-bit blocks.
Dedup works on the blocks or either recordsize or volblocksize. The
checksum is made per block written, and
Hi,
I am playing with opensolaris a while now. Today i tried to deduplicate the
backup VHD files Windows Server 2008 generates. I made a backup before and
after installing AD-role and copied the files to the share on opensolaris
(build 134). First i got a straight 1.00x, then i set recordsize
You might note, dedupe only dedupes data that is writen after the flag is set.
It does not retroactivly dedupe already writen data.
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
It was active all the time.
Made a new zfs with -o dedup=on, copied with default record size, got no dedup,
deleted files, set recordsize 4k, dedup ratio 1.29x
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
A few things come to mind...
1. A lot better than...what? Setting the recordsize to 4K got you some
deduplication but maybe the pertinent question is what were you
expecting?
2. Dedup is fairly new. I haven't seen any reports of experiments like
yours so...CONGRATULATIONS!! You're probably
Dedup is a key element for my purpose, because i am planning a central
repository for like 150 Windows Server 2008 (R2) servers which would take a lot
less storage if they dedup right.
--
This message posted from opensolaris.org
___
zfs-discuss
11 matches
Mail list logo
