Frequently Asked Questions

How can I perform differential backup of my MS SQL Server?

To perform differential backup,

1. Sign in to the IDrive application and click 'Server Backup' tab. A slider menu will appear.
2. Click 'MS SQL'. The MS SQL connection screen appears. By default, 'MS SQL backup' is selected.
   
3. Provide the relevant authentication information when prompted. IDrive provides two modes of MS SQL server authentication. Click 'Connect to MS SQL'.
   
4. Select 'Online Backup', or 'Local Backup', or 'IDrive Express™ Backup'.

Note: On selecting 'Online Backup', the data will be stored on the IDrive cloud whereas on selecting 'Local Backup' or 'IDrive Express™ Backup' the data will be stored in the local drive.

5. Select the database(s) from the list which appears and specify MS SQL backup temporary path for local backup.

Note: Once the local backup is initiated, '.ServerBackup' folder is auto-created.

6. Click 'Schedule Now'.
   
7. The 'Scheduler’ appears, from where you can schedule the backup for any future day and time or perform an immediate backup of the selected databases. Click 'Save Changes'.
   

1. Note: IDrive for Windows allows you to schedule the MS SQL server backup for different instances. For easy identification of the SQL server backup set, the name of the backup set will be 'IDSQLServerBkset' followed by the instance name scheduled for backup.
   Example: If the instance name is 'MJOHN\INSTMJOHN' then the name of the backup job is 'IDSQLServerBkset (MJOHN##INSTMJOHN)'

How can I perform incremental backup of my MS SQL server?

To perform incremental backup,

1. Sign in to the IDrive application and click 'Server Backup'. A slider menu will appear.
2. Click 'MS SQL'. The MS SQL connection screen appears. By default, 'MS SQL backup' is selected.
   
3. Provide the relevant authentication information when prompted. IDrive provides two modes of MS SQL server authentication. Click 'Connect to MS SQL'.
   
4. Select 'Online Backup', or 'Local Backup', or 'IDrive Express™ Backup'.

   Note: On selecting 'Online Backup', the data will be stored on the IDrive cloud whereas on selecting 'Local Backup' or 'IDrive Express™ Backup' the data will be stored in the local drive.

   
5. Select the database(s) from the list which appears and select the 'Incremental' option.

Note: To perform the incremental backup, the database should be in full/bulk-logged recovery model.

6. Specify the local backup location and click 'Schedule Now'.
7. In the 'Scheduler’ that appears, schedule the backup for any future day and time or perform an immediate backup of the selected databases. Click 'Save Changes'.
   

Under what name and extension are the MS SQL server backup files stored on IDrive?

The backed up files are stored in your IDrive account with the extension '.dmp', file name enclosed within square brackets.

Format of the file name: [ ].dmp

Examples: [model].dmp, [pubs].dmp, [order list].dmp.

Can I backup databases from multiple instances of MS SQL server?

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.

I am unable to view the databases in the instance of MS SQL server that I am logged into. Why?

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.

Can I backup the MS SQL server in the 'Mirror Path' mode?

No, even if you opt to backup using the 'Mirror Path' option, they will take place in the 'Relative Path'.

Can I backup Microsoft SQL server 'tempdb' database?

No. You cannot backup your Microsoft SQL server 'tempdb' database.

How do I restore my database backup file to my MS SQL server?

IDrive lets you restore your database backup file to a different database and perform point-in-time database recovery.

To restore,

1. Sign in to the IDrive desktop application and click 'Restore'.
2. Select 'Online Restore', or 'Local Restore', or 'IDrive Express™ Restore'.
3. Locate and select the database backup file (IDSQLBackup) in your IDrive account or local drive.

Note: If 'Local Restore' is selected, you can choose the required version from the 'Version' list.

4. Click the 'Restore Now' button, to restore the database backup file (IDSQLBackup) to the local computer.
   
5. Once the IDSQLBackup file is restored, click 'Server Backup'. A slider menu will appear.
   
6. Click 'MS SQL'. The MS SQL connection screen appears.
   
7. Click 'MS SQL restore'.
8. Provide the relevant MS SQL server authentication information when prompted. Click 'Connect to MS SQL'.
9. Browse and choose the database backup (IDSQLBackup) file (restored earlier from your IDrive account or local drive).
   
