Log into IDrive desktop application and click the 'Server Backup' tab.
Under MS SQL Server section, click 'Backup'.
Provide the relevant authentication information when prompted. IDrive 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 which appears and specify the local backup location.
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: IDrive 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 '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)'
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.
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/.
I am receiving an error message stating “VDS::Create Fails : 0x80770005” during SQL Server Backup. Why?
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.
How do I set 'sysadmin' role to the "NT AUTHORITY\SYSTEM" or the "BUILTIN\Administrators group" in my SQL Server?
For SQL Server 2008 and earlier, the 'sysadmin' role is automatically applied to the NT AUTHORITY\SYSTEM and BUILTIN\Administrators groups. However, for 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,
SQL Server Management Studio:
Launch 'Microsoft SQL Management Studio'.
Navigate to Security > Logins > NT AUTHORITY\SYSTEM.
Right-click NT AUTHORITY\SYSTEM and select Properties.
In the 'Login Properties- NT AUTHORITY\SYSTEM' window, click Server Roles.
Select the sysadmin check box, and click OK.
SQL Server Command Line Utility:
Open the Command Prompt with an administrator privilege.
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)