Access the SQLsafe Help

Transcription

1 Access the SQLsafe Help While the Release Ntes prvide yu with the mst current infrmatin regarding SQLsafe, the main Help gives yu the detail yu need t understand SQLsafe and hw it prvides a pwerful backup and recvery slutin. Yu can use the main SQLsafe Help t: Manually back up yur database Autmate yur backups and restres Instantly restre yur database Updated: 2/2/ :31 PM

2 What is SQLsafe? Idera SQLsafe (SQLsafe) prvides a high-perfrmance backup and recvery slutin fr Micrsft SQL Server. SQLsafe saves mney by reducing database backup times by up t 50% ver native backups and reducing backup disk space requirements by up t 95%. SQLsafe als enables cmplete hands-free' autmated backups f yur entire SQL Server infrastructure and ensures cmpliance with yur rganizatin s backup and recvery plicies. Frm implementatins with tens f SQL Servers t enterprises with hundreds f instances spread arund the glbe, SQLsafe is the nly SQL Server backup and recvery slutin that scales t meet the challenge.

3 Hw des SQLsafe help me? In many rganizatins tday, SQL Server databases are the repsitries fr large vlumes f business-critical data. As database size grws, the time required t back up yur data using native tls can easily exceed yur maintenance windws, plus a huge amunt f strage space is needed fr the files. Restre peratins als becme time-cnsuming. DBAs need a pwerful backup and recvery slutin that greatly reduces backup and recvery time, minimizes strage requirements, and prvides enterprise management capabilities t cnduct backups acrss a large numbers f servers simultaneusly. SQLsafe has been specifically designed t meet these requirements, resulting in increased applicatin and business availability fr yur critical SQL Server infrastructure. As a state-f-the-art backup and recvery slutin, SQLsafe prvides: Maximum backup file cmpressin Minimum backup times Reduced failures due t netwrk glitches Accelerated mean time t restre Ensured cmpliance with crprate backup plicies