10. Click the 'Restore Now' button to restore the selected database backup file (*.dmp) to your MS SQL server.
    
    

Can IDrive backup the entire SQL server database?

Yes. IDrive can backup the entire MS 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.

Can I restore my database file to a different MS SQL server database?

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.

Under what circumstance should I restore the MS SQL server 'master' database?

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 the Microsoft SQL server master database, visit http://www.microsoft.com/sql/.

How do I restore the MS SQL server master database?

To restore the MS SQL server master database,

1. Start the Microsoft SQL server in the 'Single User Mode'.
2. In the Start menu, click 'Run'. Type 'compmgmt.msc' and click 'OK' to open the Computer Management Wizard.
3. Select 'SQL server Configuration Manager' from 'Services and Application'.
4. Click 'SQL Server Services'.
5. Right-click the SQL server ('Instance') service and select 'Properties'.
6. Click 'Startup Parameters'.
7. Add the parameter (-m) as shown below and click 'OK'.

8. Restart 'SQL Server Service'.
9. Use the IDrive MS SQL server 'Restore' option to restore the master database.

Note: Run IDrive service in the Administrator account as follows:

1. Run -> Services.msc
2. Right-click 'IDriveService' and go to 'Properties' -> Log on -> 'This Account'.
3. Enter the Administrator account credential and password.
4. Restart IDrive service and provide the 'sysadmin' role to the administrator account in the SQL server.

When should I restore the 'model', 'msdb' and 'distribution' databases?

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/.

My MS SQL restore operation failed. How do I proceed?

The Microsoft ODBC error: Use the WITH REPLACE or WITH STOPAT Clause of the Restore statement, Restore Database is terminating abnormally.

If the MS SQL restore operation fails and you see the above error message, use the WITH REPLACE or WITH STOPAT Clause. We recommend changing the data file location, log file location and database name and then performing the restore.

I am receiving an error message stating "VDS::Create Fails: 0x80770005" during MS SQL server backup. Why?

The error message implies that your MS 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 MS 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.

I am receiving an error message stating 'Check registration of SQLVDI.DLL and value of IID' during MS SQL server backup. Why

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:

1. Stop the SQL server.
2. 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.'
3. Restart the SQL server.

Can I restore database files to multiple MS SQL server instances?

Yes. You can restore multiple database files to the MS SQL server instances one by one.

How do I set 'sysadmin' role to the "NT AUTHORITY\SYSTEM" or the "BUILTIN\Administrators group" in my MS SQL server?

For MS SQL server 2008 and earlier, the 'sysadmin' role is automatically applied to the NT AUTHORITY\SYSTEM and BUILTIN\Administrators groups. However, for MS SQL server 2012 and higher versions, you must first apply the 'sysadmin' role manually to the NT AUTHORITY\SYSTEM or the BUILTIN\Administrators group.

You can set the 'sysadmin' role using the following techniques.

1. SQL Server Management Studio:
   1. Launch 'Microsoft SQL Management Studio'.
   2. Navigate to 'Security' > 'Logins' > 'NT AUTHORITY\SYSTEM'.
   3. Right-click 'NT AUTHORITY\SYSTEM' and select 'Properties'.
      
   4. In the 'Login Properties- NT AUTHORITY\SYSTEM' window, click 'Server Roles'.
   5. Select the 'sysadmin' check box, and click 'OK'.
      
2. SQL Server Command Line Utility:
   1. Open the Command Prompt with an administrator privilege.
   2. Use the following command to connect to a named instance by using Windows Authentication and provide a sysadmin role.
      

      sqlcmd -S <ComputerName>\<InstanceName> or sqlcmd -S <ComputerName> (For default instance)

      exec sp_addsrvrolemember 'NT AUTHORITY\SYSTEM', 'sysadmin' ;

      go;

What are the recovery models that IDrive supports for MS SQL server database backup and restore?

A recovery model is a database property that handles how all MS SQL transactions are logged. Furthermore, it decides whether a transaction log requires (and allows) backing up and the different types of restore operations that are available.

MS SQL server database backup, restore, and recovery operations are based on these recovery models:

1. Simple Recovery Model
   • Supports full and differential backups
   • The simplest among all recovery models
   • Doesn't support transaction log backups
