On Tue, 11 May 2010 10:11:17 +0200, Henrik Johansen <henrik AT scannet DOT dk>  
wrote:

> If you are storing your system state backup on C you'll need to apply
> the reg fix as pointed out in http://support.microsoft.com/kb/944530  
> first.

Thanks for the fix, but even with that:

wbadmin START BACKUP -backupTarget:D: -systemState -exclude:C:,D:  
-include:d:\temp.txt
..
The backup storage location is invalid. You cannot use a volume that is  
included in the backup as a storage location.

(I was trying to work around not being able to exclude the C: and D:  
volumes, temp.txt is a dummy file)

If I just use:

wbadmin START SYSTEMSTATEBACKUP -backupTarget:D:
..
This will back up the system state from volume(s) System Reserved (100.00  
MB),Local Disk(C:),Local Disk(D:) to D:.

And this results in 6+ GB of data in 2 small and 1 large .vhd file.  
Astonishingly, the logfile does not actually contain any registry hive  
that I can see (e.g. ntuser.dat files).

Apparently the default systembackup job includes *all* local volumes and  
*excludes* what it's supposed to backup. #$@$# Microsoft...

Does anyone know how to fix this mess? Can you simply forget about wbadmin  
and have Bacula-fd back up live registry hives (because it should be VSS  
aware right?) - and restore them when needed?

------------------------------------------------------------------------------

_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users