Comments (8)
No way. This can potentially be a very dangerous feature. And deleting all the photos using your camera is not that difficult.
from little-backup-box.
@dmpop, how would such an Option be more dangerous than deleting in camera?
I would Think it is Safer if the script does it after a verify.
Data loss would be almost impossible, whereas if I delete on cam, i am not 100% sure if the little box shut down before copying all files, eg. Due to power loss.
Am i wrong?
Anyways, i guess it will be not too hard to add a rm -r to the end of the copy-script...
I too need a fully automatic system, that clears the card before next use. So little box helps a lot, thanks for all the work.
from little-backup-box.
It's not about what's more dangerous. It's about using Little Backup Box to keep your data safe. Deleting data on storage cards either in the camera or using Little Backup Box is just asking for trouble. However, if you are an adventurous type, feel free to add rm -rf
to the script. 😄
from little-backup-box.
Yes, i understand this is your position.
I like to learn from it.
Would u mind to elaborate where u see trouble arise?
Where/why do u disagree with my thought that a delete by script is safer than manual delete?
from little-backup-box.
For my pics to be safe, I need to know with 100% that all files are backed up before i clear the card and take new pics.
How can i manually check this? Open every pic, or maybe see a logfile/message that says backup completed and verified.
A script can do a data integrity check and then delete the source.
If I see the empty card, I know 100% that backup was a success. If pics remain, I know there was an issue.
A shut down pi can not be a good indicator of success, as there are many more ways leading to a shutdown.
That's what I think, and I am thankful if u correct me, before I loose any data.
What is your recommended workflow to check success?
from little-backup-box.
Firstly, the backup script uses rsync that performs integrity check during the backup operation. Secondly, even with all the integrity checks in place, there is no guarantee that your data will remain safe (what if you lose the USB stick with your backup data or it turns up to be faulty after you backed up your photos?). Basically, what I'm trying to say is that Linux Backup Box is designed to give you one more copy of your file, and not the only copy.
from little-backup-box.
what I'm trying to say is that Linux Backup Box is designed to give you one more copy of your file, and not the only copy.
Ok, now that's a clear statement.
So, the following is meant as feedback/help to improve, not to insist on "make me this feature"...
From the readme, i had gotten the impression that it's not only/mainly meant for Backup in the sense of "duplication for security", but more as a tool with which photographers can automate a number of the tasks they regularly have:
- take pics,
- store them safely,
- present the pics
- (make room for more pics,)
- start over...
The readme mentions "Transfer" on bullet point 2 vs. Backup in 1st bullet, this implies to me transfer is different to backup, i interpreted it as "move"...
Now, if you state such a high emphasis on data security (a good thing, i agree), then i think the recommended usage "insert card, wait for shutdown" is dangerous, as described above. A shutdown may have happened due to other reasons than successful rsync, so that's a danger for the user, right?
Maybe that danger should be described in the readme, or fixed...
- You could replace the shutdown with some led-blinking.
- Or, as i suggested, deleted source-files could be a unmistakable sign for success.
Sure, the 2nd copy issue is not solved with this. But there could be an option to rsync to more than one destination for that. - Without deleting the source, another way to communicate success could be to write a jpg back to card, that has text in it "last backup at YMD-H:S successfullly finished.
I just think that many users who like the automatism of little-box, might trust the backup's success and delete their card without double-checking for success.
Because, making room on the card is inevitable at some point, unless you have unlimited cards.
So it would be cool to automate that step too, in a save way. Maybe by default only allow delete if box can do at least 2 backups to independent destinations.
For the manual delete, i even don't see how i could do a backup-integrity check without repeating what the box does, which would render the whole automatism useless... I think only the remote- option is save, where the UI can give me a success message.
from little-backup-box.
Thank you for sharing your thoughts. I'll take your comments under consideration.
from little-backup-box.
Related Issues (20)
- Development version: Create thumbnails. Task list contains already completed ones
- "Power down after idle-time" does not work HOT 30
- Wifi connection stopped after backup started HOT 9
- No read/write permission for subfolders inside the Backup folder HOT 10
- Can't back up to cloud services HOT 2
- Backup not starting [dev branch; specific Hardware ] HOT 4
- Code injection vulnerability
- Problem or Operator Failure HOT 32
- bookworm causes problems
- Installation problems fixed
- Network connection fails - wireguard broken: fixed HOT 2
- Instructions for defining source and target devices (and paths) HOT 5
- Raspberry Pi 5: GPIO functions (display and buttons) do not work HOT 6
- Mail does not work when "user" is not an e-mail address HOT 6
- Unable to login after global password set HOT 7
- Raspberry Pi Zero W - No display on I2C display (sh1106) HOT 1
- Unable to backup to Samsung T7 Touch HOT 14
- EN Translation error HOT 1
- Update freezes at "Setting Up Comitup (1.41-1) ..." HOT 2
- Question About Transfer Speed HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from little-backup-box.