Does that imply then that a TMC backed up sparse file could not be
restored to the same device it came off of? Would TMC attempt to restore
all 26G?
On 07/21/2010 12:14 PM, David Boyes wrote:
Sparse files. OK. Then the next question, how can I store a 26G file in
a machine that isn't that large?
Because sparse files are just a bunch of pointers -- the data doesn't really
exist. It's just diddling around with the directory inode.
And to add to this, why does the
filesystem backup really dump 26G into our TSM server?
TSM doesn't process sparse files correctly on many platforms. In this case
it's using APIs that don't recognize sparse files and so it's dumping all
26G.
-- db
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
--
Dave Jones
V/Soft
www.vsoft-software.com
Houston, TX
281.578.7544
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
