Irritating backup warning message I cannot get rid of.

Topic

New Reply

My computer is running Windows 10 AU (WinX-AU for short) that I’ve enabled both File History and the Win7-like backup of Backup and Restore. The backup drive is a 1 TB Seagate portable hard drive that is plugged into a USB 3.0 port of a Dell Alienware X51 R2. I also have setup a network share on another machine that I then added to the “Music” library.

Now, I thought that when I configured Backup and Restore, I told it NOT to back up anything on the network share. Yet, every backup since have generated the following warning message log: “Backup skipped backing up ‘\Shared Music‘ as it is not on local machine.” Note that the root of the network share is “Shared Music“…the one warning is coming from a third sublevel folder inside the network share.. As far as I’ve figured out…none of the other music folders are apparently trying to force a backup of themselves over the home ‘net.

Despite my efforts to search for a solution, I’ve hit a hard wall of why I’m getting this message. Any ideas of where I should go to investigate a possible solution to this problem (meaning to make the app STOP blurbing out it’s advice to check the backup!). Aside from giving up and “putting down” the portable drive AND the computer involved?

OH…the network share is on a 15 year old Dell Dimension 8200 running Win7 Home Premium. Additionally, all my home LAN PCs are part of a common Homegroup. These three pieces of information are probably unrelated to my difficulty, but as I’m otherwise flummoxed, I mention them just in case of a weird side-effect.

TIA,

AE :huh::o::mellow::mad:

Reply | Quote

Replies

I’ve just learned, after nearly half a year, why I was seeing a “Some files were skipped. Please check your backup” (admittedly paraphrased…I was tired of seeing it when I either tried to perform a backup manually or let the computer run the backup on a schedule). If a network share is in one library, ALL libraries pick up on it.

The log file always noted that a subfolder inside my music network share was not backed up, as it was not on the local disk. This share is part of my Music library. I thought it was odd that it wasn’t the root of the network share it was complaining about, but rather a subfolder in this share that is four levels deep. I also thought it was odd that my Documents library did not also throw a warning, as I have a network share included in that library also. So I went into Backup and Restore’s settings, and unselected just the music library, as I had made that network share part of that library. Doing so did NOT fix the warning. Then I tried unselecting my documents library, still no joy. Finally, I unselected ALL my libraries from the backup set. Performing this “Alexandrian Solution” finally got rid of the warning. It appears to me that Windows 10 has a problem with symbolic links inside libraries when at least one of them points to a network share. It is just a guess, but, I’m not getting nagged to death about a skipped file or directory now.

“Additional locations” settings in Backup and Restore for my Standard account are still checked, so my AppData folder, Contacts, Desktop, Downloads, Favorites, Links, Saved Games, and Searches folders should still be getting backed up.

I had tried running chkdsk /f, followed by sfc /scannow, before trying my work-around. I had not progressed to the dism command. Should I still try running that? Also, I noted that when the computer ran chkdsk /f, it got to 40% and rebooted again. The primary drive is a 2TB unit that only has about .20 TB currently in use. Did chkdsk merely note that it was seeing a lot of unused space, and exited normally, which rebooted my system again? Or should I be concerned that there is a really deep issue going on? Sfc /scannow didn’t report any issues with the system folders, which I ran after the reboot triggered by chkdsk.

I am now running Windows 10 AU (ver. 1607), using primarily a Standard Account, and the backups are going to an external 1 TB drive.

Reply | Quote

Duplicate thread. Please post additional replies in the Windows 10 forum

--Joe

Reply | Quote