Backup Exec broke my SQL!

It could be that the SQL Native Client got messed up. Try
reinstalling the SQL Native Client.
-Sue
On Fri, 23 Mar 2007 13:54:28 -0700, Just Guessing
<JustGuessing@.discussions.microsoft.com> wrote:

>I installed Symantec Backup Exec 11d on a new Windows 2003 Small Business
>Server R1. I had many problems and after talking forever with Dell support,
>I uninstalled Backup Exec "manually" (believe it or not, there's no other
>way). This included downloading the Microsoft uninstaller and deleting
>registry entries manually.
>Now, when I try to reinstall Backup Exec, the installation fails when it
>tries to install SQL. This is the installation log:
>Symantec Backup Exec (TM) 11.0 for Windows Servers Installation Log
>03-14-2007,22:09:46 : E:\WINNT\INSTALL\BE\setup.exe
>03-14-2007,22:09:46 : CSetupApp::LoadSetupXML
>03-14-2007,22:09:46 : CSetupApp::ScanXML
>03-14-2007,22:09:46 : E:\WINNT\INSTALL\BE\Bin\Setup.xml
>03-14-2007,22:09:46 : MSI File Name = WindowsInstaller-KB893803-v2-x86.exe
>03-14-2007,22:09:46 : MSI Version = 3.1
>03-14-2007,22:09:46 : MSI Package Name = Symantec Backup Exec for Windows
>Servers.msi
>03-14-2007,22:09:46 : System Central Processor = 86
>03-14-2007,22:09:46 : Product Type = SETUP_BE
>03-14-2007,22:09:46 : Product Name = Symantec Backup Exec for Windows Servers
>03-14-2007,22:09:46 : Current Installing GUID
>={BEA465C8-2923-42C6-9141-BE44739A6A80}
>03-14-2007,22:09:46 : Product Version = 11.0
>03-14-2007,22:09:46 : CSetupSupport::IsValidMSIPackage
>03-14-2007,22:09:46 : E:\WINNT\INSTALL\BE\Symantec Backup Exec for Windows
>Servers.msi
>03-14-2007,22:09:48 : {BEA465C8-2923-42C6-9141-BE44739A6A80}
>03-14-2007,22:09:48 : {BEA465C8-2923-42C6-9141-BE44739A6A80}
>03-14-2007,22:09:48 : Equal PID
>03-14-2007,22:09:50 : Product version: 11.0.6235
>03-14-2007,22:09:51 : StartBESequence
>03-14-2007,22:09:51 : Executing BE_PreCheckInstall
>03-14-2007,22:09:51 : MDAC 2.82.1830.0 is installed on this system.
>03-14-2007,22:09:51 : Executing BE_SetSQLxLangVersion. Setting language
>version of SQL Express BKUPEXEC instance.
>03-14-2007,22:09:51 : BKUPEXEC SQLx setup file is SQLEXPR.EXE.
>03-14-2007,22:09:51 : MDAC 2.82.1830.0 is installed on this system.
>03-14-2007,22:09:51 : Executing StartBESequence
>03-14-2007,22:09:51 : Pulling user data from the MSI
>03-14-2007,22:09:51 : Upgrade state set to 0
>03-14-2007,22:09:51 : Executing SSO::PullDataMSI()
>03-14-2007,22:09:51 : Executing TSM_GetTSMSettings.
>03-14-2007,22:09:51 : Executing CDlgCAS::PullDataMSI()
>03-14-2007,22:09:51 : /TS:
>03-14-2007,22:09:51 : MSI processing complete
>03-14-2007,22:09:51 : Pulling user data from the command line
>03-14-2007,22:09:51 : COMMAND LINE: Checking UIMODE value
>03-14-2007,22:09:51 : COMMAND LINE: Checking for program group placement
>value
>03-14-2007,22:09:51 : COMMAND LINE: Checking for main feature selection
>03-14-2007,22:09:51 : COMMAND LINE: Checking for serialization values
>03-14-2007,22:09:51 : CDlgChooseCustom::PullDataSilent
>03-14-2007,22:09:51 : After check for parameter file exists.
>03-14-2007,22:09:51 : CDlgLocalChooseCustom Pass Function.
>03-14-2007,22:09:51 : After Check for INSTALL_CHOICE.
>03-14-2007,22:09:51 : After Check for INSTALL_TYPE.
>03-14-2007,22:09:51 : After Check for INSTALL_MODE.
>03-14-2007,22:09:51 : CDlgLocalChooseCustom Pass Function.
>03-14-2007,22:09:52 : InitData failed to open the cluster wrapper
>03-14-2007,22:09:52 : InitData failed to open the cluster wrapper
>03-14-2007,22:09:52 : COMMAND LINE: Checking for service account values
>03-14-2007,22:09:52 : Not in Maintenance mode
>03-14-2007,22:09:52 : Getting the Silent Params.
>03-14-2007,22:09:52 : COMMAND LINE: checking for SSO values
>03-14-2007,22:09:52 : COMMAND LINE: checking for DlgChooseDBServer values
>03-14-2007,22:09:52 : COMMAND LINE: Checking for tape drivers values
>03-14-2007,22:09:52 : COMMAND LINE: Checking for TSM values
>03-14-2007,22:09:52 : CDlgTSMConfig Pass Function.
>03-14-2007,22:09:52 : After Check for INSTALL_MODE.
>03-14-2007,22:09:52 : CDlgTSMConfig Pass Function.
>03-14-2007,22:09:52 : COMMAND LINE: checking for CASO values
>03-14-2007,22:09:52 : COMMAND LINE: Checking for clone values
>03-14-2007,22:09:52 : COMMAND LINE: Checking progress settings
>03-14-2007,22:09:52 : COMMAND LINE: Checking for NOINSTALL value
>03-14-2007,22:09:52 : Setup Command Line = "E:\WINNT\INSTALL\BE\setup.exe"
>03-14-2007,22:09:52 : List of switches set follows:
>03-14-2007,22:09:52 : /DEST: = C:\Program Files\Symantec\Backup Exec\
>03-14-2007,22:09:52 : /TS:
>03-14-2007,22:09:52 : Command line processing complete
>03-14-2007,22:09:52 : Executing BEDiag utility
>03-14-2007,22:09:52 : E:\WINNT\INSTALL\BE\Bin\Bediag.exe CORBETS1
>/o:C:\DOCUME~1\ALLUSE~1\APPLIC~1\Symantec\BACKUP~1\ Logs\Pre-Install_BEDiag.log
>03-14-2007,22:09:52 : BEDiag utility has been launched in asynchronous
>execution mode. Review
>C:\DOCUME~1\ALLUSE~1\APPLIC~1\Symantec\BACKUP~1\L ogs\Pre-Install_BEDiag.log
>for results.
>03-14-2007,22:09:52 : Install set to run in UI mode
>03-14-2007,22:09:58 : Validating license data
>03-14-2007,22:10:01 : InitData failed to open the cluster wrapper
>03-14-2007,22:10:01 : m_bUseNativeClient = 1
>03-14-2007,22:10:01 : Executing SQL_GetSQLServerEdition.
>03-14-2007,22:10:01 : DRIVER={SQL Native
>Client};SERVER=CORBETS1\SBSMONITORING;Trusted_Con nection=Yes
>03-14-2007,22:10:16 : V-225-206: Encryption not supported on the client.
>Client unable to establish connection An error has occurred while
>establishing a connection to the server. When connecting to SQL Server 2005,
>this failure may be caused by the fact that under the default settings SQL
>Server does not allow remote connections. ***To search for information about
>this error, click here
>03-14-2007,22:10:16 : V-225-226: Unable to connect to SQL Server. ***To
>search for information about this error, click here
>03-14-2007,22:10:16 : Executing SQL_GetSQLServerEdition.
>03-14-2007,22:10:16 : DRIVER={SQL Native
>Client};SERVER=CORBETS1\SHAREPOINT;Trusted_Connec tion=Yes
>03-14-2007,22:10:27 : V-225-206: Encryption not supported on the client.
>Client unable to establish connection An error has occurred while
>establishing a connection to the server. When connecting to SQL Server 2005,
>this failure may be caused by the fact that under the default settings SQL
>Server does not allow remote connections. ***To search for information about
>this error, click here
>03-14-2007,22:10:27 : V-225-226: Unable to connect to SQL Server. ***To
>search for information about this error, click here
>03-14-2007,22:10:27 : Executing SQL_GetSQLServerEdition.
>03-14-2007,22:10:27 : DRIVER={SQL Native
>Client};SERVER=CORBETS1\WSUS;Trusted_Connection=Y es
>03-14-2007,22:10:28 : V-225-206: Encryption not supported on the client.
>Client unable to establish connection An error has occurred while
>establishing a connection to the server. When connecting to SQL Server 2005,
>this failure may be caused by the fact that under the default settings SQL
>Server does not allow remote connections. ***To search for information about
>this error, click here
>03-14-2007,22:10:28 : V-225-226: Unable to connect to SQL Server. ***To
>search for information about this error, click here
>03-14-2007,22:10:52 : CDlgValidationSummary::ValidateData
>03-14-2007,22:10:52 : CDlgSerialNumber Pass Function.
>03-14-2007,22:10:52 : After Check for Remote_Install.
>03-14-2007,22:10:52 : After Check for RA_INSTALL.
>03-14-2007,22:10:55 : Validating serialization data
>03-14-2007,22:10:56 : CDlgLocalChooseCustom Pass Function.
>03-14-2007,22:10:56 : After Check for INSTALL_CHOICE.
>03-14-2007,22:10:56 : After Check for INSTALL_TYPE.
>03-14-2007,22:10:56 : After Check for INSTALL_MODE.
>03-14-2007,22:10:56 : CDlgLocalChooseCustom Pass Function.
>03-14-2007,22:10:56 : On Init of CDlgChooseCustom
>03-14-2007,22:10:56 : Leaving Init of CDlgChooseCustom
>03-14-2007,22:10:56 : CDlgLocalChooseCustom::OnInitDialog
>03-14-2007,22:10:56 : On Init of CDlgLocalChooseCustom
>03-14-2007,22:10:56 : InitData failed to open the cluster wrapper
>03-14-2007,22:10:56 : InitData failed to open the cluster wrapper
>03-14-2007,22:10:56 : Leaving Init of CDlgLocalChooseCustom
>03-14-2007,22:11:01 : Validating Local Options Data
>03-14-2007,22:11:01 : InitData failed to open the cluster wrapper
>03-14-2007,22:11:01 : InitData failed to open the cluster wrapper
>03-14-2007,22:11:01 : InitData failed to open the cluster wrapper
>03-14-2007,22:11:01 : InitData failed to open the cluster wrapper
>03-14-2007,22:11:11 : Validating service account data
>03-14-2007,22:11:12 : CDlgSSO Pass Function.
>03-14-2007,22:11:12 : After Check for INSTALL_MODE.
>03-14-2007,22:11:12 : DlgChooseDBServer Pass Function.
>03-14-2007,22:12:22 : Validating DlgChooseDBServer data
>03-14-2007,22:12:39 : m_bUseNativeClient = 1
>03-14-2007,22:14:12 : CDlgSSO Pass Function.
>03-14-2007,22:14:12 : After Check for INSTALL_MODE.
>03-14-2007,22:14:19 : Validating service account data
>03-14-2007,22:14:19 : CDlgLocalChooseCustom Pass Function.
>03-14-2007,22:14:19 : After Check for INSTALL_CHOICE.
>03-14-2007,22:14:19 : After Check for INSTALL_TYPE.
>03-14-2007,22:14:19 : After Check for INSTALL_MODE.
>03-14-2007,22:14:19 : CDlgLocalChooseCustom Pass Function.
>03-14-2007,22:14:21 : Validating Local Options Data
>03-14-2007,22:14:21 : InitData failed to open the cluster wrapper
>03-14-2007,22:14:21 : InitData failed to open the cluster wrapper
>03-14-2007,22:14:21 : InitData failed to open the cluster wrapper
>03-14-2007,22:14:21 : InitData failed to open the cluster wrapper
>03-14-2007,22:14:23 : Validating service account data
>03-14-2007,22:14:39 : CDlgSSO Pass Function.
>03-14-2007,22:14:39 : After Check for INSTALL_MODE.
>03-14-2007,22:14:39 : DlgChooseDBServer Pass Function.
>03-14-2007,22:15:32 : Validating DlgChooseDBServer data
>03-14-2007,22:15:32 : m_bUseNativeClient = 1
>03-14-2007,22:15:32 : There is no MSSQL$BKUPEXEC Service
>03-14-2007,22:15:32 : Unable to connect to a SQL Server CORBETS1\BKUPEXEC on
>machine CORBETS1.
>03-14-2007,22:16:39 : Validating DlgChooseDBServer data
>03-14-2007,22:17:01 : Validating DlgChooseDBServer data
>03-14-2007,22:17:01 : m_bUseNativeClient = 1
>03-14-2007,22:17:01 : There is no MSSQL$BKUPEXEC Service
>03-14-2007,22:17:01 : Unable to connect to a SQL Server CORBETS1\BKUPEXEC on
>machine CORBETS1.
>03-14-2007,22:23:17 : Validating DlgChooseDBServer data
>03-14-2007,22:23:17 : Drive C: Required: 956 MB Available: 14445 MB
>03-14-2007,22:23:17 : CDlgChooseTapeDrivers Pass Function.
>03-14-2007,22:23:17 : After Check for INSTALL_MODE.
>03-14-2007,22:23:17 : After Check for INSTALL_CHOICE.
>03-14-2007,22:23:17 : After Check for INSTALL_TYPE.
>03-14-2007,22:23:17 : CDlgSerialNumber Pass Function.
>03-14-2007,22:23:28 : CDlgTSMConfig Pass Function.
>03-14-2007,22:23:28 : After Check for INSTALL_MODE.
>03-14-2007,22:23:28 : CDlgTSMConfig Pass Function.
>03-14-2007,22:23:28 : CDlgCAS Pass Function.
>03-14-2007,22:23:28 : After Check for INSTALL_MODE.
>03-14-2007,22:23:28 : CDlgClone Pass Function.
>03-14-2007,22:23:28 : CDlgClone not passed.
>03-14-2007,22:23:28 : CDlgRemoteChooseCustom Pass Function.
>03-14-2007,22:23:28 : After Check for INSTALL_CHOICE.
>03-14-2007,22:23:28 : Install Summary XML File:
>03-14-2007,22:23:28 :
>C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\{BEA465C8-2923-42C6-9141-BE44739A6A80}\InstallReview.xml
>03-14-2007,22:23:28 : Install Summary XSL File:
>03-14-2007,22:23:28 : E:\WINNT\INSTALL\BE\Bin\InstallSummary.xsl
>03-14-2007,22:23:28 : Install Summary HTML File:
>03-14-2007,22:23:28 :
>C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\{BEA465C8-2923-42C6-9141-BE44739A6A80}\InstallReview.htm
>03-14-2007,22:23:28 : Entering GetSQLAndCASOInformation
>03-14-2007,22:23:28 : Leaving GetSQLAndCASOInformation
>03-14-2007,22:23:28 : MDAC 2.82.1830.0 is installed on this system.
>03-14-2007,22:23:28 : m_bUseNativeClient = 1
>03-14-2007,22:24:00 : Executing BE_InstallMDAC.
>03-14-2007,22:24:00 : MDAC 2.82.1830.0 is installed on this system.
>03-14-2007,22:24:05 : Installing .Net Framework 2.0.
>03-14-2007,22:24:05 : .NET Framework was detected. Skipping install.
>03-14-2007,22:24:06 : Installing Microsoft Report Viewer Redistributable 2005
>03-14-2007,22:24:06 : m_bUseNativeClient = 1
>03-14-2007,22:24:06 : Installing SQL Express 2005 BKUPEXEC instance.
>03-14-2007,22:24:06 : "E:\WINNT\INSTALL\SQLExpress\SQLEXPR.exe" /wait /qn
>/norestart /lv "C:\Program Files\Microsoft SQL Server\90\Setup
>Bootstrap\LOG\Summary.txt" INSTANCENAME=BKUPEXEC INSTALLSQLDIR="C:\Program
>Files\Microsoft SQL Server\" INSTALLSQLDATADIR="C:\Program Files\Microsoft
>SQL Server\" INSTALLSQLSHAREDIR="C:\Program Files\Microsoft SQL Server\"
>ADDLOCAL=SQL_Engine,SQL_Data_Files,SQL_Replicatio n,Client_Components,Connectivity SAPWD=**** DISABLENETWORKPROTOCOLS=0
>03-14-2007,22:25:09 : V-225-53: ERROR: Failed to install SQL Express
>BKUPEXEC instance with error 1923. ***To search for information about this
>error, click here
>03-14-2007,22:25:10 : Please review C:\Program Files\Microsoft SQL
>Server\90\Setup Bootstrap\LOG\Summary.txt for more details.
>03-14-2007,22:25:10 : Failed to install third party products.
>I get the impression I need to reinstall SQL server?
>I installed using the administrator account. Thanks!!!
>
>
>
Thanks for the reply. I have not been able to find anything about that in
the Microsoft KB. Do you have any links you could send me on doing that?
Thanks!
"Sue Hoegemeier" wrote:

