if I could remove the drive letter from my portable backup storage device and still be able to register it in Veeam
While I am eager to hear the details behind you request too, can say that Endpoint Backup does not rely on the drive letters in terms of drive identification if we are talking about the removable storage.
makes sense if there is a need to have additional layer of protection for created backups
On a side note, what if you want to copy these files somewhere? You will need to assign drive letter and this should not change the behavior of configured backup task, correct?
BTW, are you planning to use portable device for all Endpoint backups or there is one device for each Endpoint?
Personally, I like the idea of how Windows Backup treats storage devices: "This device is for backup, keep your fingers out of it and I won't have to say: 'I told you so', later."
I am not sure if you are talking about technicalities that happen under the hood.
Don't forget, that it's annoying to have that drive in the explorer… Run mountvol.exe in CMD to see what I am talking about.
Have to disagree on this one. For most non-IT guys the situation may look scary: you plugged in the device, but it does not appear in my computer, so something is broken – call IT… Though, thinking of a temporary workaround in existing version, you should be able to mount the volume as a folder (somewhere in non root premises) and configure local backup to this folder.
CryptoWall will encrypt data files on network shares only if that network share is mapped as a drive letter on the infected computer. If it is not mapped as a drive letter, then CryptoWall will not encrypt any files on a network share.
Users browsing this forum: Google [Bot] and 15 guests