SQL Backup - 7.2
Maintenance Plan Conversion Wizard - SQL Backup
SQL Backup provides a wizard to guide you through the process of converting maintenance plans created with SQL Server Management Studio or SQL Server Enterprise Manager so that they use SQL Backup features such as compression and encryption for backup tasks.
The wizard converts maintenance plans generated by SQL Server Management Studio or SQL Server Enterprise Manager, including legacy maintenance plans upgraded from SQL Server 2000 to SQL Server 2005 or SQL Server 2008.
Please note that the wizard does not support features introduced by SQL Backup 6 or later, including compression level 4, optimization and reminders.
You can launch the Maintenance Plan Conversion Wizard by:
- selecting Tools > Utilities > Maintenance Plan Conversion Wizard from the SQL Backup menu (SQL Backup 6 and later)
- running the file SQBMaintPlanConv.exe; this file is located in your SQL Backup folder.
You can run the program on any server on which you have installed the SQL Backup server components.
The Maintenance Plan Conversion Wizard comprises the following steps:
Step 1: select the SQL Server
This page is for selecting the SQL Server instance on which the maintenance plans are located.
In the SQL Server box, type the name of the SQL Server instance, or click to browse to a SQL Server instance on the local network.
Select the authentication method to connect to the SQL Server instance. For SQL Server authentication, enter the Login name and Password.
Step 2: select the maintenance plans
This page is for selecting the maintenance plans to convert.
A maintenance plan is displayed in the list if:
- the associated SQL Server agent jobs are enabled
- there is at least one valid native backup step
- A step is valid if it contains one or more referenced databases.
- For SQL Server 2005 and SQL Server 2008, the backup step must be enabled. If a maintenance plan is not displayed in the list, this may because the maintenance plan has already been converted, or because it does not contain any steps to convert.
If you select a maintenance plan that has backup tasks for more than one backup type, for example full, differential, and transaction log, when you click Next the wizard displays a page asking you whether you want to use the same settings for all backup types or use different settings for each backup type.
If you select apply different options for different backup types, the options pages in the following step are repeated for each backup type.
Step 3: configure settings for features provided by SQL Backup
This page is for specifying the locations and file names for backups, and for managing existing backup files.
- Backup folder is the name of the folder to back up to. You can optionally use the <tags> available in SQL Backup (see File Location Tags for more information).
- File name is the name of the file to back up to; this requires use of the <tags>. To reset the file name format to its default value, click Reset.
- Overwrite existing files overwrites backup files of the same name that already exist.
- Delete backup files older than deletes any backups of the same type, on the same server and database that are older than the specified time frame.
- Verify files after completion of backup performs some additional checks to confirm that the backup has not been damaged or corrupted.
The next page is for specifying compression and encryption settings.
Compress backup uses compression to reduce the size of the backup file. Higher compression levels generally produce smaller files, but may take slightly longer to produce. The compression levels available to you depend on the edition of SQL Backup you are using. For more information, see Compression Levels.
Encrypt backup uses 128-bit or 256-bit encryption to secure the backup file against unauthorized users. The encryption levels available to you depend on the edition of SQL Backup you are using. Type a password for the backup in Password, and again in Confirm password.
Send to sends an email when the backup is completed (on success or failure). If you select the Send email only on error check box, emails are sent only on failure. You must configure the email settings on the Options dialog box in the SQL Backup graphical user interface. For more information about configuring email settings, see Email Notification Options.
Step 4: review and apply the changes
This page provides a summary for reviewing your settings.
When you click Start, the wizard displays the progress of the conversion, including any issues that occur.
Step 5: verify the changes
When the maintenance plans have been converted, you are recommended to check them in SQL Server Management Studio or SQL Server Enterprise Manager.
For SQL Server 2000 and legacy maintenance plans, a new maintenance plan and SQL Server Agent job is created with the settings you specified in the Maintenance Plan Conversion Wizard; the SQL Server Agent job in the old maintenance plan is disabled.
For SQL Server 2005 and SQL Server 2008, the existing maintenance plan is modified. Any backup tasks with native SQL Server backups are disabled and replaced with steps that use SQL Backup; any links or relationships between job steps should remain intact.
An example of a maintenance plan before conversion:
An example of a maintenance plan after conversion and reorganization:
Was this article helpful?
Thanks for your feedback!
- Backups stop working when the SQL account passwords are changed
- Backups and restores taking longer each time they run
- Improving performance by leveraging multi-processor hardware
- Checking the status of a backup or restore
- SQL Backup Agent doesn't start on named instance
- No backup files are erased when the verify option is also used
- Log shipping initialisation failing with error 3176
- Installing SQL Backup unattended
- Issues faced when upgrading an MSCS cluster server
- Cannot schedule log shipping on case-sensitive servers
- Activation fails because response does not match registration properties
- SQL error -1 on backup with 64-bit
- Could not find procedure 'master...sqbutility'
- 'Does not exist' error manually creating a generic service resource
- Backing up log shipping standby databases
- Stopping a backup or restore whilst in progress
- Backing up full-text catalogs using SQL Backup
- Cannot resolve collation conflict
- Microsoft cluster installation (version 4)
- Informing the SQL Agent of job failures
- Database log files may continue to grow even though transaction logs are backed up
- Cannot load xp_sqlbackup.dll
- Minimum Windows Rights Required for SQL Backup Agent
- Bringing a log shipping standby database online
- Console does not support editing the command you selected
- Malformed database disk image error
- Cannot use a local account to run SQL Backup Agent on cluster
- Preparing SQL Servers for remote installation
- SQL error 18210 and VDI error 1010
- Log shipping jobs not deleting old .sqb files
- Scheduled backups may not include new databases
- VDI error 1010 due to an abort request
- Cannot save or see backup templates
- Not all databases appear in the log shipping wizard
- No mapping between account names and security IDs was done
- SQL error 3101 (database is in use) during log shipping
- Insufficient quota to complete the requested service
- Configuring SQL Server procedure memory
- Backing up and restoring on SQL Server Express Edition
- Cannot run two database backups at the same time
- Restoring database backups across a local network
- In some situations the last compressed data block fails to be written to disk
- Configuring permissions for the SQL Backup Agent service
- Restoring backups from one server to a second server using the user interface
- Using SQL Backup tags to automate backup file naming
- VDI 1010 Error
- SQL Backup 5 cannot connect to servers running SQL Backup 4.0
- Files are created when NOWRITE or NOCOMPRESSWRITE is used in conjunction with multiple threads
- Cannot backup a database when full-text catalogs are not online
- Moving a full-text catalog on RESTORE
- Preventing backups over the network from timing out
- Deleting backup history manually
- SQL Backup installation from SQL Toolbelt installer only installs the console
- Console taking a long time to start up
- Reporting across multiple servers, login fails for user NT AUTHORITY\ANONYMOUS LOGON
- SQL Backup Agent cannot start due to account lookup error
- IO Error on backup or restore restart-checkpoint file
- Unable to edit SQL Backup Scheduled Jobs via the Jobs Tab in the SQL Backup GUI (version 5)
- VDI error 1000 caused by improperly installed VDI interface
- VDI Error 1000 caused by account lookup failure
- VDI error 1000 caused by insufficient permissions
- Error 193: %1 is not a valid Win32 application.
- Installing SQL Backup on a cluster
- Restoring the SQL Server MASTER database
- VDI Error 1010: Failed to get the configuration from the server because the timeout interval has elapsed
- Changing the default data location used by SQL Backup
- Index was outside the bounds of the array error during registration
- Repairing the SQL Backup server-side data store
- Troubleshooting slow backup and restore tasks
- Completed backup jobs showing "in progress" status (version 5)
- Restore wizard: files incorrectly labeled 'Missing' when browsing for a backup file to restore.
- When creating a backup job using the wizards some of the user databases may not be listed
- How to restore a filegroup
- System error 1453 while backing up (Insufficient quota to complete the requested service)
- SQL Backup VDI 1030: Failed to create VirtualServiceSet component
- Backups fail on named instances on custom ports
- SQL error 3101 (database is in use) during full database restore
- Error acquiring mutex occurring during use
- Transaction log continually growing on disaster recovery database
- Reseeding a disaster recovery database
- SMTP mail options not being saved
- SQL Backup Activation NullReferenceException Error
- Scheduling SQL Backup restore jobs
- SQL Backup Error 880: permission denied in database
- Deleting remote backup files after a specified time period (version 5)
- SQL Backup Unable to Login to Perform Backup or Restore
- Restore operation errors with exitcode 680
- "Failed to initialize local data store" error
- Trouble browsing network shares when backing up or restoring
- System error 32 (The process cannot access the file because it is being used by another process)
- Log backup failing because there is no current database backup
- Error locating server or instance of SQL Server
- How to set up log shipping between machines on different domains
- SQL Backup and CPU affinity
- SQL Backup mirrored backups
- Error trying to run backup job
- "Access to the database file is not allowed" error
- The server principal NT AUTHORITY\SYSTEM is not able to access the database
- Browsing while using SQL Server authentication is disabled on the selected server
- Cannot generate SSPI context message
- Log ship to multiple servers
- File browser does not work for remote servers
- Configuring Log Shipping to two Target Databases
- Previous backups not deleted according to ERASEFILES setting
- SQL Backup Reporting fails after upgrading to Version 6 from Version 5 for Multiple
- VDI error 1010 error on log backup when no backup is available
- SQL Backup failed with exit code: 1010 SQL error code: 3101 [SQLSTATE 42000] (Error 50000). The step failed.
- Log backup for a database failing to get copied to the log shipping share
- Mirrorfile backup jobs producing corrupt files
- Activity monitor showing sqlbackup status as wait type MSQL_XP
- Backup and restore processes using high percentage of CPU resources
- Warning 485: File does not exist encountered during a restore (but the process completes successfully)
- Log Shipping error 130 when moving restored file
- SQL Backup "Warning 110" generated
- Attempting to restore data into a SQL Express database that exceeds limit
- SQL error 3241 when restoring database
- A nonrecoverable I/O error encountered on Backup or restore operation
- SQL error 15404
- General log-in problem: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
- Warning: System error 1450 when Backing up
- Problems with "Auto-Close" option set when backing up
- Warning: System error 64 (The specified network name is no longer available) on backing up across a network
- SQL error 4208 encountered on backing up
- Warning 170: "Log files are not in sequence" - on log shipping (restore) operation
- Warning: System error 121 (The semaphore timeout period has expired)
- Changing your participation in the quality improvement program
- Installing SQL Backup server components unattended
- Changing your participation in the quality improvement program
- Verifying backups of the master database
- Log files
all SQL products
- Compatibility of Red Gate tools in 64-bit environments
- Application has encountered an error and needs to close
- Error message after installing SQL Toolbelt - The description for Event ID ( 1 ) in Source ( nview_info ) cannot be found.
- Changing the temporary directory used by the installer
- Toolbelt Installer "hanging" while "scanning volumes"
- Login failing with "trusted SQL Server connection" error when using RunAs
- Some Red Gate products identified as containing a trojan by Anti-Virus software
- Activation may fail with Unknown Error -1
- Product uses web help although a CHM file is available locally
- Argument exception resulting from missing environment variable
- Check for updates may fail when used through proxies
- 'Unidentified Publisher' error when repairing or uninstalling
- Licensing activates product as standard edition
- Moving Red Gate software products to another machine
- Red Gate tools log locations
- The application UI opening slowly when there is no internet access
- Getting help offline
- Using SQL Backup to back up to a network share
- Manually installing SQL Backup server components on clusters (Windows Server 2003)
- Manually installing SQL Backup server components on clusters (Windows Server 2008)
- Using SQL Backup log shipping to maintain a standby server
- SQL Backup release notes - version 6.xx
- SQL Backup release notes - version 7.xx
- Working with the new features in SQL Backup 6
- Using flexible licensing with SQL Backup Pro and SQL HyperBac
- Using SQL Backup Pro and SQL HyperBac together on the same server
all SQL products
- Red Gate product acknowledgements
- Activating your products
- Activating your products
- Red Gate bundle history
- Check for updates
- Troubleshooting Check for Updates errors
- Current versions
- Deactivating your products
- Installing Red Gate products from the .msi file
- Requesting additional activations
- Serial numbers for bundles
- Reactivating using a different serial number
- Extending your trial
- Finding your serial numbers
- Moving a serial number from one computer to another
- No response received for manual activation
- Licensing and activation resources
- Licensing and activation resources
- Troubleshooting licensing and activation errors
- Licensing and activation FAQs
- Red Gate tools log file locations
- Download old versions of products
- Download product prerequisites & utilities
- Support & upgrades
- Upgrading your software
- Upgrading FAQs