#339 Issue closed: Unable to take rear backup of Physical SUSE Servers , but it working fine with VMWARE client¶
Labels: support / question
ocvelux opened issue at 2013-11-29 14:09:¶
Hi Team,
I have installed rear backup tool version rear-1.15-5 in HP Server , OS
Suse 10.
While taking rear backup , it fails with below error :
Relax-and-Recover 1.15 / Git
Using log file: /var/log/rear/rear-bwaqaxxx.log
The preparation phaseOK
Creating disk layout
Creating root filesystem layout
Copying files and directories
Copying binaries and libraries
Copying kernel modules
Creating initramfs
Making ISO image
Wrote ISO image: /var/lib/rear/output/rear-bwaqaxxx.iso (30M)
Copying resulting files to locationERROR: Could not copy /var/log/rear/rear-bwaqaxxx.log to location
Aborting due to an error, check /var/log/rear/rear-bwaqaxxx.log for details
Terminated
Below is the log file:
Max brk space used 0
14992 extents written (29 MB)
2013-11-29 12:46:00 Wrote ISO image: /var/lib/rear/output/rear-bwaqaxxx.iso (30M)
2013-11-29 12:46:00 Including output/ISO/Linux-i386/90_transfer_image.sh
2013-11-29 12:46:00 Including output/default/94_grub_rescue.sh
`/tmp/rear.omnyvXyrFv14443/tmp/initrd.cgz' -> `/boot/rear-initrd.cgz'
2013-11-29 12:46:01 Including output/NETFS/default/95_copy_result_files.sh
2013-11-29 12:46:01 Copying files '/var/lib/rear/output/rear-bwaqaxxx.iso' to location
cp: target `/tmp/rear.omnyvXyrFv14443/netfs/bwaqaxxx/' is not a directory: No such file or directory
/usr/share/rear/output/NETFS/default/95_copy_result_files.sh: line 15: ProgressStopIfError: command not found
/usr/share/rear/output/NETFS/default/95_copy_result_files.sh: line 19: /tmp/rear.omnyvXyrFv14443/netfs/bwaqaxxx/VERSION: No such file or directory
/usr/share/rear/output/NETFS/default/95_copy_result_files.sh: line 20: ProgressStopIfError: command not found
cp: cannot create regular file `/tmp/rear.omnyvXyrFv14443/netfs/bwaqaxxx/README': No such file or directory
/usr/share/rear/output/NETFS/default/95_copy_result_files.sh: line 22: ProgressStopOrError: command not found
/usr/share/rear/output/NETFS/default/95_copy_result_files.sh: line 23: /tmp/rear.omnyvXyrFv14443/netfs/bwaqaxxx/rear.log: No such file or directory
2013-11-29 12:46:01 ERROR: Could not copy /var/log/rear/rear-bwaqaxxx.log to location
=== Stack trace ===
Trace 0: /usr/sbin/rear:249 main
Trace 1: /usr/share/rear/lib/mkbackup-workflow.sh:30 WORKFLOW_mkbackup
Trace 2: /usr/share/rear/lib/framework-functions.sh:79 SourceStage
Trace 3: /usr/share/rear/lib/framework-functions.sh:40 Source
Trace 4: /usr/share/rear/output/NETFS/default/95_copy_result_files.sh:23 source
Message: Could not copy /var/log/rear/rear-bwaqaxxx.log to location
===================
2013-11-29 12:46:01 Running exit tasks.
rmdir: removing directory, /tmp/rear.omnyvXyrFv14443/outputfs
rmdir: /tmp/rear.omnyvXyrFv14443/outputfs: Device or resource busy
datashare2v:/export/DATASHARE2/vm_stage/linux_boot_images/ umounted
rmdir: removing directory, /tmp/rear.omnyvXyrFv14443/outputfs
2013-11-29 12:46:01 Finished in 20 seconds
2013-11-29 12:46:01 Removing build area /tmp/rear.omnyvXyrFv14443
rmdir: removing directory, /tmp/rear.omnyvXyrFv14443
2013-11-29 12:46:01 End of program reached
gdha commented at 2013-11-29 14:36:¶
what is the output of mount | grep tmp ? The /tmp must be writable
for root.
gdha commented at 2013-11-29 14:36:¶
Ok, did you upgrade rear? If yes, please remove it first and re-install it again.
schlomo commented at 2013-11-30 20:30:¶
​Do we have an upgrade problem? Replacing dirs with links or links
with
dirs?​
On 29 November 2013 15:36, gdha notifications@github.com wrote:
​O​
k, did you upgrade rear? If yes, please remove it first and re-install it
again.
gdha commented at 2013-12-03 11:52:¶
@ocvelux were you able to fix your problem?
ocvelux commented at 2013-12-04 11:33:¶
Yes I have removed and reinstalled again .. but same issue.
/tmp has full permission to write the files.
gdha commented at 2013-12-04 15:08:¶
what is the output of grep -r ProgressStopIfError /usr/share/rear ?
gdha commented at 2013-12-20 08:47:¶
@ocvelux are you sure you can mount
datashare2v:/export/DATASHARE2/vm_stage/linux_boot_images/ and write
into it as root?
gdha commented at 2014-03-03 07:56:¶
@ocvelux any update or can this issue be closed?
avinash4any1 commented at 2014-03-03 09:28:¶
Hi, Please close it, we have upgraded the OS and issues has been reolved.
[Export of Github issue for rear/rear.]