fore? Any suggestions on how to resolve
it?
Client OS: Microsoft Windows Server 2003, Standard Edition (32 bit)
Bacula version: 5.0.3
--
Regards,
Avery Ceo
Systems Administrator
Enterprise Hosting
--
RSA(R) Conference
On Mon, 2011-11-07 at 21:59 +0400, Konstantin Khomoutov wrote:
> On Mon, 07 Nov 2011 11:40:18 -0500
> Avery Ceo wrote:
>
> > We have been running Bacula on Windows with VSS disabled, but would
> > like to turn it on for disaster recovery purposes. In our tests on a
> &g
ime lag from when the snapshot
was taken to when those files were hit. The log I linked to was
generated from the test I ran on just the problem drive to decrease the
time between snapshot and read. The errors started with the same file
on both tes
qldumps. What I do expect is that the
inconsistent database files be read rather than causing the remainder of
the backup to fail. If it were our server rather than a client's, then
running a mysqldump in the run before is exactly how I would handle
consistent database backups, but that still
load/en/details.aspx?displaylang=en&id=2349
> 0 might do the trick on 2003. Once you've created the snapshot, see if
> you can access the files just by copying them to somewhere else. At
> least then you'll know if you have a general VSS problem or if it is
> specific to
The answers will make more sense if I rearrange the questions:
On Tue, 2011-11-08 at 08:07 -0500, Avery Ceo wrote:
> On Tue, 2011-11-08 at 10:17 +1100, James Harper wrote:
> Create a snapshot manually. This guy blogs about how to do it
> http://blogs.msdn.com/b/adioltean/archive/2005/01/
> https://lists.sourceforge.net/lists/listinfo/bacula-users
Igor,
You will usually need to set Heartbeat Interval on the client as well.
Regards,
Avery Ceo
Systems Administrator
Enterprise Hosting
678.317.9019 x7602
--
