Forgot to hit the reply button first^^^^

Old backup programs are always uninstalled after the first successful backup and restore.

Restarting VSS and running the backup does help, but the error just happens again in a couple days. The backups also complete successfully when run manually with having to do any restarting. It's just when the scheduled backup runs that this error is observed.

The issue was just the fact that full image backups cannot be browsed for individual files in the online portal. This applies to both S3 and B2. As soon as I set up the file level backup the files were immediately available in the online portal. I did the file backup in B2 and it has been working fine.

I appreciate your help. I just created an account on S3 and started our first test backup. I'm hoping to kill all three birds with one stone and I will let you know how it goes.

That does sound like the best option. Thanks for your help!

Thanks for the reply! I will look into that link, but if you do get any word about a feature in MBS do let me know!

That's exactly what I was looking for, thank you so much!!

I'm confused as to why this wasn't added as a secondary option. In MBS there are many tiers of licenses, and having the ability to just backup files on a domain PC to a local server is our primary goal. When speaking with your sales department they offered the MBS file level license at a slightly discounted rate, but since the cost for that is re-occurring the cheaper option would have been to stick to the increased rate of the desktop backup.

We have been using this desktop software in congruence with MBS to backup the workstations to the servers and having the added features at almost double the cost per computer has made it hard to use. Since we only use the image backups for servers I was wondering if there was a possibility to have the old feature set available for the old price. Since workstations on a domain cannot use the freeware we have to use the paid version, but we are only using it to backup files locally to a server.

Just looked through the log to see if I could find those errors (As I have seen them before) but it seems that this is a different issue. I can upload the whole log if needed.


2018-03-15 21:46:36,643 [Base] [11] ERROR - Request failed, retrying in 400 msec, 3 attempts left
System.IO.IOException
Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host.
at System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.Security._SslStream.StartWriting(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security._SslStream.ProcessWrite(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.ConnectStream.InternalWrite(Boolean async, Byte[] buffer, Int32 offset, Int32 size, AsyncCallback callback, Object state)
at System.Net.ConnectStream.Write(Byte[] buffer, Int32 offset, Int32 size)
at xa.Write(Byte[] , Int32 , Int32 )
at xD.Write(Byte[] , Int32 , Int32 )
at xm.A(Stream , Stream , Int32 , ICancelable )
at uW.A(uR )
at uW.B(uR )
at uW.b(uR )
at uW.C(uR )
System.Net.Sockets.SocketException
An existing connection was forcibly closed by the remote host
at System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32 size)

2018-03-15 21:46:43,194 [Base] [4] WARN - MemoryManager: Memory allocation limit is used. Available: 14376192, Need: 100000000
2018-03-15 21:46:43,195 [Base] [4] WARN - Allocating 100000000 bytes store on disk.
2018-03-15 21:46:44,331 [Base] [12] ERROR - Request failed, retrying in 400 msec, 3 attempts left
System.IO.IOException
Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host.
at System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.Security._SslStream.StartWriting(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security._SslStream.ProcessWrite(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.ConnectStream.InternalWrite(Boolean async, Byte[] buffer, Int32 offset, Int32 size, AsyncCallback callback, Object state)
at System.Net.ConnectStream.Write(Byte[] buffer, Int32 offset, Int32 size)
at xa.Write(Byte[] , Int32 , Int32 )
at xD.Write(Byte[] , Int32 , Int32 )
at xm.A(Stream , Stream , Int32 , ICancelable )
at uW.A(uR )
at uW.B(uR )
at uW.b(uR )
at uW.C(uR )
System.Net.Sockets.SocketException
An existing connection was forcibly closed by the remote host
at System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32 size)

2018-03-15 21:48:09,986 [Base] [4] WARN - MemoryManager: Memory allocation limit is used. Available: 14376192, Need: 100000000
2018-03-15 21:48:09,986 [Base] [4] WARN - Allocating 100000000 bytes store on disk.

I have not received a response yet.

Thank you

Sounds good, I'll update this post tomorrow following the next backups.

The MBS backup is just cloud, we already have a system for local backups. The instance sizes range from around 200gb of data backed up to just over 1tb. Some of our customer's ISPs are very fast while others are not so much. The synthetic backup looks good except we would have to switch over to S3 (currently on B2).

My question is does the versions kept apply to every backup done? or just the files themselves. Like does the backup consist of 7 changes of each file that is purged? If there is any documentation on the retention policy I would be happy to take a look at it.

Thank you both for your replies. Those links have really good information, especially the "Block Level Backup and Full Backup Explained" linked in the article that Denis linked.

Our current schedule for backups is:
Backup options:
Compression: enabled
Encryption: disabled
Retention policy:
purge version older than 7 day(s)
keep only 7 versions
Schedule backup:
Occurs every week on Monday, Tuesday, Wednesday, Thursday, Friday at 12:00 AM.
Full backup options:
Full backup schedule:
Occurs every week on Saturday at 12:00 AM.

This was created during a remote session with a support rep and I wanted to confirm that what we are doing is not incorrect. The RTO and RPO are definitely going to be customer specific and that will be something I will have to go over with them. For the time being, I wanted to get the current situation in order. From what I read in the article linked above the "Full Backup" does not reimage the server, but reuploads all the files that had previously been backed up using block level backup. That does make a lot of sense so what I had thought of doing is performing a block level backup two-three times a day and a full backup once a night at midnight. What I wanted to confirm is how many versions we wanted to keep in the cloud. As I had said before with our current local backups we can see the previous versions going back years so to cut costs I would like to have only 1-2 versions available. Storage space is the main deterrent from keeping more versions and I would like to keep the backups as small as possible.

Let me know what you guys think.

That did the trick, thank you so much!

I have tried to use that before but it seems like I am trying to reinvent the wheel. Is there any way I can copy the code from the default backup email notifications and just add the backup plan name to the email subject?