After running my first ever (mirror)fbackup, most (but not all) folders residing on my external drives were empty in the destination location. The huge backup log was to big to be opened by notepad, but wordpad opened it properly. Hundereds of "network path not found" references, even though my external drives are directly plugged in to my computer (through a USB hub).
On the backup of an external USB disk drive most but not all of the folders were empty, those that were not, weren't anywhere close to complete.
On the backup of an external USB Flash drive, all folders were completely empty, though loose files (not in folders) copied properly.
Thanks to all for any insights that can be given.
empty folders from external drive backup
-
- Posts: 1978
- Joined: Thu May 23, 2013 7:57 am
Hi,
- Do you have the latest version of FBackup 4.8.286 ?
- You mentioned the warning "network path not found" but you use external drive for destination? Those warnings seems to be for source files. Is that correct?
- Do you have the latest version of FBackup 4.8.286 ?
- You mentioned the warning "network path not found" but you use external drive for destination? Those warnings seems to be for source files. Is that correct?
Do you know you can monitor your backups remotely with Backup4all Monitor? You can read more here: https://www.backup4all.com/backup4all-monitor.html
Hello, thanks for responding. Yes, 4.8.286 which I downloaded from the fbackup site a few days ago. Here is a sample log entry:
"[10/15/2012 1:16:15 AM] Warning: Skipping file F:\EDIROL\Max's Band\Audacity Projects\On the Sunny Side of the Street in C_data\b00141.au
Network path was not found (mirr1)"
My C drive is a SATA hard drive in my computer tower. The destination is drive"H", which is a new 750GB USB external disk drive that is plugged in to a USB hub.
The two source drives that are not being read properly are the F drive, which is another external USB disk drive, and drive G which is a 2GB USB flash drive. Both of these are also plugged into the same USB hub as the destination drive.
btw, fbackup seemed to backup my C drive without problem. The backup was designed to back up from all 3 source drives during the same backup. Thanks again.
yuyakay
"[10/15/2012 1:16:15 AM] Warning: Skipping file F:\EDIROL\Max's Band\Audacity Projects\On the Sunny Side of the Street in C_data\b00141.au
Network path was not found (mirr1)"
My C drive is a SATA hard drive in my computer tower. The destination is drive"H", which is a new 750GB USB external disk drive that is plugged in to a USB hub.
The two source drives that are not being read properly are the F drive, which is another external USB disk drive, and drive G which is a 2GB USB flash drive. Both of these are also plugged into the same USB hub as the destination drive.
btw, fbackup seemed to backup my C drive without problem. The backup was designed to back up from all 3 source drives during the same backup. Thanks again.
yuyakay
-
- Posts: 1978
- Joined: Thu May 23, 2013 7:57 am
Hi,
Please send me:
- the last backup log
- the backup catalog (.fkc file) from the backup destination.
Put both files into a zip archive and send it to info[at]fbackup[dot]com
Please send me:
- the last backup log
- the backup catalog (.fkc file) from the backup destination.
Put both files into a zip archive and send it to info[at]fbackup[dot]com
Do you know you can monitor your backups remotely with Backup4all Monitor? You can read more here: https://www.backup4all.com/backup4all-monitor.html
-
- Posts: 1978
- Joined: Thu May 23, 2013 7:57 am
Hi,
As I assumed, the warnings are for source files which resides on a network path.
How did you manage to add those source files as you are not allowed to add sources from network/mapped drives in FBackup?
You should open Backup Properties->Sources and remove all network sources from that list.
As I assumed, the warnings are for source files which resides on a network path.
How did you manage to add those source files as you are not allowed to add sources from network/mapped drives in FBackup?
You should open Backup Properties->Sources and remove all network sources from that list.
Do you know you can monitor your backups remotely with Backup4all Monitor? You can read more here: https://www.backup4all.com/backup4all-monitor.html
I'm sorry. I didn't understand your last posting at all.
I don't know what the definition of a network path is. As all my drives (except C) are connected directly to my computer (albeit through a USB hub), I would have thought that "network path" was not an issue here, as there is no router or wi-fi involved at all.
If directly connected drives can't be used as sources, what's the point of a backup program?
The fact that I was able to add the files that reside on those drives to the backup specifications seems to indicate (to me)that those drives are not on a network path.
I am completely confused at this point.
I don't know what the definition of a network path is. As all my drives (except C) are connected directly to my computer (albeit through a USB hub), I would have thought that "network path" was not an issue here, as there is no router or wi-fi involved at all.
If directly connected drives can't be used as sources, what's the point of a backup program?
The fact that I was able to add the files that reside on those drives to the backup specifications seems to indicate (to me)that those drives are not on a network path.
I am completely confused at this point.
-
- Posts: 1978
- Joined: Thu May 23, 2013 7:57 am
Hi,
I need to connect to your computer to solve this problem. You say the drive is an external one connected via USB and FBackup says that is a network drive.
Can you give me access to your computer using TeamViewer?
I need to connect to your computer to solve this problem. You say the drive is an external one connected via USB and FBackup says that is a network drive.
Can you give me access to your computer using TeamViewer?
Do you know you can monitor your backups remotely with Backup4all Monitor? You can read more here: https://www.backup4all.com/backup4all-monitor.html
Well the log seems to have thought during the time of the backup that there was a network drive, but the program itself does not see them as network drives, and allows me to select files on those drives for the backup.
I'm wondering if the problem may be that I've got the destination drive and two source drives all plugged into a USB hub. I'm going to try another backup, this time with the smaller (source) USB disk drive plugged into my tower rather that the USB hub.
I'll let you know what happens. Thanks.
I'm wondering if the problem may be that I've got the destination drive and two source drives all plugged into a USB hub. I'm going to try another backup, this time with the smaller (source) USB disk drive plugged into my tower rather that the USB hub.
I'll let you know what happens. Thanks.
Good news. I unplugged a USB disk source drive from the USB hub, and then plugged it in to a USB port on the back of my tower. The USB hub now only had the USB disk destination drive, and a USB flash thumb drive. The backup, with practically identical source files and folders chosen as before, was performed without a hitch, and reasonably quickly too; about 150GB backed up and tested within the time span of 4 or 5 hours ... and my computer was usable during that time.
Apparently USB hubs can cause problems under some circumstances, although I'm not sure what those might be. FWIW, I am using a Rosewill 4port USB 2.0 hub. I guess I might make a recommendation to avoid putting a USB disk source drive and a USB disk destination drive on the same hub, but that is entirely unscientific and the cause of the problem might have been something else. All I know is removing the source USB disk drive from the hub seemed to eliminate the problem.
Apparently USB hubs can cause problems under some circumstances, although I'm not sure what those might be. FWIW, I am using a Rosewill 4port USB 2.0 hub. I guess I might make a recommendation to avoid putting a USB disk source drive and a USB disk destination drive on the same hub, but that is entirely unscientific and the cause of the problem might have been something else. All I know is removing the source USB disk drive from the hub seemed to eliminate the problem.