> It could be that the SQL Native Client got messed up. Try
> reinstalling the SQL Native Client.
> -Sue
> On Fri, 23 Mar 2007 13:54:28 -0700, Just Guessing
> <JustGuessing@.discussions.microsoft.com> wrote:
>
>
|||I'm having the EXACT same issue. A brand new install of BE 11d SBS Ed
on my client's brand new Win 2k3 SBS R2 server got hosed and jobs in
it refused to run at all. I finally got BE uninstalled by temporarily
disabling SAV and stopping all of its processes after the uninstall
and repair install would not run normally. Now I get the same error
you listed when I try to install BE back onto the server. Please let
me know if you find an answer to this. I'm calling Symantec and
Microsoft later today about this if not.
|||You could try a repair from the Add/Remove Programs - it's
listed under SQL Server Native Client.
Or the installer is sqlncli.msi. It's on the installation
CD.
-Sue
On Tue, 27 Mar 2007 18:12:40 -0700, Just Guessing
<JustGuessing@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Thanks for the reply. I have not been able to find anything about that in
>the Microsoft KB. Do you have any links you could send me on doing that?
>Thanks!
>"Sue Hoegemeier" wrote:
|||Heh.
[vbcol=seagreen]
An extremely common problem for anyone using SQL Server 2005 on Windows 2003
SP1 or later. Search the newsgroups for anything to do with remote
connections to SQL Server, for example, the "ss2005 connection problems"
thread.
And I wouldn't touch Symantec products with a barge pole. Install/uninstall
procedures are convuluted at best, and in most cases they don't play nice
with other 3rd party products.
It's a real shame there is no easy way to create a Virtual PC of a real
server so you can dry-run a product install to see what complications there
are.
sql

