Recent Discussions
Netbackup KMS
hi Guys, kindly educate me - At one of remote site our NBU server was short circuit. Rebuild done after 6 months and handover to backup guys on friday(27sept). We need to install NBU on it, it had tape backups with KMS encryption (i had documentation available). In 2019 -- NBU 8.1 was installed on window OS (hardware) + HP tape TL, KMS was configured( this encryption feature is free) then in year 2020 we upgraded NBU to 8.3.1. Cut to 27sept 2024 - i have to reinstall NBU - rebuild KMS and try to restore finance data. What NBU version should be installed --- 8.1 or 8.3.1 -- kindly educate me. [i cannot go to netbackup support]
Instant Access for vmware problem
Hi, I have netbackup 10.4 to protect vmware workloads. my primary and media server are installed on rhel 8.10 and storage unit is msdp. when I create instant access virtual machine and start job I get this errors: error nbmwc /usr/openv/pdde/vpfs/bin/vpfs_actions failed (1): unable to importostimage. could not import the ost image id. /usr/openv/pdde/vpfs/bin/cata2map failed (38) failed to create an instant access virtual machine (vm). (4004) my storage is msdp and it's accessible. vcenter credential is ok and backup jobs are ok. in recovery target I changed display name and I checked create a new bios and instance uuid. vpfs_actions log: error system_utils._wrappedpopen /usr/openv/pdde/vpfs/bin/cata2map failed (38): error vpfs.fs.sharecommands could not import the ost image id /usr/openv/pdde/vpfs/bin/cata2map failed (38): error system_utils._utils unable to importostimage. could not import the ost image id. /usr/openv/pdde/vpfs/bin/cata2map failed (38) error system_utils._utils returning: 1 cata2map log: failed to mount loop device /dev/loop0 to /msdp/vol0/meta_dir/.../.../head with fstype xfs, err=38, msg = function not implemented. failed to mount dev_file /msdp/vol0/meta_bdev_dir/.../.../head to mnt /msdp/vol0/meta_dir/.../.../head, ret=38 failed to mount block device /msdp/vol0/meta_bdev_dir/.../.../head to /msdp/vol0/meta_dir/.../.../head, ret=38, msg = function not implemented failed to mount block device /msdp/vol0/meta_bdev_dir/.../.../head to /msdp/vol0/meta_dir/.../.../head, ret=38 mapobject::mountvolumes(): failed to mount head volume
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! 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?!
Getting ms-windows assets via api
Hey guys and girls, I want to write a local check for my monitoring system (checkmk), so I can monitor if backups are running and if my servers are protected. I don't have much experience with Netbackup, a supplier set up the system for us, I'm just a backup admin (amongst many other things). I'm quite competent with python and api's, but haven't played around with netbackup's api until yesterday. For my checkmk 'local check' I want an overview of all machines that I make backups of, and when the last succesful backup was run. Now I have two different workloads: vmware and ms-windows. For the vmware workload, it's quite easy, I found there's an assetservice api endpoint, where I can get info on all my vm's, and when the last succesful backup was. Easy peasy! But for the ms-windows workload, it seems like it's a bit more complex. The assetservice api does not seem to recognize the ms-windows workload? I can get a list of all the recent jobs, look for the WINDOWS_NT type, and massage the data the way I want it, but then I have to aggregate all streams for a specific host, do manual stuff on it, etc. You guys know if there's an easier endpoint to use for this?
Inquiry regarding using Netbackup appliances across domain
We are currently managing two separate Netbackup domains, each with its own unique setup, and we are looking to make some changes to streamline our infrastructure. Below is a summary of current configuration. Domain one configuration: Master server with two Netbackup appliances( serving as media servers) Domain two configuration: Master server with two BYO servers( serving as media servers). LUN is assigned to these media servers from HP3par storage and configured as MSDP. We are trying to get rid off HP3par storage for future backups so, Is it possible to use the Netbackup appliances from Domain 1 as a media servers for domain 2 as well to manage future backups? If not, could you kindly suggest alternative approach to achieve this while eliminating the HP3par storage from domain 2.
BMR: Could not read saved configuration file=X:\bmrcli.xml
I am testing Bare Metal Recovery. Test environment is virtual (VMware).The recovered system is booted from boot ISO. It connects to the master server but during the step "Establishing restore environment" this error message is shown: The restore has stopped due to the following error: Could not read saved configuration file, file=X:\bmrcli.xml NetBackup servers and client version is 10.3. Any ideas? Thank you.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. 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.
