Force NBSERVER setting in an MSSQL Intelligent policy batch file
Hello I have a new Netbackup 5250 appliance that is taking backups for a Production and Lab environment. The Management Interface of the Appliance is configured in the Production environment. The Appliance has different NICs configured on the Prod and Lab networks for backup payload data. I have a problem with Lab MSSQL intelligent policies that wants to use the Production Management Interface for backups. Since the Lab network does not have access to the Prod network, the Lab MSSQL client cannot be backed up using the Management Interface of the Appliance. I was able to grab the .bch file that is auto-generated on the client to see the NBSERVER setting and it is the Appliance Prod hostname. So my question is, is it possible to force/override the NBSERVER setting in the autogenerated .bch file for Intelligent MSSQL Policies? The same client is able to be backed-up in a regular Windows policy since it is using the right hostname of the Appliance. Example in the auto-generated .bch file: Instead of, NBSERVER = "Prod5250hostname" (this is the autogenerated config right now) I want NBSERVER = "Lab5250hostname" (same appliance but different network interface) I could create a DNS entry in the Lab DNS server to point to the IP of the Appliance Lab interface, but I would like to avoid that. Thank you.981Views0likes3CommentsRestoring PaaS Assets with NetBackup 10
If you haven’t moved some of your workloads to cloud, you’re probably thinking about it right now. The cloud offers many benefits—cost savings, security, flexibility, mobility, insight, increased collaboration, quality control, disaster recovery (DR), loss prevention, automatic software updates, competitive edge, sustainability, and more. The flexibility and power of the cloud can also come with some confusion about what services are needed, however. Terms like software as a service (SaaS), infrastructure as a service (IaaS), and platform as a service (PaaS) can be confusing and may lead to more expense and support than needed. Let’s assume you need something between SaaS and IaaS—a service that includes the servers, storage, and networking layers so you can focus more time and effort on application development and deployment. PaaS eliminates the need to deploy servers, networking, and virtualization, presenting an application layer that is ready for development. Want to build a Microsoft Azure SQL Server instance without the headache of building the environment yourself? This scenario is where PaaS comes in. The introduction of the cloud has opened the doors to many opportunities, including as a means of eliminating the traditional data center. But what about backups? It’s true cloud providers do provide backup utilities, and PaaS applications may also have their own built-in backup utilities. However, NetBackup provides unparalleled next-generation data protection by minimizing costs and complexity and ensuring greater business continuity with a solution that unifies data protection across the entire enterprise. If you’re using multiple applications in your PaaS environment, having a single solution like NetBackup to orchestrate backup and recovery is both efficient and cost-effective. NetBackup has the ability to connect and back up cloud resources directly from its web UI, making it the perfect partner to your PaaS infrastructure. NetBackup also discovers and reports on the backup status of your PaaS resources and helps manage recovery using the vendor’s recovery tools. Using NetBackup PaaS to Restore Azure SQL Databases Azure SQL Database is a fully managed PaaS database engine that handles most of the database management functions. Azure SQL Database is always running on the latest stable version of the SQL Server database engine and patched operating system (OS) with 99.99 percent availability. The PaaS capabilities built into Azure SQL Database let you focus on the domain-specific database administration and optimization activities that are critical for your business. NetBackup combines the capabilities of Azure PaaS with the ease of use, cost savings, and ability to store your data wherever you want it. You can use NetBackup to protect and recover PaaS Azure SQL Database in four easy steps: PaaS Azure SQL Database backs up data NetBackup discovers the PaaS assets and Azure-created backups Restore is initiated from within the cloud section in NetBackup Restore is successful NetBackup is not only your trusted on-premises backup suite, it’s also your one-stop choice to back up all your cloud resources with simple tools that accomplish complex tasks. Whether your cloud goals include SaaS, IaaS, or PaaS, NetBackup enterprise tools make backing up your data easier and will help lower your organization’s long-term storage costs as well.1.1KViews2likes1CommentBackup timestamp not getting updated in SQL Studio for VMware SQL aware backups
Hello, We are taking a SQL aware VMware snapshot backup for a SQL VM and the backups/restores are all runnign fine. But the timestamp for the backup date in the SQL studio is not getting updated. It is still reflecting an old date when it was backed up via Avamar which is stopped now as we moved to netbackup and used snapshot backups. Has anyone any idea how to fix this? How can NBU inform SQL that the DB has been backed up and it can update the timestamp? NBU version - 8.3 SQL version - Microsoft SQL Server Enterprise 2014 DBA is running the below query to fetch the backup timestamp: SELECT CONVERT(CHAR(100), SERVERPROPERTY('Servername')) AS Server, msdb.dbo.backupset.database_name, MAX(msdb.dbo.backupset.backup_finish_date) AS last_db_backup_date FROM msdb.dbo.backupmediafamily INNER JOIN msdb.dbo.backupset ON msdb.dbo.backupmediafamily.media_set_id = msdb.dbo.backupset.media_set_id WHERE msdb..backupset.type = 'D' GROUP BY msdb.dbo.backupset.database_name ORDER BY msdb.dbo.backupset.database_name and it doesnt provide the updated backup time for the backup taken by Netbackup.624Views0likes1CommentSharePoint 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.3KViews0likes2CommentsSQL error in Netbackup Opscenter 8.3
Hello All, We use some custom reporting scripts in our netbackup infra created by Veritas professional services few years back. We were using NBU 7.7 at that time. Over the years we have upgraded to 8, 8.1, 8.2 and we didnt face any issues with the reporting. Today, we upgraded to netbackup to 8.3 including opscenter and now the scripts are no longer running. We are getting error as below. Wed Nov 4 09:20:01 2020 [REPORT_CONFIG] return=dbisql ERROR: Cannot find the language resource file (dblgen17.res). Wed Nov 4 09:20:01 2020 [REPORT_CREATION] problem in SQL I searched for the file - dblgen17.res and it is present in the same location. I assumed may be the version is new for 8.3. So replaced it with the old version in 8.2 but still the same error. Has anyone faced this issue or any idea how to fix it?Solved1.3KViews0likes1CommentSharePoint 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 ThanksSolved12KViews1like4CommentsInstalling 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.5KViews0likes2Comments