Backup Exec and MDAC update

I have a client in a Windows 2000 SP4 network environment
that is using Backup Exec 9.0 with a remote agent for
Exchange and a remote server. They ran the Windows
Updates last Friday and now they are receiving errors on
their backup job when it tries to back up the server that
they updated. The event id in the event viewer is 34323
and reads as follows:
Update to catalog file Catalog index database failed.
Reason: [Microsoft][ODBC SQL Server Driver][SQL Server]
Violation of PRIMARY KEY
constraint 'PK_CatMedia_68487DD7'. Cannot insert dupl
cat_RecordSet:Reopen[]
d:\be\tybee\4367r\becat\server\dll\catme
dia.cpp[753]
I also get the following event id 34338 in conjunction
with the above error:
Backup Exec Alert: Catalog Error
[Server:"servername"]ODBC access error. Possible lost
connection to database or unsuccessful access to catalog
index in the database.
I have submitted this to Veritas forum as well but if
anyone has any ideas, I would appreciate it. The Windows
Update apparently applied KB832483 which is an MDAC
update. I don't see where I can roll this back either.
Thanks. DeannaDeanna,
did you ever figure out a solution to this problem? i'm experiencing
the same thing in the same type of environment.
thank you,
Lenny.
Deanna wrote:
> *I have a client in a Windows 2000 SP4 network environment
> that is using Backup Exec 9.0 with a remote agent for
> Exchange and a remote server. They ran the Windows
> Updates last Friday and now they are receiving errors on
> their backup job when it tries to back up the server that
> they updated. The event id in the event viewer is 34323
> and reads as follows:
> Update to catalog file Catalog index database failed.
> Reason: [Microsoft][ODBC SQL Server Driver][SQL Server]
> Violation of PRIMARY KEY
> constraint 'PK_CatMedia_68487DD7'. Cannot insert dupl
> cat_RecordSet:Reopen[]
> d:\be\tybee\4367r\becat\server\dll\catme
dia.cpp[753]
> I also get the following event id 34338 in conjunction
> with the above error:
> Backup Exec Alert: Catalog Error
> [Server:"servername"]ODBC access error. Possible lost
> connection to database or unsuccessful access to catalog
> index in the database.
> I have submitted this to Veritas forum as well but if
> anyone has any ideas, I would appreciate it. The Windows
> Update apparently applied KB832483 which is an MDAC
> update. I don't see where I can roll this back either.
> Thanks. Deanna *
lennyi
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message422513.html

