September 2, 2010 at 12:03 pm
Hi,
We have a 2 node cluster setup for SQL Server 2008 on Windows 2008.
We have the following shared disks in SQLGroup resource
C - OS -> Local
D - Data -> Shared disk
E - Loga -> Shared disk
T - TempDb -> Shared disk
Z - Backup -> Shared disk
Q - Witness -> Shared disk
Y - MSDTC -> Shared disk
Now, I'm configuring the log shipping for the databases and want to create a Shared folder on Z drive to keep the Log backup files (.trn files)
Question:
1. Can we directly create a Shared folder as we create in Standalone Server? or
2. We must need to create File Share resource from Failover cluster Manager?
Please advice
September 2, 2010 at 12:36 pm
Hi,
I have created a normal Shared folder LogBackups" on Z drive and given the following path for the backup settings in Log shipping wizrad (Here, I have given the Virtual Server name in the backup path)
\\SQLVS\LogBackups
and it's working fine on Node1. But when I move to Node2, the log shipping backup job is failing with the below message:
Message
Executed as user: abc\mssqlsrv. The process could not be created for step 1 of job 0x50A3BCCAD4A43142B64E1E5FBD7E5D88 (reason: The system cannot find the path specified). The step failed.
So does that mean, we need to MUST create File share resource instead of Normal Shared folder?
Please advice
September 2, 2010 at 4:38 pm
I have created the shared folder following the below steps:
In the Failover Cluster Management, Expand Services and Applications, Select the SQLGroup ->RightClick->Add a shared folder.
The Create a Shared Folder Wizard appears and followed the instructions in the wizard to specify the settings for the shared folder, including path, name, and permissions
On node1, the log shipping backups are running fine but when I moved the resources to Node2, log shipping backup job is failing with the below message:
Message
Executed as user: ABC\mssqlsrv. The process could not be created for step 1 of job 0x21BEEAF354A5484684269457B6389F29 (reason: The system cannot find the path specified). The step failed.
Please advice...The same file share used to work like charm in Windows 2003 cluster with SQL Server 2005
Thanks
September 2, 2010 at 10:38 pm
This is Known issue with SQL Server 2008 Add node operation.
Please go through the below link:
Thanks
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply