On Wed, 14 Aug 2024 at 20:13, <dave.man...@loopscorpio.net> wrote: > As you can see here the lsdirs picks up that theres a d:/ drive, but the > lsfiles shows nothing. >
Hi Dave, I would not expect to see any files in case of this command: .bvfs_lsfiles jobid="419440,41925,91907,41874" path="" limit="2000" because it is the main path on Windows host where there are listed the drive letters. To see files you need specify the path like this: .bvfs_lsfiles jobid="419440,41925,91907,41874" path="d:/Company Files/Private/Archive Files/All Departments/School Folders/RECIPES/" limit="2000" (the path can be different, of course) > A standard list files for those jobids snippet shows as follows > > > > Here you can see after trying the lsfiles command it just moves back to > the command prompt > > > > I thought it may have been to a database fault so I attempted an upgrade > to 11, Silly mistake!!! > > > > Then realised I didn’t have a backup of the original as the backup command > isn’t working either but I will leave that for a minute. As I was already > at disaster point I deleted the database and created a new one using the > create database and create tables command, then started full backups of all > my clients. > > > > Im now faced with this error when selecting a job from the job list and > the directory listing still does not work on the new jobs completed. Is > this a baculum fault or bacula? > For this error it is known problem reported here: https://gitlab.bacula.org/bacula-community-edition/bacula-community/-/issues/2722 Fortunately it is fixed now, however there isn't any Baculum version yet that includes this fix. Best regards, Marcin Haba (gani)
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
