Backup Central

On Thu, Jun 10, 2010 at 7:35 AM, Casey Rodarmor <casey < at > rodarmor.com> wrote:
And just to clarify, the data that I copied over from A to B was just
a plain backup, with no rdiff-backup meta-data.


and what about the data on A? was that rdiff-backed up across? If so,
u could simply copy the rdiff-backup metadata dir across.

-jf


--
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."
--Richard Stallman

"It's so hard to write a graphics driver that open-sourcing it would not help."
-- Andrew Fear, Software Product Manager, NVIDIA Corporation
http://kerneltrap.org/node/7228

_______________________________________________
rdiff-backup-users mailing list at rdiff-backup-users < at > nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

On 10/06/10 01:35, Casey Rodarmor wrote:
And just to clarify, the data that I copied over from A to B was just
a plain backup, with no rdiff-backup meta-data.

rdiff-backup will use existing files no matter what, just like rsync.
However, it will complain like this:

Fatal Error: Destination directory

dst

exists, but does not look like a rdiff-backup directory. Running
rdiff-backup like this could mess up what is currently in it. If you
want to update or overwrite it, run rdiff-backup with the --force
option.

So, just add --force for the first run.

Jakob

_______________________________________________
rdiff-backup-users mailing list at rdiff-backup-users < at > nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki