Hi, Andreas!
On Sat, Feb 15, 2014 at 9:38 AM, <[email protected]> wrote: > That the reason to use VSS after all. All provider register for the volume > in question and set their files to a save state before the snapshot > requested by Bareos happens. So Bareos actually triggers all providers > listed for the volume. It should look like this in the Bareos log: > > 14-Feb 19:16 swyx-fd JobId 8194: Generate VSS snapshots. Driver="Win32 > VSS", Drive(s)="C" > 14-Feb 19:17 swyx-fd JobId 8194: VSS Writer (BackupComplete): "System > Writer", State: 0x1 (VSS_WS_STABLE) > 14-Feb 19:17 swyx-fd JobId 8194: VSS Writer (BackupComplete): > "SqlServerWriter", State: 0x1 (VSS_WS_STABLE) > 14-Feb 19:17 swyx-fd JobId 8194: VSS Writer (BackupComplete): > "MSDEWriter", State: 0x1 (VSS_WS_STABLE) > 14-Feb 19:17 swyx-fd JobId 8194: VSS Writer (BackupComplete): "COM+ REGDB > Writer", State: 0x1 (VSS_WS_STABLE) > 14-Feb 19:17 swyx-fd JobId 8194: VSS Writer (BackupComplete): "Registry > Writer", State: 0x1 (VSS_WS_STABLE) > 14-Feb 19:17 swyx-fd JobId 8194: VSS Writer (BackupComplete): "Event Log > Writer", State: 0x1 (VSS_WS_STABLE) > 14-Feb 19:17 swyx-fd JobId 8194: VSS Writer (BackupComplete): "BITS > Writer", State: 0x1 (VSS_WS_STABLE) > 14-Feb 19:17 swyx-fd JobId 8194: VSS Writer (BackupComplete): "WMI > Writer", State: 0x1 (VSS_WS_STABLE) > > Bareos then simply backup the snapshot and destroy it afterwards. > > > Great info, so - if I understood this correctly - Bareos will backup all snapshots generated by any registered VSS Writers? This is good news, hope to test it this week. Thanks a lot! -- //DG LOC(NJ) //* -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
