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.Restoring 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.
Backup 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.
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
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.
