![]() ![]() I had this with QNAPs years ago and had to remove this to resolve the problems. ![]() Hi write cache being disabled will certainly help. My internal backups are using a virtual backup server with to a Synology NAS connected as a RDM disk in VMware that is passed along to the Server 2012 R2 repo server with a NTFS formatted volume….guessing that’s going to be a pretty similar configuration. ![]() Not to say it wouldn’t happen, but if you need me to check on any of my Synology’s, I certainly can to see if any settings might differ. ![]() To my knowedge, I haven’t see that issue and I have serveral Synology and QNAP NAS’s in place across my client base. That said, how is your volume formatted? REFS has been known to occasionally cause issues on ISCSI volumes to NAS’s and can be seen in the health checks at the end of the backups, or so I’ve read per With that said, I haven’t personally experienced it (to my knowledge.some of that is semi-transparent), but going forward, any NAS repo’s I have will be using NTFS and not REFS….possibly might try XFS with a linux repo server, but haven’t done the research and tried it out yet.Įdit: Just read your comment above and noted you’re trying to disable caching on the drives. NFS would be preferred over SMB if you had to use a network protocol. ISCSI is the way (unless you can use local disks) - better performance than SMB and NFS, I believe mostly due to multipathing. Is there another lower-cost storage appliance with a Veeam integration that would be better for what I am trying to do? My goal is to develop a better solution maybe this problem is linked to the DS416play or how we are setting this up? Maybe Veeam? I know it's not the WAN we used a slow POS USB drive for years and never had a problem. We had the Synology DS416play sitting around, so we deployed it thinking this would give us some redundancy and more space. The ISCSI method increased the speed jobs were flying and working! But over time, we started getting "Stg.CheckMetadataCorrupt" errors? Doing an Active Full would resolve this, but only a few days or weeks this has become a maintenance nightmare!īefore moving to the Synology, we had a large USB HD connected to a windows ten box this worked for years and worked well, but I never liked the thought of a single drive and the limited space. Then we created a LUN and attached the Veeam server with ISCSI creating a drive letter and pointing the repository to this. Then we changed this to an SMB share connected to a repository on the Veeam server again, this was slow, and jobs would never finish. At first, we set this up as an NFS share connected to a repository on the Veeam server doing it, this was very slow, and backups failed. We have a backup copy job that pushes backups off-site over a VPN to Synology DS416play. We have Veeam installed on a server in our primary data center, this server has 64TB, and all our primary backups are stored here. Good morning I have been having some problems with our current setup, I'm ok with smashing my hardware and starting over, but I want something I know will work! I am having issues with a backup copy job moving our backups off-site to another location. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |