How to restore SQL Server backup

Hi Folks,

I have taken a backup from a PC has localhost server with Windows authentication, and I want to restore this backup to another PC which has a localhost server with Windows authentication.

I tried to restore it from SQL Server Management Studio, but it does not appear like other.bak files I mean when you choose a backup file to restore all files with (.bak) extension will appear and as I noticed only backup files who created by the same PC will appear, as I know this problem is because a connection string is different from the first PC to the second PC.

Is there any way to restore it?

And I don’t want to make a script file, I need it as a backup file. anyone help please.

Thank you

Related:

automatic version import is importing files partially?

(Deployment component):-We are doing filesystem deployment through UCD. when we do deployment for eg, 8 files are deployed at the destination replacing the existing 8 files of the same name. but before depoyment **backup version** of the existing 8 files is done.

———-

(Backup component):- then while doing rollback the **backup version** is treated as patch and redeployed at the destination. the **backup version** imported automatically in the backup component as we have checked the “Import Versions Automatically”
for the backup component.

———-

Earlier it was working fine . But now in the Backup component ,the backup versions are import automatically but only partially. I would like to repeat that earlier this same procedure was working perfectly.

Related:

Event ID 546 — Backup Operations

Event ID 546 — Backup Operations

Updated: January 27, 2011

Applies To: Windows Server 2008

You can use the Windows Server Backup snap-in or the wbadmin command to create and manage backups to protect your operating system, volumes, files, and application data. Backups can be saved to single or multiple disks, DVDs, removable media, or remote shared folders. They can also be scheduled to run automatically or manually.

However, system state backup is only available for the command line and is not available in the Windows Server Backup snap-in user interface. Also, you cannot configure a scheduled backup to create system state backups—but you can script the wbadmin start systemstatebackup command to run backups on a schedule.

In addition, you can use the Local Group Policy Editor snap-in (Gpedit.msc) to allow or disallow certain types of backups or backup locations. Policy settings for Windows Server Backup are located at: Local Computer Policy\Computer Configuration\Administrative Templates\Windows Components\Backup\Server.

Event Details

Product: Windows Operating System
ID: 546
Source: Microsoft-Windows-Backup
Version: 6.0
Symbolic Name: ADMIN_BACKUP_FAILED_DID_NOT_START_EVENT
Message: Backup attempted at ‘%1’ failed to start, error code ‘%2’.

Resolve
Review event details for why backup failed to start

If a backup fails to start, review the details for the applicable events to find out why the backup operation failed. Then re-run the backup.

To do this, follow these general steps:

  1. Find the applicable events in Event Viewer, and then review the details for those events to find out why the backup operation failed. For more information, see “Review event details in Event Viewer.”
  2. Confirm that the location to perform the backup to is online.
  3. After resolving any errors that you find in performing the steps above, re-run another backup. For more information, see “Peform a backup using the command line.”

To perform these procedures, you must have membership in Backup Operators or Administrators, or you must have been delegated the appropriate authority.

Review event details in Event Viewer

To review event details for a backup in Event Viewer:

  1. Open Event Viewer. Click Start, click Administrative Tools, and then click Event Viewer.
  2. In the left pane, double-click Applications and Service Logs, double-click Microsoft, double-click Windows, double-click Backup, and then click Operational.
  3. Look at the error code mentioned in the event details to find out why the backup failed to start.

Perform a backup using the command line

Make sure that the backup storage location specified by -backupTarget is online.

Note: If the backup operation that failed was a scheduled backup, you can use wbadmin start backup with no parameters. This will run a backup using the settings for the scheduled backup.

To perform a one-time backup:

  1. Open an elevated Command Prompt window. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
  2. At the prompt, type: wbadmin start backup. Use parameters, as needed. (To view the parameters and help for this command, at a command line, type: wbadmin start backup /?).

    For example, to create a backup that will be stored on drive f, of volumes e:, d:\mountpoint, and \\?\Volume{cc566d14-4410-11d9-9d93-806e6f6e6963}, type: wbadmin start backup -backupTarget:f: -include:e:,d:\mountpoint,\\?\Volume{cc566d14-44a0-11d9-9d93-806e6f6e6963}\.

