Apparently I need to do much more comprehensive restore testing, because
when I need, it my bacula installation has fallen down around me. This
is just the worst of several problems I will be reporting.
First, I ran a restore. The original client is a now-dead XP box, the
target client is a new XP box:
The log indicates success.
02-Jul 09:04 packrat-dir JobId 33124: Start Restore Job
RestoreFiles.2009-07-02_09.04.49_02
02-Jul 09:04 packrat-dir JobId 33124: Using Device "VS160"
02-Jul 09:05 crow-sd JobId 33124: Ready to read from volume "tape-pool1-0008" on device
"VS160" (/dev/nst0).
02-Jul 09:05 crow-sd JobId 33124: Forward spacing Volume "tape-pool1-0008" to
file:block 82:2807.
02-Jul 09:17 packrat-dir JobId 33124: Bacula packrat-dir 3.0.1 (30Apr09):
02-Jul-2009 09:17:40
Build OS: i686-redhat-linux-gnu redhat
JobId: 33124
Job: RestoreFiles.2009-07-02_09.04.49_02
Restore Client: joe2-fd
Start time: 02-Jul-2009 09:04:51
End time: 02-Jul-2009 09:17:40
Files Expected: 1,688
Files Restored: 1,688
Bytes Restored: 5,338,764,394
Rate: 6942.5 KB/s
FD Errors: 0
FD termination status: OK
SD termination status: OK
Termination: Restore OK
02-Jul 09:17 packrat-dir JobId 33124: Begin pruning Jobs.
02-Jul 09:17 packrat-dir JobId 33124: No Jobs found to prune.
02-Jul 09:17 packrat-dir JobId 33124: Begin pruning Files.
02-Jul 09:17 packrat-dir JobId 33124: No Files found to prune.
It reported success. I watched bacula-fd with procmon (from sysinternals.com)
because I simply could not believe the results I was getting. I had specified
where=/tmpr2, and I watched it restore the 1,688 files with procmon. Now look
what I see:
(The folder C:\tmpr was from a different restore performed earlier)
C:\>cd \tmpr2
C:\tmpr2>dir
Volume in drive C has no label.
Volume Serial Number is CC21-996C
Directory of C:\tmpr2
File Not Found
C:\tmpr2>cd
C:\tmpr2
C:\tmpr2>dir
Volume in drive C has no label.
Volume Serial Number is CC21-996C
Directory of C:\tmpr2
File Not Found
C:\tmpr2>cd \
C:\>dir
Volume in drive C has no label.
Volume Serial Number is CC21-996C
Directory of C:\
07/01/2009 11:45 PM 1,024 .rnd
07/01/2009 05:40 PM 0 AUTOEXEC.BAT
07/01/2009 05:40 PM 0 CONFIG.SYS
07/01/2009 05:44 PM <DIR> Documents and Settings
07/02/2009 08:29 AM <DIR> Program Files
07/02/2009 09:18 AM <DIR> SysinternalsSuite
07/02/2009 08:18 AM <DIR> tmpr
07/02/2009 08:27 AM <DIR> WINDOWS
3 File(s) 1,024 bytes
5 Dir(s) 6,451,523,584 bytes free
C:\>dir tmpr
Volume in drive C has no label.
Volume Serial Number is CC21-996C
Directory of C:\tmpr
07/02/2009 08:18 AM <DIR> .
07/02/2009 08:18 AM <DIR> ..
07/02/2009 08:18 AM <DIR> C
0 File(s) 0 bytes
3 Dir(s) 6,451,523,584 bytes free
C:\>dir tmpr2
Volume in drive C has no label.
Volume Serial Number is CC21-996C
Directory of C:\tmpr2
File Not Found
C:\>cd tmpr2
C:\tmpr2>cd \
C:\>cd tmpxxx
The system cannot find the path specified.
C:\>cd \tmpr2\C
C:\tmpr2\C>dir
Volume in drive C has no label.
Volume Serial Number is CC21-996C
Directory of C:\tmpr2\C
File Not Found
C:\tmpr2\C>cd "Documents and Settings"
C:\tmpr2\C\Documents and Settings>dir
Volume in drive C has no label.
Volume Serial Number is CC21-996C
Directory of C:\tmpr2\C\Documents and Settings
File Not Found
C:\tmpr2\C\Documents and Settings>
...
C:\tmpr2\C\Documents and Settings\Joe>dir
Volume in drive C has no label.
Volume Serial Number is CC21-996C
Directory of C:\tmpr2\C\Documents and Settings\Joe
File Not Found
C:\tmpr2\C\Documents and Settings\Joe>dir "My Documents" | more
Volume in drive C has no label.
Volume Serial Number is CC21-996C
Directory of C:\tmpr2\C\Documents and Settings\Joe\My Documents
11/16/2007 12:37 PM 47,302 06_clearing_account_rpt.pdf
09/28/2006 11:18 AM 38,400 0927 Seaman (07).xls
04/09/2007 05:20 PM 16,384 10# Satinwrap
colors-Spec-Sheet.xls
01/26/2005 12:41 PM 16,896 16 GSM White Coach tissue.xls
07/18/2006 10:46 AM 26,812 17gsm tissue for printing.jpg
08/27/2004 09:57 AM 905,728 2004 stock program G&G r .doc
12/11/2003 05:31 PM 93,696 2004CrossReference.xls
06/25/2004 11:00 AM 80,896 2005 Projections.xls
.
.
.
It looks for all the world like bacula-fd (3.0.1 from the sourceforge
site) has silently corrupted this NTFS file system. Can anyone one else
suggest what might be happening?
I tried it on a different client with the 2.2.6 client and it appears to
have worked normally. Any advice?
The original backup was probably done with a 2.* client
------------------------------------------------------------------------------
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
