Log warning messages - "The following link target was not backed up: C:/Users/..."
TIH 2012 Up2 (7119)
I have three warnings about old non existent links to user links which no longer exist. But I can't see where I can "untick" them in my folder selection list. I want to be able to see a clean log entry without these irrelevant warnings?
Ideas?
Mark
| Attachment | Size |
|---|---|
| event_log_2013-03-13_00-30-33.jpg | 16.57 KB |
| file_backup_2013-03-13_00-31-47.jpg | 22.9 KB |
- Log in to post comments
Thank you very much for taking the time to respond. But I am afraid you have lost me. I don't follow what you suggest I do, or if you are trying to explain the root cause of the problem. I hope there was enough info in the screen shots. But if not, I can do others?
Tks,
Mark J
- Log in to post comments
The root cause is that some folders under c:\user\public are NTFS junctions, and the folders they point to are not backed up if they are included in the original selection. In my first reply I was incorrect - the links may reside under c:\users\public folder. Unfortunately link itself is not logged, so you have to run junction utility with -s parameter - download it from http://technet.microsoft.com/en-us/sysinternals/bb896768.aspx in c:\users\public and find junctions that point to non-existent folders like c:\users\mark_asus and either delete them, uncheck them or put them to exclusions.
- Log in to post comments
OK. Making a little more sense. Am used to symbolic links in *nix. These look the same sort of thing. I do recognise them as links to old defunct other machines that used to be on the network. I attach a list of ALL my junctions on my C drive. I can see some of the offending ones. But can't seem to navigate to them in the real dir tree. Also not sure which way round to read the list. i.e. which is the real dir an which is the symbolic pointer...
These are three which definitely don't exist anymore:
============================
Directory of C:\Users\mark\Documents\asus_users\jacqui_asus.000
22/02/2011 23:57 PrintHood [C:\Users\jacqui_asus.000\AppData\Roaming\Microsoft\Windows\Printer Shortcuts]
0 File(s) 0 bytes
Directory of C:\Users\mark\Documents\asus_users\mark_asus
23/02/2011 00:12 PrintHood [C:\Users\mark_asus\AppData\Roaming\Microsoft\Windows\Printer Shortcuts]
0 File(s) 0 bytes
Directory of C:\Users\mark\Documents\asus_users\mark_asus\Documents
23/02/2011 00:30 My Pictures [C:\Users\mark_asus\Pictures]
0 File(s) 0 bytes
====================================
They don't seem to have anything to do with the c:\users\public folder which you were referring too.
Maybe I just use junction.exe to delete them something like this:
(Using the first example above)
junction -d C:\Users\mark\Documents\asus_users\jacqui_asus.000
or is it
junction -d C:\Users\jacqui_asus.000\AppData\Roaming\Microsoft\Windows\Printer Shortcuts
Tks,
Mark J
| Attachment | Size |
|---|---|
| 127601-107014.txt | 6.74 KB |
- Log in to post comments
C:\Users\mark\Documents\asus_users\jacqui_asus.000
22/02/2011 23:57 PrintHood [C:\Users\jacqui_asus.000\AppData\Roaming\Microsoft\Windows\Printer Shortcuts]
PrintHood is the name of junction,
it points to folder in brackets that doesn't exist in your case. So you can just delete this PrintHood using windows explorer, and the other two pointing to mark_asus. Other junctions point to the files included in the backup set and don't generate this warning.
- Log in to post comments
Excellent! All sorted. I found and deleted the three offending JUNCTIONS. Errors disappear from Acronis Backup log. Superb! Thank you very much for not only answering but persisting in my (possibly) irritating questions.
Regards,
Mark J
- Log in to post comments