Verify

To verify that backup operations are running, or will run, successfully, you should do one or more of the following, as needed:

  • For any backup operations that you have run, look for Event ID 4, which indicates that the operation completed successfully with no errors.
  • Verify that no other backup or recovery operations are running so that you can start an operation.
  • Verify that you have enabled a scheduled backup, and is configured correctly.
  • Verify that the location where you plan to store your backups is available and online.

To perform these procedures, you must have membership in Backup Operators or Administrators, or you must have been delegated the appropriate authority.

Verify the backup completed with no errors

To verify that a backup operation completed with no errors:

  1. Open Event Viewer. Click Start, click Administrative Tools, and then click Event Viewer.
  2. In the left pane, double-click Applications and Service Logs, double-click Microsoft, double-click Windows, double-click Backup, and then click Operational.
  3. In the Event ID column, look for event 4.  
  4. For this event, confirm that the value in the Source column is Backup.

Verify another operation is not running

To verify that another backup or recovery operation is not running:

  1. Open an elevated Command Prompt window. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
  2. At the prompt, type: wbadmin get status.
  3. If the command output indicates that no operation is running, then you can start a backup.

Verify scheduled backup is enabled

To verify that a scheduled backup is enabled:

  1. Open an elevated Command Prompt window. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
  2. At the prompt, type: wbadmin enable backup.
  3. If the command output shows a schedule, then a scheduled backup is enabled.
  4. Confirm that the schedule contains the correct parameters.

Verify storage location is online

To verify that a disk used to store backups is online:

  1. For the computer that contains the storage disk, open Disk Management. Click Start, click Run, and then type: diskmgmt.msc.
  2. Click View, click Top, and then click Disk List.
  3. For the disk that contains the volume that you will use to store backups, confirm that the value in the Status column is Online.

Related Management Information

Backup Operations

File Services

Related:

Event ID 19 — Backup Operations

Event ID 19 — Backup Operations

Updated: January 27, 2011

Applies To: Windows Server 2008

You can use the Windows Server Backup snap-in or the wbadmin command to create and manage backups to protect your operating system, volumes, files, and application data. Backups can be saved to single or multiple disks, DVDs, removable media, or remote shared folders. They can also be scheduled to run automatically or manually.

However, system state backup is only available for the command line and is not available in the Windows Server Backup snap-in user interface. Also, you cannot configure a scheduled backup to create system state backups—but you can script the wbadmin start systemstatebackup command to run backups on a schedule.

In addition, you can use the Local Group Policy Editor snap-in (Gpedit.msc) to allow or disallow certain types of backups or backup locations. Policy settings for Windows Server Backup are located at: Local Computer Policy\Computer Configuration\Administrative Templates\Windows Components\Backup\Server.

Event Details

Product: Windows Operating System
ID: 19
Source: Microsoft-Windows-Backup
Version: 6.0
Symbolic Name: BACKUP_FAILED_DID_NOT_START_EVENT
Message: Backup attempted at ‘%4’ failed to start, error code ‘%5’.

Resolve
Review event details for why backup failed to start

If a backup fails to start, review the details for the applicable events to find out why the backup operation failed. Then re-run the backup.

To do this, follow these general steps:

  1. Find the applicable events in Event Viewer, and then review the details for those events to find out why the backup operation failed. For more information, see “Review event details in Event Viewer.”
  2. Confirm that the location to perform the backup to is online.
  3. After resolving any errors that you find in performing the steps above, re-run another backup. For more information, see “Peform a backup using the command line.”

To perform these procedures, you must have membership in Backup Operators or Administrators, or you must have been delegated the appropriate authority.

Review event details in Event Viewer

To review event details for a backup in Event Viewer:

  1. Open Event Viewer. Click Start, click Administrative Tools, and then click Event Viewer.
  2. In the left pane, double-click Applications and Service Logs, double-click Microsoft, double-click Windows, double-click Backup, and then click Operational.
  3. Look at the error code mentioned in the event details to find out why the backup failed to start.

Perform a backup using the command line

Make sure that the backup storage location specified by -backupTarget is online.

Note: If the backup operation that failed was a scheduled backup, you can use wbadmin start backup with no parameters. This will run a backup using the settings for the scheduled backup.

To perform a one-time backup:

  1. Open an elevated Command Prompt window. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
  2. At the prompt, type: wbadmin start backup. Use parameters, as needed. (To view the parameters and help for this command, at a command line, type: wbadmin start backup /?).

    For example, to create a backup that will be stored on drive f, of volumes e:, d:\mountpoint, and \\?\Volume{cc566d14-4410-11d9-9d93-806e6f6e6963}, type: wbadmin start backup -backupTarget:f: -include:e:,d:\mountpoint,\\?\Volume{cc566d14-44a0-11d9-9d93-806e6f6e6963}\.

Verify

To verify that backup operations are running, or will run, successfully, you should do one or more of the following, as needed:

  • For any backup operations that you have run, look for Event ID 4, which indicates that the operation completed successfully with no errors.
  • Verify that no other backup or recovery operations are running so that you can start an operation.
  • Verify that you have enabled a scheduled backup, and is configured correctly.
  • Verify that the location where you plan to store your backups is available and online.

To perform these procedures, you must have membership in Backup Operators or Administrators, or you must have been delegated the appropriate authority.

Verify the backup completed with no errors

To verify that a backup operation completed with no errors:

  1. Open Event Viewer. Click Start, click Administrative Tools, and then click Event Viewer.
  2. In the left pane, double-click Applications and Service Logs, double-click Microsoft, double-click Windows, double-click Backup, and then click Operational.
  3. In the Event ID column, look for event 4.  
  4. For this event, confirm that the value in the Source column is Backup.

Verify another operation is not running

To verify that another backup or recovery operation is not running:

  1. Open an elevated Command Prompt window. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
  2. At the prompt, type: wbadmin get status.
  3. If the command output indicates that no operation is running, then you can start a backup.

Verify scheduled backup is enabled

To verify that a scheduled backup is enabled:

  1. Open an elevated Command Prompt window. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
  2. At the prompt, type: wbadmin enable backup.
  3. If the command output shows a schedule, then a scheduled backup is enabled.
  4. Confirm that the schedule contains the correct parameters.

Verify storage location is online

To verify that a disk used to store backups is online:

  1. For the computer that contains the storage disk, open Disk Management. Click Start, click Run, and then type: diskmgmt.msc.
  2. Click View, click Top, and then click Disk List.
  3. For the disk that contains the volume that you will use to store backups, confirm that the value in the Status column is Online.

Related Management Information

Backup Operations

File Services

Related:

The user accounts database (NET.ACC) is missing. The local security system is restoring the backup database made at %1. Any updates made to the database made after this time are lost.

Details
Product: Windows Operating System
Event ID: 3184
Source: System
Version: 5.0
Symbolic Name: NELOG_LocalSecFail2
Message: The user accounts database (NET.ACC) is missing. The local security system is restoring the backup database made at %1. Any updates made to the database made after this time are lost.
   
Explanation

This message should occur only on a workstation. Any action to correct the problem should be performed on that computer. Local security could not start because the user accounts database file, NET.ACC, is missing or damaged and no backup file exists on the hard disk.

   
User Action

Restore NET.ACC from a backup. The backup file will be named either NET.ACC or NETACC.BKP. Then restart the computer. If there is no backup, reinstall LAN Manager using the Setup program.

