Hi Johan, and thanks for the fast responce,
I'm running the restore job from the Web UI, as you assume.
I have checked, and PoolV3Enabled is ON (1)
I can browse and restore single files via the browser, but as it
concerns about 2TB of data it is some job!!.
The RSync Paths/Commands/Args are pretty much default, like:
###########################################################################
# Rsync/Rsyncd Configuration
# (can be overwritten in the per-PC log file)
###########################################################################
#
# Path to rsync executable on the client. If it is set, it is passed to
# to rsync_bpc using the --rsync-path option. You can also add sudo,
# for example:
#
# $Conf{RsyncClientPath} = 'sudo /usr/bin/rsync';
#
# For OSX laptop clients, you can use caffeinate to make sure the laptop
# stays awake during the backup, eg:
#
# $Conf{RsyncClientPath} = '/usr/bin/sudo /usr/bin/caffeinate -ism
/usr/bin/rsync';
#
# This setting only matters if $Conf{XferMethod} = 'rsync'.
#
$Conf{RsyncClientPath} = '/usr/bin/rsync';
#
# Full path to rsync_bpc on the server. Rsync_bpc is the customized
# version of rsync that is used on the server for rsync and rsyncd
# transfers.
#
$Conf{RsyncBackupPCPath} = "/usr/bin/rsync_bpc";
#
# Ssh arguments for rsync to run ssh to connect to the client.
# Rather than permit root ssh on the client, it is more secure
# to just allow ssh via a low-privileged user, and use sudo
# in $Conf{RsyncClientPath}.
#
# This setting only matters if $Conf{XferMethod} = 'rsync'.
#
$Conf{RsyncSshArgs} = [
'-e', '$sshPath -l root',
];
#
# Share name to backup. For $Conf{XferMethod} = "rsync" this should
# be a file system path, eg '/' or '/home'.
#
# For $Conf{XferMethod} = "rsyncd" this should be the name of the module
# to backup (ie: the name from /etc/rsynd.conf).
#
# This can also be a list of multiple file system paths or modules.
# For example, by adding --one-file-system to $Conf{RsyncArgs} you
# can backup each file system separately, which makes restoring one
# bad file system easier. In this case you would list all of the mount
# points:
#
# $Conf{RsyncShareName} = ['/', '/var', '/data', '/boot'];
#
$Conf{RsyncShareName} = '/datard1/documentation';
#
# Rsync daemon port on the client, for $Conf{XferMethod} = "rsyncd".
#
$Conf{RsyncdClientPort} = 873;
#
# Rsync daemon username on client, for $Conf{XferMethod} = "rsyncd".
# The username and password are stored on the client in whatever file
# the "secrets file" parameter in rsyncd.conf points to
# (eg: /etc/rsyncd.secrets).
#
$Conf{RsyncdUserName} = '';
#
# Rsync daemon username on client, for $Conf{XferMethod} = "rsyncd".
# The username and password are stored on the client in whatever file
# the "secrets file" parameter in rsyncd.conf points to
# (eg: /etc/rsyncd.secrets).
#
$Conf{RsyncdPasswd} = '';
#
# Additional arguments for a full rsync or rsyncd backup.
#
# The --checksum argument causes the client to send full-file checksum
# for every file (meaning the client reads every file and computes the
# checksum, which is sent with the file list). On the server, rsync_bpc
# will skip any files that have a matching full-file checksum, and size,
# mtime and number of hardlinks. Any file that has different attributes
# will be updating using the block rsync algorithm.
#
# In V3, full backups applied the block rsync algorithm to every file,
# which is a lot slower but a bit more conservative. To get that
# behavior, replace --checksum with --ignore-times.
#
$Conf{RsyncFullArgsExtra} = [
'--checksum',
];
#
# Arguments to rsync for backup. Do not edit the first set unless you
# have a good understanding of rsync options.
#
$Conf{RsyncArgs} = [
'--super',
'--recursive',
'--protect-args',
'--numeric-ids',
'--perms',
'--owner',
'--group',
'-D',
'--times',
'--links',
'--hard-links',
'--delete',
'--partial',
'--log-format=log: %o %i %B %8U,%8G %9l %f%L',
'--stats',
#
# Add additional arguments here, for example --acls or --xattrs
# if all the clients support them.
#
#'--acls',
#'--xattrs',
];
#
# Additional arguments added to RsyncArgs. This can be used in
# combination with $Conf{RsyncArgs} to allow customization of
# the rsync arguments on a part-client basis. The standard
# arguments go in $Conf{RsyncArgs} and $Conf{RsyncArgsExtra}
# can be set on a per-client basis.
#
# Examples of additional arguments that should work are --exclude/--include,
# eg:
#
# $Conf{RsyncArgsExtra} = [
# '--exclude', '/proc',
# '--exclude', '*.tmp',
# '--acls',
# '--xattrs',
# ];
#
# Both $Conf{RsyncArgs} and $Conf{RsyncArgsExtra} are subject
# to the following variable substitutions:
#
# $client client name being backed up
# $host hostname (could be different from client name if
# $Conf{ClientNameAlias} is set)
# $hostIP IP address of host
# $confDir configuration directory path
#
# This allows settings of the form:
#
# $Conf{RsyncArgsExtra} = [
# '--exclude-from=$confDir/pc/$host.exclude',
# ];
#
$Conf{RsyncArgsExtra} = [];
#
# Arguments to rsync for restore. Do not edit the first set unless you
# have a thorough understanding of how File::RsyncP works.
#
# If you want to disable direct restores using rsync (eg: is the module
# is read-only), you should set $Conf{RsyncRestoreArgs} to undef and
# the corresponding CGI restore option will be removed.
#
# $Conf{RsyncRestoreArgs} is subject to the following variable
# substitutions:
#
# $client client name being backed up
# $host hostname (could be different from client name if
# $Conf{ClientNameAlias} is set)
# $hostIP IP address of host
# $confDir configuration directory path
#
# Note: $Conf{RsyncArgsExtra} doesn't apply to $Conf{RsyncRestoreArgs}.
#
$Conf{RsyncRestoreArgs} = [
'--recursive',
'--super',
'--protect-args',
'--numeric-ids',
'--perms',
'--owner',
'--group',
'-D',
'--times',
'--links',
'--hard-links',
'--delete',
'--partial',
'--log-format=log: %o %i %B %8U,%8G %9l %f%L',
'--stats',
#
# Add additional arguments here
#
#'--acls',
#'--xattrs',
];
I have tried an incr. backup, and that leads to the exact same RSync error.
I do not have the equivalent V3 settings at hand, but they could be
found. I do remenber the V3 RSync-commands were executed without ssh, as
the file- and backup-server is the same machine (just using different
discs).
I have generated ssh-keys, and transferred it into
/root/.ssh/authorized_keys, but if I had made a mistake with it, I would
have expected an error concerning ssh and not RSync? Of cause I could be
wrong.
About the syntax for executing the restore from the command-line i'm not
quite sure, maybe you could elaborate a bit about that (If you still
think it's worth while).
Best Regards
Ib H. Rasmussen
On 04/24/2017 12:05 PM, Johan Ehnberg wrote:
> Hi Ib,
>
> I am assuming you are running an restore job from the web UI.
>
> First, make sure that PoolV3Enabled is on since you are accessing a V3
> pool from a V4 installation. This is found under Server settings general
> parameters.
>
> As a quick solution just to get access to the data or to do a manual
> restore, you can of course browse the web UI for the required files and
> download them through the browser. On the command line, you can use
> BackupPC_tarCreate for a faster approach directly on the server,
> especially when using large files. Do the files show up? Does this work
> or are you getting errors?
>
> In order to get the proper restore functions working, can you please
> post your Rsync Paths/Commands/Args? Can you make a successful backup
> using those? Essentially, comparing the backup and restore args is
> essential, if the backups are working.
>
> If it is not working, do you still have the V3 equivalents for these
> settings at hand to compare against?
>
> Also ensure that SSH keys are installed on the new server and that SSH
> is accepting the new host key (of the client) automatically or add it
> manually.
>
> To debug the action itself, you can run BackupPC_restore on the command
> line on the server with the -v flag to get verbose output.
>
> Post these details and we should be able to find out what is not working
> properly.
>
> Best regards,
> Johan Ehnberg
>
>
> On 04/24/2017 11:21 AM, Ib H. Rasmussen wrote:
>> I have just installed BackupPc v4.1.1 from Github on a new CentOS7 server.
>>
>> The backup-server is at the same time my file-server. Unfortunately I
>> have lost a number of my data-directories, but I do still have several
>> backup's from a previous BackupPC v3 installation.
>>
>> So my priority is to restore the backup's of the missing data. I'm using
>> rsync (which was also used to originally backup the data), and the data
>> directory is world writeable to rule-out any access-right problem.
>>
>> Selinux has been deactivated for the same reason.
>>
>> When restoring, I get the following error in the BackupPC LOG-file:
>>
>> 2017-04-20 11:38:30 User ihr requested restore to ihrsrv31-documentation
>> (ihrsrv31-documentation)
>> 2017-04-20 11:38:30 Started restore on ihrsrv31-documentation (pid=6542)
>> 2017-04-20 11:38:32 Restore failed on ihrsrv31-documentation (rsync
>> error: unexplained error (code 255) at io.c(629) [sender=3.0.9.6])
>>
>> BackupPC::XS and Rsync-bpc are both installed from Github
>>
>> How can I remedy this problem, and get my data back?
>>
>> Best Regards
>>
>> [email protected]
>>
>>
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> _______________________________________________
>> BackupPC-users mailing list
>> [email protected]
>> List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
>> Wiki: http://backuppc.wiki.sourceforge.net
>> Project: http://backuppc.sourceforge.net/
>>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
BackupPC-users mailing list
[email protected]
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
