Hi everybody.

I can confirm this issue, too. Since we upgraded to 16.2.4 we get these warnings. I just upgraded to 16.2.5, same issue.
Are there any news on this?

Thanks a lot and many greets
Stephan

Am 03.02.2017 15:17 schrieb Chris Sheaves:
On Tuesday, January 24, 2017 at 7:57:55 AM UTC-5, lst_...@kwsoft.de wrote:
Hello,

we have installed the lates 16.2.4 Client for Windows on a Windows
2008 R2 Server with MS-SQL Express 2008R2. With up until the 15.2
Version of the client this has worked as expected. Now we got the
following "warning" from Bareos:

Warning: VSS Writer "SqlServerWriter" has invalid state. ERR=The
writer vetoed the shadow copy creation process during the backup
preparation state.
Warning: VSS Writer "SqlServerWriter" has invalid state. ERR=The
writer vetoed the shadow copy creation process during the backup
preparation state.
VSS Writer (PrepareForBackup): "SqlServerWriter", State: 0x7
(VSS_WS_FAILED_AT_PREPARE_BACKUP)
Warning: VSS Writer "SqlServerWriter" has invalid state. ERR=The
writer vetoed the shadow copy creation process during the backup
preparation state.

In the Event Log of the system the following is found:

Protokollname: Application
Quelle:        SQLWRITER
Datum:         23.01.2017 20:13:43
Ereignis-ID:   8203
Aufgabenkategorie:Keine
Ebene:         Fehler
Schlüsselwörter:Klassisch
Benutzer:      Nicht zutreffend
Beschreibung:
SQL Writer-Fehler: Der 2-Sicherungstyp wird nicht unterstützt.

I will try a reboot of the machine tonight, but i doubt this will cure
the problem. Any idea what could cause this in the 16.2.4 Release?

Thanks

Andreas

I can confirm Andreas' issue. 16.2.4 generates a VSS warning, 15.2.4 does not.

--
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 bareos-users+unsubscr...@googlegroups.com.
To post to this group, send email to bareos-users@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to