2. Full Recovery Model
   • All transactions are fully recorded in the transaction log file
   • Supports full backup, differential backup, and incremental (log) backups
   • Incremental (log) backups are the transactions that have changed since the last backup
3. Bulk-Logged Recovery Model
   • A unique purpose database configuration option that works similar to the full recovery model, except that certain bulk operations can be minimally logged
   • Supports full backup, differential backup, and incremental (log) backups
   • Incremental (log) backups are the transactions that have changed since the last backup

How to run the MS SQL server instance from the administrator or local account?

To run SQL server instance,

1. Go to the services wizard, right-click 'SQL Server Instance' and select 'Properties'.
2. Go to 'Log On' and select 'This account'.
3. Browse the administrator account, enter your account credentials and click 'Apply'.
4. Restart the service.
   
   
   

How can I backup MS SQL server database backup from a NAS / mapped drive?

In order to perform MS SQL server database backup to a network mapped drive / NAS drive, you have to map your network location to your system.

To backup,

1. Click 'Server Backup'. A slider menu will appear.
2. Click 'MS SQL'. The MS SQL connection screen appears. By default, 'MS SQL backup' is selected.
   
   
   
3. Provide the relevant MS SQL server authentication information when prompted. IDrive provides two modes of MS SQL server authentication. Click 'Connect to MS SQL'.
   
4. Select 'Online Backup', or 'Local Backup' or 'IDrive Express™ Backup'.
5. Select the database that you want to backup to your account.
6. Select backup type as 'Differential' or 'Incremental'.
7. Select the network mapped drive / NAS drive as the location for creating the MS SQL database backup. Click 'OK' and then click 'Schedule Now'.
   
8. Enter your username and password to authenticate network mapped drive / NAS drive. Click 'Authenticate'.
   
9. The 'Scheduler' appears from where you can schedule MS SQL database backup to perform the backup operation to a network mapped drive / NAS drive. Click 'Save Changes'.

How can I restore MS SQL server database backup from a NAS / mapped drive?

To perform the MS SQL server database restore from a NAS / mapped drive, you have to map your network location to your system.

To restore,

1. Click 'Server Backup'. A slider menu will appear.
2. Click 'MS SQL'. The MS SQL connection screen appears.
   
3. Click 'MS SQL restore'.
4. Provide the relevant authentication information when prompted. IDrive provides two modes of MS SQL server authentication. Click 'Connect to MS SQL'.
   
5. Browse the ‘IDSQLBackup’ backup folder from the NAS / mapped drive to locate the MS SQL database backup file. Download the ‘IDSQLBackup’ folder from your IDrive account or local drive to a NAS / mapped drive. Click ‘OK’ to proceed.
   
6. Select the database(s) you want to restore to your MS SQL server.
7. Click 'Restore Now'.
8. Network authentication window will appear. Enter your username and password for network drive authentication. Click 'Authenticate' to proceed.
   
   

Note: It is recommended to run SQL server instance service from the administrator / local account to restore the database backup from NAS or mapped drive.

How to change the database model from simple to full or bulk-logged in order to perform incremental backup?

To change from simple to full or bulk-logged database model,

1. Log in to Microsoft SQL management studio.
   
2. Click the 'Databases' folder. A list of databases will appear.
3. Right-click on the required database and click 'Properties'. The database properties page appears.
   
4. Click 'Options' from the menu.
   
5. Change the recovery model from 'Simple' to 'Full' or 'Bulk-logged'.
   
6. Click 'OK'.

Once this is completed, you can go to the IDrive application and backup the database using the incremental backup option.

How do I remove the MS SQL server databases that are not required for restore?

To remove the databases,

1. Sign in to the IDrive application and click 'Server Backup'. A slider menu will appear.
2. Click 'MS SQL'. The MS SQL connection screen appears.
3. Click 'MS SQL restore'.
4. Provide the relevant MS SQL server authentication information when prompted. IDrive provides two modes of MS SQL server authentication. Click 'Connect to MS SQL'.
5. Browse and choose the database backup (IDSQLBackup) file (restored earlier from your IDrive account or local drive).
   After loading IDSQLBackup file the 'SQL Server backup/restore wizard' appears.
6. Right-click on the database you wish to remove and click 'Delete'.
   
7. Click 'Yes' in the confirmation window.