Re: [BackupPC-users] restore issue on backuppc 4.1.5
On 2019-05-22 05:32, Philip Parsons (Velindre - Medical Physics) wrote: Hi, I'm having an issue with restoring to a share and am trying to deal with this before it becomes a need to restore situation! We're using BackupPC v4.1.5. I've had the following error when trying to restore: Running: /usr/bin/smbclient servername\\sharename -U accountname -E -d 1 -c tarmode\ full -mSMB3 -Tx - Running: /usr/local/BackupPC/bin/BackupPC_tarCreate -h servername -n 211 -s sharename -t -r / -p /temp/ /restorefolder Xfer PIDs are now 48288,48289 WARNING: The "syslog" option is deprecated [ skipped 1 lines ] tar:316 tarmode is now full, system, hidden, noreset, quiet tar:1597 Can't mkdir temp: NT_STATUS_OBJECT_NAME_COLLISION readOutput: sysread returns 0 and got EOF (exit ok = , ) XferErr Non-zero exit status from smbclient restore failed: BackupPC_tarCreate failed Does anyone know what could be causing this? Thanks in advance, Phil It looks like you're trying to restore to a directory called temp, which already exists, but is hidden. You probably just want to choose a different directory to restore to. ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
[BackupPC-users] restore issue on backuppc 4.1.5
Hi, I'm having an issue with restoring to a share and am trying to deal with this before it becomes a need to restore situation! We're using BackupPC v4.1.5. I've had the following error when trying to restore: Running: /usr/bin/smbclient servername\\sharename -U accountname -E -d 1 -c tarmode\ full -mSMB3 -Tx - Running: /usr/local/BackupPC/bin/BackupPC_tarCreate -h servername -n 211 -s sharename -t -r / -p /temp/ /restorefolder Xfer PIDs are now 48288,48289 WARNING: The "syslog" option is deprecated [ skipped 1 lines ] tar:316 tarmode is now full, system, hidden, noreset, quiet tar:1597 Can't mkdir temp: NT_STATUS_OBJECT_NAME_COLLISION readOutput: sysread returns 0 and got EOF (exit ok = , ) XferErr Non-zero exit status from smbclient restore failed: BackupPC_tarCreate failed Does anyone know what could be causing this? Thanks in advance, Phil ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
[BackupPC-users] Strange "file vanished" errors
Hello you all, We are seeing, since a few days and a full machine restore on the targeted computer, weird rsync/file vanished errors. A short example : This is the rsync child about to exec /usr/bin/rsync_bpc Xfer PIDs are now 12922,12924 xferPids 12922,12924 [ skipped 18 lines ] file has vanished: "/root/libpcre2-8.pc" file has vanished: "/root/libpcre2-32.pc" file has vanished: "/root/Makefile" file has vanished: "/root/libpcre2-posix.pc" file has vanished: "/root/libtool" file has vanished: "/root/config.log" file has vanished: "/root/src" file has vanished: "/root/config.status" file has vanished: "/root/libpcre2-16.pc" file has vanished: "/root/pcre2-config" [ skipped 423 lines ] file has vanished: "/usr/portage/app-crypt/heimdal/files/heimdal_build-headers-before-use.patch" file has vanished: "/usr/portage/app-crypt/heimdal/files/heimdal_fix-db60.patch" file has vanished: "/usr/portage/app-crypt/heimdal/files/heimdal_hcrypto.patch" rsync_bpc: fstat "/usr/portage/app-crypt/heimdal/files/heimdal_build-headers-before-use.patch" failed: No such file or directory (2) rsync_bpc: fstat "/usr/portage/app-crypt/heimdal/files/heimdal_fix-db60.patch" failed: No such file or directory (2) rsync_bpc: fstat "/usr/portage/app-crypt/heimdal/files/heimdal_hcrypto.patch" failed: No such file or directory (2) Those messages are weird because : 1/ for the "/root/xxx" ones, the designated files *do not exist* in the directory, before, during or after the backup. 2/ for the "/usr/portage/yyy" messages, the files do exist before, during and after the backup. We are at a loss about what is occuring here. In case this may be useful, the "full restore" we've spoken of was made because of a bad case of creeping filesystem corruption. We've restored the machine to a pre-corrupt state dating back several weeks. Any help will be appreciated. -- B&A Consultants - Sécurité informatique - www.ba-consultants.fr ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
