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?
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
Backup Exec: EC2 and On-Premises CAS/MBES configuration
We are working with a client who wants to move all his on-premises infrastructure to AWS cloud. There is a limitation with his WAS bandwidth which is 1gb. Their total data size is 30TB. Since the data size is big and the WAN bandwidth is limited they are going with a transportable disk which will take the initial full back to the cloud and then there will be just incremental backups that will be sent to cloud. My query is has anyone done a configuration where there is a CAS and an MBES on EC2 virtual machines and then there is another MBES which is on premises. Can we have some pointers on how we can achieve this setup. How will the communication between the CAS Backup Exec server on the EC2 and the on-premises MBES server happen? What are VPN configurations that need to be done to get this configurations working. I believe that if the communications between all the servers is working, then this setup should work and the customer can achieve what he is looking for. Any pointers regarding this will help a lot. Thanks in advance!