Re: [Bacula-users] Could not stat - Windows permission problems

Hi,

17.07.2008 22:51, Nils Blanck-Wehde wrote:
>   Unfortunately the problem remains even with disabled VSS.
> This job only works about every second time.
> 
> How do I enable debug-logging on a windows-fd? where does it store the 
> logfile?

In bconsole 'setdebug level=<level> client=<client-fd> trace=1'

I'd start with a debug level of 100.

The trace file should be generated in the working directory of the FD, 
on my Vista installations it's in C:\ProgramData\Bacula\Work. It might 
also appear in C:\ProgramData\Bacula - I didn't verify this recently.

The file is locked while the FD accesses it, so you might need to turn 
off tracing before you can look into it with an editor. 
"more<C:\ProgramData\Bacula\Work\Host-fd.trace" works, IIRC.

Arno

> 
> Nils Blanck-Wehde schrieb:
>> Hi Lee!
>>
>> Thanks a lot! I will try that right away. You are right, I don't need 
>> VSS for that job.
>>
>> I'll keep you posted!
>>
>> Nils
>>
>> Lee Verberne schrieb:
>>>
>>> I had almost exactly this problem, only my situation was even 
>>> simpler.  I was doing a vanilla directory backup with 2.4.0 on 
>>> Windows Server 2003 and every _other_ backup would result in the 
>>> following:
>>>
>>> 07-Jul 19:04 fs-fd JobId 5: Generate VSS snapshots. Driver="VSS Win 
>>> 2003", Drive(s)="D"
>>> 07-Jul 19:04 fs-fd JobId 5:      Could not stat d:/Shares: ERR=Access 
>>> is denied.
>>>
>>> This would result in the same "Backup OK -- with warnings" as your 
>>> output below.  It would fail reliably 50% of the time.  I did a naive 
>>> test of VSS by running ntbackup several times and it succeeded every 
>>> time, so I just disabled VSS with "Enable VSS = no" in the FileSet.  
>>> All my backup jobs since have been successful.
>>>
>>> Since you're backing up dumped files, I don't imagine you need VSS 
>>> anyway.
>>>
>>> -lee
>>>
>>>
>>>
>>> On Jul 15, 2008, at 9:14 AM, Nils Blanck-Wehde wrote:
>>>
>>>> Hi,
>>>>
>>>> I just set the debug level and ran the job again, this time it 
>>>> worked like a charm. I didn't make any changes to the configuration 
>>>> except for the debug level.
>>>> Do you know where the default working directory of bacula-fd on a 
>>>> windows system is? The configuration file saved during installation 
>>>> doesn't mention it. I didn't find the debug output of this fd so far.
>>>> I checked my logs: The job crashed with the same error the last 
>>>> three times it was sheduled. When I manually ran it again, it worked.
>>>> I wonder if there ist something going on on the server at this point 
>>>> of time. Would a running antivirus scan cause bacula-fd to be unable 
>>>> to stat a directory?
>>>>
>>>> The job is sheduled for this night again, I'll see what happens.
>>>>
>>>> Thanks, Nils
>>>>
>>>> Arno Lehmann schrieb:
>>>>>
>>>>> Hi,
>>>>>
>>>>> 15.07.2008 10:51, Nils Blanck-Wehde wrote:
>>>>>
>>>>>> Hello list,
>>>>>>
>>>>>> looks like I need some help here.
>>>>>> I am backing up our Exchange server by first exporting all mailboxes
>>>>>> with ExMerge to separate .pst-files and then backing those files 
>>>>>> up with
>>>>>> bacula. The exported pst files are also being copied to our 
>>>>>> fileserver
>>>>>> where they are included in our weekly backup to tape.
>>>>>> bacula-fd is running as domain-admin on our Windows 2003 SBS. This is
>>>>>> proven by calling "whoami" in the Client -Run-Before-script.
>>>>>> All Mailboxes get exported and copied quite fine, still the actual
>>>>>> backup crashes with:
>>>>>>
>>>>>> Could not stat D://Backup/Exchange Backup//: ERR=Zugriff 
>>>>>> verweigert (Access denied)
>>>>>>
>>>>> ...
>>>>>
>>>>>> 14-Jul 21:41 company-server1-fd JobId 71: Generate VSS snapshots. 
>>>>>> Driver="VSS Win 2003", Drive(s)="D"
>>>>>> 14-Jul 21:41 company-server1-fd JobId 71:      Could not stat 
>>>>>> D://Backup/Exchange Backup//: ERR=Zugriff verweigert
>>>>>>
>>>>>> 14-Jul 21:43 company_bacula-sd JobId 71: Job write elapsed time = 
>>>>>> 00:00:18, Transfer rate = 0  bytes/second
>>>>>> 14-Jul 21:41 company-server1-fd JobId 71: VSS Writer 
>>>>>> (BackupComplete): "System Writer", State: 0x1 (VSS_WS_STABLE)
>>>>>> 14-Jul 21:41 company-server1-fd JobId 71: VSS Writer 
>>>>>> (BackupComplete): "MSDEWriter", State: 0x1 (VSS_WS_STABLE)
>>>>>> 14-Jul 21:41 company-server1-fd JobId 71: VSS Writer 
>>>>>> (BackupComplete): "FRS Writer", State: 0x1 (VSS_WS_STABLE)
>>>>>> 14-Jul 21:41 company-server1-fd JobId 71: VSS Writer 
>>>>>> (BackupComplete): "Registry Writer", State: 0x1 (VSS_WS_STABLE)
>>>>>> 14-Jul 21:41 company-server1-fd JobId 71: VSS Writer 
>>>>>> (BackupComplete): "Dhcp Jet Writer", State: 0x1 (VSS_WS_STABLE)
>>>>>> 14-Jul 21:41 company-server1-fd JobId 71: VSS Writer 
>>>>>> (BackupComplete): "TermServLicensing", State: 0x1 (VSS_WS_STABLE)
>>>>>> 14-Jul 21:41 company-server1-fd JobId 71: VSS Writer 
>>>>>> (BackupComplete): "Event Log Writer", State: 0x1 (VSS_WS_STABLE)
>>>>>> 14-Jul 21:41 company-server1-fd JobId 71: VSS Writer 
>>>>>> (BackupComplete): "COM+ REGDB Writer", State: 0x1 (VSS_WS_STABLE)
>>>>>> 14-Jul 21:41 company-server1-fd JobId 71: VSS Writer 
>>>>>> (BackupComplete): "NTDS", State: 0x1 (VSS_WS_STABLE)
>>>>>> 14-Jul 21:41 company-server1-fd JobId 71: VSS Writer 
>>>>>> (BackupComplete): "WINS Jet Writer", State: 0x1 (VSS_WS_STABLE)
>>>>>> 14-Jul 21:41 company-server1-fd JobId 71: VSS Writer 
>>>>>> (BackupComplete): "IIS Metabase Writer", State: 0x1 (VSS_WS_STABLE)
>>>>>> 14-Jul 21:41 company-server1-fd JobId 71: VSS Writer 
>>>>>> (BackupComplete): "WMI Writer", State: 0x1 (VSS_WS_STABLE)
>>>>>> 14-Jul 21:43 company_bacula-dir JobId 71: Bacula 
>>>>>> company_bacula-dir 2.4.1 (07Jul08): 14-Jul-2008 21:43:32
>>>>>>
>>>>> This looks funny... the VSS snapshot is started and either that
>>>>> creates the error message (which I dount) or your run before script
>>>>> does (which is possible, but the script should be terminated by that
>>>>> time), or Bacula ceates that message (which it shouldn't, because it
>>>>> still has to wait for the snapshot to be finished...)
>>>>>
>>>>> In short, I believe there seems to be something broken, but I don't
>>>>> know what that would be.
>>>>>
>>>>> Can you verify your script terminates and doesn't leave any other
>>>>> process running in the background? (This is unlikely, I believe...)
>>>>>
>>>>> Other than that, I believe running the FD with debug tracing might
>>>>> reveal some details why Bacula tries to access a file before the
>>>>> snapshot is done.
>>>>>
>>>>> 'setdebug level=100 trace=1 client=company-server1-fd' should create a
>>>>> trace file in the FD's working directory.
>>>>>
>>>>> Arno
>>>>>
>>>>>
>>>>
>>>> -- 
> 
> 
> ------------------------------------------------------------------------
> 
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Bacula-users mailing list
> Bacula-users AT lists.sourceforge DOT net
> https://lists.sourceforge.net/lists/listinfo/bacula-users

-- 
Arno Lehmann
IT-Service Lehmann
www.its-lehmann.de

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users