Replies: 4 comments 3 replies
-
1. My Nikon Z6 saves files in subfolders of DCIM like 103NCZ_6, 104NCZ_6
and so on. This folder structure is kept in lbb's backup. That means,
collisions are impossible. I'm not sure, but I would expect, any Nikon
camera would work like this?
2. There is no renaming yet. It wouldn't be a very big deal to implement
this after backup. Maybe a nice idea. I configured my Z6 to name the
images like "Z6P_2309.NEF". Why not renaming it to "2024-10-18 11-26-51
- Z6P_2309.NEF"? Is this what you mean?
|
Beta Was this translation helpful? Give feedback.
1 reply
-
1: Backup directly from camera is done to a path containing the cameras
serial. on backup from storage cards every card gets a unique ID. This
ID is part of the backup path.
2: After implementing a renaming step: If you keep your files at
source,they will be copied again next time, because the original file
name does not exist at target. I do not see a clean and secure way to
prevent this.
3: Powercuts are always a big risk to break linux, be sure to have one
or two spare lbb-SDs with you in case one gets broken. Incomplete
transferred files will be copied next time.
|
Beta Was this translation helpful? Give feedback.
1 reply
-
My decission is clear, I separate data and os. I do not expect to lose
all the data in case of a crashed os but why to take a risk?
|
Beta Was this translation helpful? Give feedback.
1 reply
-
The renaming function is implemented, I just forgot to post this here, sorry. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I found this great project and want to build one but I had a couple questions before I did.
Beta Was this translation helpful? Give feedback.
All reactions