I'd start with verifying the backup file using the following statements:
restore headeronly from disk = 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.DBASE\MSSQL\Restore\DBASE.BAK'
...returns a result set containing all the backup header information for all backup sets on a particular backup device.
restore verifyonly from disk = 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.DBASE\MSSQL\Restore\DBASE.BAK'
...Verifies the backup but does not restore it, and checks to see that the
backup set is complete and the entire backup is readable. However,
RESTORE VERIFYONLY does not attempt to verify the structure of the data
contained in the backup volumes. In Microsoft SQL Server, RESTORE VERIFYONLY
has been enhanced to do additional checking on the data to increase the
probability of detecting errors. The goal is to be as close to an actual
restore operation as practical.
If the backup file is ok then you can continue with shutting down the database and ensuring nobody else accesses the database:
ALTER DATABASE DBASE SET OFFLINE WITH ROLLBACK IMMEDIATE;
ALTER DATABASE DBASE SET ONLINE
ALTER DATABASE DBASE SET RESTRICTED_USER
(make sure your SQL Server Management Studio doesn't have the database DBASE selected in the pulldown menu in the query window.)
After which you can commence with restoring the database using.
RESTORE DATABASE DBASE
FROM DISK = 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.DBASE\MSSQL\Restore\DBASE.BAK'
MOVE 'DBASE' TO 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.DBASE\MSSQL\DATA\DBASE.MDF',
MOVE 'DBASE_LOG' TO 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.DBASE\MSSQL\DATA\DBASE_1.LDF',
STATS = 10
If you aren't restoring the backup to a new location, then you can ommit the MOVE commands, as they are only required when restoring to a new location.
This should bring your database back online.
BTW, having multiple Transaction Log files doesn't benefit much unless you run out of space on your disk during an incident. Transaction log files are written serially and never in parallel. The only reason to temporarily having multiple transaction log files:
Alternatives for responding to a full transaction log include
- Adding a log file on a different disk.
...as can be found here: Troubleshoot a Full Transaction Log (SQL Server Error 9002)
Good luck with your restore.