DBAWinnipeg
Programmer
OK here's a fun little challenge
I have a production environment and take nightly full backups.
I have a reporting server that I would like to restore the production database backup to.
I shared the folder that the production backups are held (to everyone for now until I get it working)... and when I terminal service or PC Anywhere onto the reporting box I am able to map a drive to that location and can do whatever I want with the backup file
BUT
When I try and restore the file I get to the setting the device location
( \\CRMSQL01\data\BACKUPFILENAME.BAK)
and it is unable to verify the location.
So the troubleshooting I went through is
a) can I through START -> RUN go to the share - YES
b) can I rename the backup file (to ensure the file isn't locked by another user) - YES
c) can I restore the database onto the same server under a different name - YES
So I'm assuming it's something to do with SQL's ability to connect to the share... but I was under the assumtion that with the security being (SQL Server and Windows) that if I can map to the drive through START -> RUN and the path that I should be able to map to the share and get SQL to do a restore.
Any ideas??
Thanks in advance!!!
Colin in da 'Peg
I have a production environment and take nightly full backups.
I have a reporting server that I would like to restore the production database backup to.
I shared the folder that the production backups are held (to everyone for now until I get it working)... and when I terminal service or PC Anywhere onto the reporting box I am able to map a drive to that location and can do whatever I want with the backup file
BUT
When I try and restore the file I get to the setting the device location
( \\CRMSQL01\data\BACKUPFILENAME.BAK)
and it is unable to verify the location.
So the troubleshooting I went through is
a) can I through START -> RUN go to the share - YES
b) can I rename the backup file (to ensure the file isn't locked by another user) - YES
c) can I restore the database onto the same server under a different name - YES
So I'm assuming it's something to do with SQL's ability to connect to the share... but I was under the assumtion that with the security being (SQL Server and Windows) that if I can map to the drive through START -> RUN and the path that I should be able to map to the share and get SQL to do a restore.
Any ideas??
Thanks in advance!!!
Colin in da 'Peg