Unable to Create Restore Plan Due to Break in the LSN Chain

Sometimes when you restore your database backup you can get:

“Unable to Create Restore Plan Due to Break in the LSN Chain” error.:

Let’s assume that you have to administer a database with the help of Microsoft SQL Server Management Studio (SSMS). All backups are made as scheduled and everything works just fine, and then, suddenly, a failure occurs and now you need to restore your database. You have all backups that you need to restore your database, so you start the restoration process from the last full backup with NORECOVERY option. After a successful operation you restore last differential backup file with the RECOVERY option but suddenly something goes wrong and you get the following error message:

This error occurs due to a problem with Microsoft products, and can occur in SQL Server Management Objects and only when you use Microsoft SQL Server Management Studio for database recovery.

To solve this issue you need to restore the database manually using the following T-SQL commands to perform full and differential backups: 

RESTORE DATABASE BILLING FROM DISK = 'full.bak' WITH NORECOVERY, 

REPLACE

RESTORE DATABASE BILLING FROM DISK = 'diff.bak' WITH RECOVERY

If you prefer to continue working with Microsoft SQL Server Management Studio you have to restore backups not one by one but all at once.

But if you need to restore your full backup quickly, then use One-Click SQL Restore. It is a simple and free tool that restores full MS SQL server database backups.

Note: Microsoft recommends installing the latest cumulative update for SQL Server to avoid getting “unable to create restore plan due to break in the lsn chain” error message in future.

My backup plan is:

1. Full backup - once a day

                      2. Differential backup - every four hours

                               3. Transaction Log backup - every 30 minutes

So, to solve this issue and restore your database to point-in-time use T-SQL commands:

Restore your last full backup 

RESTORE DATABASE your_database FROM DISK = 'd:/full' WITH NORECOVERY, REPLACE

Restore your last differential backup

 RESTORE DATABASE your_database FROM DISK = 'd:/diff' WITH NORECOVERY

Restore your transaction log backups,

when you will restore the last transaction log backup point the time you need to restore your database

 RESTORE LOG your_database FROM DISK = 'd:/log1' WITH NORECOVERY RESTORE LOG your_database FROM DISK = 'd:/log2' WITH STOPAT = '2016-01-05 13:29:59.000', RECOVERY

Resource Governor

Resource Governor is a new technology in SQL Server 2008 that enables you to manage SQL Server workload and resources by specifying limits on resource consumption by incoming requests. In the Resource Governor context, workload is a set of similarly sized queries or requests that can, and should be, treated as a single entity. This is not a requirement, but the more uniform the resource usage pattern of a workload is, the more benefit you are likely to derive from Resource Governor. Resource limits can be reconfigured in real time with minimal impact on workloads that are executing.

In an environment where multiple distinct workloads are present on the same server, Resource Governor enables you to differentiate these workloads and allocate shared resources as they are requested, based on the limits that you specify. These resources are CPU and memory.

Resource Governor is available only on the Enterprise, Developer, and Evaluation editions of SQL Server.

Types of Resource Issues

Resource Governor is designed to address the following types of resource issues which are commonly found in a database environment:

• Run-away queries on the server. In this scenario a resource intensive query can take up most or all of the server resources.
• Unpredictable workload execution. In this scenario concurrent applications on the same server have workloads of different size and type. For example, two data warehouse applications or a mix of OLTP and data warehouse applications. These applications are not isolated from each other and the resulting resource contention causes unpredictable workload execution.
• Setting workload priority. In this scenario one workload is allowed to proceed faster than another or is guaranteed to complete if there is resource contention. Resource Governor enables you to assign a relative importance to workloads.

-- Which resource pool is using how much of memory
SELECT pool_id
,NAME
,min_memory_percent
,max_memory_percent
,max_memory_kb / 1024 AS max_memory_in_MB
,used_memory_kb / 1024 AS used_memory_in_MB
,target_memory_kb / 1024 AS target_memory_in_MB
FROM sys.dm_resource_governor_resource_pools

Above DMV shows how the Resource Governor pools are configured and the values of memory currently. In case we have InMemory based databases, we need to understand which databases are configured to resource pools and what memory is currently mapped. This can also be got from the DMVs as shown below:

-- Check DB and pool binding

SELECT d.database_id
,d.NAME AS DbName
,d.resource_pool_id AS PoolId
,p.NAME AS PoolName
,p.min_memory_percent
,p.max_memory_percent
FROM sys.databases d
LEFT OUTER JOIN sys.resource_governor_resource_pools p
ON p.pool_id = d.resource_pool_id

