> Hi all,
>
> we have a 2 Node Active-Active SQL Cluster and wanted to enlarge disk
> space.
> The following steps we made:
> - Backup RAID 5 (Image)
> - Delete logical Volume by RaidManager
> - Changed Discs
> - Create new logical Volume by RaidManager
> - Restore of the Backup
>
> - Node1 started
> - Cluster Manager started
> - All "new" Volumes shows failure.
> - SQL Service shows failure
> - I deleted physical Resources and SQL Resoures in Cluster Manager
> - Create new physical Reources and SQL Resources in Cluster Manager
>
> Now the physical Resource is online and seems working, but the SQL
> Resource
> is not starting.
> Has anybody some experience with that problem?

"Russ Kaufmann [MVP]" wrote:

> "Andre Scheiberle" <AndreScheiberle@discussions.microsoft.com> wrote in
> message news:2EDB8977-93F5-48D2-A912-0C2080FF1C16@microsoft.com...
> > Hi all,
> >
> > we have a 2 Node Active-Active SQL Cluster and wanted to enlarge disk
> > space.
> > The following steps we made:
> > - Backup RAID 5 (Image)
> > - Delete logical Volume by RaidManager
> > - Changed Discs
> > - Create new logical Volume by RaidManager
> > - Restore of the Backup
> >
> > - Node1 started
> > - Cluster Manager started
> > - All "new" Volumes shows failure.
> > - SQL Service shows failure
> > - I deleted physical Resources and SQL Resoures in Cluster Manager
> > - Create new physical Reources and SQL Resources in Cluster Manager
> >
> > Now the physical Resource is online and seems working, but the SQL
> > Resource
> > is not starting.
> > Has anybody some experience with that problem?
>
> The SQL resources are probably still pointing to the old drives as
> dependencies.
>
>
> --
> Russ Kaufmann
> MVP - Windows Server - Clustering
> ClusterHelp.com, a Microsoft Certified Gold Partner
> Web http://www.clusterhelp.com
> Blog http://msmvps.com/clusterhelp
>
>