<div>
NEED HELP on this ASAP! &nbsp;This is production if you can believe it!<br />
<br />
Thanks so much!
</div>


NEED HELP on this ASAP!  This is production if you can believe it!

Thanks so much!

<div>
&lt;&lt;The drive was backed up without the databases being stopped! &gt;&gt;<br />
A disk backup is not a good way to backup live databases as you noticed now. The sql backup is there for to see it is usable.<br />
<br />
Don't forget to change your backup-strategy that any new database will automaticly be in your backup-job.
</div>


<<The drive was backed up without the databases being stopped! >>
A disk backup is not a good way to backup live databases as you noticed now. The sql backup is there for to see it is usable.

Don't forget to change your backup-strategy that any new database will automaticly be in your backup-job.

<div>
Found answer by googling but it gave credit to finding the answer on experts-exchange. &nbsp;Followed steps and it corrected the suspect databases.
</div>


Found answer by googling but it gave credit to finding the answer on experts-exchange.  Followed steps and it corrected the suspect databases.

<div>
<div class="content wysiwyg-content">
Today, someone added space to one of our disks where our log files reside. &nbsp;The drive was backed up without the databases being stopped! &nbsp;Before restoring the drive, the database was stopped. &nbsp;Luckily, no new data to the database had been added since we did the backup.<br />
<br />
When we brought up the databases, they all became suspect. &nbsp;Luckily, I had a backup of two of the databases but the other two, the ReportServer and ReportServerTempTempDB, we have never done a backups!!!<br />
<br />
I believe the reason it is suspect is because our log files are out of sync. &nbsp;Our .mdf should be fine but the .ldf is not. &nbsp;Is there a way I can bring the database out of suspect?<br />
<br />
Thanks!
</div>
</div>


Today, someone added space to one of our disks where our log files reside.  The drive was backed up without the databases being stopped!  Before restoring the drive, the database was stopped.  Luckily, no new data to the database had been added since we did the backup.

When we brought up the databases, they all became suspect.  Luckily, I had a backup of two of the databases but the other two, the ReportServer and ReportServerTempTempDB, we have never done a backups!!!

I believe the reason it is suspect is because our log files are out of sync.  Our .mdf should be fine but the .ldf is not.  Is there a way I can bring the database out of suspect?

Thanks!

Databases in Suspect Mode

Microsoft SQL Server is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.SQL Server is available in multiple versions, typically identified by release year, and versions are subdivided into editions to distinguish between product functionality. Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning.

Microsoft SQL Server

Microsoft SQL Server 2008 is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning. Major improvements include the  Always On technologies and support for unstructured data types.

Microsoft SQL Server 2008

SQL Server Reporting Services (SSRS) is a server-based report generation software system from Microsoft. It can prepare and deliver a variety of interactive and printed reports and is administered via a web interface or its web service. Its web services interface also supports the development of custom reporting applications. Finally, SSRS can also be integrated with SharePoint. SSRS competes with other business intelligence tools, most prominently Crystal Reports.