Azure Cloud Connector - Storage Warning (V-275-1017) - Unable to connect to the OpenStorage device
Hi all, We are attempting to configure a "Back Up to Disk and then Duplicate to Cloud" job. We have an Azure Tenancy in place already, which is in use for other services. When configuring the Cloud Storage, we receive the below error: "Azure: azure. azure.com:%server% - Unable to connect to the OpenStorage device. Ensure that the network is properly configured between the device and the Backup Exec server." It refers you to Article V-275-1017, however, this does not actually exist anywhere! It seems to relate to an issue with named proxies. If we allow proxy-bypass (or use a transparent proxy) the Cloud Storage configured correctly and shows Online, and can be used ok. However, if the proxy is named and explicitly detailed, then the storage cannot be created. If you create storage with a tranparent proxy, but then set a named proxy after the creation, the storage shows as Offline. Has anyone else seen an issue with named proxies, using Cloud Storage? This is a real issue as we have multiple sites that cannot use a direct connection, or transparent proxy. Thanks Graham
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 10.1 - New PaaS Workload Protection
Starting with NetBackup 10, Veritas began expanding the support for PaaS workloads. In NetBackup 10.1, Veritas built an extensive framework designed to promote accelerated adoption of PaaS workloads protection. As a testament to that framework, NetBackup 10.1 adds support for the following 13 new PaaS workloads: Azure Workloads AWS Workloads GCP Workloads Azure PostgreSQL Amazon RDS Postgres Google MySQL Azure MySQL Amazon RDS MySQL Google PostgreSQL Azure Managed SQL Amazon RDS MariaDB Azure SQL Amazon Aurora SQL Azure MariaDB Amazon Aurora PostgreSQL Amazon DynamoDB The process of protecting and recovering PaaS workloads is easy and streamlined via NetBackup Web UI. NetBackup Snapshot Manager needs to be configured to facilitate the discovery of the supported PaaS workloads. Media Server with MSDP Universal Share configuration is also a requirement. After NetBackup Snapshot Manager and cloud provider credentials are configured, discovery process will be triggered automatically or can be started manually. Once the discovery runs successfully, supported workloads will be populated on the Web UI PaaS tab: Add PaaS credentials as required for the workloads to be protected. Credentials can be created previously and leveraged later for the workload to be protected or created as new during configuration. On this example, credential is being created previously using Credential Management tab: Add the credential to the PaaS workloads to be protected. Please note the “validation host” is the Media Server hostname that will be utilized to communicate with the cloud provider and PaaS workload. Media Server need to be able to resolve PaaS services to validate credentials: After that, it is just a matter of creating Protection Plan as usual. The following two prompts are specific to PaaS workloads: 1-) Protection Plan is for Cloud, same as the one used to protect virtual machines in the Cloud, for example. Check “Protect PaaS assets only” to be able to call the correct workflow and framework for PaaS: 2-) On step 4 (Backup options), storage path is the previously configured Universal Share mount point: Just complete Protection Plan workflow and that’s it! Protection Plan will run according to the schedule configuration and recoveries will be fully managed by NetBackup Web UI as well. Veritas NetBackup 10.1 now makes it easier to protect PaaS workloads, with a streamlined process guided by Web UI and leveraging benefits of NetBackup deduplication service (MSDP) and RBAC (role-base access control) to empower workload owners and administrators as needed. Here are some good references for more information about PaaS Workload protection with NetBackup 10.1: NetBackup 10.1 Web UI Cloud Administrator's Guide - Protecting PaaS objects NetBackup 10.1 Web UI Cloud Administrator's Guide - Recovering PaaS assets
How to Configure Synthetic Backups to Cloud with Full and Incremental Backup to Disk?
I am currently doing Full backups to disk at the end of the work week with incremental backups to disk at the end of each work day. The Full backups are retained on disk for a month. The Incremental backups are retained for a week. What I am hoping to do is also duplicate these backups to the cloud. However a regular duplicate of the Full to the cloud would be both time and cost prohibitive. To minimize the amount of data to be transferred, it looks like synthetic backups are the way to go for cloud backup. So what I am hoping to do is: Full weekly backups to disk to be retained for one month on disk. Incremental daily backups to disk to be retained for one week on disk. Synthetic full backup to cloud to be retained perpetually. Duplicate the incremental daily backups to the cloud to be retained for one week. How would I configure this in Backup Exec? A Synthetic Backup is defined in Backup Exec as a baseline Full, Incrementals, and a Synthetic Full Backup. So when defining the backup job: Do I configure the Full and Incrementals to go to Disk and then configure the Synthetic Full Backup to go directly to the cloud? Or do I have to configure the Full, Incrementals, and Synthetic Full to go to Disk and then add a separate duplicate task for the Synthetic Full Backup to go to the Cloud? Or do I have to do configure it a different way? Best regards.
Duplicate deduped NDMP backup (block-level) to cloud?
Hello, we have a Backup Exec (16 FP2) job which backups data (mostly vm images) from a NetApp to a deduplication storage via NDMP. As it is a file-level-based backup and the data of the vm images changes rapidly, no real incremental or differntial backups are possible. Is it possible to duplicate this deduped backup-set to a cloud storage (as offsite-backup) on a block-level base, so that incremental backups can be used and the data sent can be reduced? And can I use this duplicated backup to restore (single files) back directly to the NetApp or do I have to restore it first to a local storage and then back to the NetApp? Thomas
Why should i use cloud backup solution like AWS..?
Hi Team I have one query. Today lot of organizations are talking about cloud backup service. If i have infrastructurecreated in cloud itself (AWS instances, Databases etc.,), do i need to deploy enviornment inside cloud as we deploy in on-premise? Cloud offers few native features such as Snapshot mechanims for AWS instances Database availability and consistency Data availability across multiple region. In this scenario, why should i use backup software since they will charge me license cost.
