How can we help you today? How can we help you today?
randyj
I have keys named HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\PRODUCTION and HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Staging But no keys under those corresponding to 'Cluster\ClusterName' / comments
I have keys named HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\PRODUCTION and HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Staging But no keys under those corresponding ...
0 votes
services are installed and running on both nodes of the cluster. On one node of the cluster, I see C:\Program Files\Red Gate\SQL Backup\(LOCAL) and C:\Program Files\Red Gate\SQL Backup\Production On the other node, I see C:\Program Files\Red Gate\SQL Backup\(LOCAL), C:\Program Files\Red Gate\SQL Backup\Production and C:\Program Files\Red Gate\SQL Backup\Staging. The second node was installed when both the Production and Staging DB resources were resident on the second node. Currently (and in all cases except when failover occurs for whatever reason) each node should have a (local) and one or the other of Production / Staging instances resident. IE Node1 should have (LOCAL) and PRODUCTION, and Node2 should have (LOCAL) and STAGING. I have registered both Servers in the GUI tool, using the 'Cluster' Name, rather than the DNS name, so that they should be able to backup / restore to the DB, regardless of which node has control of the physical assests. Each physical node of the cluster has control of the appropriate resources : For 'Production' SQL IP Address (PROD-PDB01) SQL Network Name (PROD-PDB01) SQL Server (Production) SQL Server Agent (Production) SQL Server Fulltext (Production) Production DataDisk Production LogDisk I have installed the Server on both nodes. When I attempt to backup a db on Node1 (Production) FROM Node1, I get an error: Backup Account   Backing up Account (full database) on PRODUCTION instance to: N:\Microsoft SQL Server\MSSQL.1\MSSQL\Backup\FULL_PRODUCTION_Account_20060123_124454.sqb Login timeout expired Login timeout expired SQL Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF]. SQL error code: -1 This error is repeated no matter what combination of server / db I attempt on. A 'Bug Report' is generated, but I do not want to post it here. I'm happy to provide it to a support email address, though. So ... what the heck is going on ? / comments
services are installed and running on both nodes of the cluster. On one node of the cluster, I see C:\Program Files\Red Gate\SQL Backup\(LOCAL) and C:\Program Files\Red Gate\SQL Backup\Production O...
0 votes
A thought occurs to me - Could this be because we run on 'non-standard' ports ? If so, how do I work around this ? / comments
A thought occurs to me - Could this be because we run on 'non-standard' ports ? If so, how do I work around this ?
0 votes
Thats part of my problem - I cannot register a server /instance to select to install /upgrade. In the beta, we had to do 'sqbcoreservice -install -i <instance name> ' and then add the x_sprocs thru a query. / comments
Thats part of my problem - I cannot register a server /instance to select to install /upgrade. In the beta, we had to do 'sqbcoreservice -install -i <instance name> ' and then add the x_sprocs thru...
0 votes