Re: [Bacula-users] Windows Client, VSS Issues, 2.0.3?
Sent: Friday, March 30, 2007 12:48 PM
To: bacula-users@lists.sourceforge.net
Cc: Robert Nelson
Subject: Re: [Bacula-users] Windows Client, VSS Issues, 2.0.3?
Bacula backup sitting at 0 bytes. Floppy drive and hard drive did a
seek like a normal VSS startup.
vssadmin list shadows:
vssadmin 1.0 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.
No shadow copies present in the system.
---
When I try to run the vssadmin list writers, it waits for a response.
Like VSS is just hung up. I never do get a response from the vssadmin
list writers unless I kill the FD and the VSS process.
It is difficult for me to reproduce the hung at end scenario. But
I'll certainly get you the output the next time I see it.
With the failed VSS components...When I check and Bacula hasn't been run
yet on the system, both are listed as stable. I did see another as
failed, and sometimes they return a status: 7, failed.
I do run some MS backups on this system as well. Hopefully those aren't
causing any conflicts.
Thanks again. A great community here.
Mike
Robert Nelson wrote:
-Original Message-
From: [EMAIL PROTECTED] [mailto:bacula-users-
[EMAIL PROTECTED] On Behalf Of Michael Gerszewski
Sent: Friday, March 30, 2007 12:07 PM
To: bacula-users@lists.sourceforge.net
Cc: Robert Nelson
Subject: Re: [Bacula-users] Windows Client, VSS Issues, 2.0.3?
Thanks for the quick response.
vssadmin list writers:
vssadmin 1.0 - Volume Shadow Copy Service administrative command-line
tool
(C) Copyright 2001 Microsoft Corp.
Writer name: 'MSDEWriter'
Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
Writer Instance Id: {b9048c82-c0b6-42e8-b885-3ddc806474bd}
State: [1] Stable
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {a4358c3f-d8b3-4e32-971a-a1aa47f7b0fb}
State: [9] Failed
Writer name: 'IIS Metabase Writer'
Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
Writer Instance Id: {38ebb2dd-0122-48e1-915e-23ce2aed2e95}
State: [9] Failed
Interesting the above two seemed to have failed their initialization.
Writer name: 'Microsoft Writer (Bootable State)'
Writer Id: {f2436e37-09f5-41af-9b2a-4ca2435dbfd5}
Writer Instance Id: {9470d858-515e-47d9-bf71-ba1a26782a69}
State: [1] Stable
Writer name: 'Microsoft Writer (Service State)'
Writer Id: {e38c2e3c-d4fb-4f4d-9550-fcafda8aae9a}
Writer Instance Id: {1a9ca255-4ad6-4172-9d04-d433e9958d33}
State: [1] Stable
--
vssadmin list shadows (while backup is running):
vssadmin 1.0 - Volume Shadow Copy Service administrative command-line
tool
(C) Copyright 2001 Microsoft Corp.
Contents of shadow copy set {26035bf3-a48b-4993-afcb-6f48affefd4c}
(The shadow copy set contained 1 shadow copies at creation time, 1
shadow copie
s exist now)
'MS Software Shadow Copy provider 1.0' shadow copy
{d6dc446b-5cae-46bb-a555-d344
c70d65e5} on volume \\?\Volume{d27e6118-47d1-11d9-aa59-806d6172696f}\
--
That looks good.
vssadmin list shadows (after backup completes):
vssadmin 1.0 - Volume Shadow Copy Service administrative command-line
tool
(C) Copyright 2001 Microsoft Corp.
No shadow copies present in the system.
-
That looks very good, doesn't seem we have any leftover crud.
A couple more notes that may or may not make a difference. I am
running
SQL Server Express 2005 on this system, and the event logs show the
databases freezing and unfreezing during the bacula backups. The log
is
telling me the database was successfully backed up, but I am not
backing
up anything from my SQL databases (to my knowledge).
That's expected, the system doesn't know what we'll be backing up at the
time we initiate the shadow.
Thanks
Mike
Can you also post the output from vssadmin list shadows when the
backup is
hung? Meanwhile, I'll check and make sure we release all our interface
pointers.
Robert Nelson wrote:
What is the output from the command vssadmin list writers?
Also what is the output from the command vssadmin list shadows after
the
successful backup but prior to the next backup?
-Original Message-
From: [EMAIL PROTECTED] [mailto:bacula-
users-
[EMAIL PROTECTED] On Behalf Of Michael Gerszewski
Sent: Friday, March 30, 2007 11:27 AM
To: bacula-users
Subject: [Bacula-users] Windows Client, VSS Issues, 2.0.3?
Greetings,
I have been evaluating Bacula for the School District I work for as a
backup option for our Windows 2003 Servers. I like many of the
features
Bacula has compared to other solutions. I have been testing with
2.0.3
with the director on a linux box, a storage daemon on a Windows 2003
box, and a file daemon on an XP box. I installed the Linux portion
from
RPMs and the Windows client with the windows installer.
I have it configured to do Disk backups. The first couple of days,
everything worked OK with small backups without
Re: [Bacula-users] Windows Client, VSS Issues, 2.0.3?
On a whim, I decided to stop my SQL Server running on this FD. The
backups then ran properly. After I restarted the SQL Server, the FD
continues to backup properly. It has been backing up properly for the
past two days.
I am also free of the error logs being generated by SQL Server and VSS.
Maybe there was something strange about my SQL Server instance, and it
causing issues with VSS? Maybe VSS just wanted my SQL Server to be
restarted while the system was running?
I still don't know why it is working now, when after a reboot it
wouldn't work properly. I will continue to monitor the situation, watch
to see if any more backups hang, and report any log messages on the
Windows box that are possibly relevant.
Some additional notes for others out there that might experience this
problem...When I initially installed the FD client on this Windows XP
box, there were errors in my Application Log relating to VSS and SQL
Server stating that some of my databases did not have a simple
recovery plan. Sure enough, the recovery plan was set to Full on the
databases that errored out. I did change the recovery plan on the
databases and restarted the SQL Server, and that is about when my
hanging backup problems started. Maybe the SQL Server just needed to be
warm restarted again to fully implement the changes and make VSS happy?
Just a guess, and something for others with this issue to try.
Thanks again for your time and efforts.
Mike
Robert Nelson wrote:
Okay great, I think this should give me something to work with. I'll try
and repro it here.
-Original Message-
From: [EMAIL PROTECTED] [mailto:bacula-users-
[EMAIL PROTECTED] On Behalf Of Michael Gerszewski
Sent: Friday, March 30, 2007 12:48 PM
To: bacula-users@lists.sourceforge.net
Cc: Robert Nelson
Subject: Re: [Bacula-users] Windows Client, VSS Issues, 2.0.3?
Bacula backup sitting at 0 bytes. Floppy drive and hard drive did a
seek like a normal VSS startup.
vssadmin list shadows:
vssadmin 1.0 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.
No shadow copies present in the system.
---
When I try to run the vssadmin list writers, it waits for a response.
Like VSS is just hung up. I never do get a response from the vssadmin
list writers unless I kill the FD and the VSS process.
It is difficult for me to reproduce the hung at end scenario. But
I'll certainly get you the output the next time I see it.
With the failed VSS components...When I check and Bacula hasn't been run
yet on the system, both are listed as stable. I did see another as
failed, and sometimes they return a status: 7, failed.
I do run some MS backups on this system as well. Hopefully those aren't
causing any conflicts.
Thanks again. A great community here.
Mike
Robert Nelson wrote:
-Original Message-
From: [EMAIL PROTECTED] [mailto:bacula-users-
[EMAIL PROTECTED] On Behalf Of Michael Gerszewski
Sent: Friday, March 30, 2007 12:07 PM
To: bacula-users@lists.sourceforge.net
Cc: Robert Nelson
Subject: Re: [Bacula-users] Windows Client, VSS Issues, 2.0.3?
Thanks for the quick response.
vssadmin list writers:
vssadmin 1.0 - Volume Shadow Copy Service administrative command-line
tool
(C) Copyright 2001 Microsoft Corp.
Writer name: 'MSDEWriter'
Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
Writer Instance Id: {b9048c82-c0b6-42e8-b885-3ddc806474bd}
State: [1] Stable
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {a4358c3f-d8b3-4e32-971a-a1aa47f7b0fb}
State: [9] Failed
Writer name: 'IIS Metabase Writer'
Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
Writer Instance Id: {38ebb2dd-0122-48e1-915e-23ce2aed2e95}
State: [9] Failed
Interesting the above two seemed to have failed their initialization.
Writer name: 'Microsoft Writer (Bootable State)'
Writer Id: {f2436e37-09f5-41af-9b2a-4ca2435dbfd5}
Writer Instance Id: {9470d858-515e-47d9-bf71-ba1a26782a69}
State: [1] Stable
Writer name: 'Microsoft Writer (Service State)'
Writer Id: {e38c2e3c-d4fb-4f4d-9550-fcafda8aae9a}
Writer Instance Id: {1a9ca255-4ad6-4172-9d04-d433e9958d33}
State: [1] Stable
--
vssadmin list shadows (while backup is running):
vssadmin 1.0 - Volume Shadow Copy Service administrative command-line
tool
(C) Copyright 2001 Microsoft Corp.
Contents of shadow copy set {26035bf3-a48b-4993-afcb-6f48affefd4c}
(The shadow copy set contained 1 shadow copies at creation time, 1
shadow copie
s exist now)
'MS Software Shadow Copy provider 1.0' shadow copy
{d6dc446b-5cae-46bb-a555-d344
c70d65e5} on volume \\?\Volume{d27e6118-47d1-11d9-aa59-806d6172696f}\
--
That looks good.
vssadmin list shadows (after backup completes):
vssadmin 1.0 - Volume Shadow Copy Service administrative command-line
tool
(C) Copyright 2001 Microsoft Corp.
No shadow copies present in the system
Re: [Bacula-users] Windows Client, VSS Issues, 2.0.3?
Thanks for the quick response.
vssadmin list writers:
vssadmin 1.0 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.
Writer name: 'MSDEWriter'
Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
Writer Instance Id: {b9048c82-c0b6-42e8-b885-3ddc806474bd}
State: [1] Stable
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {a4358c3f-d8b3-4e32-971a-a1aa47f7b0fb}
State: [9] Failed
Writer name: 'IIS Metabase Writer'
Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
Writer Instance Id: {38ebb2dd-0122-48e1-915e-23ce2aed2e95}
State: [9] Failed
Writer name: 'Microsoft Writer (Bootable State)'
Writer Id: {f2436e37-09f5-41af-9b2a-4ca2435dbfd5}
Writer Instance Id: {9470d858-515e-47d9-bf71-ba1a26782a69}
State: [1] Stable
Writer name: 'Microsoft Writer (Service State)'
Writer Id: {e38c2e3c-d4fb-4f4d-9550-fcafda8aae9a}
Writer Instance Id: {1a9ca255-4ad6-4172-9d04-d433e9958d33}
State: [1] Stable
--
vssadmin list shadows (while backup is running):
vssadmin 1.0 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.
Contents of shadow copy set {26035bf3-a48b-4993-afcb-6f48affefd4c}
(The shadow copy set contained 1 shadow copies at creation time, 1
shadow copie
s exist now)
'MS Software Shadow Copy provider 1.0' shadow copy
{d6dc446b-5cae-46bb-a555-d344
c70d65e5} on volume \\?\Volume{d27e6118-47d1-11d9-aa59-806d6172696f}\
--
vssadmin list shadows (after backup completes):
vssadmin 1.0 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.
No shadow copies present in the system.
-
A couple more notes that may or may not make a difference. I am running
SQL Server Express 2005 on this system, and the event logs show the
databases freezing and unfreezing during the bacula backups. The log is
telling me the database was successfully backed up, but I am not backing
up anything from my SQL databases (to my knowledge).
Thanks
Mike
Robert Nelson wrote:
What is the output from the command vssadmin list writers?
Also what is the output from the command vssadmin list shadows after the
successful backup but prior to the next backup?
-Original Message-
From: [EMAIL PROTECTED] [mailto:bacula-users-
[EMAIL PROTECTED] On Behalf Of Michael Gerszewski
Sent: Friday, March 30, 2007 11:27 AM
To: bacula-users
Subject: [Bacula-users] Windows Client, VSS Issues, 2.0.3?
Greetings,
I have been evaluating Bacula for the School District I work for as a
backup option for our Windows 2003 Servers. I like many of the features
Bacula has compared to other solutions. I have been testing with 2.0.3
with the director on a linux box, a storage daemon on a Windows 2003
box, and a file daemon on an XP box. I installed the Linux portion from
RPMs and the Windows client with the windows installer.
I have it configured to do Disk backups. The first couple of days,
everything worked OK with small backups without much change (~100 MB
full, 1-2 MB incremental). Then I switched to a larger amount of files
(~28 GB with ~800 MB of change per day). Now the FD seems to hang up.
Here are the symptoms:
If I start off a fresh boot, the first backup on this machine will work
fine. If I do not reboot the computer, or kill the bacula-fd and
vssvc.exe processes, the next backup will do one of two things:
1) Backup all the way to the end, and just hang
or
2) Not start the backup at all and sit at 0 Bytes/files
I can break this cycle by killing the vssvc.exe process (Volume Shadow
Copy). Then the backup finishes successfully, and incidentally
vssvc.exe start again. If it hung at the beginning, it will generally
give a warning or error that VSS could not start and the backup will be
done without VSS.
One thing that seems odd is that the vssvc.exe process is always
running, even when there isn't a backup running. When I look at our
servers that are running the MS backup utility, vssvc.exe is only
running while a backup is in progress.
For our implementation, I really need to be able to use VSS, so I have
not tried it with VSS disabled.
Any assistance would be appreciated.
Thanks
Mike Gerszewski
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay
Re: [Bacula-users] Windows Client, VSS Issues, 2.0.3?
Bacula backup sitting at 0 bytes. Floppy drive and hard drive did a
seek like a normal VSS startup.
vssadmin list shadows:
vssadmin 1.0 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.
No shadow copies present in the system.
---
When I try to run the vssadmin list writers, it waits for a response.
Like VSS is just hung up. I never do get a response from the vssadmin
list writers unless I kill the FD and the VSS process.
It is difficult for me to reproduce the hung at end scenario. But
I'll certainly get you the output the next time I see it.
With the failed VSS components...When I check and Bacula hasn't been run
yet on the system, both are listed as stable. I did see another as
failed, and sometimes they return a status: 7, failed.
I do run some MS backups on this system as well. Hopefully those aren't
causing any conflicts.
Thanks again. A great community here.
Mike
Robert Nelson wrote:
-Original Message-
From: [EMAIL PROTECTED] [mailto:bacula-users-
[EMAIL PROTECTED] On Behalf Of Michael Gerszewski
Sent: Friday, March 30, 2007 12:07 PM
To: bacula-users@lists.sourceforge.net
Cc: Robert Nelson
Subject: Re: [Bacula-users] Windows Client, VSS Issues, 2.0.3?
Thanks for the quick response.
vssadmin list writers:
vssadmin 1.0 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.
Writer name: 'MSDEWriter'
Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
Writer Instance Id: {b9048c82-c0b6-42e8-b885-3ddc806474bd}
State: [1] Stable
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {a4358c3f-d8b3-4e32-971a-a1aa47f7b0fb}
State: [9] Failed
Writer name: 'IIS Metabase Writer'
Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
Writer Instance Id: {38ebb2dd-0122-48e1-915e-23ce2aed2e95}
State: [9] Failed
Interesting the above two seemed to have failed their initialization.
Writer name: 'Microsoft Writer (Bootable State)'
Writer Id: {f2436e37-09f5-41af-9b2a-4ca2435dbfd5}
Writer Instance Id: {9470d858-515e-47d9-bf71-ba1a26782a69}
State: [1] Stable
Writer name: 'Microsoft Writer (Service State)'
Writer Id: {e38c2e3c-d4fb-4f4d-9550-fcafda8aae9a}
Writer Instance Id: {1a9ca255-4ad6-4172-9d04-d433e9958d33}
State: [1] Stable
--
vssadmin list shadows (while backup is running):
vssadmin 1.0 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.
Contents of shadow copy set {26035bf3-a48b-4993-afcb-6f48affefd4c}
(The shadow copy set contained 1 shadow copies at creation time, 1
shadow copie
s exist now)
'MS Software Shadow Copy provider 1.0' shadow copy
{d6dc446b-5cae-46bb-a555-d344
c70d65e5} on volume \\?\Volume{d27e6118-47d1-11d9-aa59-806d6172696f}\
--
That looks good.
vssadmin list shadows (after backup completes):
vssadmin 1.0 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.
No shadow copies present in the system.
-
That looks very good, doesn't seem we have any leftover crud.
A couple more notes that may or may not make a difference. I am running
SQL Server Express 2005 on this system, and the event logs show the
databases freezing and unfreezing during the bacula backups. The log is
telling me the database was successfully backed up, but I am not backing
up anything from my SQL databases (to my knowledge).
That's expected, the system doesn't know what we'll be backing up at the
time we initiate the shadow.
Thanks
Mike
Can you also post the output from vssadmin list shadows when the backup is
hung? Meanwhile, I'll check and make sure we release all our interface
pointers.
Robert Nelson wrote:
What is the output from the command vssadmin list writers?
Also what is the output from the command vssadmin list shadows after
the
successful backup but prior to the next backup?
-Original Message-
From: [EMAIL PROTECTED] [mailto:bacula-users-
[EMAIL PROTECTED] On Behalf Of Michael Gerszewski
Sent: Friday, March 30, 2007 11:27 AM
To: bacula-users
Subject: [Bacula-users] Windows Client, VSS Issues, 2.0.3?
Greetings,
I have been evaluating Bacula for the School District I work for as a
backup option for our Windows 2003 Servers. I like many of the
features
Bacula has compared to other solutions. I have been testing with 2.0.3
with the director on a linux box, a storage daemon on a Windows 2003
box, and a file daemon on an XP box. I installed the Linux portion
from
RPMs and the Windows client with the windows installer.
I have it configured to do Disk backups. The first couple of days,
everything worked OK with small backups without much change (~100 MB
full, 1-2 MB incremental). Then I switched to a larger amount of files
(~28 GB with ~800 MB of change per day). Now the FD seems to hang up
Re: [Bacula-users] Windows Client, VSS Issues, 2.0.3?
Okay great, I think this should give me something to work with. I'll try
and repro it here.
-Original Message-
From: [EMAIL PROTECTED] [mailto:bacula-users-
[EMAIL PROTECTED] On Behalf Of Michael Gerszewski
Sent: Friday, March 30, 2007 12:48 PM
To: bacula-users@lists.sourceforge.net
Cc: Robert Nelson
Subject: Re: [Bacula-users] Windows Client, VSS Issues, 2.0.3?
Bacula backup sitting at 0 bytes. Floppy drive and hard drive did a
seek like a normal VSS startup.
vssadmin list shadows:
vssadmin 1.0 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.
No shadow copies present in the system.
---
When I try to run the vssadmin list writers, it waits for a response.
Like VSS is just hung up. I never do get a response from the vssadmin
list writers unless I kill the FD and the VSS process.
It is difficult for me to reproduce the hung at end scenario. But
I'll certainly get you the output the next time I see it.
With the failed VSS components...When I check and Bacula hasn't been run
yet on the system, both are listed as stable. I did see another as
failed, and sometimes they return a status: 7, failed.
I do run some MS backups on this system as well. Hopefully those aren't
causing any conflicts.
Thanks again. A great community here.
Mike
Robert Nelson wrote:
-Original Message-
From: [EMAIL PROTECTED] [mailto:bacula-users-
[EMAIL PROTECTED] On Behalf Of Michael Gerszewski
Sent: Friday, March 30, 2007 12:07 PM
To: bacula-users@lists.sourceforge.net
Cc: Robert Nelson
Subject: Re: [Bacula-users] Windows Client, VSS Issues, 2.0.3?
Thanks for the quick response.
vssadmin list writers:
vssadmin 1.0 - Volume Shadow Copy Service administrative command-line
tool
(C) Copyright 2001 Microsoft Corp.
Writer name: 'MSDEWriter'
Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
Writer Instance Id: {b9048c82-c0b6-42e8-b885-3ddc806474bd}
State: [1] Stable
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {a4358c3f-d8b3-4e32-971a-a1aa47f7b0fb}
State: [9] Failed
Writer name: 'IIS Metabase Writer'
Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
Writer Instance Id: {38ebb2dd-0122-48e1-915e-23ce2aed2e95}
State: [9] Failed
Interesting the above two seemed to have failed their initialization.
Writer name: 'Microsoft Writer (Bootable State)'
Writer Id: {f2436e37-09f5-41af-9b2a-4ca2435dbfd5}
Writer Instance Id: {9470d858-515e-47d9-bf71-ba1a26782a69}
State: [1] Stable
Writer name: 'Microsoft Writer (Service State)'
Writer Id: {e38c2e3c-d4fb-4f4d-9550-fcafda8aae9a}
Writer Instance Id: {1a9ca255-4ad6-4172-9d04-d433e9958d33}
State: [1] Stable
--
vssadmin list shadows (while backup is running):
vssadmin 1.0 - Volume Shadow Copy Service administrative command-line
tool
(C) Copyright 2001 Microsoft Corp.
Contents of shadow copy set {26035bf3-a48b-4993-afcb-6f48affefd4c}
(The shadow copy set contained 1 shadow copies at creation time, 1
shadow copie
s exist now)
'MS Software Shadow Copy provider 1.0' shadow copy
{d6dc446b-5cae-46bb-a555-d344
c70d65e5} on volume \\?\Volume{d27e6118-47d1-11d9-aa59-806d6172696f}\
--
That looks good.
vssadmin list shadows (after backup completes):
vssadmin 1.0 - Volume Shadow Copy Service administrative command-line
tool
(C) Copyright 2001 Microsoft Corp.
No shadow copies present in the system.
-
That looks very good, doesn't seem we have any leftover crud.
A couple more notes that may or may not make a difference. I am
running
SQL Server Express 2005 on this system, and the event logs show the
databases freezing and unfreezing during the bacula backups. The log
is
telling me the database was successfully backed up, but I am not
backing
up anything from my SQL databases (to my knowledge).
That's expected, the system doesn't know what we'll be backing up at the
time we initiate the shadow.
Thanks
Mike
Can you also post the output from vssadmin list shadows when the
backup is
hung? Meanwhile, I'll check and make sure we release all our interface
pointers.
Robert Nelson wrote:
What is the output from the command vssadmin list writers?
Also what is the output from the command vssadmin list shadows after
the
successful backup but prior to the next backup?
-Original Message-
From: [EMAIL PROTECTED] [mailto:bacula-
users-
[EMAIL PROTECTED] On Behalf Of Michael Gerszewski
Sent: Friday, March 30, 2007 11:27 AM
To: bacula-users
Subject: [Bacula-users] Windows Client, VSS Issues, 2.0.3?
Greetings,
I have been evaluating Bacula for the School District I work for as a
backup option for our Windows 2003 Servers. I like many of the
features
Bacula has compared to other solutions
