Synametrics Technologies

One of our users, at whom we've installed Syncrify build 649, snail-mailed us a copy of her 6 GB SQL database, prior to her first online Syncrify back-up. We copied the .bak file into the correct repository folder, and fired up the remote back-up. At first, everything seemed to work out perfectly; we saw an incremental _synver file being created, but few seconds later, the incremental file disappeared, and the original full back-up file was decimated to 1.99 GB, deeming it unrecoverable. Can anyone confirm Syncrify supports MS SQL back-ups larger than 2 GB?

It appears we have multiple users where the MS SQL plug-in doesn't back up anything beyond exactly 2,147,479,552 bytes (just a few bytes short of 2 gigs). Should we give up on the plug-in?

We have a SQL Server that creates a 4.5 GB file and it works fine. Do you know if your SQL server creates a .BAK file larger than 2GB?

>We have a SQL Server that creates a 4.5 GB file and it works fine. Do you know if >your SQL server creates a .BAK file larger than 2GB? In case of .bak files larger than 2 GB, Syncrify chops off anything beyond 2 GB. I believe this issue has only emerged from build 630ish onwards. Earlier Syncrify builds didn't seem to suffer from this bug. Could it be you're using an older build, Petarian? What's more, it doesn't even seem limited to .bak files or the MS SQL plug-in; as a work-around for this bug we've been trying to back-up our SQL users file based in stead of through the plug-in. It turns out that whether we back up a +2 GB .bak file, or have the SQL plug-in back up the db directly, any file exceeding 2 GB is decimated.

I am using the latest version (build 649) and can definitely backup file larger than 2GB. My largest file is about 12GB and it gets backed up fine. Did you check the log files for error?

>I am using the latest version (build 649) and can definitely backup file larger than >2GB. My largest file is about 12GB and it gets backed up fine. > >Did you check the log files for error? I am also using build 649 and I definitely have a problem with large databases being cut off at the 2GB mark. I am using a windows 64 bit client with a Linux 32 bit server. Need to find an answer to get this working sooner than later. Anyone have any ideas? Thank you,

Hi Sam, Thank you for posting in Synametrics Support forums. This behavior is not normal for Syncrify and is most likely a configuration issue on your machine. Ives, the original poster of the this thread, contacted support during which we found that the backup repository was out of disk space. Please contact support for help as this is an issue isolated to individual systems. We have tried recreating this error on our end, but were not successful. Feel free to call us by phone. Thank you, Synametrics Support >>I am using the latest version (build 649) and can definitely backup file larger than >>2GB. >My largest file is about 12GB and it gets backed up fine. >> >>Did you check the log files for error? > >I am also using build 649 and I definitely have a problem with large databases being >cut off at the 2GB mark. I am using a windows 64 bit client with a Linux 32 bit server. > Need to find an answer to get this working sooner than later. Anyone have any ideas? >Thank >you,

I was able to solve the problem by specifying a new temp location for the work being done in the background. I used this post as a reference http://web.synametrics.com/syncrifytempfolder.htm and all is well now. Thank you for the help. >Hi Sam, > >Thank you for posting in Synametrics Support forums. This behavior is not normal >for Syncrify and is most likely a configuration issue on your machine. > > >Ives, the original poster of the this thread, contacted support during which we found >that the backup repository was out of disk space. > > >Please contact support for help as this is an issue isolated to individual systems. > We have tried recreating this error on our end, but were not successful. Feel free >to call us by phone. > >Thank you, > >Synametrics Support > >>>I am using the latest version (build 649) and can definitely backup file larger >than >>>2GB. >>My largest file is about 12GB and it gets backed up fine. >>> >>>Did you check the log files for error? >> >>I am also using build 649 and I definitely have a problem with large databases being >>cut >off at the 2GB mark. I am using a windows 64 bit client with a Linux 32 bit server. >> >Need to find an answer to get this working sooner than later. Anyone have any ideas? >>Thank >>you,

Basically did the same thing as Sam, i.e. moved the entire repository path. Ever since, SQL databases above 2 GB back-up just fine. A bit of a shame it took so much trouble, but all's well that ends well.