Computer Associates SQLSTQ99000600 Microsoft SQL Guide - Page 124

Restore Types and Methods, Restore Overview, Agent for Microsoft SQL Server Guide

Get Computer Associates SQLSTQ99000600 - Unicenter SQL-Station 6.0.0 PDF manuals and user guides
UPC - 757943257441
View all Computer Associates SQLSTQ99000600 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 124 highlights

Restore Overview Microsoft SQL Server locks a database while restoring it, so that the database cannot be modified during the restore operation. However, users can access and modify other Microsoft SQL Server databases during this time. Note: If a restore is attempted when you are accessing a database, Microsoft SQL Server will not allow the restore operation. Important! By default, Microsoft SQL Server 2005 will not allow a restore to be attempted if a database is online and is using the Full or Bulk-Logged Recovery Models. To restore these databases, you must either take the database offline by performing a Transaction Log backup with the Log Tail option so that no transactions are lost, or restore with the Overwrite Existing Database and Files ("WITH REPLACE") option. The only exception to this is an Online Torn Page Repair restore. If a failure occurs while a database is being restored, Microsoft SQL Server notifies the system administrator but does not recover the partially restored database. You must restart the database restore to complete the restore job. Note: If you cancel a restore job, the database may be left in a loading state and will be unusable until the restore sequence is completed. If the session that was being restored when the job was cancelled is not the first session in the restore sequence, you may have to start the restore sequence over from the beginning. The destination database must have at least as much storage space available for it as the backed up database. The actual amount of data in the backed up database is not relevant for this requirement. To get information about allocated storage space, use the Microsoft SQL Enterprise Manager or Management Studio, or the DBCC CHECKALLOC statement. If the database is offline, then check the file sizes listed in the file tree of the Agent Restore Options dialog for that session, or in the ARCserve Database Manager view. If you have a media failure, restart Microsoft SQL Server. If, after a media failure, Microsoft SQL Server cannot access a database, it marks the database as Suspect, locks it, and displays a warning message. You may have to drop (detach from Microsoft SQL Server) a damaged database, a process that you can perform using the Microsoft SQL Server Enterprise Manager or Management Studio. Restore Types and Methods You can restore from the following types of backup sessions: ■ Database Full and Differential backups ■ Partial Full and Differential backups ■ Transaction log backups ■ File and FileGroup Full and Differential backups 124 Agent for Microsoft SQL Server Guide

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
Restore Overview
124
Agent for Microsoft SQL Server Guide
Microsoft SQL Server locks a database while restoring it, so that the database
cannot be modified during the restore operation. However, users can access and
modify other Microsoft SQL Server databases during this time.
Note
: If a restore is attempted when you are accessing a database, Microsoft
SQL Server will not allow the restore operation.
Important!
By default, Microsoft SQL Server 2005 will not allow a restore to be
attempted if a database is online and is using the Full or Bulk-Logged Recovery
Models. To restore these databases, you must either take the database offline by
performing a Transaction Log backup with the Log Tail option so that no
transactions are lost, or restore with the Overwrite Existing Database and Files
(“WITH REPLACE”) option. The only exception to this is an Online Torn Page
Repair restore.
If a failure occurs while a database is being restored, Microsoft SQL Server
notifies the system administrator but does not recover the partially restored
database. You must restart the database restore to complete the restore job.
Note
: If you cancel a restore job, the database may be left in a loading state and
will be unusable until the restore sequence is completed. If the session that was
being restored when the job was cancelled is not the first session in the restore
sequence, you may have to start the restore sequence over from the beginning.
The destination database must have at least as much storage space available for
it as the backed up database. The actual amount of data in the backed up
database is not relevant for this requirement. To get information about allocated
storage space, use the Microsoft SQL Enterprise Manager or Management
Studio, or the DBCC CHECKALLOC statement. If the database is offline, then
check the file sizes listed in the file tree of the Agent Restore Options dialog for
that session, or in the ARCserve Database Manager view.
If you have a media failure, restart Microsoft SQL Server. If, after a media
failure, Microsoft SQL Server cannot access a database, it marks the database as
Suspect, locks it, and displays a warning message. You may have to drop
(detach from Microsoft SQL Server) a damaged database, a process that you can
perform using the Microsoft SQL Server Enterprise Manager or Management
Studio.
Restore Types and Methods
You can restore from the following types of backup sessions:
■
Database Full and Differential backups
■
Partial Full and Differential backups
■
Transaction log backups
■
File and FileGroup Full and Differential backups