The above shows the mapping of DB’s to resource pools. Do let me know if you have something similar used in your environments? If so, please share the same via comments.

Full backup and Copy-only full backup difference?

When you have a full backup and a set of log file backups, a log chain is maintained using the LSN (Log Sequence Number). If you want to do a backup without breaking the log chain, then do a copy-only backup.

If you do not do a copy-only backup, the log chain is broken and the backup you take will be the latest full backup. This means that the previous log backups cannot be applied to the newly taken full backups. The log chain is mostly maintained for point in time recoveries or log shipping scenarios.

For example: say you have a backup scenario that takes full backups every 6 hours (midnight, 6 am, noon, 6 pm) and log backups every 15 minutes. A request comes in at 9 am to have a copy of your DB placed on a test server. You want to take the backup without breaking your log chain or disrupting your backup jobs. This is when a copy-only backup is taken. The copy only backup will not disrupt your regular backup sets.

max worker threads option

Purpose of max worker threads option:

Thread pooling helps optimize performance when large numbers of clients are connected to the server. Usually, a separate operating system thread is created for each query request. However, with hundreds of connections to the server, using one thread per query request can consume large amounts of system resources. The max worker threads option enables SQL Server to create a pool of worker threads to service a larger number of query request, which improves performance.

Use the max worker threads option to configure the number of worker threads available to Microsoft SQL Server processes. SQL Server uses the native thread services of the Microsoft Windows 2000 and Windows Server 2003 operating systems so that one or more threads support each network that SQL Server supports simultaneously, another thread handles database checkpoints, and a pool of threads handles all users.

The max worker threads option is an advanced option. If you are using the sp_configure system stored procedure to change the setting, you can change max worker threads only when show advanced options is set to 1. The system must be restarted in order for the new setting to take effect.

Calculating max worker threads:

The default value for max worker threads, 0, allows SQL Server to automatically configure the number of worker threads at startup. This setting is best for most systems; however, depending on your system configuration, setting max worker threads to a specific value sometimes improves performance.

The following table shows the automatically configured number of max worker threads for various combinations of CPUs and versions of SQL Server.

Number of CPUs	32-bit computer	64-bit computer
<= 4 processors	256	512
8 processors	288	576
16 processors	352	704
32 processors	480	960

Note: We recommend 1024 as the maximum for 32 bit SQL Server.

When the actual number of query request is less than the amount set in max worker threads, one thread handles each query request. However, if the actual number of query request exceeds the amount set in max worker threads, SQL Server pools the worker threads so that the next available worker thread can handle the request.

Note: When all worker threads are active with long running queries, SQL Server may appear unresponsive until a worker thread completes and becomes available. Though not a defect, this can sometimes be undesirable. If a process appears to be unresponsive and no new queries can be processed, then connect to SQL Server using the dedicated administrator connection (DAC), and kill the process. To prevent this, increase the number of max worker threads.

Different Windows credential in SSMS

Connecting SQL Database with Different Windows credential in SQL Server Management Studio (SSMS)

1. Just open the command prompt (Start ->Run->CMD)

     runas /user:rajdiscoms\nagaraju.n ssms.exe

2. Then enter the password it will opened with respected login:

Interview Questions Answers – Clustering

1) What is Windows Cluster?

Clustering can be best described as a technology that automatically allows one physical server to take over the tasks and responsibilities of another physical server that has failed. The obvious goal behind this, given that all computer hardware and software will eventually fail, is to ensure that users running mission-critical applications will have very less downtime when such a failure occurs.

2) What is a Cluster Node?

A cluster node is a server within the cluster, and it has Windows Server and the Cluster service installed.

3) What is Cluster Service?

The cluster service manages all the activity that is specific to the cluster. One instance of the cluster service runs on each node in the cluster.

The cluster service does the following

• Manages Cluster Objects and Configurations
• Manages the local restart policy
• Coordinates with other instances of the cluster service in the cluster
• Handles event notification
• Facilitates communication among other software components
• Performs failover operations

4) What is called a Resource in Windows cluster?

A resource is a physical or logical entity, which has below properties:

• Can be brought online and taken offline
• Can be managed in the failover cluster
• Can be owned by only one node at a time

To manage resources, Cluster service communicates with a resource DLL through Resource Monitor.

5) What are the different states of a Resource in Windows cluster?

All resources can have following states