Backup Error

Hi
I have SQL7 running and is being backed up with ArcServ 9. The server has ArcServ SQL backup client running but the backups keep coming up with errors when trying to backup the contents of the \MSSQL\FTDATA directory. The message is "The process cannot access the file because it is being used by another process.
Is it important to backup the FTDATA directory
cheer
nuvethe arcserve is not able to backup ftdata directory cause its used by sql
server.. it might have mdf and ldf files in it..
ur already using arcserv sql backup client .. why dont u use that to backup
sql database instead of backing up the whole directory. (if u dont have
arcserve open file backup agent this directory will never be backed up)
other alternate is backup the database using sql jobs in to one of the
directory may be d:\backup and backup this directory by arcserve .
Hope this would solve your query ..
Regards,
Mayur
"Nuve" <anonymous@.discussions.microsoft.com> wrote in message
news:8B7872E2-9CBB-4E44-AC44-E1A03E9525AB@.microsoft.com...
> Hi
> I have SQL7 running and is being backed up with ArcServ 9. The server has
ArcServ SQL backup client running but the backups keep coming up with errors
when trying to backup the contents of the \MSSQL\FTDATA directory. The
message is "The process cannot access the file because it is being used by
another process."
> Is it important to backup the FTDATA directory?
> cheers
> nuve|||The ftdata directory does not have any databases in it (.mdf or .ldf files).
This is the location where the full text search indexes and catalogs are
kept.
If Arcserve will not backup open files, then you will have to bring the
databases, or the server down in order to backup that directory... and if
you are using full text search it is important. ( But can be regenerated
from the data in the tables if you must... It would just take a while.)
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Nuve" <anonymous@.discussions.microsoft.com> wrote in message
news:8B7872E2-9CBB-4E44-AC44-E1A03E9525AB@.microsoft.com...
> Hi
> I have SQL7 running and is being backed up with ArcServ 9. The server has
ArcServ SQL backup client running but the backups keep coming up with errors
when trying to backup the contents of the \MSSQL\FTDATA directory. The
message is "The process cannot access the file because it is being used by
another process."
> Is it important to backup the FTDATA directory?
> cheers
> nuve

