From: Phil S. <al...@me...> - 2012-12-01 23:21:40
|
I just tried to restore two files to my workstation. I have two SDs, one running an LTO4 drive attached to the workstation (babylon5), one controlling a 12TB ZFS array on my NAS server (babylon4). Here's the BSR: Storage="babylon4-file" Volume="INCR-20121129-04:30" MediaType="File" Device="FileStorage" VolSessionId=296 VolSessionTime=1349979764 VolAddr=1000065656-1999914423 FileIndex=3108-3109 Count=2 But director status says "waiting on Storage babylon5-sd", and the console says: $ $ $ Warning default storage overridden by "babylon5-sd" on command line. Warning default storage overridden by "babylon5-sd" on command line. Bootstrap records written to /var/lib/bacula/epsilon3-dir.restore.1.bsr The job will require the following Volume(s) Storage(s) SD Device(s) =========================================================================== INCR-20121129-04:30 babylon4-file FileStorage Volumes marked with "*" are online. 2 files selected to be restored. 2 files selected to be restored. .mod restoreclient="babylon5" fileset="Dummy" storage="babylon5-sd" replace="always" when="2012-12-01 18:08:41" bootstrap="/var/lib/bacula/epsilon3-dir.restore.1.bsr" where="/bacula-restores" priority="10" yes OK to run? (yes/mod/no): Job queued. JobId=2076 .messages 01-Dec 18:09 epsilon3-dir JobId 2076: Start Restore Job Restore.2012-12-01_18.08.59_59 So, wait, what, now? The files are located on babylon4-sd, so why is the Director waiting on babylon5-sd...? Why does submitting ther restore job override where the files actually are? I left the Storage selection in BAT's restore job dialog at the default. Shouldn't it be auto-selecting the correct Storage based on where the files to be restored are? It seems to me there's something wrong in the interface logic here. Do we need to have some kind of "AUTOSELECT STORAGE" default for restores? -- Phil Stracchino, CDK#2 DoD#299792458 ICBM: 43.5607, -71.355 al...@ca... al...@me... ph...@co... Renaissance Man, Unix ronin, Perl hacker, SQL wrangler, Free Stater It's not the years, it's the mileage. |
From: <lst...@kw...> - 2012-12-03 08:47:45
|
Zitat von Phil Stracchino <al...@me...>: > I just tried to restore two files to my workstation. I have two SDs, > one running an LTO4 drive attached to the workstation (babylon5), one > controlling a 12TB ZFS array on my NAS server (babylon4). > > Here's the BSR: > > Storage="babylon4-file" > Volume="INCR-20121129-04:30" > MediaType="File" > Device="FileStorage" > VolSessionId=296 > VolSessionTime=1349979764 > VolAddr=1000065656-1999914423 > FileIndex=3108-3109 > Count=2 > > But director status says "waiting on Storage babylon5-sd", and the > console says: > > $ $ $ Warning default storage overridden by "babylon5-sd" on command line. > Warning default storage overridden by "babylon5-sd" on command line. > Bootstrap records written to /var/lib/bacula/epsilon3-dir.restore.1.bsr Looks like some setting has forced Bacula to use the (wrong) SD. Check your restore Job for all settings which might pin to a SD like Pool statements and the like. Regards Andreas |
From: Rodrigo R. B. <rod...@gm...> - 2012-12-05 11:18:29
|
If the files are located in "babylon4-sd", why are you passing "babylon5-sd" in the command line? .mod restoreclient="babylon5" fileset="Dummy" storage=*"babylon5-sd"* 2012/12/3 <lst...@kw...> > > Zitat von Phil Stracchino <al...@me...>: > > > I just tried to restore two files to my workstation. I have two SDs, > > one running an LTO4 drive attached to the workstation (babylon5), one > > controlling a 12TB ZFS array on my NAS server (babylon4). > > > > Here's the BSR: > > > > Storage="babylon4-file" > > Volume="INCR-20121129-04:30" > > MediaType="File" > > Device="FileStorage" > > VolSessionId=296 > > VolSessionTime=1349979764 > > VolAddr=1000065656-1999914423 > > FileIndex=3108-3109 > > Count=2 > > > > But director status says "waiting on Storage babylon5-sd", and the > > console says: > > > > $ $ $ Warning default storage overridden by "babylon5-sd" on command > line. > > Warning default storage overridden by "babylon5-sd" on command line. > > Bootstrap records written to /var/lib/bacula/epsilon3-dir.restore.1.bsr > > Looks like some setting has forced Bacula to use the (wrong) SD. Check > your restore Job for all settings which might pin to a SD like Pool > statements and the like. > > Regards > > Andreas > > > > > ------------------------------------------------------------------------------ > Keep yourself connected to Go Parallel: > BUILD Helping you discover the best ways to construct your parallel > projects. > http://goparallel.sourceforge.net > _______________________________________________ > Bacula-users mailing list > Bac...@li... > https://lists.sourceforge.net/lists/listinfo/bacula-users > |
From: Phil S. <al...@me...> - 2012-12-05 16:12:01
|
On 12/05/12 06:18, Rodrigo Renie Braga wrote: > If the files are located in "babylon4-sd", why are you passing > "babylon5-sd" in the command line? > > .mod restoreclient="babylon5" fileset="Dummy" storage=*"babylon5-sd"* The answer is, *I* didn't. BAT did that "for" me without asking. My point was, why does BAT even fill that in for a restore? It should be automatically filled in with the SD that actually has the files to be restored ... or *not filled in at all*, because the information on which volume(s) - and therefore which pool(s) and hence which sd(s) - will be required to complete the restore *is in the BSR file anyway*. Specifying an SD on a restore by default not only contributes nothing, it actually *breaks* the restore. BAT should default to *not* specifying a SD for restores unless the user specifically chooses to do so. -- Phil Stracchino, CDK#2 DoD#299792458 ICBM: 43.5607, -71.355 al...@ca... al...@me... ph...@co... Renaissance Man, Unix ronin, Perl hacker, SQL wrangler, Free Stater It's not the years, it's the mileage. |