Configuring 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 handful of remote offices around the world, with two of them in different sites in China. In each of those China offices we run a 7.7.3 NetBackup 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 AND crosssite 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 initiative tests was to replicate to S3, but AmazonAWS has a separate China 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 actual solution 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 to s3-cn-north-1.amazonaws.com.cn Bidirectional TCP: (5637, 80, 443)
finally on 7.7.3
NBU 7.7.3 at last! i was forced to bite the bullet as the post yesterday EOSL is this Wednesday. but i'm glad i did! view hierarchy SIP Always On for AG but the last two can't be together still :-( anyway, converting my SQL backups to SIP. note: you haven't upgraded yet its easy. took me only less than 2 hours. just make sure to do the SORT tool preparedness thing and read up on the upgrade guide.
Bckup error 811, 37 after uograde to 7.7.2
After upgrading clustered master/media server or servers with multiple interfaces to Netbackup 7.7.2, one can beging to experience error 811 and 37 which are related to connectivity. Running ./bptestbpcd -verbose -debug -client completes with status 0 but reading through shows connecting to invalid server which is the cause of error. Netbackup 7.7.2 does not acknowledge parameters set for PREFERED and REQUIRED interfaces. This causes netbackup to pick any other IP on the server. We experienced this and was resolved by applying EEB from veritas. Best is to avoid 7.7.2 and upgrade to 7.7.3 Suspected issues in https://www.veritas.com/support/en_US/article.000108202 NEXT STEPS: Customer to apply EEB for 3874054
