LINGSAEED
asked on
Veritas 10d
i am having veritas 10d and when i am defining my backup in selection i select my sqlserver data base through d:\sqldata and when i am running my backup i am getting this error
"
Unable to attach to CJDC01.
V-79-57344-33932 - Unable to attach to a resource. Make sure that all selected resources exist and are online, and then try again.
Unable to attach to CJDC01\SBSMONITORING.
V-79-57344-33932 - Unable to attach to a resource. Make sure that all selected resources exist and are online, and then try again.
"
any help
thanks
"
Unable to attach to CJDC01.
V-79-57344-33932 - Unable to attach to a resource. Make sure that all selected resources exist and are online, and then try again.
Unable to attach to CJDC01\SBSMONITORING.
V-79-57344-33932 - Unable to attach to a resource. Make sure that all selected resources exist and are online, and then try again.
"
any help
thanks
You need to have the SQL agent installed and also the remote agent. If you don't have these veritas agents installed you would have to stop the SQL service before making the backup, or use your SQL management software to make dumps of the database and then backup these dumps.
ASKER
how i know i have a sql agent and what is sql agent becuase its was working before now its not working.
thanks
thanks
Open your services, the backupexec agents should be listed there. If you have been using a trial backupexec version, then all the agentsw were originaly active. After the testperiod expires those agents also expire.
ASKER
These are services are there.
Backup Exec Device & Media Service
Backup Exec Job Engine
Backup Exec Agent Browser
Backup Exec Remote Agent for Windows Servers
Backup Exec Server
SQLSERVERAGENT
thanks
Backup Exec Device & Media Service
Backup Exec Job Engine
Backup Exec Agent Browser
Backup Exec Remote Agent for Windows Servers
Backup Exec Server
SQLSERVERAGENT
thanks
And are they running?
ASKER
Yes they are running
Maybe a reboot is called for.
If a reboot does not work....
a) reinstall BE on top of itself
b) go to the website and check out updates and patches.
a) reinstall BE on top of itself
b) go to the website and check out updates and patches.
ASKER
yes i reboot several time. what do mean by instal BE on top of iteslf . you mean reinstall BE veritas software.
Are there any eventlogs and BE logs which may shed some light?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
For the SBSMONITORING instance, http://seer.support.veritas.com/docs/274303.htm
For the vantiTest instance - your useful data - BackupExec is meant to skip the raw .mdf and .log files if the databases are selected under the SQL option. It will stop the error message if you deselect the ..\MSSQL\DATA folder but then you have to verify that that the databases have been backed up by doing a restore of the SQL data to a test database.
I am a bit concerned that it used to backup the (normally disabled) SBSMONITORING instance but doesn't do that now, are you sure it used to work on this box under SBS? Do you have the vantiTest database properly selected under the SQL options, the failure to automatically exclude the raw files may be down to it not being able to interrogate the database properties properly to find out where the raw files are, the account used by BE has to have sa type permission since a regular SQL user account may not have full rights to these things.
For the vantiTest instance - your useful data - BackupExec is meant to skip the raw .mdf and .log files if the databases are selected under the SQL option. It will stop the error message if you deselect the ..\MSSQL\DATA folder but then you have to verify that that the databases have been backed up by doing a restore of the SQL data to a test database.
I am a bit concerned that it used to backup the (normally disabled) SBSMONITORING instance but doesn't do that now, are you sure it used to work on this box under SBS? Do you have the vantiTest database properly selected under the SQL options, the failure to automatically exclude the raw files may be down to it not being able to interrogate the database properties properly to find out where the raw files are, the account used by BE has to have sa type permission since a regular SQL user account may not have full rights to these things.
ASKER
Unable to open the item D:\Program Files\Microsoft SQL Server\MSSQL\Data\AvantiTe
Unable to open the item D:\Program Files\Microsoft SQL Server\MSSQL\Data\AvantiTe
Unable to open the item D:\Program Files\Microsoft SQL Server\MSSQL\Data\CDAvanti
any comments
very urgent