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. CheersUpdate on Microsoft SharePoint platform support (Online and Server)
Microsoft continues to evolve the SharePoint collaboration platform. SharePoint is now available both online as part of the Microsoft Office 365 service and as a standalone server. For Microsoft Office 365 Veritas recently introduced Veritas SaaS Backup with support for Microsoft Office 365, Google G-Suite and SalesForce. Veritas SaaS Backup support for Microsoft Office 365 includes support for Email, SharePoint and OneDrive with more information available athttps://www.veritas.com/product/backup-and-recovery/saas-backup/preview. Microsoft SharePoint platform continues to be an important part of Veritas Backup Exec customer’s on-premises environments. Microsoft SharePoint 2016 is the latest server-version of the platform and continues to be on our radar. Please keep monitoring this forum for additional information and latest updates on Microsoft SharePoint platform support. BackupMikko
Sharepoint backup fails majority of time BE 2014
Hi guys This is my first post on here so please be gentle :) I'm getting a lot of backups failing with the following. The odd one does succeed though which confuses things a bit. The job itself is running on a web box but also looking at a DB box which is what it's referring to below (I'm new to Backup Exec and backups in general tbh). It mentions the remote agent on the DB box and I have checked it's installed which it is. However I've seen a lot of instances of this around the time the job fails: . Do you think the crashes might be the cause or a symptom of another issue? Can anyone help get these backups working again please? Any help would be hugely appreciated. Cheers :)Missing List items from Sharepoint Restore
Hello all, I've been tasked with backing up/restoring data from a sharepoint 2013 farm and having issues with seeing the list items on restore. I've added the RAWS to the SQL box(2012 SQL/2008 server) and to the sharepoint box(2012 R2 server) and was able to add the farm with out issue and I can do a backup of the farm without any errors. The system logon account has DB_Owner to the DBs on SQL and has all admin rights under sharepoint. I've even tested with another account and get the same results. Also Instant GRT is enabled. I did test this on a sandbox sharepoint but the main difference is, SQL is installed on the same box as sharepoint. I was able to backup the farm and see all list items and even restore single list items. I've talked with support and they where no help at all. Would anyone have any ideas on what I'm missing? If I've missed any information please let me know I should be able to provide. ThanksSharepoint Farm Client Selection
Hi, We have a large Sharepoint Farm with 8 nodes (2 SQL, 2 Front End Web, 2 app Server, 2 Workflow Manager, 2 Office Web Apps), we have installed and configured the netbackup client on all of the nodes. In the Administration guide, it is suggested to create 3 separate policies ( 1 for GRT, 1 for Full Farm, 1 for Disaster Recovery), but the clarification we need is which client to specify on each of those policies, i only found by looking in the community that for the Full Farm only Front End Web should be specified (should we put the 2 of them in case of one down ?), and how about the other Policy for GRT, which client should be specified ? ( i guess that for DR, we should backup all of the clients.) Thank you
SQL or Sharepoint Agents?
Issue started when SQL DBA reported differential restore failure due to break in SQL LSN (SQL Message<3136>The differential backup cannot be restored because the database has not been restored to the correct earlier state ). The full restore is succesful. here's our scenario we are taking sharepoint backup, and this database is part of the farm. so we are backing up the databases in the sharepoint backups. also we are taking backup of databases from sql server, here's the conflict. Can anyone suggest best practices: 1.Can you backup sharepoint without having it to backup DB's? 2.There are drawbacks in using either SQL or Sharepoint agents. Using both causes restore issues. What are others using in their environment?