Re: [BackupPC-users] Error BackupPC_tarCreate

[Les M. <les...@gm...>]

On Wed, Apr 10, 2013 at 4:49 AM, Nicolas Cauchie
<ni...@fr...> wrote:
>
> Hello,
>
> I'm trying to use the "program" BackupPC_tarCreate.
>
> I have a test-host wich has been backuped 4 times incrementally, and one time fully :
>     - 0 : Full
>     - 1 : Incr
>     - 2 : Incr
>     - 3 : Incr
>     - 4 : Incr
>
> So, I want to use tarCreate to make an archive of this host in the folder named "/home/testback". So, here's my command :
>
> # su backuppc
> $ /usr/share/backuppc/bin/BackupPC_tarCreate -t -h test-host -s * -n -1 /home/testback/test.tar (to start from the last backup)
>
> I also used :
>     -    $  /usr/share/backuppc/bin/BackupPC_tarCreate -t -h test-host -s * -n 0 /home/testback/test.tar (to test with a positive number...?)
>     -    $  /usr/share/backuppc/bin/BackupPC_tarCreate -t -h test-host -s * -n -1 (to see if it was the path I put making mess...)
>
> The error message is still the same : /usr/share/backuppc/bin/BackupPC_tarCreate: bad dump number ''
>
> What this message stands for ? I didn't found any help on Google...

There are several things wrong with your command line.  First the
shell will expand an unquoted * to the list of files in your current
directory so it would be unpredictable what the program actually sees
as the resulting command line.   Use either \* or '*' to prevent shell
expansions of wildcards.  BackupPC_tarCreate doesn't want the output
file name on the command line - it writes to stdout, so you should use
shell redirection (>/path/to/file or | program), which again will
happen before the program sees the command line.   Also, you do need
to specify the files/directories to include - using . or / will work
for 'everything'.   Try:
/usr/share/backuppc/bin/BackupPC_tarCreate -t -h test-host -s '*' -n
-1 /  >/home/testback/test.tar
or for testing you can:
/usr/share/backuppc/bin/BackupPC_tarCreate -t -h test-host -s '*' -n
-1 /  | tar -tvf -
(list the filenames as they go by)
Also, note that it may not make sense to wild-card the shares if they
weren't collected in the natural mounted tree locations (for example,
if you have windows shares of C$, E$, etc.)

--
   Les Mikesell
      les...@gm...