| Summary: | 10 mn to open a backup tar file ! | ||
|---|---|---|---|
| Product: | [Applications] kbackup | Reporter: | Philippe ROUBACH <philippe.roubach> |
| Component: | general | Assignee: | Martin Koller <kollix> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| See Also: | https://bugs.kde.org/show_bug.cgi?id=433858 | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | the answer of dolphin | ||
|
Description
Philippe ROUBACH
2021-02-28 17:10:31 UTC
It's unclear for me if kbackup produced an incorrect tar file or not. Can you list the content of the tar file on the command line via tar -tvf filename.tar ? Info requested in Comment 1, thus setting status to NEEDSINFO. Yes I can list the contents of the tar file Created attachment 136272 [details]
the answer of dolphin
See the answer of dolphin after several mns.
My wild guess is that this may be a problem with ktar (karchive), if you can list / extract all the contents of that tar file successfully. The tar archive is 80 GB so it probably has a very large number of files inside? >> The tar archive is 80 GB so it probably has a very large number of files inside?
Yes a very large number.
consequence : several mns to access to the contents of the archive with Ark. That's why I wish folder instead of archive to store the backup.
Then the conclusion is: it's not a kbackup problem since it produces a correct tar file, which is what it should do. If you want smaller tar archives, you can define the max size per slice in the settings. If you want some completely different way of backing up your files, then kbackup is the wrong solution. >> If you want some completely different way of backing up your files, then kbackup is the wrong solution.
What backup app do you advise ?
To be honest I don't know. For my backup scenario kbackup is the right solution. Did you try to reduce the max slice size ? I will try. Is there any log ? It is necessary to be alerted if there are some errors. kbackup shows all progress and problems it encounters in the right bottom area. What do you think is not shown ? I don't want to use manually kbackup but with a cron job. Ah you mean where you can see the output of kbackup when run from cron ? I get the output in a mail from cron. My crontab looks like this: #do (incremental) system backup every day at 3:10 10 3 * * * /root/kbackup-cron where in that script I do: #!/bin/bash eval `dbus-launch --sh-syntax` /usr/bin/kbackup --autobg /root/martin-full.kbp kill $DBUS_SESSION_BUS_PID Today I made a cron incremental backup. I received the report by mail. I am going to test kbackucup during one week. |