During a file level restore of a file level backup symbolic links seem to be replaced with hard links.
How can you enforce symbolic links to be restored as symbolic links?
An example is the "C:\Documents and Settings" symbolic link, it points to the "C:\users" folder
During restore the mounted volume containing the to be restored data does contain the correct symbolic links but the "copy to" command does not recognize it is a symbolic link and creates a whole folder tree for "C:\Documents and Settings" instead of only creating a symbolic link file
-
- Novice
- Posts: 5
- Liked: never
- Joined: Mar 29, 2022 5:23 am
- Full Name: Erik Kaashoek
- Contact:
-
- Product Manager
- Posts: 15126
- Liked: 3232 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
- Contact:
Re: Incorrectly restoring symbolic links as hard links
Hello,
looks like expected behavior. Copy to "c:\users\..." is the way to go.
"Copy to" is pretty similar to Windows explorer "copy & paste"... and with Windows explorer this also does not work the way you ask (or I misunderstood something, then please describe step by step what you did)
Best regards,
Hannes
looks like expected behavior. Copy to "c:\users\..." is the way to go.
"Copy to" is pretty similar to Windows explorer "copy & paste"... and with Windows explorer this also does not work the way you ask (or I misunderstood something, then please describe step by step what you did)
Best regards,
Hannes
-
- Novice
- Posts: 5
- Liked: never
- Joined: Mar 29, 2022 5:23 am
- Full Name: Erik Kaashoek
- Contact:
Re: Incorrectly restoring symbolic links as hard links
I understand what you say but restoring a backup becomes impossible with this behavior.
What I would like to happen is:
1: When you copy_to a folder the folder and all its data is copied.
2: When you copy_to a symlink the symlink is created in the "to" location with the same content as the symlink in the backup.
I know that above is not the behavior of windows copy & paste but for restoring data its the only logical behavior
What also needs to be done is to show in the VEEAM restore explorer window what items are symlinks.
Windows solves this problem by hiding the symlinks in the users root folder (such as "Application Data", "Coockies" and "Local settings") . But they are present and copied to the backup.
Keep in mind symlinks could be anywere in the many gigabytes being restored.
With the current behavior you have to compare the content and repair all the symlinks.
What I would like to happen is:
1: When you copy_to a folder the folder and all its data is copied.
2: When you copy_to a symlink the symlink is created in the "to" location with the same content as the symlink in the backup.
I know that above is not the behavior of windows copy & paste but for restoring data its the only logical behavior
What also needs to be done is to show in the VEEAM restore explorer window what items are symlinks.
Windows solves this problem by hiding the symlinks in the users root folder (such as "Application Data", "Coockies" and "Local settings") . But they are present and copied to the backup.
Keep in mind symlinks could be anywere in the many gigabytes being restored.
With the current behavior you have to compare the content and repair all the symlinks.
Who is online
Users browsing this forum: Bing [Bot], Semrush [Bot] and 56 guests