Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

OS Error when configuring Log Shipping Expand / Collapse
Author
Message
Posted Thursday, September 20, 2012 3:48 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Monday, August 11, 2014 1:29 PM
Points: 31, Visits: 121
I am attempting to set up Log Shipping, and after going through the configuration wizard, I continually get the following error when I try to kick it off:

"Cannot open backup device '\\Servername\sharename\filename.bak'. Operating system error 2(The system cannot find the file specified.).
RESTORE FILELIST is terminating abnormally. (Microsoft SQL Server, Error: 3201)

And on the secondary server, I have the following error in the event viewer:

BackupDiskFile::OpenMedia: Backup device '\\Servername\sharename\filename.bak' failed to open. Operating system error 2(The system cannot find the file specified.).

The service account used in the SQL Server Agent on both servers is a domain account with full permissions to the shares in both locations. It completes the initial backup, then goes to the copy and that's where it breaks. Any ideas?
Post #1362361
Posted Thursday, September 20, 2012 4:38 PM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 6:36 AM
Points: 6,423, Visits: 13,818
thotvedt (9/20/2012)
is a domain account with full permissions to the shares in both locations. It completes the initial backup, then goes to the copy and that's where it breaks. Any ideas?

Besides the share permissions you must also set the ntfs permissions on the security tab


-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs"
Post #1362375
Posted Friday, September 21, 2012 9:25 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Monday, August 11, 2014 1:29 PM
Points: 31, Visits: 121
Yes, sorry. I did those as well. For the sake of testing, the account has full permissions under both tabs, and is the service account used for the SQL Server Agent.
Post #1362781
Posted Friday, September 21, 2012 12:26 PM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 6:36 AM
Points: 6,423, Visits: 13,818
can you post a screenshot of the point in the wizard where the error appears?

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs"
Post #1362903
Posted Friday, September 21, 2012 12:46 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Monday, August 11, 2014 1:29 PM
Points: 31, Visits: 121
I attached a jpeg screenshot. I apologize for size ration, but you should be able to zoom in and scroll over.

Essentially, the error occurs upon completion of the wizard when I select "Okay" to kick off the creation of the Log Shipping config. It performs the backup, but cannot restore it to the secondary.


  Post Attachments 
LogShipping.jpg (17 views, 298.04 KB)
Post #1362916
Posted Saturday, September 22, 2012 10:50 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 6:36 AM
Points: 6,423, Visits: 13,818
Get back to basics, firstly the agent service account on the primary doesn't need any access to the copy location on the secondary server. It doesn't know about it and indeed, should not have access. The agent service account on the secondary must be able to access the share on the primary unchallenged.

On the primary you have created a folder to hold the LS backups, this folder is shared, list the share permissions below



Now list the security permissions applied to the folder




Now list the agent accounts for the primary node and secondary node sql server agent services


-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs"
Post #1363133
Posted Saturday, September 22, 2012 2:15 PM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 6:36 AM
Points: 6,423, Visits: 13,818
One further question,

When you set the details on the restore tab did you edit the restore options and enter different paths for the target\secondary data and log files?


-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs"
Post #1363170
Posted Tuesday, September 25, 2012 11:42 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Monday, August 11, 2014 1:29 PM
Points: 31, Visits: 121
Perry Whittle (9/22/2012)
Get back to basics, firstly the agent service account on the primary doesn't need any access to the copy location on the secondary server. It doesn't know about it and indeed, should not have access. The agent service account on the secondary must be able to access the share on the primary unchallenged.

Bear in mind, I'm merely testing right now. I intend to tighten security once I have a good handle on everything and move to production. I am using the same domain account as the SQL Server Agent Service account for both servers. My intent was to completely rule out rights issues in the OS while testing log shipping.

On the primary you have created a folder to hold the LS backups, this folder is shared, list the share permissions below

Full control

Now list the security permissions applied to the folder

Full control


Now list the agent accounts for the primary node and secondary node sql server agent services


Same domain account. And it also has full control on the secondary for the share under sharing and security tabs.
Post #1364205
Posted Tuesday, September 25, 2012 12:18 PM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 6:36 AM
Points: 6,423, Visits: 13,818
Perry Whittle (9/22/2012)
One further question,

When you set the details on the restore tab did you edit the restore options and enter different paths for the target\secondary data and log files?

?


-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs"
Post #1364227
Posted Tuesday, September 25, 2012 2:17 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Monday, August 11, 2014 1:29 PM
Points: 31, Visits: 121
No I didn't. My understanding is that it would use the default restore paths for the secondary instance.
Post #1364282
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse