Genie Backup Manager ensures backup to multiple SQL databases without the need to disconnecting from the SQL Server using advanced API technologies. However, if you encounter difficulties during backup or restore, please review this checklist to find potential solutions.
1. Ensure that you are using the latest SQL Server service pack
To check which SQL service pack you are running, you may download the latest service packs and SQL servers from the following link:
http://www.microsoft.com/technet/downloads/sql/default.mspx
2. Ensure that you have the appropriate permissions to make a backup/restore
To backup a database or transaction log, you should have BACKUP DATABASE or BACKUP LOG permissions granted to you, or you should be a member of the sysadmin fixed server role, or of the db_owner or db_backupoperator fixed database roles.
To restore a database, please make sure to select Create new Database if the database being restored does not exist along with specifying the DB and logs location under Move database location. If the database being restored does exist, you should have RESTORE permissions granted to you, or you should be a member of the sysadmin or dbcreator fixed server roles, or you need to be the owner (dbo) of the database.
3. If you want to make a backup of the transaction log, check that the ‘trunc. log on chkpt’ option is turned off
You cannot make a backup of the transaction log if the ‘trunc. log on chkpt’ option is turned on, because in this case the transaction log will be truncated on checkpoint and will be empty.
4. If you encountered Error 3023 during a backup operation, reissue the backup operation after the conflicting operation has completed
The error 3023 indicates that GBM backup at the same time as creating, deleting, or shrinking database files. So, to resolve this error you should try to perform the backup again after the conflicting operation has finished.
5. If you encountered Error 3036 during a backup operation, use backups from your primary server until operations have switched to the standby
The error 3036 indicates that the database is in the non operational state this occurs when GBM is currently restoring backups and keeps database non operational, when the database is non operational GBM cannot be backup until the entire restore sequence is completed and Leave database non-operational is unchecked.
6. If you encountered Error 3154 during a restore operation, overwrite the existing database by Restore over existing database is selected, or restore the backup set to a different database name
The error 3154 indicates that you tried to restore database over an existing database, but the existing database was created by a different CREATE DATABASE statement than the database in the backup set.
7. If you encountered Error 3249 during a restore operation, replace the current volume with a volume containing the start of the target backup set
The error 3249 indicates that the media family spans multiple volumes, and the backup set to be processed by the restore operation starts on an earlier volume than the one inserted into the named device.
8. If you encountered Error 3256 during a restore operation, restore a different database backup and use log backups to roll forward, if you were restoring a database backup; otherwise, restore the next log backup if you were restoring a log backup
This error indicates that the backup set is not complete because the backup operation that created the backup set did not finish successfully.
9. If you encountered Error 3267 or Error 3627 during a backup or restore operation, retry the operation after reducing the server load
These errors indicate the server is too busy to perform the backup or restore operation.
10. Perform a full database backup before backing up the transaction log. Otherwise, you can encounter Error 4214 during the restore operation
The error 4214 indicates that there is no current database backup. To restore the database after failure, you should have a full database backup or a complete set of file backups, this full backup has to be performed using GBM.
11. If you encountered Error 4305 during a restore operation, restore the transaction log backups in the order they were created
The error 4305 indicates that the restore operation found a gap between the last restore and the transaction log that you attempted to apply. So, to resolve this error you should restore transaction logs in the same order in which they were backed up.