BE 15 fp 5 backup to the private S3
I'm currently trying to test configuration with backup to our private S3 which is compatible with Amazaon S3 but unfortunately I am unable to complete it. here is the list of my actions: 1) configure cloud instance using BE MCLI according to BE MCLI *.chm help. It finishes with success. 2) Configure Cloud Storage using BE GUI. All configuration wizard steps completes with success, wizard even successfully retrieves the list of S3 buckets from the S3 service, and completes the configuration with no error. 3) At the end of configuration BE offers to restart it's services to finalize the cloud storage. 4) After the restart device is still shown as offline. There is an alert at the time of services start: Unable to connect to to the OpenStorage device. Ensure that the network is properly configured between the device and the Backup Exec server. For more information, see V-275-1017 on the Symantec Knowledge Base. However, I was unable to find any useful reference in KB to solve this particular issue. The main question is to understand what is missing from either configuration steps or S3 itself. Does anyone know how this can be debugged?
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 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)
Netbackup 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.
Backup Exec 16 - AWS S3 or Tape Gateway
Icurrently have the aws tape gateway setup to do weekly backups for our servers. Its working well minus the auto ejecting after the job is over (will see if this issue still happens with backupexec 16, just upgraded yesteraday). I noticed backupexec 16 has the ability to add AWS S3 as a storage. Can someone please explain the advantages/disadvantages of s3 versus tape gateway? Thanks
Configuring 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.