• Offline
• Offline_Pending
• Online
• Online_Pending
• Failed

6) What is a Cluster Group?

Conceptually, a cluster group is a collection of logically grouped cluster resources. It may contain cluster-aware application services, such as SQL Server Group, File Server.

7) What is Public Network?

A public network (also called as External network) provides client systems with access to cluster application services and IP address resources are created on networks that provide clients access to cluster services.

8) What is Private Network?

A private network (sometimes called as interconnect or heartbeat connect) is a network that is setup between the nodes of the cluster and it carries only internal cluster communications.

9) What is Heartbeat in Windows cluster?

Heartbeats are messages that Cluster Service regularly sends between the instances of Cluster Service that are on each node to manage the cluster.

10) What Failover and Failback terms mean in Windows Cluster?

Failover: Failover is the process of moving a group of resources from one node to another in the case of a failure. For example, in a cluster where Microsoft SQL Server is running on node A and node A fails, SQL Server automatically fails over to node B of the cluster.

Failback: Failback is the process of returning a resource or group of resources to the node on which it was running before it failed over. For example, when node A comes back online, SQL Server can fail back from node B to node A.

11) What is Quorum Drive?

This is a logical drive assigned on the shared disk array specifically for Windows Clustering. Clustering services write constantly on this drive about the state of the cluster. Corruption or failure of this drive can fail the entire cluster setup. It also acts as a voter in the fail over process in case of odd number of nodes.

12) Different types of Quorum Models supported in windows Server 2008?

• Node Majority – Used when Odd number of nodes are in cluster.
• Node and Disk Majority – Even number of nodes (but not a multi-site cluster)
• Node and File Share Majority – Even number of nodes, multi-site cluster
• No Majority: Disk Only – This is the traditional MSCS quorum model, where a shared quorum disk must be online and nodes must be able to communicate with that disk

13) What is Node Majority model?

This type of quorum is optimal for clusters having an odd number of nodes. In this configuration, only the nodes have votes. The shared storage does not have a vote. A majority of votes are needed to operate the cluster.

14) What is Node and Disk Majority model?

Nodes and a shared disk get votes. This configuration allows a loss of half the nodes, providing the disk witness is available, or over half the nodes are available without the disk witness being available. This is recommended for even number of nodes in the cluster.

15) What is Node and File Share Majority model?

This type of quorum is optimal for clusters having an even number of nodes when a shared witness disk is not an option. Other characteristics include the following:

• each node and the file share “witness” gets a vote
• it does not require a shared disk to reach a quorum
• the file share has no special requirements
• the file share should be located at a third site, making this type of quorum the best solution for geographically dispersed clusters

16) What is No Majority: Disk only mode?

The disk witness must be available to have quorum, but the number of available nodes doesn’t matter. If you have a four-node cluster and only one node is available, but the disk witness is available, you have quorum. If the disk witness isn’t available, then even if all four nodes are available you can’t have quorum.

17) What I Split Brain situation in Cluster?

Cluster nodes communicate with each other over the network (port 3343). When nodes are unable to communicate with each other, they all assume the resources of the other (unreachable) nodes have to be brought online. Because the same resource will be brought online on multiple nodes at the same time, data corruption may occur. These results in a situation called “Split Brain.”

18) How Spilt Brain situation is resolved?

To prevent Split Brains we need to bring the cluster resource online on a single node (rather than multiple nodes).  Each of the online node cast vote for majority and the resources come online on that group which has more votes or has majority. In case of Even number of nodes Quorum also acts as a voter to eliminate split brain situation.

19) What are the Hardware requirements for Windows Server Cluster?

Windows Cluster

• Two windows servers (nodes)
• At least one shared disk array that supports, either SCSI or fibre channel.
• Each server must have a SCSI or fiber channel adapter to talk to the shared disk array. The shared disk array cannot use the SCSI controller used by the local hard disk or CD-ROM.
• Each server must have two PCI network cards (one for the private connection and one for the public connection)
• 1 IP Address for Windows virtual cluster name

20) What are the Hardware requirements for SQL Server Cluster?

• 1 IP Address for MSDTC service
• 1 IP Address for SQL Server Active\Passive Instance or 2 IP address for SQL Server Active\Active Instance
• 1 IP Address for SQL Server Analysis services (if needed)

21) How many IP Addresses we require for setting up Active\Passive SQL Server cluster?

• 2 Windows nodes – Public
• 2 Private IP Addresses – Private
• 1 Windows Virtual Cluster Name
• 1 MSDTC
• 1 SQL Server Virtual Network Name

22) How many IP Addresses we require for setting up Active\Active SQL Server cluster with Analysis services?

• 2 Windows nodes – Public
• 2 Private IP Addresses – Private
• 1 Windows Virtual Cluster Name
• 1 MSDTC
• 1 SQL Server Virtual Network Name
• 1 SQL Server Analysis Services

23) How do you open a Cluster Administrator?

Start Menu > Run >  Cluadmin.msc

24) What is SQL Server Network Name (Virtual Name)?

This is the SQL Server Instance name that all client applications will use to connect to the SQL Server.

25) Different types of SQL Server Cluster?

• Active\Passive
• Active\Active

26) What is the difference between Active\Passive and Active\Active cluster?

·         An Active – Passive cluster is a failover cluster configured in a way that only one cluster node is active at any given time. The other node, called as Passive node is always online but in an idle condition, waiting for a failure of the Active Node, upon which the Passive Node takes over the SQL Server Services and this becomes the Active Node, the previous Active Node now being a Passive Node.

·         An Active – Active cluster is a failover cluster configured in a way that both the cluster nodes are active at any given point of time. That is, one Instance of SQL Server is running on each of the nodes always; when one of the nodes has a failure, both the Instances run on the only one node until the failed node is brought up (after fixing the issue that caused the node failure). The instance is then failed over back to its designated node.

27) Difference between SQLSERVER 2005 and SQLSERVER 2008 Cluster Installation?

In sql2005 we have the option of installing SQL in remaining nodes from the primary node, But in sql2008 we need to go separately (Login to the both nodes) for installing SQL cluster

28) Can we change the Quorum settings after installing the windows cluster?

·         Yes, we can change the Quorum setting after the Windows Cluster installation.

29) Is it mandatory to configure MSDTC in Windows 2008 cluster before installing SQL Server cluster?

·         No it’s not mandatory to configure MSDTC service to install SQL Server in Windows 2008 cluster. Installation will give you a warning but will not stop the installation.

30) What are the Benefits of SQL Server Cluster?

• Reduces downtime to a bare minimum.
• Permits an automatic response to a failed server or software. No human intervention is required.
• It allows you to perform upgrades without forcing users off the system for extended periods of time.
• It allows you to reduce downtime due to routine server, network, or database maintenance.
• Clustering doesn’t require any servers to be renamed. So when failover occurs, it is relatively transparent to end-users.
• Failing back is quick, and can be done whenever the primary is fixed and put back on-line.

31) What are the Drawbacks of SQL Server Cluster?

• More expensive than other failover alternatives, such as log shipping or stand-by servers.
• Requires more set up time than other alternatives.
• Requires more on-going maintenance than other alternatives.
• Requires more experienced DBAs and network administrators.

1. What new functionality does failover clustering provide in Windows Server 2008?

New validation feature. With this feature, you can check that your system, storage, and network configuration is suitable for a cluster.

Support for GUID partition table (GPT) disks in cluster storage. GPT disks can have partitions larger than two terabytes and have built-in redundancy in the way partition information is stored, unlike master boot record (MBR) disks.

2. What happens to a running Cluster if the quorum disk fails in Windows Server 2008 Cluster?

Cluster continues to work but failover will not happen in case of any other failure in the active node.

3. What happens to a running Cluster if the quorum disk fails in Windows Server 2003 Cluster?

In Windows Server 2003, the Quorum disk resource is required for the Cluster to function. In your example, if the Quorum disk suddenly became unavailable to the cluster then both nodes would immediately fail and not be able to restart the cluster service.

4. What are Virtual Servers?

Groups that contain an IP address resource and a network name resource (along with other resources) are published to clients on the network under a unique server name. Because these groups appear as individual servers to clients, they are called virtual servers. Users access applications or services on a virtual server the same way they access applications or services on a physical server. They do not need to know that they are connecting to a cluster and have no knowledge of which node they are connected to.

5. How do you bring the SQL Server down?

In the Cluster Administrator, rick click on the SQL Server Group and from the popup menu item choose Take Offline.

6. How will you add a disk to the SQL Group cluster?

After adding the shared disk in the storage, we can add disk to the respective SQL Server Group.

7. What is the maximum number of nodes in an MNS cluster in Windows Server 2008, Enterprise x64 Edition?

Maximum 16.

8. What does a failover cluster do in Windows Server 2008?

