A self-restore portal simplifies the restoration process for enhanced data availability. Introduction to Active Backup for Business Synology recently launched a set of new data backup packages: Active Backup for Business, Active Backup for G Suite, and a new version of Active Backup for Office 365. Its backup scope includes the complete set of Microsoft 365 productivity data that small businesses rely on to collaborate, communicate and operate efficiently, from Exchange Online information (mail, calendars, contacts, notes, etc. I recall it taking over 30 minutes when I … Veeam Backup for Microsoft Office 365.
The software is intuitive with a user friendly interface which is uncluttered. If an overwhelming number of requests occurs, throttling helps maintain optimal performance and reliability of the Microsoft Graph service.
CodeTwo Backup for Office 365 is a desktop application that lets you perform full or incremental backups of selected Microsoft 365 (Office 365) mailboxes and public folders, SharePoint Online and OneDrive for Business sites, as well as Microsoft Teams data. Back up your NAS to Previously I’d already covered Synology’s Microsoft 365 Backup software which I was a big fan of, for simplicity of use and an incredibly cheap price point for a small to medium business as a Microsoft 365 data backup solution. Your case maybe different, depending on the root cause your resolution maybe different then what was discussed here.Ĭheers stay safe everyone.Synology active backup 365 Hyper Backup is used to backup your Synology NAS data to another device, either a USB drive or a remote Synology NAS, or even to a cloud account like Synology C2, Dropbox, Google Drive, Amazon S3 etc. Honestly I just followed the Veeam KB which was a great source reference to troubleshooting the issue. More than likely the hostname look up for the ESXi host in which the VM will be created on. You may notice that the ESXi hostname is not within the initial error, it only tells your the datastore, the Veeam logs will indicate which lookup failed. So in this case… to resolve it I added a record in the Proxy’s local host file 172.x.x.x It’s important to note that when these types of choices are made it is well documented WHY they were made. Since this is a self hosted instance of a Veeam proxy, there’s a good chance DNS access might not be available when time comes, so this option was chosen. (DNS server not required, but if hostname or IP changes needs to be adjusted manually here)Īs you can see I have the exactly 2 options similar to my first post, the difference is now it was fully dependent on DNS.
The funny part about this is… 1) it’s the same server/proxy 2) Again DNS related 3) Again going to stick with host file to avoid dependencies on DNS servers Now that I know what the issue is… this feels familiar… oh yeah the Veeam Soap Fault issue I had to deal with… It was using a server within the routes I had removed, and didn’t create a dedicated /32 for, as I wasn’t expecting any systems here to need to communicate to that subnet. So I followed along, checking the main Veeam server log areas didn’t have the log file in question, so was pretty confident it was still using the proxy at the alt site.Ĭhecking the log as mentioned by the KB, sure enough the same error line showed up which indicated it was DNS related.
I love Veeam, they got a nice KB to help with this. I decided to do regular troubleshooting to get more details to the root cause. Since I wasn’t exactly sure which was the cause. I had also just patched the host in question and was testing jobs after the patch. NFC path: note on this, I did some changes, I changed a route between sites (as I needed to reduce a entire network from being improperly routed, but some of services still required access from the main location, thus some dedicated /32 routes were put in their place). Check error, huh haven’t this one before… 11:22:16 AM :: Processing VMName Error: NFC storage connection is unavailable.