VERITAS NETBACKUP WITH RED HAT CEPH STORAGE
We are using netbackup with ceph storage where ceph is presented to the media servers as a MSDP. Since MSDP has limitations of one pool per media and a sizing limit of 96 TB, we are planning to use CEPH as a S3 - backup target for the new media servers we have to configure. I want to know if we configure Ceph as a S3 cloud storage, can Netbackup perform deduplication? Will all dedup be just on client server using accelerator or we can have target dedup by netbackup as well? Or netbackup will send all backup data it receives to Ceph without any dedup, leaving all data reduction to be handled by CEPH? Can CEPH as a cloud storage perform dedup on its own? With CEPH 4 , we will have erasure coding, so the total storage used will be less but in terms of dedup what advantages can I have by using ceph as cloud storage instead of a MSDP. If anyone is using Netbackup with Ceph, could you share your approach please.Solved1.8KViews0likes1CommentNetbackup integration with S3 ...
Hi All, I am evaluating a scenario with netbackup 8.0 i have integrated netbackup with AWS S3 as backup target in S3, i have applied lifecycle rule where data will move to glacier after 1 day (netbackup will write data in S3, after 1 day, AWS will automatically transition data to glacier storage class) Now while restoring from netbackup, i am unable to get that data since data is stored in glacier and netbackup cannot talk to galcier directly. just want to verify if anyone have tested such scenario.3.3KViews0likes3CommentsConfiguring cloud storage using CLI
Has anyone successfully configured S3 cloud storage (from start to finish) using the CLI? The csconfig documentation (from the reference guide) is not that helpful. It's unclear how the access key and secret are entered, how the disk pool is configured (will nbdevconfig work with cloud storage), and so on. Almost every single document references the GUI but there are statements indicating that the csconfig command can be used but with no decent examples.1.1KViews0likes1CommentConfiguring Amazon S3 in China (Blog)
(This isn't a question, just documentation of how we fixed an issue I couldn't find an answer to online. I have no doubt all of this is in the Cloud Admin Guide, I just decided to take the long route and skip that part :manembarrassed: ) My company has a handfulof remoteofficesaround the world, with two of themin different sitesin China.In each of those China offices we run a 7.7.3NetBackup Master Server, (Windows 2008), to back up local data to disk, and use SLP to replicate those images across the WAN to the other office for offsite protection. This has been working successfully for 3 years, but we've slowly been adding more data to these offices and can no longer do local backups ANDcrosssite replication without filling up the disk targets. We're using "borrowed storage"from another server to protect our offsite copies at the moment while we decide where to go next. One of our new initiativetests was to replicate to S3, but AmazonAWS has a separateChina environment different from the amazonaws.com that the rest of the world can access, amazonaws.com.cn. Our Cloud Admin set up a new S3 instance in China without an issue, but the problem is the default Amazon cloud instance in NetBackup 7.7.3 is not customizable, and does not include the China Amazon region. The problem is the cloudprovider.xml file (C:\Program Files\Veritas\NetBackup\db\cloud) is locked and there are no commands available to add the China region to the Amazon plugin. I was able to get a new cloudprovider.xml from NetBackup support, but that was only because the tech working my case had one on his desktop from helping another customer. The actualsolution to this, and any other provider that isn't a default Cloud option, is to contact the vendor and request the plugin directly from them. (You may need help combining customized instances with the new .xml but I didn't experience that so I don't know the procedure). Also, my device mappings were about a year old so I had to update that file as well. (https://sort.veritas.com/checklist/install/nbu_device_mapping) After replacing the cloudprovider.xml and upgrading the device mappings I was able to see the amazonaws.com.cn instance and, (having already opened the firewall), connected the very first attempt. Firewall: source tos3-cn-north-1.amazonaws.com.cn Bidirectional TCP: (5637,80,443)4.2KViews6likes4Comments