How to delete a bad BackInTime backup (of a failed/unavailable installation)?
- Vous devez vous identifier ou créer un compte pour écrire des commentaires
Can someone please enlighten me on the best way to remove a BackInTime profile and its backback? The backup is not only bad, it is also big.
The profile in question was placed (by BackInTime) inside the main profile's directory, i.e, BackInTime profile 2, inside BackIntime profile 1 (profile 1 being a good one, which I must keep safe).
Should I remove the bad profile and backup using BackInTime? If so, how do I access the profile of a failed installation, (which is now gone!)?
With huge pre-thanks for any help!
Just select the profile in Settings and press Remove. Keep in mind that you can not remove Main Profile.
https://github.com/bit-team/backintime/issues/904#issuecomment-402278589
I tried that Magic Banana, but have no access to the settings of that sub-directory.
It seems BackInTime has separated the profiles, and made each one relative to its own installation of Trisquel.
EDIT:
-------
This is how the backup folder looks:
/backintime/backintime/
I can access the main backintime directory (the good one), but not the inner one (created by mistake).
I hope BackInTime was not corrupted!
I can access the main backintime directory (the good one), but not the inner one (created by mistake).
If, in Back In Time, no profile corresponds to the inner directory, I guess you can simply remove it from the disk.
I hope BackInTime was not corrupted!
If Back In Time reports no error when it makes a new snapshot, I believe you are fine. Anyway, instead of removing the inner directory, as I just wrote, you may first move it or rename it and then test your backup, restoring some old file.
That sounds wise, thank you Magic Banana! Once again!!
I would be moving and/or removing that inner backintime directory from an external drive. Could I bug you for instructions, so I don't make another mistake?
Magic Banana, sorry for being a pest, but I have one more question, if that is OK.
I am unsure of which commands to use to 'find' and 'move' a directory located on an external drive.
Could you please let me know?
First of all: you are not a pest. As you have probably already noticed, I love to help people here (and I have been in holidays at home, but that comes to an end next week).
mv moves or rename a file (directory included). Automatic mounts usually happen in /media/$USER (hence, probably no need for 'find'). But you can do that with your favorite file manager too!
Thank you for being there Magic Banana!
mv moves or rename a file (directory included)
So, how do I know if I'm moving or renaming the directory? Are there different ways to use the "mv" command? And how should I write each of those commands (to rename + to move)?
NOTE:
Hope you having a refreshing holiday! Please don't worry, and take your time, I'm not in a hurry.
I am a translator!
how do I know if I'm moving or renaming the directory?
mv a b
If b is an existing directory, this is moving a (directory or file) to b, otherwise this is renaming a to b.
Note that, if there was already a file a in b (if b is a directory) or a file b in the current directory, such a file is also deleted. If you don't want that, you can use
mv -n a b
If you write commands yourself, there are things to know about how bash splits a command into words (spaces and tabs are considered as separators) and how the words are interpreted. In particular, there are special things to do if your filenames include whitespace characters or start with -.
Especially for mv, it may be wise to use a test directory and create files and directories in it, in order to test your command on them first.
It is a little complex but there is a nice guide at https://mywiki.wooledge.org/BashGuide/CommandsAndArguments
That was very helpful, Avron - thank you for the detailed info and link to the guide (I'll go back to read it)!
I'll also follow your advice on testing + will add it here, to remind myself and avoid any more mistakes:
Especially for mv, it may be wise to use a test directory and create files and directories in it, in order to test your command on them first.
Will try to make a habit of it!
EDIT:
I want to move+rename the bad directory (with bad profile) to a folder outside BackInTime, a kind of neutral zone, so if all goes well, I can delete that failed thing... do you think this could create problems for the existing BackInTime backups (the good ones)?
- Vous devez vous identifier ou créer un compte pour écrire des commentaires