A failover cluster is a group of independent computers that work together to increase the availability of applications and services. The clustered servers (called nodes) are connected by physical cables and by software. If one of the cluster nodes fails, another node begins to provide service (a process known as failover). Users experience a minimum of disruptions in service.

9. What are Services and Application folder represent?

Services and applications are managed as single units for configuration and recovery purposes. If a resource depends on another resource, both resources must be a member of the same service or application. For example, in a file share resource, the service or application containing the file share must also contain the disk resource and network resources (such as the IP address and NetBIOS name) to which clients connect to access the share. All resources within a service or application must be online on the same node in the cluster.

10. What kinds of permissions are required in the active directory to setup the SQL Server cluster objects?

Service account needs create object permissions in the Active Directory.

11. Why do we keep SQL Services in manual mode on each of the instance?

SQL Services should always be in manual mode in case of cluster because these are managed by the Cluster service and it’s taken online on its respective owner node based on the failover.

12. What is Distributed lock management?

Distributed lock management (DLM): Distributed lock management (DLM) enables two servers to access the same physical disk at the same time without corrupting the data. If a device is updating a particular file or piece of data, the device gets locked so that another controller can’t seize ownership and overwrite the data. NT does not currently support DLM, so disks are dedicated to one node or the other.

13. What is “Look Alive”?

LooksAlive: Verifies that the SQL Server service runs on the online node every 5 seconds by default.

14. What is “IS Alive”?

IsAlive: Verifies that SQL Server accepts connections by executing sp_server_diagnostics. This health detection logic determines if a node is down and the passive node then takes over the production workload.

15. What are SQL Server Cluster aware services?

• SQL Server Service
• SQL Server Agent Service
• SQL Server Analysis Service

16.  What are SQL Server Cluster unaware services?

• SQL Server Reporting Service
• SQL Server Integration Service

17.  What are Validation tests in Windows Cluster?

Validation test is a mechanism of verifying that all the components which are participating in the Windows cluster are fine and failover is happening between the nodes.

18. What are the basics tests done by the validation tests in Windows Cluster?

• Cluster Configuration tests: Validate important cluster configuration settings.
• Inventory tests: Provide an inventory of the hardware, software, and settings (such as network settings) on the servers, and information about the storage.
• Network tests: Validate that networks are set up correctly for clustering.
• Storage tests: Validate that the storage on which the failover cluster depends is behaving correctly and supports the required functions of the cluster.
• System Configuration tests: Validate that the system software and configuration settings are compatible across servers.

19. Where the results of validation tests are stored?

These reports are automatically stored for you in C:\Windows\Cluster\Reports as MHTML files.

20. Is SQL Server a Load balancing solution or not?

No, it’s not a Load balancing solution.

21. Will there be any downtime in Active\Active cluster in case of any failover?

Yes, definitely there will be downtime when SQL Server failover from one node to another.

22 Can we use other SQL Server cluster Nodes for reporting purpose as we can do in Logshipping and Database mirroring?

No it’s not possible in SQL Server Cluster feature.

23. Can we place out Non Critical SQL Server User Databases on a Clustered Instance on Disks that are not clustered to Save Money?

No, it’s not possible. SQL Server 2012 and all previous versions of SQL Server require databases be created on clustered resources. Internal drives or drives which are not part of the cluster group cannot hold user databases.

24. Can we configure Tempdb database on a local drive?

With the introduction of SQL Server 2012 Microsoft officially supports local disk TempDB in SQL Server cluster configurations.

25. Can we configure Windows cluster between two servers which are having different hardware and software configurations?

No it is not possible.

26. What is SMB share?

SMB stands for Server Message Block file server which can be used as a storage option starting SQL Server 2012 to store system databases (Master, Model, MSDB, and TempDB), and Database Engine user databases .

27. How can we check the current node/host name where SQL Server is running?

Select serverproperty(‘ComputerNamePhysicalNetBIOS’)

28. How to view the Cluster Nodes using command line?

C:\Windows\System32>cluster node

--or

C:\Windows\System32>cluster node /status

29. How to view the status for all cluster resource groups.

C:\Windows\System32>cluster group

--or

C:\Windows\System32>cluster group /status

30. How to get a listing of all available cluster resources?

C:\Windows\System32>cluster resource

--or

C:\Windows\System32>cluster resource /status

31. How to failover a service from one node to another?

C:\Windows\System32>cluster group "groupname" /move:nodeName