It’s nice to have a set and forget strategy but ultimately things can and will go wrong so it’s always a good idea to check the logs regularly just to make sure everything has gone to plan. There’s nothing worse then setting and literally forgetting only to come time to restore and find that it hasn’t worked for what ever reason.
Please refer to Source and Destination above for naming limitations of folder names.
RoboCopy has an excellent built in detailed logging option but it can be overwhelming at times especially if you have lots of data as the logs can be very long. That’s why LockDown has an excellent summary log that you can quickly glance at. It gives you everything you need to know about the backup all in one easy to read file.
All log files are located in c:\LocDN\FreeEd\logs and the detailed logs will use the following naming convention of “current_day dash source folder dash destination_folder“ this creates a unique file for each source / destination pair and allows for easy recognition when scanning for the files to study the logs.
example: Source is “C:\Users\Loc\Documents” + Destination is “E:\Backup_USB” = Output log file will be “Wednesday-Documents-Backup_USB.txt”
If there are spaces in the folder names it will remove the spaces. ie “Locs Documents“ and “Backup USB“ will result in “Wednesday-LocsDocuments-BackupUSB.txt”
It’s important to choose different destination folder names so that the first log won’t get overridden by subsequent logs with the same name.
As you can see in the sample summary log everything you need to know is easily seen
The summary is grouped into sections based on the destination.
To break down the summary you get the following:
- Start Day, Date and time
- The Destination(s) Drive or Folder(s)
- The Source(s) Drive or Folder(s)
- Time taken to backup each folder and the total amount of time taken to backup all folders
- It will also tell if it detected any errors during the backup
- Then finally it even gives you a summary of your disk space usage
You can compare the summary log above with just one file of the detailed log below.
That’s pretty much it! If you have followed all the steps and everything worked along the way then you’re on your way to having a pretty good starting point for a backup!