deedasmi / ruckup Goto Github PK

Things like -b shouldn't be so slow

Recursive backups are bad.

Surely rust has some way to resolve a relative path into an absolute path.

I should clean up the codebase

A lot of the preferences stuff could be moved into a function.

Allow user to configure:

• Cores
• Number of file versions

Sorta depends on #3. How changed files are stored changes whether we can store nonce in metadata table.

Backup solution: Prepend nonce

Could append/inject a nonce somewhere into encrypted file, then re-hash. If we tell server what/where to put that nonce, and then ask them what their new hash is, that should prove they have not modified the original file.

Pro:

• Proves server is at least storing unmodified file
• May be able to interface with local backup (if exits) to save CPU time.

Con:

• Does not guarantee server will return unmodified file.
• Requires client to have encrypted file

Network backup shouldn't by multi threaded, but should be asynchronous. Local background should be multi threaded.

Local=filesystem

The deleting of old files and file creation should probably be handled by lib::lib instead. Maybe wrap the file encryption functions? Probably should also look into using BufReader and BufWriter.

Currently recovers all files, and only the most recent change will be recovered. However, #9 will break this, and the recovered file will then be undefined.

Valid path/access/etc.

Will make value more portable between server and client, as well as reducing meta_data table size.

Ala 'Vacuum'

Chrono?

Should take a location and recreate all files in the destination

Related to #29.

Currently, a massive amount of size goes into repeating the absolute paths of every file. Might be able to make a lookup table to reduce the file size.