Related:

Repair has invalidated the differential bitmap for database NAME. The differential backup chain is broken. You must perform a full database backup before you can perform a differential backup.

Details
Product: SQL Server
Event ID: 2516
Source: MSSQLServer
Version: 9.0
Component: SQLEngine
Symbolic Name: DBCC_REPAIR_DIFF_MAP_INVALIDATED
Message: Repair has invalidated the differential bitmap for database NAME. The differential backup chain is broken. You must perform a full database backup before you can perform a differential backup.
   
Explanation

This informational message is returned when error MSSQLEngine_2515 is repaired.

   
User Action

Perform a full database backup.

Related:

process name (process id) Server registered: name / service name (callback DLL DLL name, flags value).

Details
Product: Exchange
Event ID: 905
Source: ESE BACKUP
Version: 6.5.6940.0
Component: Microsoft Exchange Extensible Storage Engine Backup
Message: process name (process id) Server registered: name / service name (callback DLL DLL name, flags value).
   
Explanation

This is an informational event typically associated with an Exchange store database or a Site Replication Service (SRS) database that dismounts with an error or cannot be mounted with an error.

Note   “Server registered” always refers to Exchange Server and means that the Extensible Storage Engine (ESE) backup endpoints have been registered. The service referenced in the event can be the Microsoft Exchange Information Store service or the SRS.

See User Action for some specific causes and resolutions to this error.

   
User Action

The following are some specific causes and resolutions associated with ESEBackup Event 905:

  • The version of antivirus software being used had a problem that caused the database shutdown, and required an upgrade of the version, a downgrade of the version, or a fix. Check to determine whether this could be caused by the current state of the antivirus software installed on the server that is running Exchange. For information about troubleshooting this potential cause, contact your antivirus software vendor.
  • The incorrect restore file was selected for an online Exchange-aware restore. Rerun the restore process using the correct backup file.
  • Some of the log files used by the Exchange store database and the storage group had been removed and replaced. For information about troubleshooting Exchange transaction log file problems during data recovery, see Microsoft Knowledge Base article 812592 “How and when to manipulate Exchange transaction logs in disaster recovery” (http://go.microsoft.com/fwlink/?LinkId=3052&kbid=812592).

If you still cannot restore your backup, examine the Application log for associated events that may help you determine the root cause of the Exchange store database failure or the SRS database failure.

Related:

() The restored logfile does not have the correct log signature.

Details
Product: Exchange
Event ID: 433
Source: ESE
Version: 6.5.6940.0
Component: Microsoft Exchange Extensible Storage Engine
Message: <process name> (<process id>) <storage group name>The restored logfile <file name> does not have the correct log signature.
   
Explanation

Some of the restored files are damaged.

   
User Action

Perform Restore again. If the failure persists, refer to the backup set to identify the affected log files. If the corrupted log file is outside the backup set, remove the files outside the backup set and run restore again. If the corrupt log file is contained in the backup set, revert to a previous backup.

Loss of data may occur. If the problem persists, contact Microsoft Product Support Services.

Related:

() The timestamp for restored logfile does not match the timestamp recorded in the logfile previous to it.

Details
Product: Exchange
Event ID: 434
Source: ESE
Version: 6.5.6940.0
Component: Microsoft Exchange Extensible Storage Engine
Message: <process name> (<process id>) <storage group name>The timestamp for restored logfile <file name> does not match the timestamp recorded in the logfile previous to it.
   
Explanation

The time stamp for restored log file does not match the time stamp recorded in the previous log file. The log files must be replayed in order.

   
User Action

Perform Restore again. If the failure persists, refer to the backup set to identify the affected log files. If the corrupted log file is outside the backup set, remove the files outside the backup set and run restore again. If the corrupt log file is contained in the backup set, revert to a previous backup.

Loss of data may occur. If the problem persists, contact Microsoft Product Support Services.

Related: