Hi,
last friday i updated our backup-server from bacula 5.0.3 (mysql) to 
bacula 5.2.1 (postgresql).
During the update i change the jukebox (Neo2000E): before the jukebox 
was partitioned and used from two nodes (both via bacula-sd), after the 
update bacula use the whole jukebox from one node.

Restore-tests from old data runs well (also backup). But on the weekend 
i decided to change the storage-name of the jukebox again (from NEO-LTO4 
to NEO2000E).

Today an restore failed with following error messages:
22-Nov 14:53 backup-srv-dir JobId 93751: Start Restore Job 
RestoreFiles.2011-11-22_14.53.53_15
22-Nov 14:53 backup-srv-dir JobId 93751: Using Device "LTO4-DRIVE1"
22-Nov 14:53 backup-srv-dir JobId 93751: Warning: Could not get storage 
resource 'NEO-LTO4'.
22-Nov 14:53 backup-srv-sd JobId 93751: Fatal error: No Volume names 
found for restore.
22-Nov 14:53 abc-server1-fd JobId 93751: Fatal error: job.c:2004 Bad 
response to Read Data command. Wanted 3000 OK data, got 3000 error

22-Nov 14:53 backup-srv-dir JobId 93751: Fatal error: Could not get 
storage resource 'NEO-LTO4'.
22-Nov 14:53 backup-srv-dir JobId 93751: Error: Bacula backup-srv-dir 
5.2.1 (30Oct11):

In bat the right storage (NEO2000E) was selected. The same error occur 
when starting the restore-job with bconsole.
I switch back the name to NEO-LTO4 and be able to restore the files...

But i think this should not ne happend, or?

Any hints? Change the storage-name in the database?


Best regards

Udo





------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure 
contains a definitive record of customers, application performance, 
security threats, fraudulent activity, and more. Splunk takes this 
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users