MS SQL Server Backup
- How do I backup my Microsoft SQL Server?
- Under what name and extension are the MS SQL Server backup files stored on IBackup?
- Can I backup databases from multiple instances of MS SQL Server?
- I am unable to view the databases in the instance of MS SQL Server that I am logged into. Why?
- Can I backup the MS SQL Server in the 'Mirror Path' mode?
- Can I backup Microsoft SQL Server 'tempdb' database?
- How do I restore my database backup file to my MS SQL Server?
- Can IBackup backup the entire SQL Server database?
- Can I restore my database file to a different MS SQL Server database?
- Under what circumstance should I restore the MS SQL Server 'master' database?
- How do I restore the MS SQL Server master database?
- When should I restore the 'model', 'msdb' and 'distribution' databases?
- I am receiving an error message stating “VDS::Create Fails : 0x80770005” during SQL Server Backup. Why?
- I am receiving an error message stating 'Check registration of SQLVDI.DLL and value of IID' during SQL Server Backup. Why?
- Can I restore database files to multiple SQL Server instances?
To backup your MS SQL Server,
- Log into IBackup desktop application and click the ‘Server Backup’ tab.
- Under MS SQL Server section, click 'Backup'.
- Provide the relevant authentication information when prompted. IBackup provides two modes of MS SQL Server authentication. You can connect to your database using:
- Windows Authentication Mode: When you connect through a Windows user account, SQL Server validates the account name and password using the Windows principal token in the operating system. This means that your identity is confirmed by Windows. SQL Server does not ask for the password and does not perform the identity validation. Windows Authentication is the default authentication mode, and is more secure than SQL Server Authentication.
- SQL Server Authentication Mode: When using SQL Server Authentication, logins are created in SQL Server that are not based on Windows user accounts. Both the username and the password are created by using SQL Server and stored in SQL Server. While connecting using SQL Server Authentication, you must provide your credentials (login and password) every time. When using SQL Server Authentication, you should set strong passwords for all SQL Server accounts.
Note: If you attempt to connect to an instance of MS SQL Server by providing a blank login name, the SQL Server uses the Windows Authentication. Additionally, if you connect to an instance of SQL Server configured for Windows Authentication Mode using a specific login, the login is ignored and the Windows Authentication is used.
- Select the database(s) from the list displayed, specify the temporary local backup path.
- Select Online Backup or Local Backup radio button, and click Schedule Now.
- The ‘Schedule backup’ screen is displayed where you can schedule the backup for any future day and time or perform an immediate backup of the selected databases.
Note: IBackup allows you to schedule the SQL Server backup for different instances. For easy identification of the SQL Server Backup set, the name of the backup set will be 'IBSQLServerBkset' followed by the instance name scheduled for backup.
Example: If the instance name is 'MJOHN\INSTMJOHN' then the name of the backup job is 'IBSQLServerBkset (MJOHN##INSTMJOHN)'
The backed up files are stored in your IBackup account with the extension '.dmp', file name enclosed within square brackets.
Format of the file name: [
Examples: [model].dmp, [pubs].dmp, [order list].dmp.
Yes. You can backup databases from multiple instances of the MS SQL Server running on your local computer. However, you may be unable to backup databases from multiple instances of MS SQL Server hosted at multiple locations on your network.
You may be unable to view all the databases under the instance, due to lack of proper access permissions/privileges for the username that you are logged in with. We recommend you to contact your database administrator to obtain the privileges to access the databases.
No, even if you opt to backup using the 'Mirror Path' option, they will take place in the 'Relative Path'.
No. You cannot backup your Microsoft SQL Server 'tempdb' database.
IBackup lets you restore your database backup file (IBSQLBackup) to a different database and perform point-in-time database recovery.
- Log into IBackup desktop application and click the 'Restore' tab.
- Locate and select the database backup file (IBSQLBackup) in your IBackup account.
- Click the 'Restore Now' button, to restore the database backup file (IBSQLBackup) to the local computer.
- Once the IBSQLBackup file has been successfully restored, click the 'Server Backup' tab.
- Click 'Restore', under MS SQL Server section.
- Provide the relevant MS SQL Server authentication information when prompted.
- Browse and select the database backup file (IBSQLBackup) from your local computer (the location where the database backup file (IBSQLBackup) was restored earlier from your IBackup account).
- The 'SQL Server backup/restore' screen is displayed.
- Click the 'Restore' button to restore selected database backup file (*.dmp) to your MS SQL Server.
Yes. IBackup can backup the entire SQL Server database along with the corresponding database log file, containing the entire structure and components of the database, to your online account.
You can also backup multiple databases wherein each database has its own corresponding '[ <database name>].dmp' file.
Yes. You can restore your database backup file (.dmp) to a different database by providing a new database name. Further, it is possible to change the data and transaction log file location as desired.
You need to restore the master database if you are:
- Rebuilding all your databases from scratch.
- Changing any server-wide or database configuration options.
- Adding logins or other login security-related operations.
- Creating or removing logical backup devices.
- Configuring the server for distributed queries and remote procedure calls such as adding linked servers or remote logins.
Note: If you just want to restore a user database, there is no need to restore your master database. For details on Microsoft SQL Server master database, visit http://www.microsoft.com/sql/.
To restore the MS SQL Server master database:
- Start Microsoft SQL Server in the 'Single User Mode'.
- Right-click the Microsoft SQL Server and select 'Properties'.
- Click the 'Startup Parameters' button under the 'General' tab.
- Select and add the required parameters as shown below.
- Restart the Microsoft SQL Server. From the SQL Server Enterprise Manager, right-click 'Microsoft SQL Servers', select 'Stop' and then 'Start'.
- Use the IBackup – MS SQL Server 'Restore' option to restore the master database.
You should restore the 'model' database, if you have changed the database template of your MS SQL Server.
Restore the 'msdb' database, if you have changed the scheduling information or want to restore the backup and restore history of your databases.
If you are running the replication components of MS SQL Server, then restore your 'distribution' database.
Note: You need not restore these databases, if you just want to restore a user database. For more information on Microsoft SQL Server model, msdb and distribution database, visit http://www.microsoft.com/sql/.
The error message implies that your SQL Server service on your computer is running under a start up account with the format .\UserName.
To resolve this issue, contact your system administrator to configure the startup account of the SQL Server service to use the LocalSystem account. Alternately, use a start up account that has the full name of the domain account instead of a period (.) to start the service. For example, use the startup account DomainName\UserName to start the service.
This message appears when the application tries to use a sqlvdi.dll file that has not been registered.
To resolve this problem, register the sqlvdi.dll file again using the following steps:
- Stop the SQL Server.
- Click Start, click Run, type Regsvr32
\SQLVDI.DLL in the Open box and click 'OK'. The default path of the Sqlvdi.dll file is 'C:\Program Files\Microsoft SQL Server\80\COM.'
- Restart the SQL Server.