Downtime for installation?

• 
  A SQL Backup cluster installation entails the following:
  
  - installing the SQL Backup server components on both the active and passive nodes
  - setting up the SQL Backup Agent service as a cluster resource in the SQL Server cluster group
  - registering the SQL Backup extended stored procedures on the clustered SQL Server instance
  
  Assuming your cluster is 'normal', for a new installation, all the above activities do not require a reboot of the machine nor a restart of the SQL Server instance.
  
  For an upgrade, you may need to bounce the SQL Server instance if the extended stored procedures cannot be replaced, usually because SQL Server does not release the library from its process space. This is more common on SQL Server 2000 instances.

  petey September 29, 2010 12:20

  - 0 +
• 
  Doesn't each node have a copy of the SQLBackupAgent?
  
  In making it a cluster resource, do you mean making it critical to the cluster, so if it fails, the cluster fails over?

  kingrudedog September 29, 2010 16:21

  - 0 +
• 

  Doesn't each node have a copy of the SQLBackupAgent?

  Yes, each nodes requires a SQL Backup Agent service running. And your point being?
  

  In making it a cluster resource, do you mean making it critical to the cluster, so if it fails, the cluster fails over?

  Actually, the SQL Backup cluster resource by default is set up so that it does not fail over the entire cluster. After installation, you should run it for a few days or so to check that everything's in order, before deciding to make it a critical resource.

  petey September 29, 2010 20:22

  - 0 +

Add comment

Please sign in to leave a comment.