4 Find answers using this dcumentatin This dcumentatin set includes a cmprehensive nline Help system as well as additinal resurces that supprt yu as yu install and use the prduct. Yu can als search Idera Slutins, available at the Idera custmer service prtal (

5 Cntact Idera Please cntact us with yur questins and cmments. We lk frward t hearing frm yu. Fr supprt arund the wrld, please cntact us r yur lcal partner. Fr a cmplete list f ur partners, please see ur Web site ( Sales GO.IDERA ( ) (nly in the United States and Canada) Sales sales@idera.cm Supprt Website GO.IDERA ( ) (nly in the United States and Canada)

6 Definitin f terms The fllwing terms are used in the prduct and thrughut the dcumentatin. Applicatin Feature SQLsafe perfrms tasks and displays infrmatin depending n the Applicatin Feature yu have selected. Yu can change the applicatin feature by clicking a buttn in the navigatin pane n the Management Cnsle. SQLsafe Tday, an additinal feature, can be reached by clicking the glbe icn n the menu bar, r thrugh the View menu. Backup Agent The Backup Agent is a service that runs n each f the SQL Server instances hsting databases yu want t backup and restre. Befre yu can deply a Backup Agent t a SQL Server instance, yu must register the SQL Server instance with SQLsafe. Operatin An Operatin is a wrk item that can be scheduled t be perfrmed by the Backup Agent. Backups and restres are executed as peratins. Plicy A plicy cnsists f a list f databases, a set f peratins t be perfrmed n thse databases, and a set f schedules accrding t which the peratins will be perfrmed. Plicies allw yu t define a maintenance plan acrss multiple SQL Server instances, which can reside n ne r mre physical servers. Yu can then use the Management Cnsle t mnitr the status f plicies and their assciated database backup peratins. Server Grups Server Grups are cllectins f similarly tasked SQL Server instances, whse perfrmance and plicy status is mre easily mnitred tgether. Yu are nt required t place SQL Server instances int grups but, in an enterprise with hundreds f servers, cmpliance review can be greatly simplified.

7 Hw t use the Help This Help system can be accessed either thrugh the Start menu, thrugh the Help menu n the Management Cnsle, r by pressing F1 n yur keybard while n the windw fr which yu wuld like mre infrmatin. TIP The nline Help requires Internet Explrer versin 7.0 r later.

8 Abut Idera At Idera, we deliver a new generatin f tls fr managing, administering, and securing yur Micrsft Windws Servers, including SQL Server, SharePint, PwerShell and Micrsft Dynamics. We emply numerus industry experts wrldwide wh are devted t bringing prven slutins t yu, the administratr. Idera prvides slutins that help yu ensure server perfrmance and availability and reduce administrative verhead and expense. Our award-winning prducts install in minutes, cnfigure in hurs and deply wrldwide in days. Idera is a Micrsft Gld Certified Partner headquartered in Hustn, Texas, with ffices in Lndn, UK, Melburne, Australia, and Sa Paul, Brazil.

9 Idera prducts Our tls are engineered t scale - frm managing a single server t enterprise deplyments with thusands f servers. Idera prducts cmbine ease f use with a design that installs in minutes, cnfigure in hurs, and deply wrldwide in days. T learn mre abut Idera prducts, visit ur Web site (

10 Legal ntice Idera a divisin f BBS Technlgies, Inc. IntelliCmpress, DTx, Idera Newsfeed, Newsfeed, Pint admin tlset, PwerShellPlus, SharePint admin tlset, SharePint backup, SharePint perfrmance mnitr, SQL admin tlset, SQL change manager, SQLcheck, SQLcmpliance, SQL cmpliance manager, SQLcnfig, SQL defrag manager, SQL diagnstic manager, SQL diagnstic manager mbile, SQLdm, SQLdm Mbile, SQL dctr, SQL jb manager, SQLpermissins, SQL mbile manager, SQLsafe, SQLsafe Freeware Editin, SQLscaler, SQLschedule, SQLsecure, SQLsmarts, SQLstats, SQLtl, Idera, BBS Technlgies and the Idera lg are trademarks r registered trademarks f BBS Technlgies, Inc., r its subsidiaries in the United States and ther jurisdictins. All ther cmpany and prduct names may be trademarks r registered trademarks f their respective cmpanies BBS Technlgies, Inc., all rights reserved. THIS DOCUMENT AND THE SOFTWARE DESCRIBED IN THIS DOCUMENT ARE FURNISHED UNDER AND ARE SUB- JECT TO THE TERMS OF A LICENSE AGREEMENT. EXCEPT AS EXPRESSLY SET FORTH IN SUCH LICENSE AGREE- MENT, BBS TECHNOLOGIES, INC., PROVIDES THIS DOCUMENT AND THE SOFTWARE DESCRIBED IN THIS DOCUMENT "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIM- ITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. SOME STATES DO NOT ALLOW DISCLAIMERS OF EXPRESS OR IMPLIED WARRANTIES IN CERTAIN TRANSACTIONS; THEREFORE, THIS STATEMENT MAY NOT APPLY TO YOU. YOU ARE ENCOURAGED TO READ THE LICENSE AGREE- MENT BEFORE INSTALLING OR USING THIS DOCUMENTATION OR SOFTWARE. Sme cmpanies, names, and data in this dcument are used fr illustratin purpses and may nt represent real cmpanies, individuals, r data. This dcument culd include technical inaccuracies r typgraphical errrs. Changes are peridically made t the infrmatin herein. These changes may be incrprated in new editins f this dcument. BBS Technlgies, Inc., may make imprvements in r changes t the sftware described in this dcument at any time BBS Technlgies, Inc., all rights reserved. U.S. Gvernment Restricted Rights: The sftware and the dcumentatin are cmmercial cmputer sftware and dcumentatin develped at private expense. Use, duplicatin, r disclsure by the Gvernment is subject t the terms f the BBS Technlgies, Inc., standard cmmercial license fr the sftware, and where applicable, the restrictins set frth in the Rights in Technical Data and Cmputer Sftware clauses and any successr rules r regulatins.

11 7.0 Release Ntes Yu need a pwerful backup and recvery slutin that greatly reduces backup and recvery time, minimizes strage requirements, and prvides enterprise management capabilities t cnduct backups acrss a large numbers f servers simultaneusly. SQLsafe has been specifically designed t meet these requirements, resulting in increased applicatin and business availability fr yur critical SQL Server infrastructure. Learn abut key new features in this release Review issues fixed by this release Review previus features and fixed issues See knwn issues See list f recmmended Idera Slutins Updated: 2/2/ :31 PM

12 New features and fixed issues SQLsafe 7.0 prvides the fllwing new features and fixed issues. 7.0 new features Access yur database quickly during a restre SQLsafe gives yu the ptin t bring yur database back nline quickly when perfrming a restre. The InstantRestre feature lets yu wrk n restring a database while allwing users t perfrm read and write peratins t the database during this prcess. InstantRestre is available nly fr restring full databases and des nt supprt a restre f individual files r file grups. Autmatically run a Full backup prir t a Diff/Lg backup SQLsafe simplifies the initial setup prcess by autmatically detecting and perfrming a Full backup prir t a Differential r Transactin Lg backup fixed issues SQLsafe applicatins and services n lnger experience a lng delay when starting if Windws cannt verify the Authenticde signature n the assciated applicatins and services. SQLsafe Agent deplyment n lnger fails due t an issue that ccurs when accessing the registry n the remte machine during installatin. The SQLsafe Management Cnsle nw prperly handles creating and re-initializing lg shipping databases that include several data files. The SQLsafe Management Cnsle nw prperly handles creating restre plicies fr databases that include several data files fixed issues The SQLsafe Tday page nw accurately displays the status fr each item n the plicy list and includes the status fr peratins that ccasinally did nt appear because the UTC ffset was set t hurs instead f minutes. 7.0 fixed issues The Retry reading backup files after netwrk errrs check bx n the Backup Sets tab f the SQLsafe Database Restre wizard is renamed Enable netwrk resiliency. The functinality remains the same while the name f the field was changed t imprve usability. The Verify (checks integrity, n data restred) ptin mved frm the Recvery State tab t the Target tab in the SQLsafe Database Restre wizard. SQLsafe nw prperly displays the selectin in the Select backup sets manually bx when the user switches frm ne database t anther using the Restre wizard. This issue affected users attempting t restre multiple databases. New rlling lgs imprve trubleshting by aviding issues that result when a single lg file cntinues t stre infrmatin and grws withut a limit. This file can cause perfrmance issues and be hard t search fr clues t find the issue yu are trying t reslve. This feature is recmmended fr use nly when instructed by Idera supprt. SQLsafe Reprting n lnger displays an errr message when a user attempts t run the Last Backup reprt. Dependent SQLsafe peratins in a series are nw assciated s that when ne f the peratins fails, all f the fllwing peratins are canceled. The Restre wizard nw prperly handles the LSN chain when there is an intermediate Full backup. Perfrmance updates imprve the speed f the SQLsafe installatin.

13 Enhancements t SQLsafe memry usage decrease the chance f memry leaks r fragmentatin. Users can nw backup a database using nly ne thread as specified in the Thread Cunt field n the SQLsafe Backup Plicy wizard Optins tab. SQLsafe alerting nw prperly handles lg shipping restre schedule start times when set t a nn-default value. SQLsafe netwrk retry updates fixed an issue that resulted when the SQLAgent jb hung during a backup and the netwrk retry functin is disabled. SQLsafe n lnger causes an extreme lad n the tempdb while backing up a database. SQLsafe nw prperly handles FQDN names when cnnecting t the Backup Service. SQLsafe n lnger truncates text within the Result Text field. Users can nw srt the list f databases in the SQLsafe Backup wizard by clicking the apprpriate clumn name. SafeTSQL users wh submit an encryptin passwrd that fails verificatin nw receive the crrect errr message. The Backup Plicy wizard n lnger re-runs the file access check after a user edits the plicy unless the change was made t the Lcatin tab. SQLsafe nw allws encryptin passwrds f mre than 24 characters. This update allws users t implement pass phrases as a mre effective methd f security. Users n lnger experience an issue causing the default SQL Server instance file path t change when re-running a failed r skipped backup. SQLsafe nw features Cancel buttns in a number f areas available when the user runs a task. Yu can cancel a task when perfrming lg shipping re-initializatin, deleting a plicy, enabling r disabling a plicy, running a jb, re-synching a plicy, r updating a license. SQLsafe nw prmpts the user immediately after a user accunt credential check fails. Imprved Cmmand-line Interface (CLI) dcumentatin regarding SQLsafe and TSM server is lcated in the SQLsafe Help tpic, Back up t the TSM Server. Accessing sample Cmmand-line Interface (CLI) and Extended Stred Prcedure (XSP) script sample access is nw dcumented in the Architecture and Cmpnents. Users wh submit a script that cntains unnecessary backslash characters in the file path n lnger receive an errr message stating, "Value cannt be null." SQLsafe nw mits the unnecessary backslash characters and cntinues the peratin. Users can nw create and run lg shipping r restre plicies n a database that cntains multiple files n different drives. The SQLsafe Management Cnsle nw cntains the prper certificate s the user n lnger receives a request fr credentials each time they launch the Cnsle. This issue affected Windws 2008 users replying n user accunt cntrl functinality. The default Cnnectin Settings detail n the SQLsafe Backup wizard Lcatins tab n lnger retains any changes made during previus use. Users can nw quickly find an instance in the SQLsafe Database Restre wizard Databases tab by typing the name directly int the instance field and selecting the apprpriate instance when it appears. Users can nw successfully change the IP address n the server hsting the SQLsafe Management Service withut causing IP address reslutin issues with the Backup Agent. Users attempting t restre an lder, inactive backup file stred t a TSM server n lnger receive an errr message. SQLsafe XSP nw crrectly handles wide-character Unicde file names. Updated file access permissins fixed a perfrmance issue caused when SQLsafe ran the Backup Plicy File Access Check n every database within a SQL Server instance. SQLsafe perfrmance is imprved when a user attempts t create r run a plicy, r lad the plicy status pages.

14 Users with large SQLsafe repsitries n lnger encunter a timeut when accessing the Backup Sets page in the Management Cnsle during a restre. If a backup plicy specifies bth a FULL as well as DIFF r LOG backups t be perfrmed, the FULL backup is autmatically run fr new databases that have n previusly-perfrmed FULL backup existing at the time the FULL, DILL, r LOG backup is scheduled, whichever ccurs first. The SQLsafe Management Cnsle n lnger prevents users frm deleting sme plicies. These plicies failed when lading frm the Repsitry befre the user attempted t delete the plicy. PDF files f the SQLsafe Help and SQLsafe Release Ntes nw include ht links t access related infrmatin within the dcument.

15 Previus features and fixed issues This build includes many fixed issues, including the fllwing updates. 6.6 build 105 fixed issues SQLsafe nw includes nly ne rw in the MSDB backupmediafamily table when yu specify a single stripe fr a backup peratin. Previusly, this table cntained multiple rws fr a backup althugh nly ne stripe was specified. Perfrmance imprvements intrduced in SQLsafe 6.6 nw enable users wh have tuning enhancements n their SQLsafe peratins t return t default values t avid any errrs resulting frm the updated cde. These imprvements benefit all users but can negatively impact users with enhancements dependant upn this SQLsafe cde fr enhancements such as: 6.6 fixed issues Thread cunts. The backup XSP script cntains a parameter such = <value>, r the CLI script may be similar t -Threads <value>. In this case, remve the threads parameter. VDI settings. The registry includes entries such as VDICnfiguratinTimeut, VDIMaxTransferSize, VDI- NumberOfBuffers, and VDITransferBlckSize. In this case, delete yur custm registry values. SQLsafe nw successfully upgrades frm 6.4 t 6.5 withut rebting the target server. This issue was mst likely t happen when the backup was nt fully cmplete and lcked sme files. When the installer discvered ne f these lcked files, it initiated a rebt n the target server. SQLsafe nw successfully upgrades frm 6.3 t 6.5 withut causing the Repsitry database upgrade t fail during the prcess. This issue was mst likely t happen t users whse initial SQLsafe installatin is versin 6.3. Perfrmance enhancements in SQLsafe nw decrease respnse times when retrieving data by reducing the number f recrds retrieved. The SQLsafe Backup Agent service nw crrectly restarts n the target server after an upgrade t SQLsafe 6.5. An ccasinal errr caused the installer agent t fail t restart. CPU utilizatin n the Repsitry database server n lnger peaks at 100% when querying the Repsitry database fr peratins needing alerts. This issue was mst likely t happen t SQLsafe users with ver 1,000 databases in a single instance. SQLsafe nw restres backups in the crrect rder when restring using lg shipping plicies. This issue was mst likely t happen with SQL Server instances in envirnments cntaining a psitive GMT ffset time zne setting. The SafeTSQL utility nw supprts cnverting backup files written by SQLsafe versin 6.5. Users previusly received an errr message when attempting t cnvert a SQLsafe backup t a native backup using SafeTSQL. The SQLsafe Restre Plicy wizard n lnger prevents users frm creating a restre plicy when the target server license is expired. While ther features are unavailable after license expiratin, database restres are allwed. The Select Archives frm TSM windw in SQLsafe nw cntains an ptin t brwse fr inactive files when lking fr a specific TSM backup archived file.yu can access this windw by right-clicking n the apprpriate SQL Server Instance in the navigatin pane and selecting Brwse TSM Archives. SQLsafe als prvides access t this windw in the SQLsafe Backup wizard after yu click Change n the Lcatins tab, and frm the SQLsafe Database Restre wizard when yu click Change n the Surces tab. SQLsafe n lnger deletes backup files when a deadlck ccurs. The SQL Server BACKUP DATABASE/LOG cmmands ccasinally encunter a deadlck errr when attempting t update msdb tables. SQLsafe interpreted these deadlck errrs as backup errrs and deleted the generated backups. SQLsafe n lnger cnsiders these msdb update deadlck errrs as a backup failure, and des nt delete the backup files.

16 6.6 features SQLsafe nw specifies the TSM ID in the restre ptins when a user attempts t perfrm a restre frm an inactive file. This issue was mst likely t cause the restre t fail as a result f nt prviding prper identificatin. The SQLsafe Restre functinality nw selects the crrect Full, Differential, and Lg backup sets when restring frm a specific pint in time. Users previusly did nt receive the Differential set. If the user manually selected the Differential backup, SQLsafe included all transactin lgs previus t the differential. SQLsafe nw ffers imprved repsitry perfrmance in large repsitries. This issue was mst likely t happen when the user attempted t expire r delete a TSM backup archive. These perfrmance enhancements include enfrcing cnsistent characters limits within SQLsafe. The [filename] clumn in the [backup_archives] table nw allws up t 400 characters and the TSM file path allws up t 260 characters. The SQLsafe Tday page and the Backup Plicies Status page nw shw cnsistent infrmatin regarding backup peratin failures. SQLsafe previusly prvided backup peratin failure detail n the Backup Plicies Status page but nt n the SQLsafe Tday page. The SQLsafe Restre Plicy wizard nw supprts scheduling weekly restres. Users previusly culd schedule nly daily restres. The SQLsafe Management Service n lnger sends an message stating that a backup did nt ccur, nly t be fllwed a minute later by an message that the backup was successful when the backup was actually successful. This issue was mst likely t ccur when the backup jb in the SQL Server agent did nt start within the first minute as scheduled. The SQLsafe Management Service n lnger reprts that cmpliant plicies are nn-cmplaint due t a timestamp failure. The issue was likely t ccur after a restre failed n a secndary server, causing the Management Service t reprt that the server was ut f date due t a future timestamp that ccurred during lg shipping. The SQLsafe Management Service als n lnger reprts that a secndary database is "TOO OLD" when a secndary restre crrectly ccurs. SQLsafe n lnger displays infrmatin that a full backup did nt start as scheduled while the backup histry displayed that the backup started as planned. SQLsafe crrectly started the backup as scheduled but was reprting it incrrectly in the plicy status. SQLsafe n lnger displays an errr message after clicking OK when editing SQLsafe Backup Agent prperties. This issue was mst likely t ccur when the number separatr and current culture did nt match. The SQLsafe Management Service n lnger encunters deadlcks when querying the Repsitry fr prcessing plicy ntificatins. This issue was the result f a cntentin between status writing and plicy ntificatin prcessing in the SQLsafe Management Service. Users n lnger receive incrrect plicy ntificatin messages. Users wh selected Only n the initial ccurrence f a selected event received ntificatin fr every ccurrence. SQLsafe restre and verify perfrmance is imprved by updating the SQLsafe Backup Agent service. A perfrmance imprvement f 10-45% is expected depending n the envirnment, including CPUs, memry, and disk speed. Users nw can cpy detail listed in the Last Operatin Status. Yu can access the Last Operatin Status by clicking the status message displayed n the Plicies tree cntent pane Last Operatin Status bx. Yu can als quickly rerun a backup, lg shipping, r restre plicy by clicking the failed peratin in the Last Operatin Status bx. SQLsafe nw crrectly displays green messaging fr successful manual backup plicies. The SQLsafe Backup Agent n lnger creates an unnecessary flder while creating the status cache flder. The additinal flder was named, "SQLsafeStatusCache." SQLsafe n lnger leaves the database in single-user mde after a user attempted t perfrm a single-user restre, and the restre failed. This issue was likely t ccur after the restre failed because f an errr such as a lack f disk space. The SafeTSQL utility n lnger displays an errr message and fails t cnvert a SQLsafe backup t a native backup in sme situatins. The errr message read, "Object reference nt set t an instance f an bject."

17 Restre perfrmance imprvements Restre perfrmance imprvements reduce recvery time by up t 40% frm previus versins f SQLsafe. Crss TSM Server Supprt Brwse, back up, and restre backup files lcated n any remte TSM Server. Imprved brwsing fr TSM files Use the Management Cnsle t brwse active and inactive backup files n the TSM Server. Imprved restre TSM 'inactive' files 6.5 features Use the Management Cnsle t restre backup files that are marked 'inactive' n the TSM Server. Restre Plicies Simplify database synchrnizatin and autmate disaster recvery by rutinely restring full backups t a secndary server. Lgin Cpy Bring recvered databases nline faster by allwing SQLsafe t create missing SQL Server lgins and reslve any rphaned database users. Granular Alerts Backup and restre alerting can nw send ntificatins fr each peratin status, including failures, skips, warnings, and successes. Delete Backup File Optin Use this CLI/XSP cmmand t delete ld backup files withut perfrming a new backup. 6.5 fixed issues SQLsafe nw crrectly determines missed backups that were scheduled t be perfrmed mnthly. SQLsafe nw can back up databases that are larger than 16TB. The Surce tab n the Resurce wizard nw includes Repsitry query perfrmance imprvements that ensure the database list will display crrectly. SQLsafe plicies nw supprt multiple databases whse names cntain the ampersand special character ("&") fixed issues SQLsafe nw crrectly calculates cmpliance when the threshld fr a Lg Shipping Plicy is set t greater than 24 hurs (e.g., 25 hurs r mre). The SQLsafe Restre wizard n lnger verwrites the TSM backup cnfiguratin stred in the SQLsafe Repsitry when validating r restring the assciated archive. This fix allws yu t recver a previusly restred r verified backup file t a different TSM Client nde. The Backup Agent nw crrectly handles Windws 2000 authenticatin when accessing the backup archive. SQLsafe jbs, such as thse created by the SQLsafe Backup Plicy wizard, nw crrectly handle databases with names that cntain ampersands ( & ). SQLsafe nw crrectly encrypts backup files fr SQL Server instances running n Windws 2000 Server cmputers. 6.4 features

18 Backup enhancements Easily re-run a previus backup frm the peratin status grid in the Management Cnsle simply select the backup and right-click, using the same r different ptins Easily run Backup Plicy jbs frm the Management Cnsle simply select the plicy and right-click Create n-demand Backup Plicies that yu can easily run, as needed, thrugh the Management Cnsle Use new backup ptins t: Set yur database recvery mde t standby r nrecvery Specify when ld mirrred r striped backup files shuld be deleted (grmed) Use the new CLI/XSP expire cmmand t mark existing TSM backup files as inactive Restre enhancements Easily verify r restre backup files frm the peratin status grid in the Management Cnsle simply select the backup and right-click Use new restre ptin t preserve replicatin settings Crss-dmain supprt Deply SQLsafe cmpnents t separate, nn-trusted dmains Back up and restre instances lcated in nn-trusted dmains Platfrm supprt SQL Server 2008 R2 6.4 fixed issues The Backup Agent service nw crrectly handles backup peratins when the TSM Server returns an errr, such as the strage pl is full. If this situatin ccurs, the agent stps the backup peratin and returns a failure status message. SQLsafe nw crrectly saves yur plicy ptins when editing a Backup Plicy that writes backup files t a TSM Server. The Backup Agent nw uses the crrect case fr the name f the target backup archive when executing the delete ptin via the SQLsafe CLI r XSP. The Backup Agent nw crrectly handles memry resurce cnstraints when generating metadata fr SQL virtual database. The Backup Agent nw uses the crrect credentials fr queued peratins. Lg Shipping Plicies nw display the lcal time f the primary and secndary servers when executing and displaying status f backup and restre peratins. The Management Cnsle nw displays the crrect backup status, times, and latency fr Lg Shipping Plicies. The Management Cnsle nw crrectly handles timeut errrs received frm the SQLsafe Repsitry when attempting t initialize a secndary database in a Lg Shipping Plicy. The Management Cnsle can nw supprt a Backup Plicy that manages a large number f databases, such as mre than 500. The Management Cnsle nw crrectly addresses TSM Clients that are nt cnfigured t use the generate passwrd ptin. SQLsafe nw crrectly restres a backup file that was stred n a different TSM Client nde. The Details pane n the server, instance, r database status view, nw displays the crrect filename fr the backup archive used t perfrm a restre. SQLsafe nw crrectly sends alert ntificatin s per Backup Plicies created using a previus release f SQLsafe. When the Retry netwrk writes n errr ptin is enabled, SQLsafe nw crrectly handles netwrk errrs at the end f a backup peratin, allwing the peratin t cmplete successfully.

19 6.3 Build 521 fixed issues SQLsafe nw successfully verifies and restres TSM backup archive set when yu select the files using the SQLsafe Repsitry histry brwser in the Restre wizard. SQLsafe nw always restres backup files extracted frm a TSM archive set. SQLsafe nw successfully grms status messages frm the Repsitry accrding t yur set schedule. 6.3 Build 508 fixed issues SQLsafe nw prvides imprved perfrmance in the TSM Brwse dialg when brwsing a TSM server with a very large number f files. The SQLsafe Backup Agent crrectly restres TSM files when the file is selected in the TSM Brwse dialg. SQLsafe nw prvides imprved management service perfrmance when writing t a remte SQLsafe Repsitry. 6.2 fixed issues The SQLsafe CLI and XSP nw crrectly handle inactive TSM backup files when yur cmmand line syntax r script includes the delete ptin (-delete SQLsafe nw prvides better cmpressin and speed when backups are perfrmed using striped files r a specific number f threads. SQLsafe nw ffers imprved perfrmance when executing backup and restre peratins n SQL Server cmputers that experience a high memry lad. The Management Cnsle nw crrectly lads plicies that cntain many unregistered SQL Server instances. SQLsafe nw crrectly uses the specified lg file lcatin when it initializes a new secndary database in yur Lg Shipping Plicy. 6.1 fixed issues SQLsafe n lnger creates deadlcks n the MSDB database when perfrming transactin lg backup peratins. This issue was mre likely t ccur when the MSDB database size was very large and the SQL Server was experiencing a significant lad. When managing databases n a Windws 2000 Server, SQLsafe can nw verify and restre Rinjdael r AES encrypted backup files created with SQLsafe 5.0 r earlier. When yu create r edit a Lg Shipping plicy, SQLsafe autmatically matches the secndary server names with the crrespnding registered instances. Previusly, if yu used a different case when specifying the instance name, SQLsafe wuld nt recgnize the instance and the plicy status wuld becme ut f cmpliance and ut f sync. SQLsafe n lnger allws yu t create a Backup r Lg Shipping plicy that des nt have a defined schedule. SQLsafe nw crrectly applies the retry write setting fr Lg Shipping plicies. Previusly, when yu enabled this ptin, SQLsafe did nt crrectly include it in the crrespnding SQL Server jb. If yur Lg Shipping plicies use this setting, their status will change t ut f sync after yu upgrade t 6.1. T crrect this, re-synch the jb. The SQLsafe Backup and Backup Plicy wizards nw ffer additinal checksum ptins. Fr example, if yu chse t ignre checksum errrs, yu can nw als select the new Cntinue n errr ptin t ensure the backup file cntinues t be restred when a checksum errr is encuntered. 6.0 fixed issues Yu can nw select the target Windws platfrm when yu remtely deply Backup Agents using the Management Cnsle.

20 The Backup Agent n lnger stps when attempting t restre a backup that cntains ne r mre crrupted pages. Instead, the Backup Agent nw returns an errr. The Backup Agent nw crrectly reprts the database size per the SQL Server prperties reprted fr the selected database. SQLsafe nw ffers significantly imprved perfrmance when reading backup files frm a TSM device. This imprvement will be mst nticeable when restring TSM backups f large databases. (12380) SQLsafe nw autmatically analyzes yur envirnment during a backup peratin, and then changes the number f threads it uses in rder t achieve ptimal speed. This enhancement significantly imprves the perfrmance f yur backup peratins, especially TSM backups, where multi-threading is nw supprted fr manual backups. If yu have scripted yur backups using the SQLsafe cmmand line interface (CLI) r extended stred prcedures (XSP), we recmmend that yu edit the jb t take advantage f this new setting. T use the default aut-threading ptin, simply delete the -Threads parameter frm the cde in yur backup jb. The SQLsafe extended stred prcedures (XSP) nw supprt spaces in the und filename. (12497) When using the -withmve ptin in a SQLsafe XSP restre peratin, yu can nw specify a backup file whse name cntains a space. (11593) The Servers tree in the Management Cnsle nw easily allws yu t mve registered instances frm ne grup t anther, crrectly displays instances that have been re-registered after a previus deletin, and enfrces case-sensitivity t ensure each instance is registered with a fully unique name. (12807) When restring a database that has multiple LDF files, SQLsafe autmatically ensures each LDF file stred within the same directry are unique. (12510) Backup and Lg Shipping plicies are nw listed in alphabetical rder in the Plicies tree f the Management Cnsle. (12701) SQLsafe nw crrectly applies the discnnect users ptin when restring shipped transactin lgs t the secndary database. This ptin kills all pen sessins n the secndary databases befre restring the lg backup files. After yu upgrade t versin 6.0, an existing lg shipping plicy that enabled this ptin may display as ut f synch. T crrect this status, right-click the target plicy frm the Plicies tree, and then click Re-Sync Plicy Jbs with Plicy n the cntext menu. (12695) SQLsafe nw prvides a mre accurate cmpliance calculatin fr Lg Shipping plicies that takes int accunt yur defined backup and replicatin schedules. (12571) SQLsafe nw prvides a mre accurate status prgress bar when executing backup and restre peratins.

21 Knwn issues Idera strives t ensure ur prducts prvide quality slutins fr yur SQL Server needs. The fllwing knwn issues are described in this sectin. If yu need further assistance with any issue, please cntact Supprt ( Installatin and cnfiguratin cnsideratins SQLsafe Repsitry n lnger supprts SQL Server 2000 SQLsafe Repsitry n lnger supprts SQL Server Supprted versins include: SQL Server 2008 R2 SQL Server 2008 Standard and Enterprise Editins SQL Server 2005 Standard and Enterprise Editins SP1 r later SQLsafe n lnger supprts Itanium SQLsafe 7.0 des nt supprt the Itanium prcessr architecture. Fr mre infrmatin, see the sftware requirements. Pentium II prcessrs are nt supprted Yu shuld nt install SQLsafe n a cmputer running a Pentium II prcessr. Fr mre infrmatin, see the hardware requirements. Backup file names that use the %timestamp% macr may change when upgrading t SQLsafe 6.5 r later When sme users upgrade t SQLsafe 6.5 r later, the backup file names using the %timestamp% macr may change. This issue affects users wh have SQLsafe grm their backup files at backup time, using either the -delete cmmand line ptin r the Remve files lder than ptin in the Backup Plicy wizard. Previus versins expand %timestamp% t the UTC time f the backup. Beginning with SQLsafe 6.5, %timestamp% expands t the lcal time f the backup. As a result, SQLsafe may write new backups t files already created by an earlier versin f SQLsafe immediately after upgrading. By default, SQLsafe appends t backup files and this issue des nt ccur as the new backup appends t the existing file. This situatin reslves itself after the time difference between UTC and lcal time passes. Fr example, this issue is reslved after five hurs in the Central Standard Time zne (US). Nte that if yu specify t verwrite, SQLsafe verwrites the existing files instead f appending the new infrmatin. If yu upgrade frm a release earlier than SQLsafe 6.4, appends fail and display an errr message. Setup prgram remves previus versin when upgrade fails If the upgrade fails while yu are upgrading frm a previus versin f SQLsafe, the setup prgram remves the previus versin frm the SQL Server cmputer n which yu attempted the upgrade. XSP installatin fails n clustered SQL Server instances When yu use the Agent Only install t manually deply the SQLsafe Backup Agent t a clustered SQL Server instance, the crrespnding SQLsafe XSP installatin will fail. After the Backup Agent install cmpletes, yu can manually install the SQLsafe XSP. Fr mre infrmatin, see the Using the SQLsafe XSP Technical Slutin lcated in the Dcumentatin flder (by default, C:\Prgram Files\Idera\SQLsafe\Dcumentatin). Remte Backup Agent install fails when SQL Server is nt installed In rder t install the SQLsafe Backup Agent remtely, the cmputer frm which yu install SQLsafe must have a versin f SQL Server already installed. Fr mre infrmatin, see the sftware requirements.

22 Table Restre wizard is n lnger available in SQLsafe versin 6.0 r later T restre bjects and data frm yur backup files, use the new Idera SQL virtual database tl. Fr mre infrmatin, see Recver bjects using SQLvdb. FIPS-cmpliant encryptin n lnger requires additinal sftware when installing SQLsafe versin 6.0 r later In a FIPS-cmpliant envirnment, SQLsafe uses nly FIPS-cmpliant algrithms t encrypt yur backup files. These encryptin methds d nt require any additinal sftware. Fr mre infrmatin, see Ensure FIPS cmpliance. Upgrade any Backup Agents that perfrm TSM backups Due t the extensive TSM enhancements included in SQLsafe 6.4 and later, lder Backup Agents are nt cmpatible with 6.4. T ensure yu can cntinue backing up yur SQL Server data t TSM, upgrade any Backup Agent that is used t perfrm TSM backups in yur envirnment. 64-bit users need additinal steps t install reprts Users with 64-bit installatins must fllw different steps t install reprts. Fr mre infrmatin, see Idera slutin 3891, "Where d I find the SQLsafe reprts," in the knwledge base at ur Custmer Service Prtal ( Knwn issues in versin 7.0 InstantRestre requires the SE_MANAGE_VOLUME_NAME privilege n yur SQL Server InstantRestre may experience a negative impact n perfrmance if the SQL Server service accunt des nt have the SE_ MANAGE_VOLUME_NAME privilege (Instant File Initializatin). InstantRestre appears t stall when restring databases that cntain read-nly file grups SQLsafe 7.0 Beta hydratin appears t stall at 99% cmplete when restring databases that cntain read-nly file grups. SQL Server triggers InstantRestre hydratin when it perfrms read/write I/O n the database files. Because SQL Server des nt perfrm read/write I/O n the read-nly files, hydratin des nt begin. Eventually, hydratin begins when SQL Server perfrms read I/O n the files. Yu can deleted the database if yu experience this issue. Adding a new drive requires yu t restart the InstantRestre Service When yu add a new drive t a server, yu must restart the SQLsafe Filter Service t make sure that the SQLsafe Filter driver is attached t the new drive. When the SQLsafe Filter Service starts, it attaches the SQLsafe Filter driver t all the fixed drives n the server. If yu add a new drive after the service starts, the driver is nt attached and any files created n this drive during InstantRestre d nt functin crrectly. T avid this issue, simply restart the SQLsafe Filter Service after adding any new drive. Nt all files are remved when yu delete a database restred using InstantRestre Sme files may remain after yu attempt t delete a database previusly restred using the InstantRestre feature. In mst cases, yu can manually delete these mdf, ndf, ldf, and vbm files. If the files are lcked, restart either the SQLsafe Filter Service r the SQL Server Instance and then delete the files manually. InstantRestre Hydratin statistics are incrrect if the IR Server restarts during Hydratin During the Hydratin phase f the InstantRestre feature, if the IR filter service is restarted, the statistics incrrectly shw the hydratin prcess reset t zer. This is nt accurate as hydratin crrectly picks up where it left ff in the prcess. Offline SQLsafe Web Help may display a blank page Sme users experience a blank page when pressing F1 and using the ffline SQLsafe Help. If this issue ccurs, access the nline versin f SQLsafe Help at

23 Previus knwn issues SQLsafe Backup Agent may crash The SQLsafe Backup Agent can ccasinally crash and SQLsafe displays an errr similar t, ".NET Runttime versin Fatal Executin Engine Errr." Micrsft recmmends that users make sure that their envirnments include the fllwing patches: Windws 2003: Windws 2008 R2/Windws 7: Imprting backup archive sets may result in an errr SQLsafe may experience an issue when yu attempt t imprt backup archive sets int yur Repsitry. Lgins data archived nly n Full backups SQLsafe archives Lgins data nly when yu perfrm a Full backup. SQLsafe des nt archive this data when yu perfrm a Differential r Lg backup. Yu can restre Lgins data nly when yu use a single backup set. When yu specify multiple backup sets such as Full, Differential, and Lg, yu cannt restre Lgins data. Plicy views may be blank after upgrading t versin 6.6 The new granular alert ntificatins available in versin 6.6 prvide mre detailed feedback abut plicy cmpliance and status. Because plicy jbs created with SQLsafe 6.4 r earlier d nt supprt this feature, the Management Cnsle plicy views will nt display cmpliance status related t previus backup r restre peratins. Instead, the plicy views will track the plicy status frm the time yu upgraded. T see the status f previus backup and restre peratins, use the backup/restre peratin status pane n the instance and database status views. N Restre Plicy supprt fr backup files stred n TSM Servers The SQLsafe 6.6 Restre Plicy des nt supprt restring a database frm a backup file stred n a TSM Server. Metadata fr SQL virtual database is nt generated SQLsafe is unable t generate SQL virtual database metadata fr backups that use the fllwing ptins: SQL Server 2008 databases that use FILESTREAM t manage unstructured data Read-write filegrups File backups Errrs ccurring when saving changes may delete plicies If an errr ccurs while saving changes t an existing plicy, the plicy may be deleted.

24 Recmmended Idera Slutins Idera strives t ensure ur prducts prvide quality slutins fr yur database needs. The fllwing Idera Slutins have been recently added t the knwledge base at ur Custmer Service Prtal ( Number Title 203 SQLsafe backup fails with the errr message "Culd nt initialize Virtual Device Set" if the Backup Agent's service accunt is nt a member f the sys_admin server rle. 727 The SQLsafe cnsle desn't shw status fr backup and restre peratins SQLsafe back/restre peratin r agent deplyment returns errr The CPU type and CPU family f <server> culd nt be determined Hw t manually install the SQLsafe extended stred prcedures Hw t install the SQLsafe Backup Agent n a clustered SQL Server.