Troubleshooting - Trusted root certificates (error code 151066)
You may receive an error message “Site Recovery configuration failed.” while configuring Azure to Azure VM replication. Most of these issues occurred due to the required trusted root certificates used for authorization and authentication aren't present on the machine. This https://docs.microsoft.com/en-us/azure/site-recovery/site-recovery-azure-to-azure-troubleshoot-errors#trusted-root-certificates-error-code-151066 details some of the possible causes and recommended actions to resolve this issue.
Linking containers in azure storage blockblob
Hi! I need to link two containers to each other, much like a soft link in a file system. I need it to avoid using storage for the same exact file twice, which I want under two containers. i.e The file https://account.blob.core.windows.net/1/image.jpg under container 1 needs to be accessible via https://account.blob.core.windows.net/2/image.jpg as well (under container 2). Notice that the whole point is to have one blob named image.jpg under two containers, not two identical files! Does anybody have any idea about how to make this happen? I did not find any documentation enabling such a feature. Thanks!Replicated Tables now generally available in Azure SQL Data Warehouse
We are excited to announce that Replicated Tables, a new type of table distribution, are now generally available in http://aka.ms/sqldw (SQL DW). SQL DW is a fully managed, flexible, and secure cloud data warehouse tuned for running complex queries fast and across petabytes of data. The key to performance for large-scale data warehouses is how data is distributed across the system. When queries join across tables and data is distributed differently, data movement is required to complete the query. The same can be said when transforming data to load, enrich, and apply business rules. With Replicated Tables, the data is available on all compute nodes, hence data movement is eliminated, and queries run faster. In some cases, such as small dimension tables, choosing a Replicated Table versus a Round Robin table, can increase performance because data movement is reduced. As with all optimization techniques, performance gains may vary and should be tested. Read about it in the https://azure.microsoft.com/en-us/blog/replicated-tables-now-generally-available-in-azure-sql-data-warehouse/.
Azure Site Recovery breaking SQL Server log chain
I'm protecting a SQL Server with ASR and doing backups with Commvault. Commvault is telling me that transaction log backups are being converted to fulls because it detected a break in the log chain probably caused by another backup product. I dug into it and found that ASR's VSS writer is taking a snapshot once an hour and SQL Server is seeing this as a full backup. Has anyone had experience with this? I feel like the ASR VSS snapshot shouldn't be counted as a full backup of the database
Azure Recovery purging recovery points?
If you have setup a backup job using Azure, and you have decided at a later date that you do not need quite as many recovery points as you once thought. Is it possible to take for instance Azure backups that are currently holding 198 recovery points and trim it down to say 30? Without losing all your backup jobs? Or do you have to delete all your old backups and start completely over?
ASR Replication Issue - Error ID 70171
Hi. I'm new to using this forum so hopefully someone can help me I have 2 x on-premise Hyper-V Windows 2012 R2 which replicate 10 servers into an Azure Recovery Vault which is used for ASR. I have a configured ASR policy which has been working for most of the year with no issues. On Thursday last week I received notification to upgrade my Hyper-V Hosts from Azure ACS to AAD for ASR. I did this and it all went well and they're on Agent Ver 5.1.2700.0 (latest) and I updated the MARS Agents to the latest too as I had a notice about these needing updating to the latest version. When I now list my 10 servers in Azure they are all RED and Replication Health is Critical and RPO column is blank. If I open ALL the servers they correctly state the App-and Crash resistance times : so why are they RED and stated as Replication Health Critical ?? The on-premise hyper-v replications says all is working and I used this article to check the finer points that replication is indeed being sent: https://docs.microsoft.com/en-us/azure/site-recovery/site-recovery-azure-to-azure-troubleshoot-errors#outbound-connectivity-for-site-recovery-urls-or-ip-ranges-error-code-151037-or-151072). Any ideas ?
Problems mapping Azure file shares on-premises
Hi. I'm new to Azure. I'm an MSP and a Microsoft Partner. I just created my Storage Account and first file share. I'm trying to map the file share from an on-premises Windows 10 workstation and Windows Server 2012. Neither work. I keep getting the error "network path not found"...error code 0x80070035. I tried to map the drive using PowerShell and Windows map drive from the GUI using the instructions for the Azure Portal (connect). I have verified that port 445 is open. Is this supported from on-premises locations?