Backup Error

Hi
I have SQL7 running and is being backed up with ArcServ 9. The server has Ar
cServ SQL backup client running but the backups keep coming up with errors w
hen trying to backup the contents of the \MSSQL\FTDATA directory. The messag
e is "The process cannot ac
cess the file because it is being used by another process."
Is it important to backup the FTDATA directory?
cheers
nuvethe arcserve is not able to backup ftdata directory cause its used by sql
server.. it might have mdf and ldf files in it..
ur already using arcserv sql backup client .. why dont u use that to backup
sql database instead of backing up the whole directory. (if u dont have
arcserve open file backup agent this directory will never be backed up)
other alternate is backup the database using sql jobs in to one of the
directory may be d:\backup and backup this directory by arcserve .
Hope this would solve your query ..
Regards,
Mayur
"Nuve" <anonymous@.discussions.microsoft.com> wrote in message
news:8B7872E2-9CBB-4E44-AC44-E1A03E9525AB@.microsoft.com...
> Hi
> I have SQL7 running and is being backed up with ArcServ 9. The server has
ArcServ SQL backup client running but the backups keep coming up with errors
when trying to backup the contents of the \MSSQL\FTDATA directory. The
message is "The process cannot access the file because it is being used by
another process."
> Is it important to backup the FTDATA directory?
> cheers
> nuve|||The ftdata directory does not have any databases in it (.mdf or .ldf files).
This is the location where the full text search indexes and catalogs are
kept.
If Arcserve will not backup open files, then you will have to bring the
databases, or the server down in order to backup that directory... and if
you are using full text search it is important. ( But can be regenerated
from the data in the tables if you must... It would just take a while.)
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Nuve" <anonymous@.discussions.microsoft.com> wrote in message
news:8B7872E2-9CBB-4E44-AC44-E1A03E9525AB@.microsoft.com...
> Hi
> I have SQL7 running and is being backed up with ArcServ 9. The server has
ArcServ SQL backup client running but the backups keep coming up with errors
when trying to backup the contents of the \MSSQL\FTDATA directory. The
message is "The process cannot access the file because it is being used by
another process."
> Is it important to backup the FTDATA directory?
> cheers
> nuvesql

