DataBK.COM

If you start from a new installed system (os ,db , reinstall), you can restore the database by doing following steps:

1 . Install SQL Server Backup on new system .

2 . Prepare and import backups to new installed SQL Server Backup , a latest full backup and it's later backups required.

3 .Create a restore job to restore your database .

4 . (Optional) . If you want a new database , just enter it in Restore As field .

5 . (Optional ) . If target database has new directory , please enter new db directory in "DB Directory" field , see above image.

**please note that
You need not restore the system database to the new database (master , msdb , temp .etc), because SQL Server will create the database by restoring a backup.

     Backups created by SQL Server Backup software has own format that supports data compression and encryption.

     To use them in Enterprise manager or SQL Server Managment Studio , you need to convert them to SQL Server native raw format data.

There are two ways to convert backup to raw data:

1 . By using "Convert2rawdata.exe" under installation directory , you can run it in Start->All programs ->SQL Server Backup->Storage Server->Convet Backup. See following.

2 . "Convert Backup" window in SQL Server Backup manager. see following.

In following instruction : Server A is the soure SQL Server , Server B is the target one.

Requirements:

• Both server have SQL Server Backup software installed.
• Both SQL server's have same database edition , at lease A is lower than B's SQL Server.
• If your servers have direct network connection , Soure server A should has a profession edition of SQL Server Backup installed , and a std edition at lease installed on server B.
• If Server A and B is on same machine ,you need only one license SQL Server Backup software.

If your servers have direct network connection , that is easy ,there two ways:

1 . Copy database by using backup and restore jobs:

• Server A : add target backup agent in SQL Instance configruation window.
• Server A : create backups job to create database backup to a backup device.
• Server A : create a restore job to restore backup to target backup agent.
• Server A : Schedule backup and restore job to run automatically.

     For this way , when the restore job runs , it always starts from a full backup . if your databse is a big one , please do not use this method.

2 . Copy database by using log shipping job:

          Getting this error most possible because SQL Server Backup Manager has not refresh license information from Backup Agent yet.

           If your Backup Agent has been registered before upgrade, you don't have to re-enter your license key once again after upgrade to latest version even if the backup manager shows it is in trial period . You just re-connect the backup agent in "SQL Instances " configuration window to refresh the license information from backup agent . See following .

           If above step still dose not work , please use following steps to resolve this issue :

1 . open "SQL Instances " window , and click the "Manage backup agents".

2 . write download the alias , and address information of the backup agent that has license issue . we will delete then re-create it.

3 . delete the backup agent that has license issue to delete the conflict license information.

4 . add this backup agent information once again .

5 . re-enter the license key for this backup agent ,in "Help->Enter registration code" menu FOR THIS backup agent.

      If a database's recovery model is simple, such as master , model .etc system databases , it has no transaction log file , you can only do full and differential backup on this type of database.

      But if you change database's recovery model to full or Bulk-logged , you can create transaction log backup from this database.

Following step show how th change a database's recovery mode :

1. Open SQL Management Studio.
2. Mouse right click on the database and select "Properties" item in the pop menu.
3. In the properties widow , select the "Options" ,then change recovery model

The logshipping job actually works as following :

1. Create log or other type of backup from source database .
2. Select backup , include backups created in backup job or previouse log shipping job that not shipped. 
3. Restore backups to target database.

     That is , even this time it fails (in backup or restore stage ), when it next runs , it will continue from last failure time point, and it can select backup or logs necessary automatidally to restore to target database.

      After it fails , all you need to do is to find and resolve the issue  that causes the failure , and wait it next time to run if it is scheduled , you can also run it manually.

     Default ports for SQL Backup software are 6000 for SQL Backup Agent and 6001  for SQL Storage Server ,both ports are TCP port  . Please make sure these ports are not blocked by firewall.  If these ports are used by another program , you can change them in Backup Agent Manager and Storage Server Manager .

(After change ports  ,you have to restart  service in first tab "Service")

(Start -> All Programs -> SQL Server Backup x -> Backup Agent -> Backup Agent Manager)

(Start -> All Programs -> SQL Server Backup x -> Storage Server -> Storage Server Manager)

For more detail about SQL Server Backup Software Architectural , please visit here :

http://www.databk.com/help/architectural_overview.htm

A ) If you plan to restart from new , just install a latest copy of SQL Server Backup onto new server , and re-enter your license key to unlock the program , please stop all databk backup program services on old server or uninstall the program from old server.

B ) If you want to keep old jobs and settings , please do following: 

1 . Install latest copy of SQL Server Backup onto new server.

2 . (New Server)  Open Control Panel->Administrative Tools->Services , stop all DataBK * service , see following

3 . (New Server) Rename all *.dat files to back them up under installation directory.

4 . Copy all *.dat files from old server to new server

5 . Restart services on new server.

6. Double check all jobs and configration setings  , the most important thing is backup devices ,  if your backup directory is changed , you have to copy existing backups to new directory too.

7 . Do a backup on a demo database on new server , see if everything is ok.

     Storage server saves backup to target shared folder , but Storage Server service is running as Local System account in default . Local System account may not have enough privileges to access the network shared folder. So you can change DataBK Storage Server service account to a new one in in Control Panel->Administrative Tools->Service , see following : (Please note that : Server that shares the folder should also has the same account name and password . )      

         Another important thing is that please DON'T use mapped drive , just use full path name when you config backup device, such as \\remote_server\shared_folder .