Hi,I am trying to utilize the bcopy utility to copy corrupt volumes to new volumes that I can bscan into bacula. I look at the documentation and it does not say whether I need to create new volumes in bacula or not, I assume I do. But, the docs say that the new volume is not recorded in the catalog. I created a volume in bacula and tried the copy but it failed with the errors attached. Also,I have loaded the patch 1560 for bcopy.
Any help is wonderful.
thanks, -- --------------------------------------------------------------------------- Jerold Lowry IT Manager / Software Engineer Engineering Design Team (EDT), Inc. a HEICO company 1400 NW Compton Drive, Suite 315 Beaverton, Oregon 97006 (U.S.A.) Phone: 503-690-1234 / 800-435-4320 Fax: 503-690-1243 Web: _www.edt.com <http://www.edt.com/>_
[jlowry@distress-sd bin]$ ./bcopy -v -c /etc/bacula/bacula-sd.conf -i hardware-0007 -o hardware-0007a /Hardware /Hardware bcopy: butil.c:281 Using device: "/Hardware" for reading. 17-May 12:59 bcopy JobId 0: Ready to read from volume "hardware-0007" on device "Hardware" (/Hardware). bcopy: butil.c:284 Using device: "/Hardware" for writing. 17-May 12:59 bcopy JobId 0: Wrote label to prelabeled Volume "hardware-0007a" on device "Hardware" (/Hardware) Volume Label Record: VolSessionId=109 VolSessionTime=1298660169 JobId=1 DataLen=176 bcopy: bcopy.c:259 Volume label not copied. 17-May 12:59 bcopy JobId 0: End of Volume "hardware-0007a" at 0:215 on device "Hardware" (/Hardware). Write of 64512 bytes got 3880. 17-May 12:59 bcopy JobId 0: End of medium on Volume "hardware-0007a" Bytes=216 Blocks=0 at 17-May-2011 12:59. bcopy: label.c:308 === ERROR: write_new_volume_label_to_dev called with NULL VolName bcopy: label.c:308 === ERROR: write_new_volume_label_to_dev called with NULL VolName 17-May 12:59 bcopy JobId 0: Warning: mount.c:221 Open device "Hardware" (/Hardware) Volume "" failed: ERR=Could not open file device "Hardware" (/Hardware). No Volume name given. bcopy: label.c:308 === ERROR: write_new_volume_label_to_dev called with NULL VolName bcopy: label.c:308 === ERROR: write_new_volume_label_to_dev called with NULL VolName 17-May 12:59 bcopy JobId 0: Warning: mount.c:221 Open device "Hardware" (/Hardware) Volume "" failed: ERR=Could not open file device "Hardware" (/Hardware). No Volume name given. bcopy: label.c:308 === ERROR: write_new_volume_label_to_dev called with NULL VolName bcopy: label.c:308 === ERROR: write_new_volume_label_to_dev called with NULL VolName 17-May 12:59 bcopy JobId 0: Warning: mount.c:221 Open device "Hardware" (/Hardware) Volume "" failed: ERR=Could not open file device "Hardware" (/Hardware). No Volume name given. bcopy: label.c:308 === ERROR: write_new_volume_label_to_dev called with NULL VolName bcopy: label.c:308 === ERROR: write_new_volume_label_to_dev called with NULL VolName 17-May 12:59 bcopy JobId 0: Warning: mount.c:221 Open device "Hardware" (/Hardware) Volume "" failed: ERR=Could not open file device "Hardware" (/Hardware). No Volume name given. bcopy: label.c:308 === ERROR: write_new_volume_label_to_dev called with NULL VolName bcopy: label.c:308 === ERROR: write_new_volume_label_to_dev called with NULL VolName 17-May 12:59 bcopy JobId 0: Warning: mount.c:221 Open device "Hardware" (/Hardware) Volume "" failed: ERR=Could not open file device "Hardware" (/Hardware). No Volume name given. Mount Volume "" on device "Hardware" (/Hardware) and press return when ready: bcopy: label.c:308 === ERROR: write_new_volume_label_to_dev called with NULL VolName bcopy: label.c:308 === ERROR: write_new_volume_label_to_dev called with NULL VolName 17-May 12:59 bcopy JobId 0: Warning: mount.c:221 Open device "Hardware" (/Hardware) Volume "" failed: ERR=Could not open file device "Hardware" (/Hardware). No Volume name given. Mount Volume "" on device "Hardware" (/Hardware) and press return when ready: bcopy: label.c:308 === ERROR: write_new_volume_label_to_dev called with NULL VolName bcopy: label.c:308 === ERROR: write_new_volume_label_to_dev called with NULL VolName 17-May 13:01 bcopy JobId 0: Warning: mount.c:221 Open device "Hardware" (/Hardware) Volume "" failed: ERR=Could not open file device "Hardware" (/Hardware). No Volume name given. Mount Volume "" on device "Hardware" (/Hardware) and press return when ready: qqq bcopy: label.c:308 === ERROR: write_new_volume_label_to_dev called with NULL VolName bcopy: label.c:308 === ERROR: write_new_volume_label_to_dev called with NULL VolName 17-May 13:01 bcopy JobId 0: Warning: mount.c:221 Open device "Hardware" (/Hardware) Volume "" failed: ERR=Could not open file device "Hardware" (/Hardware). No Volume name given. Mount Volume "" on device "Hardware" (/Hardware) and press return when ready: bcopy: label.c:308 === ERROR: write_new_volume_label_to_dev called with NULL VolName bcopy: label.c:308 === ERROR: write_new_volume_label_to_dev called with NULL VolName 17-May 13:01 bcopy JobId 0: Warning: mount.c:221 Open device "Hardware" (/Hardware) Volume "" failed: ERR=Could not open file device "Hardware" (/Hardware). No Volume name given. Mount Volume "" on device "Hardware" (/Hardware) and press return when ready: bcopy: label.c:308 === ERROR: write_new_volume_label_to_dev called with NULL VolName bcopy: label.c:308 === ERROR: write_new_volume_label_to_dev called with NULL VolName 17-May 13:01 bcopy JobId 0: Warning: mount.c:221 Open device "Hardware" (/Hardware) Volume "" failed: ERR=Could not open file device "Hardware" (/Hardware). No Volume name given. Mount Volume "" on device "Hardware" (/Hardware) and press return when ready: bcopy: label.c:308 === ERROR: write_new_volume_label_to_dev called with NULL VolName bcopy: label.c:308 === ERROR: write_new_volume_label_to_dev called with NULL VolName 17-May 13:01 bcopy JobId 0: Warning: mount.c:221 Open device "Hardware" (/Hardware) Volume "" failed: ERR=Could not open file device "Hardware" (/Hardware). No Volume name given. Mount Volume "" on device "Hardware" (/Hardware) and press return when ready:
------------------------------------------------------------------------------ What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
