On 12/06/2010 04:41 PM, ~D wrote:
Rename the destination folder at the drive itself or in the script,
should also work right?
Seems to work.
Do you prevent a shutdown or reboot when rdiff-backup is running? How?
Regards,
~D
___
Do you prevent a shutdown or reboot when rdiff-backup is running? How?
Since rdiff-backup does not like backup interruptions (and therefore is not
usable on slow or unreliable connections) I rdiff to a local repository on the
server (the server usually doesn't reboot) and rsync the entire
On 12/07/2010 03:26 PM, D. Kriesel wrote:
Do you prevent a shutdown or reboot when rdiff-backup is running? How?
Since rdiff-backup does not like backup interruptions (and therefore is not
usable on slow or unreliable connections) I rdiff to a local repository on the
server (the server
there is no valuable information shown even in the
verbose modes ...
-Ursprüngliche Nachricht-
Von: ~D [mailto:schoapp...@gmail.com]
Gesendet: Sonntag, 5. Dezember 2010 22:57
An: D. Kriesel; rdiff-backup-users@nongnu.org
Betreff: Re: AW: AW: AW: [rdiff-backup-users] rdiff-backup fails, no gzipped
Reading your error message, I agree there is no filename to be found -
please run the rdiff-backup call once again, but with the parameter
--terminal-verbosity 5 added to the command line (of course you may
exchange the parameter with -v5 to get the same console output, but in this
case you will
On 12/05/2010 07:46 PM, D. Kriesel wrote:
--terminal-verbosity 5
It doesn't seems to give memore in the backup.log file then
Previous backup seems to have failed, regressing destination now.
Regards,
~D
___
rdiff-backup-users mailing list at
On 12/05/2010 07:46 PM, D. Kriesel wrote:
--terminal-verbosity 5
It doesn't seems to give memore in the backup.log file then
Yeah, this is what I tried to say, the parameter -v5 would give you
information on every single file in both the backuplog and the terminal,
while the
On 12/05/2010 08:27 PM, D. Kriesel wrote:
On 12/05/2010 07:46 PM, D. Kriesel wrote:
--terminal-verbosity 5
It doesn't seems to give memore in the backup.log file then
Yeah, this is what I tried to say, the parameter -v5 would give you
information on every single file in both
On 12/05/2010 08:37 PM, ~D wrote:
On 12/05/2010 08:27 PM, D. Kriesel wrote:
On 12/05/2010 07:46 PM, D. Kriesel wrote:
--terminal-verbosity 5
It doesn't seems to give memore in the backup.log file then
Yeah, this is what I tried to say, the parameter -v5 would give you
information on every
On 12/05/2010 08:39 PM, D. Kriesel wrote:
If this is the _terminal_ output with --terminal-verbosity 5, its odd ...
there should be names of the files that are currently regressed ...
It is ...
___
rdiff-backup-users mailing list at
On 12/05/2010 08:46 PM, D. Kriesel wrote:
The last gz file that is mentioned seems to be
/home/backup/backup_laptop/rdiff-backup-data/rdiff-backup.tmp.0/5-_
a.snapshot.gz ... but there is so much after this, don't know if it is right ...
Hmm not sure about the next step to try to solve
: Sonntag, 5. Dezember 2010 22:57
An: D. Kriesel; rdiff-backup-users@nongnu.org
Betreff: Re: AW: AW: AW: [rdiff-backup-users] rdiff-backup fails, no gzipped
file
On 12/05/2010 08:46 PM, D. Kriesel wrote:
The last gz file that is mentioned seems to be
/home/backup/backup_laptop/rdiff-backup-data
12 matches
Mail list logo
