Table of Contents | |||
Long Term Support Stable, tested ServerTemplate assets |
|
Current revision: 2
Date published: 2013/08/30 00:03:17 +0000
MultiCloud Marketplace: https://my.rightscale.com/api/acct/2901/ec2_server_templates/316501001
This ServerTemplate is on the LTS Lineage. For the latest Infinity version, see the Infinity Release For a description of the Infinity and LTS lineages, see ServerTemplate Release Methodology This ServerTemplate configures a Microsoft SQL Server standalone database server or pair of servers in a high-availability (HA) configuration (synchronous mirroring). It supports graceful (no data loss) and forceful (possible data loss) manual failover, with the latter to be used for disaster-recovery situations. This can also be used with our SQL Server Witness ServerTemplate to provide automatic failover. Also included are built-in monitoring and alerts on CPU, memory, and disk. Key Features: * MS Best Practices for disk and database configuration. * Cloud-agnostic data storage on dynamic volumes or equivalent. * Striped data and log volumes (on supported clouds). * Automatically scheduled backups with data consistency. * Backup and restore to/from remote storage to enable data migration between clouds. Related ServerTemplates: Microsoft SQL Server Witness Microsoft Active Directory Microsoft IIS App Server Documentation: Database Manager for MS SQL Server Release Notes Tutorial
The following MultiCloud Images (MCIs) are used by the ServerTemplate. The MCIs determine which operating systems and clouds are supported.
MultiCloud Images
The Access Key ID is an Amazon Access Credential that's used to authenticate your requests to AWS services. It's unique to your AWS Account Number. The Access Key ID and Secret Access Key are used to retrieve objects from an S3 bucket that are 'private'. Log into your AWS account at aws.amazon.com to retrieve your access identifiers. It's strongly recommended that you use a RightScale Credential (Design > Credentials) to hide the actual key value from non-admin users while still allowing them to pass the appropriate value as an input. Ex: 1JHQQ4KVEVM02KVEVM02
The Secret Access Key is an Amazon Access Credential that's used to authenticate your requests to AWS services. It's unique to your AWS Account Number. The Access Key ID and Secret Access Key are used to retrieve objects from an S3 bucket that are 'private'. Log into your AWS account at aws.amazon.com to retrieve your access identifiers. It's strongly recommended that you use a RightScale Credential (Design > Credentials) to hide the actual key value from non-admin users while still allowing them to pass the appropriate value as an input. Ex: XVdxPgOM4auGcMlPz61IZGotpr9LzzI07tT8s2Ws
Name of the volume type for backup volume (on supported clouds, currently Rackspace Open and CloudStack). On Rackspace Open both SATA and SSD volume types are supported, size of the volume should be specified via BACKUP_VOLUME_SIZE input. On CloudStack-based clouds volume types depend on cloud configuration.
Name of the volume type for data volume (on supported clouds, currently Rackspace Open and CloudStack). On Rackspace Open both SATA and SSD volume types are supported, size of the volume should be specified via DATA_VOLUME_SIZE input. On CloudStack-based clouds volume types depend on cloud configuration.
The number of daily snapshots (backups) to keep (i.e. rotation size). A daily backup is defined as the latest completed snapshot of a day that is closest to the end of the day (23:59:59). (Default: 14) See "Archiving of EBS Snapshots" on RightScale's Support site for further details on the archiving logic.
ID of DNS record or zone to be updated. This input has specific meaning for each DNS provider: DNS Made Easy: 7-digit DNS record ID provided by DNS Made Easy. Ex: 1234123 DynDNS: not used Rackspace Cloud DNS: ID if Rackspace DNS zone of the record to be updated. Ex: 123456 Route53: ID of Route53 zone of the record to be updated. Ex: Z1BINKNIEY8Y9L Set to "text:" and leave blank to bypass DNS registration on boot.
Password or authentication key that is used to access and modify DNS records. Provider-specific details: DNS Made Easy: Password of your DNS Made Easy account: Ex: cred:DME_PASSWORD DynDNS: Password of your DynDNS account. Ex: cred:DYN_DNS_PASSWORD Rackspace Cloud DNS: Rackspace API authentication key. Ex: cred:RACKSPACE_AUTH_KEY Route53: Your AWS Secret Access Key. Ex: cred:AWS_SECRET_ACCESS_KEY
Username or account ID that is used to access and modify DNS records. Provider-specific details: DNS Made Easy: Username of your DNS Made Easy account: Ex: mydnsacct DynDNS: Username of your DynDNS account. Ex: mydnsacct Rackspace Cloud DNS: Username of your Rackspace account. Ex: cred:RACKSPACE_USERNAME Route53: Your AWS Access Key ID. Ex: cred:AWS_ACCESS_KEY_ID Set to "text:" and leave blank to bypass DNS registration on boot.
Enabling this option will force a SQL based transaction log backup to be issued before the volume snapshot backup is taken. This is provided to facilitate transaction log truncation when using the BACKUP_METHOD of snapshots. Note that the log backup is performed for all user databases in full recovery model and saved to temp_tlog_backups dir on logs volume.
Name of the volume type for logs volume (on supported clouds, currently Rackspace Open and CloudStack). On Rackspace Open both SATA and SSD volume types are supported, size of the volume should be specified via DATA_VOLUME_SIZE input. On CloudStack-based clouds volume types depend on cloud configuration.
Password used for encryption of master database master key. This password is used to encrypt master key when it's created or decrypt when opening existing master key. Using a credential is strictly recommended for this input. Please see our support portal for more information on using credentials. Ex: cred:MY_MASTER_KEY_PASSWORD
Certificate to be used for authentication on mirroring endpoint of Mirror server. This input is required when launching Principal, Mirror or Witness but not needed for Standalone SQL Server. Use a credential containing encoded certificate and private key generated by "DB SQLS Generate and Save a Certificate" RightScript. Note that the private key is encryped by password (MIRROR_PRIVATE_KEY_PASSWORD input). Please see our support portal for more information on using credentials for passing certificates for mirroring authentication.
Password to decrypt private key containing in MIRROR_CERTIFICATE input. This input is required when launching Principal, Mirror or Witness but not needed for Standalone SQL Server. Should be the same password which was used to generate and encode certificate and private key by "DB SQLS Generate and Save a Certificate" RightScript. Please see our support portal for more information on using credentials for passing certificates for mirroring authentication.
Number of disks used in the logical volume stripe created for the data and log volumes. A value of 1 means (no striping). This value can be between 1 and 5 depending on the cloud/instance size you are using. For Amazon EC2 the max value is 5. For CloudStack based clouds max value is 2. For Windows Azure the max value depends on the instance size you are using. For standalone configurations, determine the total disk count by multiplying the number of stripes times the total number of data and log volumes (default 2). For high availability configurations, add 1 to that total to determine your total disk count. Ex: 1
Use this input to restore from specific snapshot or remote storage backup identified by its timestamp. For snapshots-based backup the timestamp could be found in 'rs_backup:timestamp=...' tag. For remote storage backup the timestamp could be extracted from file names. If this input is undefined, the latest backup in the lineage will be used. Ex: 1306232588
Use this input to reserve drive letter for temporary volume at boot time and assign to the volume when using temp volume in mirroring initialization. Drive letters D-P are supported on EC2, D-J are supported on CloudStack. Note, that all volume letter inputs should have different values. Ex: G
Certificate to be used for authentication on mirroring endpoint of Principal server. This input is required when launching Principal, Mirror or Witness but not needed for Standalone SQL Server. Use a credential containing encoded certificate and private key generated by "DB SQLS Generate and Save a Certificate" RightScript. Note that the private key is encryped by password (PRINCIPAL_PRIVATE_KEY_PASSWORD input). Please see our support portal for more information on using credentials for passing certificates for mirroring authentication.
Password to decrypt private key containing in PRINCIPAL_CERTIFICATE input. This input is required when launching Principal, Mirror or Witness but not needed for Standalone SQL Server. Should be the same password which was used to generate and encode certificate and private key by "DB SQLS Generate and Save a Certificate" RightScript. Please see our support portal for more information on using credentials for passing certificates for mirroring authentication.
Password to encrypt private key. The password must meet the Microsoft SQL Server Strong Password requirements: Does not contain all or part of the user's account name Is more than eight characters in length Contains characters from at least three of the following categories: English uppercase characters (A through Z) English lowercase characters (a through z) Base 10 digits (0 through 9) Nonalphabetic characters (for example: !, $, #, %) For more information please see [Microsoft SQL Server Strong Password Guidelines](http://msdn2.microsoft.com/en-us/lib.../ms144284.aspx)
The Account ID or Name of the Remote Storage account which is used to authenticate your requests to Remote Storage services. It's strongly recommended that you use a RightScale Credential (Design > Credentials) to hide the actual key value from non-admin users while still allowing them to pass the appropriate value as an input. Ex: cred:AWS_ACCESS_KEY_ID
The Secret Key or Password of the Remote Storage account which is used to authenticate your requests to Remote Storage services. It's strongly recommended that you use a RightScale Credential (Design > Credentials) to hide the actual key value from non-admin users while still allowing them to pass the appropriate value as an input. Ex: cred:AWS_ACCESS_SECRET_KEY_ID
The endpoint URL for the Remote Storage provider. Currently this is used to specify endpoint for OpenStack Swift. Ex: http://myswift.com:5000/v2.0/tokens
Set this input to True to force network connection to remote storage service using private interface (if the server is located in the same cloud/datacenter as remote storage service). This input is supported for Rackspace Open cloud, SoftLayer and OpenStack. Default is False (using public network interface). Ex: True.
Certificate to be used for authentication on mirroring endpoint of Witness server. This input is required when launching Principal, Mirror or Witness but not needed for Standalone SQL Server. Use a credential containing encoded certificate and private key generated by "DB SQLS Generate and Save a Certificate" RightScript. Note that the private key is encryped by password (WITNESS_PRIVATE_KEY_PASSWORD input). Please see our support portal for more information on using credentials for passing certificates for mirroring authentication.
Password to decrypt private key containing in WITNESS_CERTIFICATE input. This input is required when launching Principal and Mirror servers with witness (and for Witness server too) but not needed for Standalone SQL Server. Should be the same password which was used to generate and encode certificate and private key by "DB SQLS Generate and Save a Certificate" RightScript. Please see our support portal for more information on using credentials for passing certificates for mirroring authentication.
Revision | Date Published | Description of Changes | Known Issues |
2 | Aug 29, 2013 | Initial release. See v13.5 LTS Release Notes. | N/A |
© 2006-2014 RightScale, Inc. All rights reserved.
RightScale is a registered trademark of RightScale, Inc. All other products and services may be trademarks or servicemarks of their respective owners.