Recent Discussions
Netbackup Catalog backup growing
Hi, in our environment we have a primary server with a catalog backup stabilized about 650Gb size with 2 week retention. By few days it's growing and backup passed from 650GB to 930Gb and now to 1,1Tb by day. No particular actions performed on primary server, on the contrary we dismissed some client. How can i check, why the catalog backup growing up very fast in last days? Any suggestion is very appreciated. Thanks,
Need an advise on Backup strategy for long term retention
Hi Team, I'm relatively new to NetBackup and Need advise on the back strategy for long term retention backups. Below is our environment: We have 2 Sites - SITE A and SITE B. Each Site is having One master(physical server), 2 media servers(physical servers) and Data Domain 9410. We are planning to install NetBackup version 10.4. Our requirement is as below : -> backing up to Data Domain with 1 month retention -> replicate the data to Site B from Site A. -> Duplicate to Azure Blob store for long term retention(13 months retention). This should happen monthly once. We want the data to be moved to cloud through media server. We don't want this at DD level. So my question is what backup strategy(backup method) we need to follow in order to move the last 1 month data to Azure Blob store once in a month? We have VADP backups, SQL backups, NDMP Backups and file level backups. We want to move the data cloud monthly once and that copy should have last 1 month. Please suggest. Also, please suggest any other better ways to achieve this. We don't have Cloud Tier license at Data Domain level, so that is not an option.
Did a catalogue restore, but seem to have missing information.
So I did a catalogue restore (full one) which honestly I felt went sideways. It said it finished partially but the only errors I could find were IOC_CHFLAG_SET errors. I had my profiles, on the file system the DB was backup to it's 375GB range. So I assumed all the data was loaded. When I login to the JavaGUI, ALL my volume pools are gone ALL my tapes are in 1 pool now. Is this normal? Because on the old system We had volume pools for each job which had tapes in it (We don't backup daily, we archive data so it goes on tape once and that's it so I believe that's why they used volume pools when they set it up ages ago). Either way. It just feels to me like I'm missing Data, and I'm not sure what to do now. I've opened a ticket but I'm running out of hours I can say "it's good let's test" vs "we need to roll back" (Let's just say it's been a long week getting to this point).
systemctl status netbackup show failed
Dear All, systemctl status netbackup show failed but netbackup services are running as expected and able to login to GUI [root@sxxxxx var]# systemctl status netbackup ● netbackup.service - LSB: NetBackup Loaded: loaded (/etc/rc.d/init.d/netbackup; generated) Active: failed (Result: exit-code) since Thu 2024-10-10 15:08:24 CEST; 22h ago Docs: man:systemd-sysv-generator(8) Process: 245515 ExecStart=/etc/rc.d/init.d/netbackup start (code=exited, status=2) Tasks: 0 (limit: 1234376) Memory: 21.5M CGroup: /system.slice/netbackup.service Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.Image Sharing Support for MSDP!
Hi Friends, Here's some more cool stuff from 10.5!! If you're interested in trying Image Sharing or setting up a Cloud Recovery Server it's easier than ever! Check out the whitepaper here. Pre NetBackup 10.4.1 Image Sharing is only supported as an all-in-one Primary server. While this works fine, Veritas has added the capability to attach an Image Sharing Media Server to an existing NetBackup Primary domain. This helps negate the extra work of creating a new Primary domain and can utilize existing resources at alternate sites. This allows for many different configurations where customers could add a new image sharing server to their backup domain or create a new image sharing server domain where they have multiple image sharing servers configured. This newly added support is specific to Bring-Your-Own (BYO) environments as image sharing is not supported in distributed environments such as CloudScale, and the existing image sharing functionality will also work on a separate media server. How to Use An image sharing Cloud Recovery Server Media Server can be deployed in two ways. All in One which is covered in the In-Cloud Data Recovery with Veritas Alta™ Recovery Vault guide. Separate Media / Cloud Recovery Server (CRS) which is covered in this technical brief. For Separate Media / CRS download the necessary NetBackup binaries for your new server and install the new Media / CRS server. Binaries can be found here. When installing the new Media / CRS server, connect to an existing NetBackup domain as normally done during a Media server installation. After adding the Media / CRS server, check the Host > Host Properties tab in the Primary WebUI. The new Media / CRS server is not available to perform image sharing. Navigate to Storage > Disk Storage. Ensure the Storage Servers tab is selected and click on Configure Disk Storage. Select Media Server Deduplication Pool (MSDP) for image sharing and select Start. Next select the Media / CRS server for both the Media and Storage servers. Enter in the credentials of the user that runs the NetBackup processes on the Primary server. Enter in the storage path the Media / CRS server will use. Other options can be used but have been left default. Review and create the new MSDP server for image sharing. Use the In-Cloud Data Recovery with Veritas Alta™ Recovery Vault guide to import your cloud backups. Isn't that cool?!Cross Provider Restore - Azure to AWS and Vice Versa!!
Hi Friends, Happy NetBackup 10.5 GA Day!! I've got a ton of new features I want to share with you, but this one is SUPER cool! At Veritas, we know that your enterprise cloud environments are heterogenous and need the ability to backup and restore your enterprise cloud virtual machines easily from AWS to Azure and vice versa. Veritas NetBackup continues to un-complicate the cloud by now offering cross cloud provider restore capabilities. Check out the paper here. Requirements Veritas NetBackup Snapshot Manager with connection credentials for your AWS and Azure environments. Note: A backup from snapshot copy must be present to restore the virtual machine to an alternate cloud provider. Cloud Snapshots can continue to be used for restores at the same cloud provider. How to Use – Azure to AWS After a backup has been completed of a cloud virtual machine, navigate to Workloads > Cloud and find the virtual machine you wish to restore to an alternate cloud service provider (CSP). Click on the virtual machine to proceed. Find the backup you wish to restore and click on Restore Virtual Machine. On the Restore Virtual Machine page, select the AWS equivalents for Azure. Target CSP Configuration Name Region to restore to Your AWS Account Number The name the VM will have in AWS. The instance machine type The AMI ID. Note: The two attached Azure volumes at the bottom of the screen image will be restored into two volume on AWS. On the next screen continue to select the AWS equivalents of the Azure VM. AWS Zone Network configuration Network security group Advanced options After the restore, log into AWS and the virtual machine will be available for use. How to Use – AWS to Azure After a backup has been completed of a cloud virtual machine, navigate to Workloads > Cloud and find the virtual machine you wish to restore to an alternate cloud service provider (CSP). Click on the virtual machine to proceed. Find the backup you wish to restore and click on Restore Virtual Machine. On the Restore Virtual Machine page, select the Azure equivalents for AWS. Target CSP Configuration Name Region to restore to Your Azure subscription Resource group in Azure to restore to The name the VM will have in Azure. The instance machine type Note: The two attached AWS volumes at the bottom of the screen image will be restored into two volume on Azure. On the next screen continue to select the Azure equivalents of the AWS VM. Azure Zone Network configuration Security group Advanced options After the restore, log into Azure and the virtual machine will be available for use.
