June 25, 2009 at 1:22 pm
Hi,
I'm configuring Log shipping for database in which the primary and secondary are in different domains.
The copy job is failing with network path does not exist even though I'm able to access the path from run->\\serverB\D$\.
The same path I have mentioned in the log shipping configuration wizard.
Please advice.
June 25, 2009 at 1:30 pm
what about the service account, it is not your account being used to hit this share.
June 25, 2009 at 2:53 pm
Thanks,
In server A, the SQL Agent runs under ABC\mssqlsrv and in other Server Server B, the SQL Agent runs under XYZ\mssqlsrv. So In this case how can I share the folder?
June 25, 2009 at 4:12 pm
I remember doing something like this a few years ago. From memory, the only way around it is to loosen your share & NTFS permissions on the folder that the transaction logs sit in. Grant the Everyone group read rights to the share & in the ACL.
MARCUS. Why dost thou laugh? It fits not with this hour.
TITUS. Why, I have not another tear to shed;
--Titus Andronicus, William Shakespeare
June 25, 2009 at 5:53 pm
Update: I have just got log shipping running between two standalone servers, no domain at all. SQL Server & Agent were configured to use local user accounts (different names & passwords between servers). I imagine your results will be the same if you substitute \ with \.
The configuration summary is:
Sundry Notes
Required sa login for initial connection between primary & secondary, when adding secondary server to log shipping configuration.
Set AdventureWorks to FULL recovery model, perform full backup.
Restored full backup to secondary server with NORECOVERY.
Schedules were set to every 2 minutes (just to speed things up) except for restore, which was every 5 minutes.
Log Shipping Configuration
Primary server: ADVSRV1
Secondary server: ADVSRV2
Primary SQL Server service accounts:
\s_ADVSRV1Srv
\s_ADVSRV1Agt
Secondary SQL Server service accounts:
\s_SQLSrv
\s_SQLAgt
Service account passwords do not match between servers.
Database: AdventureWorks
Right-click AdventureWorks on primary, All Tasks -> Ship Transaction Logs
Primary server settings:
Log Shipping Share: \\ADVSRV1\LogShipDump
Share permissions: Everyone R
Log Shipping path: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Backup\LogShipDump
LogShipDump folder permissions: Inherited + Everyone R
Secondary server settings:
Secondary database already initialized with NORECOVERY
Destination folder for copied files: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Backup\LogShipRestore
LogShipRestore folder permissions: Inherited + SQLServer2005SQLAgentUser$ADVSRV2MSSQLSERVER RW
Restore: in norecovery mode, disconnect users when restoring
MARCUS. Why dost thou laugh? It fits not with this hour.
TITUS. Why, I have not another tear to shed;
--Titus Andronicus, William Shakespeare
June 26, 2009 at 2:09 am
are they trusted domains?
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply