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.Solved1.3KViews0likes2CommentsSharePoint 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. Cheers989Views0likes3CommentsBackup 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 ThanksSolved13KViews1like4CommentsInstalling 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.1.5KViews0likes2Commentsservice 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?1.3KViews0likes2CommentsSQL - query multiple archive-databases
Hi all I'm a bloody beginner with sql-code. What I want to know is to the amount of archived data for last night (22:00-06:00) and the night before. Both for two different archives. My code is the following: (SELECT "date" = '2018-02-17', "MB mailarch1" = sum (originalsize)/1024/1024,"MB mailarch2"='' from EVVSVSArchiveMail1.dbo.Saveset with (nolock) inner join EVVSVSArchiveMail1.dbo.savesetproperty with (nolock) ON saveset.savesetidentity = savesetproperty.savesetidentity WHERE archiveddate > '2018-02-17 20:00' and archiveddate < '2018-02-18 06:00' union SELECT "date" = '2018-02-18',"MB (orig) mailarch1" = sum (originalsize)/1024/1024,"MB (orig) mailarch2"='' from EVVSVSArchiveMail1.dbo.Saveset with (nolock) inner join EVVSVSArchiveMail1.dbo.savesetproperty with (nolock) ON saveset.savesetidentity = savesetproperty.savesetidentity WHERE archiveddate > '2018-02-18 20:00' and archiveddate < '2018-02-19 06:00') UNION ALL (SELECT "date" = '2018-02-17',"MB (orig) mailarch1"='',"MB mailarch2" = sum (originalsize)/1024/1024 from EVVSVSArchiveMail2.dbo.saveset with (nolock) inner join EVVSVSArchiveMail2.dbo.savesetproperty with (nolock) ON saveset.savesetidentity = savesetproperty.savesetidentity WHERE archiveddate > '2018-02-17 20:00' and archiveddate < '2018-02-18 06:00' union SELECT "date" = '2018-02-18',"MB (orig) mailarch1"='',"MB mailarch2" = sum (originalsize)/1024/1024 from EVVSVSArchiveMail2.dbo.saveset with (nolock) inner join EVVSVSArchiveMail2.dbo.savesetproperty with (nolock) ON saveset.savesetidentity = savesetproperty.savesetidentity WHERE archiveddate > '2018-02-18 20:00' and archiveddate < '2018-02-19 06:00') The output I want is a table like: date MB mailarchive1 MB mailarchive2 2018-02-17 8556 9234 2018-02-18 9432 9834 I am sure there is a much more elegant and straightforward query, but I am not able to improve it. Has anyone of you scripted a similar thing and could let me know? Thanks a lot, MikeSolved1.6KViews0likes4CommentsSQL Wizard is unable to detect Service group
Hello Everyone, We have 2 nodes Veritas Stotage Foundastion HA 6.1 cluster. It contains one SQL Server 2012 service group. I try to modify this service group using SQL Server agent configuration wizard, but on the first step wizard is unable to detect existing SQL service group and offers just to create new one (screenshot is attached). I've tried to check wizard log but it doesn't contain any errors or warnings. Please help! P.S. OS: Windows Server 2012 VSF with HA 6.11.6KViews0likes1CommentSeeking SQL query returning per-user count of (non-legal hold) items to be expired from EV
Hi all, Long-time listener, first-time caller. Our customer is looking to turn on expiry in their environment for the first time. They use EV in a non-traditional manner, so of 32MM+ items, upwards of 2/3 (maybe even 9/10) are on legal hold via DA. Effectively the only items not on legal hold are from cases that were active but have since been closed, removing the holds. Many of the holds overlap, as well. We have successfully tested expiry in a near-duplicate QA EV environment and removed about 2MM items without incident. After presenting that result, the customer's IT team has requested that we add an additional step to present to legal before advancing into Production. They'd like as granular a report as possible of what will be removed so they can confirm the data to be expired should be expired. Criteria are below: A simple count of items to be removed per user would be the bare minimum. A better solution would include retention categories The perfect query would provide: Granular item-by-item reporting (for at least some users) A means by which at least a subset of physical savesets could be located and presented After digging around the forums for quite some time, I've tested versions of JesusWept3's query (which looks like it should do exactly what I need) but: In my lab (which does not have DA) I need to remove any references to the holdsaveset table or else it returns no results I'm considering adding DA to my lab to test it, but I have little doubt that JesusWept3 knows his stuff. I'm confident that it will work. In the QA environment, looking at just one of three vault stores, I stopped it after about 36 hours of execution, made some modifications and was unable to make it work more efficiently. I started it again and it has still not completed running after another hours. Even if it does conclude after, say, 48 hours, this is not likely to be an acceptable option to management. Please let me know if you have any tweaks, experience or advice to offer6KViews0likes10CommentsBacking 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.000108901Solved1.2KViews0likes1Comment