I sent in a support request but i havent heard anything back on this, so im going to check it in with the forums.
Currently we are testing out a procedure where we backup a system using the r-drive image software with no compression set. We then backup the .arc files using netbackup puredisk which segments files into 128kb segments, compares them to what is currently stored, and then only stores unique 128kb segments (deduplication). While I assume there wouldn't be perfect deduplication on these, i am very surprised that there is a 0% deduplication rate on a full backup taken at 12pm, and another full backup taken at 1pm from the same system. Why would the backups appear completely different from each other if no data has really changed on the system in 128kb segments? Even if i have 3-4 of these full backups from the same system, nothing appears similar between them.
Im trying to validate this as a concept to buy a heck of alot of licenses of the product, so please let me know when you can.
How is data laid out?
Forum rules
Discussion on the R-Drive Image software
Discussion on the R-Drive Image software
Re: How is data laid out?
Generally, if nothing has been changed on the disk, the images should be the same, except some small areas in the beginning and the end of the file.
R-Drive Image uses the same technique and splits the data into blocks of app.256kB. If the Backup the useful information only option turned on and something has changed at the beginning of the disk (some cluster might turn from used to not used, or vise verse), and all data may shift, making the image look different for "deduplication".
R-Drive Image uses the same technique and splits the data into blocks of app.256kB. If the Backup the useful information only option turned on and something has changed at the beginning of the disk (some cluster might turn from used to not used, or vise verse), and all data may shift, making the image look different for "deduplication".
Re: How is data laid out?
So is the appropriate size to slice with puredisk to be 256kb? and is that kilobits or kilobytes?
We'll run some additional tests to see this. If a system performs a defrag, will that change the data significantly?
We'll run some additional tests to see this. If a system performs a defrag, will that change the data significantly?
Re: How is data laid out?
It's worth trying. kilobytes.alazanowski wrote:So is the appropriate size to slice with puredisk to be 256kb? and is that kilobits or kilobytes?
That depends on how the data was fragmented. If seriously, the changes are serious.alazanowski wrote:If a system performs a defrag, will that change the data significantly?