I have a few servers which backup to a Data Domain. This is accessible via a UNC path, i.e. \\datadomain\SqlBackups\ and all that seems to be done is we give the SQL Server access to the data server via Firewall rules, and we give SQL DB Service Account full access to the SqlBackups folder.

The server is configured to map the Y:\ drive to this location so backups go to Y:\<InstanceName>\<DatabaseName>.

This works until something happens with the drive mapping. For example, sometimes on reboot the mapping is lost so backups fail.

I just want to backup to the UNC path which I've tested and it works without fault. However I'm told there are security implications for this, something about making the UNC patch visible.

Can anybody shed any light on this from a SQL Server / Windows Server Security point of view? What's so bad about backing up the UNC path?

I have a few servers which backup to a Data Domain. This is accessible via a UNC path, i.e. \\datadomain\SqlBackups\ and all that seems to be done is we give the SQL Server access to the data server via Firewall rules, and we give SQL DB Service Account full access to the SqlBackups folder.

The server is configured to map the Y:\ drive to this location so backups go to Y:\<InstanceName>\<DatabaseName>.

This works until something happens with the drive mapping. For example, sometimes on reboot the mapping is lost so backups fail.

I just want to backup to the UNC path which I've tested and it works without fault. However I'm told there are security implications for this, something about making the UNC path visible to potential hackers... which doesn't make sense to me as you can just easily find out where a mapped drive points to.

Can anybody shed any light on this from a SQL Server / Windows Server Security point of view? What's so bad about backing up the UNC path?

I have a few servers which backup to a Data Domain. This is accessible via a UNC path, i.e. \\datadomain\SqlBackups\ and all that seems to be done is we give the SQL Server access to the data server via Firewall rules, and we give SQL DB Service Account full access to the SqlBackups folder.

The server is configured to map the Y:\ drive to this location so backups go to Y:\<InstanceName>\<DatabaseName>.

his works until something happens with the drive mapping. For example, sometimes on reboot the mapping is lost so backups fail.

I just want to backup to the UNC path which I've tested and it works without fault. However I'm told there are security implications for this, something about making the UNC patch visible.

Can anybody shed any light on this from a SQL Server / Windows Server Security point of view? What's so bad about backing up the UNC path?

I have a few servers which backup to a Data Domain. This is accessible via a UNC path, i.e. \\datadomain\SqlBackups\ and all that seems to be done is we give the SQL Server access to the data server via Firewall rules, and we give SQL DB Service Account full access to the SqlBackups folder.

The server is configured to map the Y:\ drive to this location so backups go to Y:\<InstanceName>\<DatabaseName>.

This works until something happens with the drive mapping. For example, sometimes on reboot the mapping is lost so backups fail.

I just want to backup to the UNC path which I've tested and it works without fault. However I'm told there are security implications for this, something about making the UNC patch visible.

Can anybody shed any light on this from a SQL Server / Windows Server Security point of view? What's so bad about backing up the UNC path?