sql

119 Topics

Backup Exec 21.4 - change SQL version, unable to create SDR iso
Backup exec 21.4 runs on SQL 2014 express 32bit. Server 2025. Is there a way to create a new database on SQL express 64bit? I installed SQL express 2022 64bit but I think the database is still on SQL 2014 express 32bit. ADK is installed but Backup exec doesn't see it so I am unable to create a SDR iso. Thanks
Susan235680
2 months ago Place Backup Exec
19Views
0likes
0Comments
SharePoint credential failure with SQL Availability Group
We are trying to use Backup Exec 21.1 to protect a SharePoint 2016 farm that is sitting on top of a SQL 2016 Availability Group. I understand the capability to back up availability groups is new in this version. BE discovers the farm topology no problem and adds all the component servers and the database listener without issue. I can back up all these servers in the normal way as just a bunch of servers, and likewise can back up databases from the listener without issue. However when I create a job to back up the whole thing as SharePoint the credentials fail on certain components - mostly the configuration and content databases - where it works for other parts of the SharePoint farm. These are the same credentials that work successfully when I back them up as just a bunch of servers and databases. I have spent the better part of a month meticulously reviewing the permissions of our BE service account within SharePoint, within SQL, on the farm servers, and the security policy on all the farm servers. I am fairly confident it has all the right permissions. However I believe there may be a certificate issue. I say this because I have installed SQL Server Management Studio on the backup server and it produces the following error when I try to connect to the listener using the BE service account: "A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - The certificate chain was issued by an authority that is not trusted.) (Microsoft SQL Server)" Does BE attempt to make a secure connection to the database listener when it backs up SharePoint? If so, then I believe it may be encountering a similar error when it tries to connect using the same account. In the case of SSMS there is an option to force trust of the server certificate and the connection succeeds when I choose this, but I am not aware of a similar option in BE. Trust is established between BE and both nodes of the SQL cluster, however it is not possible to establish trust with the listener because it's not a real server, just cname of whichever node holds the primary role. If BE uses a certificate I am not sure how to view it or verify what name might be on it. Am I on the right path? How do I troubleshoot the communication between BE and the listener, beyond just succeed/fail of the credentials? Thanks.
Solved
mhale
5 years ago Place Backup Exec
1.4KViews
0likes
2Comments
SharePoint SQL Cluster
Hello, I'm currently trialing Veritas and am having issues getting it to backup our Sharepoint DB's as they are in a cluster. It says that before you can backup or restore, you must install the appropriate Backup Exec. Both servers in the are setup and have the client installed. It is looking for the cluster name. I have configured the sqlcli on the Veritas server for the cluster name but still no luck. Can anyone assist as to have I can get the backups to see the cluster name? If I cannot get Veritas to work with our Sharepoint setup I will have to look at another product. Cheers
Carmen_Payne
6 years ago Place Backup Exec
1KViews
0likes
3Comments
Backup Exec log files 38GB
We've had an issue with our server due to lack of free space. We've examined the contents of the drive and "C:\Program Files\Symantec\Backup Exec\Logs\" is taking up 38GB of space. Can you tell me why it would take up this much space please? More importantly how do i cap it at say 10GB? We are using Backup Exec 2010 R3 on a windows 2007 sbs server. All our backups are backup to disk folders on removable drives and we backup also backup exchange and SQL. Thanks, your help is appreciated Thanks
Solved
resolver101
6 years ago Place Backup Exec
13KViews
1like
4Comments
Installing 20.4 unable to authenticate with the user and password
Veritas support has been absymal on this. I have been speaking with several technicians for the past two weeks and none of them have provided any resolutions. I am trying to update Backup Exec 16 to 20.4 as standalone. The serever passes most of the enviroment checks successfully but has a warning that the current user does not have permissions to log on to SQL server instances that have a designation of '**' even though the account i am logged in tohas full permissions to the SQL database, can act as part of the OS, log in as service account, and create tokens. The Backup Exec SQL Upgrade Check will randomly fail. sometimes it does, soemtimes it doesnt. I'm unsure why because the SQL instance is within the compatibility range at 2008 R2S2 and cannot be upgraded. If i make it to the start instal screen, it will refuse the domain credentials we used to set up the backup server initially, suceed with local adin credentials, run for 30 minutes then fail again saying it was unable to authenticate with the user and password provided, which have been tested in RDP. Please someone help.
yrabinovich1
7 years ago Place Backup Exec
1.5KViews
0likes
2Comments
service account for mssql
how do you use a diffrent user account for sql vs the rest of the backup? the ui shows the sql is using the servers logon account the question, i am unsure how to ungrey out the mssql option to choose an alternate account. I have also attempted to change the account in the actual backup configuration but that does not seem to work either. anyone have thoughts?
seeker_87
7 years ago Place Backup Exec
1.3KViews
0likes
2Comments
Backing up SQL databases and transaction logs Clarification needed.
I am trying to make sense of the following statement from a tech article which I will be providing a link below and I am not sure if I am understanding the context properly, "Additionally, Backup Exec runs a full backup when you select the Automatic or Log backup methods if a full backup was not previously run on the database." Does that statement mean that If I have selected the following option, "Log - Back up and truncate transaction log" without scheduling a full backup to run that day it will automatically run a full backup then backup the log and trucate them every day that it is schedule for? or is it referring to only the first full backup? The reason why I am asking is the first job backup method is set by default to do a full backup of the entire database. Then the second job you can specify to do one of 9 options from log to copy, full etc.. Lastly by selecting to do a log backup and truncation is it suppose to show up as incremental backup as the Job Type under the for the selected server under backup and restore as seen below? https://www.veritas.com/support/en_US/article.000108901
Solved
Vdang
9 years ago Place Backup Exec
1.2KViews
0likes
1Comment
SQL Query for Backup Exec 12 to check media for Report
I need to have the ability to query SQL on Backup Exec 2014 so that I can check that media Offline Tape Media. I have found tables [dbo].[Media]. Does anyone know of a way to find Offline Media Types ? Or I use the wrong table?
dukedizel
9 years ago Place Backup Exec
615Views
0likes
1Comment
SQL 2012 Instance Backup exec Agent Installation By: dukedizel
Hi all! I try to install BE agent to SQL 2012 Instance but i receive error. Final error: 0xe00086cc - Access Denied. Ensure that you have the appropriate credentials to access the remote computer. If this error occurred for another reason, you can find more information at the following URL: http://www.symantec.com/docs/HOWTO80805 Final error category: Job Errors Completed status: Failed I have two "identical" the SQL 2012 Instance SHV-vdbc02 and srvdbc01 BE not see shv-vdbc02 as SQL Instance. Firewall is off. What's i must check on shv-vdbc02 ?
Solved
dukedizel
10 years ago Place Backup Exec
3.2KViews
0likes
5Comments
SQL Backup Failing
My Backup fails everyday with this issue Backup- \MSSQLSERVERV-79-57344-863 - The SQL Server backup interface has reported a problem. Further details can be found in the job log. Restarting the SQL Server service or the server may correct the problem. V-79-57344-863 - The SQL Server backup interface has reported a problem. Further details can be found in the job log. Restarting the SQL Server service or the server may correct the problem. Backup - Snapshot Technology: Initialization failure on: "System?State". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS). V-79-10000-11233 - VSS Snapshot error. A Microsoft Volume Shadow Copy Service (VSS) snapshot is already running on the target computer. Only one snapshot can run at a time. Try running the job later. No other backups are running nothing is using the VSS writers. I check wiht vssadmin list writers they are fine and I'll reboot the server run backup still have this issue. Any ideas?
OmegaDuece
10 years ago Place Backup Exec
1.9KViews
0likes
4Comments