Tag Info

New answers tagged

0

You should check everything on both sides of your backuppc config. first, check the server and try to increase it performance, but if you have other machines that perform better, lets skip this one. Next check the network! Network speed detected by the desktop, package size, cable quality. do some benchmarks, do a rsync (rsync-rsyncd) test of a big file. ...


0

It may be faster to run rsync directly on the server. You have about a million files to access over the network. There are a couple of minimal installs of rsync that you can run. I've setup BackupPC on Windows this way. You can run a full Cygwin install, or the minimal cygwin-rsycnd install available in the BackupPC project.


1

It looks like s3cmd can accept input from stdin at least according to the resolution of this bug on 2/6/2014. If your s3cmd is newer than that you should be able to do: tar -czvf - ${BACKUP_DEST} | s3cmd --reduced-redundancy put - s3://MY-S3-BUCKET/`date +\%G-\%m-\%d`_db.tar.gz --no-encrypt Most utilities use - as a filename to indicate writing to stdout ...


0

I suppose that paths specified in the SENDLOGS are relative (i.e. bin/filename.LOG is relative because it has no leading slash). Since paths are relative, make sure that the script is executed from a correct directory (the directory from which you run tar by hands). You can do that by adding the following line to your script: echo "current directory: $PWD" ...


0

You can use the 7z (7zip) archive/compression format if you have access to the p7zip-full package. On Ubuntu you can use this command to install it: $ sudo apt-get install p7zip-full To create an archive you can use 7z a <archive_name> <file_or_directory> and if you do not want to compress the files and want to just "store" them as-is, you ...


6

There is generally no need to backup anything under dev, since it's mostly generated upon boot by udev. I did a lot of OS migrations by simply rsyncing everything except stuff like proc, dev, sys etc. Just make sure when you setup your backups, ALWAYS test a recovery, to see if everything is functioning properly.


2

Here are a couple of alternatives. tar -ztf patch.tar.gz | grep -v "/$" | xargs -i sh -c 'test -f {} && echo {}' | tar -T- -zcvf backup.tar.gz or tar -ztf patch.tar.gz | grep -v "/$" | tar --ignore-failed-read -T- -zcvf backup.tar.gz The second example will exit with status zero after an attempt to backup a file that does not exist (tested on ...


1

Try use perl oneliner for this like cat filelist | perl -ne 'chomp(); if (-e $_) {print "$_\n"}' | tar -T- -zcvf backup.tar.gz



Top 50 recent answers are included