Backup Exec and SUBST drives

[dori_bashan]

Hello

Using Backup Exec 15 FP4,

Is there any way to force Backup Exec to see SUBST drives?

as for now, even that the drive is seeing as a local in Windows Explorer, Backup Exec don't see it as one of the local drives and i can't select it a the source drove for backup.

tested with Win Server 2008 R2 and Server 2012 R2

Thanks

[CraigV]

If a subt simply assigns a local drive letter to a mapped drive, BE doesn't see mapped drives and this might explain why it doesn't show up in BE at all.

Thanks!

[dori_bashan]

SUBST assigns a local drive letter to a LOCAL folder,

this is why it is weird. any option to force it

[dori_bashan]

sorry if this is a double post..

SUBST assigns a local drive letter to a LOCAL folder,

this is why it is weird. any option to force it?

[Colin_Weaver]

As well as the remote device concept mentioned by CraigV, any drive connections that operate at the user level instead of the service level cannot be used by Backup Exec

This usually applies to mapped drives over CIFS (or similar) AND does not usually apply to iSCSI connections to remote storage (or similar) to provide some examples

Looking at SUBST itself, it looks like it can be used to connect to both local and remote devices  and based on internet recommendations for making it persistent (where suggestions of using user logon profiles appear to exist) it appears to operate within the context of the user

Whether or not your condition relates to the user context, it is likely that if SUBST can connect to either local or remote resources that we may not be able to code to understand which you have used and therefore block it all.

[dori_bashan]

Understood.

many thanks for all that info. all is clear now

Dori