Backup DB to LocalMachine

alslamo alikom...

hope u all be in a good health...

ok...my problem that i have a client application that designed to adminstrate the DB server using SMO...

now iam trying to backup the desired DB from the DB server which is another machine connected to the same network...

i specified the file name and the DB name....and every thing runs smothly with no exceptions....but no file generated in the client machine....and no exception were thrown....

wish to have a solution soon plz....thx for ur time...

and here is sample code:

public bool BackupDB(string dbName, string backupFilePath)

{

try

{

// Create a new backup and specify what to back up

Backup backup = new Backup();

backup.Action = BackupActionType.Database;

backup.BackupSetDescription = "Backup " + dbName + " database";

backup.BackupSetName = dbName + " Backup";

backup.Database = dbName;

backup.Checksum = true;

backup.ContinueAfterError = true;

backup.Incremental = false;

backup.ExpirationDate = DateTime.Now.AddYears(1);

backup.LogTruncation = BackupTruncateLogType.Truncate;

backup.MediaDescription = "File Backup";

backup.Initialize = true;

backup.Restart = true;

backup.RetainDays = 7;

// Create a new backup device, in this case a file

BackupDeviceItem backupItem = new BackupDeviceItem(backupFilePath, DeviceType.File);

backup.Devices.Add(backupItem);

backup.SqlBackup(sqlServer);

return true;

}

catch(Exception ex)

{

return false;

}

}

thx again.....

alaslamo alikom...(Peace Upon You All) "IsLamic Greeting"

Hi,

SMO is just used to remote administer SQL Server. Defining backups is always relative to the Server. If you want to store the information from the server on the client you will have to define a UNC path which points to a client share or any share where you can copy the backup file to the client from in your application code.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de|||thank you very much.... Mr.Jens K. Suessmeyer

backup cannot make a copy of the database

I have a client who would like to automate the backup. I have used nti
backup for cd's and microsofts backup utility that came with windows
2000. They both state that the files cannot be backed up because the
files are in use.
any Ideas on how to automate the backup' and bypass the exclusive
holdings of the files'Yes. You have to tell SQL Server to backup the database to a file.
Then you can backup the file using whatever backup utility you like.
The command looks like this:
BACKUP DATABASE foo TO DISK = 'x:\foo.bak' WITH INIT
After the command is executed within SQL Server (HINT: you can schedule a
job to run automatically within the SQL Server Agent) the file will be in
the location specified (the root of the X drive in this example).
Keith Kratochvil
"Mike Ryan" <miker@.centralutahcomputers.com> wrote in message
news:%23IVw6PNhGHA.4104@.TK2MSFTNGP04.phx.gbl...
> I have a client who would like to automate the backup. I have used nti
> backup for cd's and microsofts backup utility that came with windows 2000.
> They both state that the files cannot be backed up because the files are
> in use.
> any Ideas on how to automate the backup' and bypass the exclusive
> holdings of the files'
>|||Keith Kratochvil wrote:
> Yes. You have to tell SQL Server to backup the database to a file.
> Then you can backup the file using whatever backup utility you like.
> The command looks like this:
> BACKUP DATABASE foo TO DISK = 'x:\foo.bak' WITH INIT
> After the command is executed within SQL Server (HINT: you can schedule a
> job to run automatically within the SQL Server Agent) the file will be in
> the location specified (the root of the X drive in this example).
>
Additionally you (or your client) should read up on BACKUP and RESTORE
strategy in Books On Line. It sounds like you aren't very familiar with
SQL backups but there are a few concepts you need to be aware of like
Recovery Model (FULL/SIMPLE), difference between FULL Database backup
and log backup and maybe even more important - RESTORE options.
Regards
Steen Schlter Persson
DBA|||Good point!
Knowing how to backup and restore a database is very important. Books
Online is a great resource and contains good information.
Keith Kratochvil
"Steen Persson (DK)" <spe@.REMOVEdatea.dk> wrote in message
news:%23LLSG3XhGHA.3572@.TK2MSFTNGP04.phx.gbl...
> Keith Kratochvil wrote:
> Additionally you (or your client) should read up on BACKUP and RESTORE
> strategy in Books On Line. It sounds like you aren't very familiar with
> SQL backups but there are a few concepts you need to be aware of like
> Recovery Model (FULL/SIMPLE), difference between FULL Database backup and
> log backup and maybe even more important - RESTORE options.
> --
> Regards
> Steen Schlter Persson
> DBA

