In a cluster, SQL Server can only address drive letters that are a
dependency of the SQL Server resource. So, that pretty much answers all of
the questions.
It has to be on a drive letter that is within the SQL Server group AND has a
dependency on the SQL Server resource. If it doesn't meet these
requirements, SQL Server won't even see the drive letter. You could still
stuff it anywhere by specifying a UNC path, but that isn't recommended. A
local disk should NEVER be used, because if you lose node in the cluster you
are dumping backups to (the whole reason you have log shipping in place),
you lose all of the backups on that local drive that hadn't been applied.
--
Mike
http://www.solidqualitylearning.com Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
[quoted text, click to view] "vkb" <vkb@discussions.microsoft.com> wrote in message
news:7532F776-2707-4CAA-871A-5643FBFFD062@microsoft.com...
>I am setting up log shipping of SharePoint databases from a two node
> active/passive cluster to a stand alone instance of SQL. Versions are SQL
> 2000 w/ SP 3a on Windows 2003 SP1. Questions:
> - When I setup log shipping and designate a shared folder, what is the
> best
> practice for the location of the folder on the cluster?
> - Should it be a share disk in order to make sure it is available in the
> event of cluster failover?
> - If so, what resource group should it reside in?
> - If not and it should be local disk, how is this config affected by
> cluster
> failover?
>
> Thanks.