I would suggest DAR (and possibly KDAR). Dar is a set of bash scripts plus a bit of binary code; kdar is the gui frontend to dar (or maybe a gui equivalent of dar). I've used Dar to backup a 7 gig installation (compressed, it's a 2.7 gig file). I haven't used kdar yet.
You can learn more about Dar here
Advantages of Dar: unlike Parted, which requires that backups must be restored to partitions of the same size, Dar doesn't care about partition sizes. Unlike tar, which makes one large file (compressed or not), Dar makes a large file of individual files. If one file is corrupt in a tar archive, you risk loosing the entire file. With a Dar archive, you risk only one file; the corrupt one. And, if the file is a text or spreadsheed file, you can "skip over" the corrupt portion and recover most of the file, and rebuild the missing part form local documents (hopefully, if you keep them).
Disadvantage of Dar: it takes a bit of study and trial until you find out what works for you. But, when you do figure it out, WOW!
I searched for 4 years for a backup solution to do what I wanted to do, always skipping over Dar in my Google searches. Finally, in desperation, I tried Dar. And there it was, all along.
Making backups is as easy as invoking a bash script (manually or via cron); making restorations is equally easy. Just be mindful that Dar backups are relative to the root of the filesystem (if you set it up that way). Therefore restores must also be relative to the root of the filesystem.