backup cannot make a copy of the database

I have a client who would like to automate the backup. I have used nti
backup for cd's and microsofts backup utility that came with windows
2000. They both state that the files cannot be backed up because the
files are in use.
any Ideas on how to automate the backup' and bypass the exclusive
holdings of the files'Yes. You have to tell SQL Server to backup the database to a file.
Then you can backup the file using whatever backup utility you like.
The command looks like this:
BACKUP DATABASE foo TO DISK = 'x:\foo.bak' WITH INIT
After the command is executed within SQL Server (HINT: you can schedule a
job to run automatically within the SQL Server Agent) the file will be in
the location specified (the root of the X drive in this example).
Keith Kratochvil
"Mike Ryan" <miker@.centralutahcomputers.com> wrote in message
news:%23IVw6PNhGHA.4104@.TK2MSFTNGP04.phx.gbl...
> I have a client who would like to automate the backup. I have used nti
> backup for cd's and microsofts backup utility that came with windows 2000.
> They both state that the files cannot be backed up because the files are
> in use.
> any Ideas on how to automate the backup' and bypass the exclusive
> holdings of the files'
>|||Keith Kratochvil wrote:
> Yes. You have to tell SQL Server to backup the database to a file.
> Then you can backup the file using whatever backup utility you like.
> The command looks like this:
> BACKUP DATABASE foo TO DISK = 'x:\foo.bak' WITH INIT
> After the command is executed within SQL Server (HINT: you can schedule a
> job to run automatically within the SQL Server Agent) the file will be in
> the location specified (the root of the X drive in this example).
>
Additionally you (or your client) should read up on BACKUP and RESTORE
strategy in Books On Line. It sounds like you aren't very familiar with
SQL backups but there are a few concepts you need to be aware of like
Recovery Model (FULL/SIMPLE), difference between FULL Database backup
and log backup and maybe even more important - RESTORE options.
--
Regards
Steen Schlüter Persson
DBA|||Good point!
Knowing how to backup and restore a database is very important. Books
Online is a great resource and contains good information.
--
Keith Kratochvil
"Steen Persson (DK)" <spe@.REMOVEdatea.dk> wrote in message
news:%23LLSG3XhGHA.3572@.TK2MSFTNGP04.phx.gbl...
> Keith Kratochvil wrote:
>> Yes. You have to tell SQL Server to backup the database to a file.
>> Then you can backup the file using whatever backup utility you like.
>> The command looks like this:
>> BACKUP DATABASE foo TO DISK = 'x:\foo.bak' WITH INIT
>> After the command is executed within SQL Server (HINT: you can schedule a
>> job to run automatically within the SQL Server Agent) the file will be in
>> the location specified (the root of the X drive in this example).
>>
> Additionally you (or your client) should read up on BACKUP and RESTORE
> strategy in Books On Line. It sounds like you aren't very familiar with
> SQL backups but there are a few concepts you need to be aware of like
> Recovery Model (FULL/SIMPLE), difference between FULL Database backup and
> log backup and maybe even more important - RESTORE options.
> --
> Regards
> Steen Schlüter Persson
> DBA

Backup a mirrored database

I have a client who is worried about his backup strategy. He has two servers
and has succesfully setup mirroring. He wants to be able to automatically
backup databaseA before and after the mirror server becomes a principal.
What is the proper procedure to ensure that a backup job doesn't fail when
the roles of principal and mirror are reversed?
For example. On the principal, my client is doing a full backup on sun,
diff monday to sat and tlog backup every hour. On the mirror he has not
scheduled a backup. If the database fails on tuesday, the backup that would
normally run on the principal server will fail. The mirror server (which is
now the principal) currently doesn't have a backup scheduled. What is the
best practice?
Thanks for any help.
Dan
Thanks for you help.
"Tibor Karaszi" wrote:

