Azure

6 Topics

How to use same Azure storage account (Blob storage Container) on two veritas server
Hi I have two Backup servers (Server A & Server B) where I have installed Backup exec and Configured the same Azure Blob storage container. I have uploaded (Backup) data from server A and not able to view same data in the backup exec configured in server B where I need to restore the same data. DO I need to run a catalog in order to view the data in server B backup exec which I uploaded from server A?
subramanyad
5 years ago Place Backup Exec
841Views
0likes
1Comment
PODCAST: Backup Exec 20.2 Instant Cloud Recovery Azure DRaaS Integration
Check out our latest Voice of Veritas podcast where Sujay Talasila from Microsoft and I discuss Backup Exec 20.2 Instant Cloud Recovery Azure DRaaS Integration https://vrt.as/2pLGSJz
BackupMikko
7 years ago Place Backup Exec
924Views
0likes
0Comments
Installing OpenDedupe to Azure and configuring Optimized Duplication with Backup Exec 16
This video shares best practices for installing OpenDedupe to Azure and configuring Optimized Duplication with Backup Exec 16.
AlexMatts
7 years ago Place Backup Exec
1.9KViews
0likes
0Comments
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
Graham_Hodgetts
8 years ago Place Backup Exec
5KViews
0likes
7Comments
Video guidance: How to deploy Backup Exec from Microsoft Azure Marketplace
Are you seeking to run Backup Exec in Azure, but unsure of how to do so? Please watch our video, How to deploy Backup Exec from Azure Marketplace, where we guide you through creating a Backup Exec server running in the Microsoft Azure Cloud.
Colin_Weaver
8 years ago Place Backup Exec
1.2KViews
3likes
0Comments
Azure backups hanging at Loading Media
We had setup several backup jobs to Azure using Backup Exec 16. All was working well for a couple of weeks, but recently we are now having an issue where most or all backup jobs are getting stuck at Loading Media... When this issue occurs, the Backup Exec software runs, but the services appear to be hung. For example, if there are scheduled jobs that need to run during this time, they do not run. During this condition, any attempts we make to change/cancel/hold the jobs or device settings are unsuccessful (timeout); however, the Elapsed Time on the running jobs continues to increase and we can click around the various tabs in the BE software. Also during this condition, the pvlsvr.exe (Backup Exec Device and Media Service) is using CPU but does appear to be hung, because any attempts to stop or restart the Backup Exec services fail/timeout. We can either reboot the server, or forcably kill the backup exec service processes to break out of this condition. We have let the condition sit for over 24 hours to see if it would eventually clear, but it did not. The Azure storage logs show various errors on GetBlob and DeleteBlog requests for various files like: 1.0;2017-05-30T14:21:41.9770882Z;DeleteBlob;ClientOtherError;404;6;6;authenticated;**storageaccountname**;**storageaccountname**;blob;"https://**storageaccountname**.blob.core.windows.net:443/container/BEOST_00000196/META_BLOCK_MAP_FILE";"/**storageaccountname**/container/BEOST_00000196/META_BLOCK_MAP_FILE";815c11b7-0001-00f9-2150-d9e47b000000;0;**IP**:62534;2015-02-21;354;0;145;215;0;;;;;;"APN/1.0 Veritas/1.0 BackupExec/16.0";; 1.0;2017-05-30T14:20:57.7580368Z;GetBlob;ClientOtherError;404;78;78;authenticated;**storageaccountname**;**storageaccountname**;blob;"https://**storageaccountname**.blob.core.windows.net:443/container/BEOST_SDrv5/META_BLOCK_MAP_FILE";"/**storageaccountname**/container/BEOST_SDrv5/META_BLOCK_MAP_FILE";e32ceac0-0001-0039-484f-d96e3f000000;0;**IP**:62515;2015-02-21;348;0;145;215;0;;;;;;"APN/1.0 Veritas/1.0 BackupExec/16.0";; In the adamm.log file, we see these logs: [03388] 05/30/17 10:20:57.696 DeviceIo: beost: Critical: Azure: CAzureManager::open_image: [03388] 05/30/17 10:21:32.495 DeviceIo: ostscsi: move error image BEOST_00000196 could not be get_proped 2060018, attempting to recreate This same issue is happening on 2 different Backup Exec servers. The servers are pointing to 2 separate Azure storage accounts (and 2 separate containers) and they are the only software using these storage accounts. The data is being Duplicated from a Data Domain appliance, but we have even experienced this issue with a test backup job directly to Azure. It also does not seem to matter whether the job is VMware VMDK files or SQL data, etc. The issue happens regardless. I do have a case open with Backup Exec, but we have not gotten anywhere yet. The ticket has been escalated. We have tried setting the "concurrent operations" setting to various things, such as 1 or 5 or 8, with no effect on the issue. Has anyone else seen this issue or can you think of anything else we should check? Thank you!
Solved
gcpato
8 years ago Place Backup Exec
2.5KViews
0likes
6Comments