Re: Debug and trace

Bill Arlofski via Bacula-users <[email protected]> Wed, 02 Oct 2024 15:34:40 +0000

Newsgroups	gmane.comp.bacula.user
Message-ID	<[email protected]>

On 10/2/24 8:34 AM, Mehrdad R. wrote:
> Hi guys
> So I am trying to trace the backup to verify that files are correctly
> scanned and backup especially in diff. mode, I am testing backing up a
> directory on a window server(Local windows FD and SD backing up to a
> local disk on the server) which contains around 200k files in around
> 5k directories and i am not sure if diff. backup is actually scanning
> and catching all the changed files which are copied there, the usually
> logs and file lists don't show anything
> 
> I came across the SET BEDUG LEVEL command and ran that in bconsole
> thinking I would get some info on what is happening in FD and SD trace
> files, but there is nothing in those files
> 
> Does this command work still(it was some old documentation describing
> it)? The bconsole seemed to buy it, but no results
> Has anyone tried this? Or maybe knows of any other way to see which
> files are actually scanned, selected, etc?? Or anyother insight to
> w
hat is actually happening in the backup process?

Hello Mehrdad,

There is really no need for debugging. You can see what the end results are with just a couple bconsole commands.

Run the Full, then make the changes and/or file additions, then run the Diff...

Then, list the files from the Full and Diff:

# echo "list files jobid=<JobidOfFull>" | bconsole | tee /tmp/full.txt

# echo "list files jobid=<JobidOfDiff>" | bconsole | tee /tmp/diff.txt

The full step is not really necessary I'd say.

But the diff.txt file list should align with any new or modified directories and files that happened after the Full.


Hope this helps,
Bill

-- 
Bill Arlofski
[email protected]

_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users

signature.asc (application/pgp-signature, 509 B)