Suggestions for backup procedures?

Blue Mountain said:
Does that include all their dependencies such as DLL files, ini files, and registry entries? If not, keeping only the .exe is akin to having a car up on blocks without also having the tires and battery in a safe place.
Click to expand...

From what I understand, when double clicking on my .exe (install) files (for apps like Calibre, Filezilla, Kindle Create etc.), and it's executed, all of the DLL files (and all the other ones associated with it) are recreated again.

When I had to buy another computer (because my original one died), It worked fine for me anyway.

Of course, you have to redo all the settings and preferences again.
 
Last edited:
Blue Mountain said:
Does that include all their dependencies such as DLL files, ini files, and registry entries? If not, keeping only the .exe is akin to having a car up on blocks without also having the tires and battery in a safe place.
Click to expand...

I'm glad you brought that up, because the .exe files I'm talking about are the ones you download to install a program (app).

Thank you.
 
Last edited:
Really dug into Robocopy (I was a support analyst, after all), and after a lot of false starts I think I got what I want. A huge copy is going now. We'll see...!
 
I tried starting robocopy with doing just one very large folder that has a lot of subfolders. It chugged along fine for a long time, but when I came back and checked later I had a black screen again, along with the not-helpful message "Your computer experienced a problem and had to shut down". Yeah, thanks -- what caused the ◊◊◊◊◊◊◊ problem?
I ran chkdsk on both the source and destination drive -- no issues. I am now working on making a robocopy .bat file to do the folders individually. With all the time I've put into it already, it would have been faster to drag and drop them. But I am a coder, and determined to automate the process so I don't have to do it the long way next time. I'm actually pretty close and will document the solution when I have it.
 
Grrr, to get away from this problem for a while I decided to work on a new 3D print design. Started the print up and came back later to find "Print aborted with unknown error." ◊◊◊◊ me. (No, it's not a network thing.)
 
In addition, trying to post that info on this Forum this afternoon, I got "database error" (as I'm sure many others did). NOTHING is working for me today.
 
The previous problem was that the output disc had filled up. Why? It had enough space.
I eventually lit on putting the output to the screen instead of directing it to a file, so I could see what was happening. I eventually figured out that I was getting recursive folders within folders due to ApplicationData being automatically created, then starting over again within that folder. Turns out it was some Linking feature. I found the parm to bypass those "junction links", and it's going again, seemingly well. I'm not seeing those recursive folders, anyway.

And I finally got the commands figured out. There is a lot of difference between having a space in a folder name, a quote mark (maybe the wrong font), a trailing slash, and a source and destination definition that might be the same, or different. Each individual one of these gave me hours of confusion and searching out the answers. Now I have the format saved in file. Oh, it seems simple now, from this perspective...

I have yet to create the massive command file that will take care of all directory copies at once (my ultimate goal.) But I'm getting closer.
 
alfaniner said:
And I finally got the commands figured out. There is a lot of difference between having a space in a folder name, a quote mark (maybe the wrong font), a trailing slash, and a source and destination definition that might be the same, or different. Each individual one of these gave me hours of confusion and searching out the answers. Now I have the format saved in file. Oh, it seems simple now, from this perspective...

I have yet to create the massive command file that will take care of all directory copies at once (my ultimate goal.) But I'm getting closer.
Click to expand...
Congrats on persisting and getting to a solution. I've been a huge command-line fan all my life, for that's pretty much all there was to computers when I started working on them. While I appreciate the ease that many things in a graphical environment offers—web browsers being a great example—for this kind of work involving hundreds of thousands of files the command line is the only way to go.
 
Last edited:
You must log in or register to reply here.

Back
Top Bottom