Data & Storage
379 TopicsReference to database and/or server name in 'Azure.dbo.XXX' is not supported in this version of SQL
I am getting an error that seemingly indicates that I'm trying to use linked server or cross-database query when I am in no way trying to. I've opened a stackexchange question w/ full details but no one has seen this scenario. Reference to database and/or server name in 'Azure.dbo.XXX' is not supported in this version of SQL Server (where XXX is my table name) See full details on https://dba.stackexchange.com/questions/170828/delete-records-from-single-azure-db-table-that-has-no-linking-reference-to-dat but basically I can SELECT, INSERT, and UPDATE to this particular table but cannot DELETE from it. When I try to run a DELETE statement, I receive the error above. Have tried disabling TRIGGERs, have tried various combinations of schema/database/tablename in the FROM clause. Pulling my hair out here.Solved105KViews0likes8CommentsProblems 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?34KViews0likes6CommentsTroubleshooting - Unable to delete Recovery Services Vault?/Can't delete Azure Backup Vault?
You may receive " Vault deletion error Vault: 'Vault name' cannot be deleted as there are existing resources within the vault. Please delete any replicated items, registered servers, Hyper-V sites (Used for Site Recovery), policy associations for System Center VMM clouds (Used for Site Recovery) and then delete the vault." when trying to remove the azure recovery services vault. Most of the Vault deletion errors that we encounter at support are due to the dependency resources exist in the vault. Please follow the steps metnioned in below articles to resolve this issue. For the site recovery resources https://docs.microsoft.com/en-us/azure/site-recovery/delete-vault For the backup resources https://docs.microsoft.com/en-us/azure/backup/backup-azure-delete-vault If you testing the product, want to rapidly delete the vault and not concerned about data loss, then you can use https://social.technet.microsoft.com/wiki/contents/articles/37967.asr-and-azure-backup-how-to-force-or-automate-deletion-of-a-site-recovery-vault.aspx to remove vault and all its dependencies.Solved33KViews0likes11CommentsAzure Backup port requirements
Hi, I have been quite successful in migrating several clients and theor various server/workstation config to backup daily to Azure Backup Services. With one exception. This client has posed challenges for me in the past. Back in the days when he was running SBS2003. The scenario is that he rents office space within another organization. Included in this arrangement is Internet access. I do not hold sway, nor provide support to the other entity. To keep the two networks separated I have placed a router on the hosts LAN and have my clients operate on a completely different subnet. Thus far, for the most part, this has worked. My challenge is getting Azure Backup to function. Bear in mind I do not have access to the Intenet facing router. I have managed to setup an account on Azure, and have managed to installed the backup client, select exclusions etc. But that's where my progress ends. The portal acknowledges a client has been installed, but no data has ever been uploaded to the servers. Other online backup services, such as Attix5, KeepItSafe etc. all function correctly, just Azure doesn't. Any guidance would be much appreciated. Paul29KViews0likes6CommentsAzure File Sync issues and errors - files/folders not syncing
We are testing Azure Files and in particular Azure File Sync currently. Admittedly, we are throwing a lot of files and shares up as a test. I have some shares that that show its 'health' with a green checkmark, but upon reviewing the Diagnostic Event Log in the Event Viewer, it appears that there are large numbers of files and directories that are not syncing (in other words they were never uploaded). I am glad I found the Event Logs otherwise I probably would have assumed everything was uploaded. 1. We are in a mixed Windows/Mac environment, and unfortunately over the years many Mac users were in the habit of naming files with a dot in the name. This is not a period, but a horizontally centered bold dot. I am trying to determine a way to rename these to an underscore in batch, but this is problematic as Windows will not search for that character. 2. Other characters are also giving issues. I believe these issues also occur with OneDrive and I understand the complexity and I'm not complaining. Just making notes for any users going through the same thing. In particular the % sign, and folder names that have a period in the name. So for instance, we have had users that have named a folder '12. Job Notes'. The 12 represents the month December, and its just the convention they have used over the years. While the folder creates on the Azure side, the files do not upload. 3. Some files will not sync, and I cannot determine a rhyme or reason. The file does not appear to be in use or locked in any way. It does not have an invalid character (that I can tell) and the file path doesn't appear to be too long. Log Name: Microsoft-FileSync-Agent/Diagnostic Source: Microsoft-FileSync-Agent Date: 12/14/2017 2:43:35 PM Event ID: 1101 Task Category: None Level: Warning Keywords: User: SYSTEM Computer: SERVER.ourdomain.local Description: The File Synchronization service failed to upload a file. File name:\\?\E:\Shares\Marketing\Public Relations\New Business - non-automotive\Carrey Della\Carrey-Della Pinterest.docx; Sync ID: {eedf85bb-61ad-4fc9-af5f-e14439f3fd00}; Error: 0x80c80065 - The file has been identified to produce persistent errors during sync. Hence, it is blocked from transfering data until the retry interval is reached. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-FileSync-Agent" Guid="{4E816BB7-D169-59A8-A02D-3892859A3B96}" /> <EventID>1101</EventID> <Version>0</Version> <Level>3</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x4000000000000000</Keywords> <TimeCreated SystemTime="2017-12-14T20:43:35.247538400Z" /> <EventRecordID>5219603</EventRecordID> <Correlation /> <Execution ProcessID="273892" ThreadID="130004" /> <Channel>Microsoft-FileSync-Agent/Diagnostic</Channel> <Computer>SERVER.ourdomain.local</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="FileName">\\?\G:\Shares\Garage\Public Relations\New Business - non-automotive\Carrey Della\Carrey-Della Pinterest.docx</Data> <Data Name="SyncId">{EEDF85BB-61AD-4FC9-AF5F-E14439F3FD00}</Data> <Data Name="HResultStr">0x80c80065 - The file has been identified to produce persistent errors during sync. Hence, it is blocked from transfering data until the retry interval is reached. </Data> <Data Name="HResult">-2134376347</Data> </EventData> </Event> 4. Lastly, 2 of the larger shares, they do not have a healthy status but instead have a red exclamation point. If you look at the error you see: The Azure sync database write lease has been lost due to another database writer. The current operation will be aborted. Interestingly, one of the shares does in fact seem to sync if you create a new file, but the other one does not seem to sync at all anymore (beyond the initial sync). I would like to add that everything has been amazingly easy to set up, and I am really excited about this product. It appears that it will require a culture change (with the Mac users), and at least currently a lot of effort to get what could be thousands of files or folders renamed to something proper.19KViews0likes1CommentBacking up Azure file storage to Azure Backup
Hi Team, We are already using Azure file Storage. This is to copy files directly to Azure Storage (file shares). A virtual drive has been mapped for this storage. Since Azure File Storage does not support Recovery/Restore Points (i.e. restore a file one week old) or Point in Time copies, we need to use Azure Backup which has these Point in Time/Recovery Points capabilities which will allows us to restore files like 2 days old in case a file has been delete or overwritten. Per our research, Azure File Storage backed up directly to Azure Backup is not possible (yet). Backup of Azure Storage is only possible on BLOB Storage but not Azure File Storage. See links below. https://docs.microsoft.com/en-us/azure/backup/backup-introduction-to-azure-backup https://github.com/levibotelho/azure-blob-backup https://docs.microsoft.com/en-us/azure/backup/backup-try-azure-backup-in-10-mins Is there any possibiltity to achieve this with current capabilities or if not, has this been taken in to the timelines for future deliveries ? any feedback is really appreciated ! Thank You Manoj Karunarathne manojviduranga@hotmail.comSolved16KViews2likes23CommentsASR Vs Azure backup
Hi, What exactly is the difference between Azure Site Recovery and "Recover as a VM" from an Azure backup? Im asking from both a cost and recover efficiency perspective. I assume both dont charge for compute resources until the resources (VM) are spinned up. Is it the time it takes to spin up the VM? Both use the same storage vault for storage so storage cost is the same, and i cant even choose Hot or Cold storage when creating the storage vault (or can i?) and/or attach disks. Besides for ASR being more expensive per protected instances, what other additional costs go along with ASR? What "Type" of storage (e.g. Unmanaged/Managed P or S) am i billed for when backing up/replicating to an Azure backup vault?15KViews0likes2CommentsSharing azure file share with read only rights.
I am currently investigating file storage within Azure with the goal of moving a local large file share/library to Azure instead of having it sitting on a physical server in our office. I have run through Azure and been able to create a file share and successfully map this to my machine as a network drive using owner/admin rights. What I'm stuck on, is how best to then share this to other users with read only rights? I've looked through the azure portal and see I can set someone with a Microsoft account to have read rights, but on doing so don't see any easy way to then translate that into a mapped drive with read only rights. Could someone please give me some pointers on how to achieve this, or the best way of making this happen with Azure? Essentially we want an admin role to load azure with all the files, and to then allow all our users (but not public) to access the location from thier generic computer with read only rights. Looking for simplest/easiest way to do this.13KViews1like1CommentDisk performance issues
Hi All, Currently have a few VM's in Azure, but have problems that disk performance seems lot slower then how they should perform. We have an open support ticket with Microsoft, but after 10 days we havn't really heard anything back from the Azure support team :-( As an example we started this a VM on Azure as VM size A2v2. At start the VM had 3x200 GB standard Managed disks that where striped to boost performance. We saw performance of maximum 30 MB/sec. when doing copy between the E: and C: drive on this VM and when trying to copy between Azure VM's by Network. To try something we upgraded the VM to sizen Ds3v3 and we have changed the Data disk (E: drive) to an 600 GB Premium disk. This VM is only used as a file and printer server with printer and file shares so nothing big. All file shares is on the Premium disk (E: drive). Antivirus product F-secure is installed but we have deactivated. Still after these changes that should make performance much better we still only sees 30 MB/sec. as maximum disk transfers? We tried we the PerfInsights support Tool from Microsoft and it confirm a maximum of around 30 MB/sec. and only 4-5 MB/sec. on the system disk drive C: ?. Can anyone help me trying to find the problem or what to do? (we fell all our Azure VM's i slow on disk!)10KViews0likes1CommentCannot connect to Azure file service from Windows
I'm using the Azure file service to store some archived files. I'm using the connection string autocreated by Microsoft to try and map a drive. net use Z: \\mystorageaccount.file.core.windows.net\archive /u:AZURE\mystoreageaccount longautogeneratedpasswordbymicrosoft== The error I get is System error 86 has occurred. The specified network password is not correct. I've tried this on a couple of different machines (W10 and Win Server 2012 R2) with the same results. I can however use the file AzFileDiagnostics.ps1 from https://gallery.technet.microsoft.com/Troubleshooting-tool-for-a9fa1fe5 to connect to the file store and map a share. Does anyone have a view why powershell works and the net use command does not.10KViews0likes1Comment