> Create the same job on both servers, both jobs are always enabled, and in the job you use the
> sys.database_mirroring catalog view it see if the database is principal or mirror.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Dan Wood" <DanWood@.discussions.microsoft.com> wrote in message
> news:F9A439EF-A131-450E-A032-12382AE9C782@.microsoft.com...
>

Backup a mirrored database

I have a client who is worried about his backup strategy. He has two server
s
and has succesfully setup mirroring. He wants to be able to automatically
backup databaseA before and after the mirror server becomes a principal.
What is the proper procedure to ensure that a backup job doesn't fail when
the roles of principal and mirror are reversed?
For example. On the principal, my client is doing a full backup on sun,
diff monday to sat and tlog backup every hour. On the mirror he has not
scheduled a backup. If the database fails on tuesday, the backup that would
normally run on the principal server will fail. The mirror server (which is
now the principal) currently doesn't have a backup scheduled. What is the
best practice?
Thanks for any help.
DanCreate the same job on both servers, both jobs are always enabled, and in th
e job you use the
sys.database_mirroring catalog view it see if the database is principal or m
irror.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Dan Wood" <DanWood@.discussions.microsoft.com> wrote in message
news:F9A439EF-A131-450E-A032-12382AE9C782@.microsoft.com...
>I have a client who is worried about his backup strategy. He has two serve
rs
> and has succesfully setup mirroring. He wants to be able to automatically
> backup databaseA before and after the mirror server becomes a principal.
> What is the proper procedure to ensure that a backup job doesn't fail when
> the roles of principal and mirror are reversed?
> For example. On the principal, my client is doing a full backup on sun,
> diff monday to sat and tlog backup every hour. On the mirror he has not
> scheduled a backup. If the database fails on tuesday, the backup that wou
ld
> normally run on the principal server will fail. The mirror server (which
is
> now the principal) currently doesn't have a backup scheduled. What is the
> best practice?
> Thanks for any help.
> Dan|||Thanks for you help.
"Tibor Karaszi" wrote:

> Create the same job on both servers, both jobs are always enabled, and in
the job you use the
> sys.database_mirroring catalog view it see if the database is principal or
mirror.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Dan Wood" <DanWood@.discussions.microsoft.com> wrote in message
> news:F9A439EF-A131-450E-A032-12382AE9C782@.microsoft.com...
>

Backup a mirrored database

I have a client who is worried about his backup strategy. He has two servers
and has succesfully setup mirroring. He wants to be able to automatically
backup databaseA before and after the mirror server becomes a principal.
What is the proper procedure to ensure that a backup job doesn't fail when
the roles of principal and mirror are reversed?
For example. On the principal, my client is doing a full backup on sun,
diff monday to sat and tlog backup every hour. On the mirror he has not
scheduled a backup. If the database fails on tuesday, the backup that would
normally run on the principal server will fail. The mirror server (which is
now the principal) currently doesn't have a backup scheduled. What is the
best practice?
Thanks for any help.
DanCreate the same job on both servers, both jobs are always enabled, and in the job you use the
sys.database_mirroring catalog view it see if the database is principal or mirror.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Dan Wood" <DanWood@.discussions.microsoft.com> wrote in message
news:F9A439EF-A131-450E-A032-12382AE9C782@.microsoft.com...
>I have a client who is worried about his backup strategy. He has two servers
> and has succesfully setup mirroring. He wants to be able to automatically
> backup databaseA before and after the mirror server becomes a principal.
> What is the proper procedure to ensure that a backup job doesn't fail when
> the roles of principal and mirror are reversed?
> For example. On the principal, my client is doing a full backup on sun,
> diff monday to sat and tlog backup every hour. On the mirror he has not
> scheduled a backup. If the database fails on tuesday, the backup that would
> normally run on the principal server will fail. The mirror server (which is
> now the principal) currently doesn't have a backup scheduled. What is the
> best practice?
> Thanks for any help.
> Dan|||Thanks for you help.
"Tibor Karaszi" wrote:
> Create the same job on both servers, both jobs are always enabled, and in the job you use the
> sys.database_mirroring catalog view it see if the database is principal or mirror.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Dan Wood" <DanWood@.discussions.microsoft.com> wrote in message
> news:F9A439EF-A131-450E-A032-12382AE9C782@.microsoft.com...
> >I have a client who is worried about his backup strategy. He has two servers
> > and has succesfully setup mirroring. He wants to be able to automatically
> > backup databaseA before and after the mirror server becomes a principal.
> > What is the proper procedure to ensure that a backup job doesn't fail when
> > the roles of principal and mirror are reversed?
> >
> > For example. On the principal, my client is doing a full backup on sun,
> > diff monday to sat and tlog backup every hour. On the mirror he has not
> > scheduled a backup. If the database fails on tuesday, the backup that would
> > normally run on the principal server will fail. The mirror server (which is
> > now the principal) currently doesn't have a backup scheduled. What is the
> > best practice?
> >
> > Thanks for any help.
> >
> > Dan
>