Bacula-users

Re: [Bacula-users] Cannot restore VMmware/ZFS

2009-12-28 21:16:05
Subject: Re: [Bacula-users] Cannot restore VMmware/ZFS
From: Marc Schiffbauer <marc AT schiffbauer DOT net>
To: bacula-users AT lists.sourceforge DOT net
Date: Tue, 29 Dec 2009 02:56:01 +0100
* Paul Greidanus schrieb am 28.12.09 um 23:44 Uhr:
> I'm trying to restore files I have backed up on the NFS server that I'm using 
> to back VMware, but I'm getting similar errors to this every time I try to 
> restore:
> 
> 28-Dec 12:10 krikkit-dir JobId 1433: Start Restore Job 
> Restore.2009-12-28_12.10.28_54
> 28-Dec 12:10 krikkit-dir JobId 1433: Using Device "TL2000-1"
> 28-Dec 12:10 krikkit-sd JobId 1433: 3307 Issuing autochanger "unload slot 11, 
> drive 0" command.
> 28-Dec 12:11 krikkit-sd JobId 1433: 3304 Issuing autochanger "load slot 3, 
> drive 0" command.
> 28-Dec 12:12 krikkit-sd JobId 1433: 3305 Autochanger "load slot 3, drive 0", 
> status is OK.
> 28-Dec 12:12 krikkit-sd JobId 1433: Ready to read from volume "000009L4" on 
> device "TL2000-1" (/dev/rmt/0n).
> 28-Dec 12:12 krikkit-sd JobId 1433: Forward spacing Volume "000009L4" to 
> file:block 473:0.
> 28-Dec 12:15 krikkit-sd JobId 1433: Error: block.c:1010 Read error on fd=4 at 
> file:blk 475:0 on device "TL2000-1" (/dev/rmt/0n). ERR=I/O error.
> 28-Dec 12:15 krikkit-sd JobId 1433: End of Volume at file 475 on device 
> "TL2000-1" (/dev/rmt/0n), Volume "000009L4"
> 28-Dec 12:15 krikkit-sd JobId 1433: End of all volumes.
> 28-Dec 12:15 krikkit-fd JobId 1433: Error: attribs.c:423 File size of 
> restored file 
> /backupspool/rpool/vm2/.zfs/snapshot/backup/InvidiCA/InvidiCA-flat.vmdk not 
> correct. Original 8589934592, restored 445841408.
> 
> Files are backed up from a zfs snapshot which is created just before the 
> backup starts. Every other file I am attempting to restore works just fine... 
> 
> Is anyone out there doing ZFS snapshots for VMware, or backing up NFS servers 
> that have .vmdk files on it?

No, but I could imagine that this might have something to do with
some sparse-file setting.

Have you checked how much space of your 8GB flat vmdk is aktually being
used? Maybe this was 445841408 Bytes at backup time?

Does the same happen if you do not use pre-allocated vmdk-disks?
(Which is better anyway most of the times if you use NFS instead of vmfs)


-Marc
-- 
8AAC 5F46 83B4 DB70 8317  3723 296C 6CCA 35A6 4134

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users