Please keep the questions coming if anything else comes up. Better to start a new thread if the topic changes. And you also have access to our Support team, if needed, for more expedited service or if you run into a more complicated issue. But you can always start on the forums.

Having local storage (NAS / File Server / SAN) will certainly help restore speeds. A low-latency, 10 GbE connection to RAID storage or any fast disk should result in far faster restores than pulling that data from the cloud over the internet. And that's how many of our customers operate. Local storage is used, if available, while cloud is used for restoring data from outside the office or in the case of disaster.

When you define the storage in the administration console, if you enter a share name, then you're prompted to enter the credentials (User Name / Password) needed to access the share.

I would like to add that Hybrid backups work by first backing up data to the file system and then reading the backed up data from the file system and copying it to cloud storage. Normally, this method results in the best performance as it only requires a single read of the source data and file system storage is normally local and high-speed. However, in your case, you are using a VPN over the internet to an NFS share. Re-reading that data may be more time-consuming than running two backups: One to the NFS storage and one to the cloud. You'll have to test performance.

1. Is there a reason you are not using Hybrid Backups? A hybrid backup plan would back up to file system storage and cloud storage in a single pass, reducing your IO on the computer by half and eliminating overlaps.

2. If you want to keep the plans separate, then you can easily use the Backup Chain option on the Pre / Post Actions to kick off the second plan once the first one completes. That would also eliminate any overlapping plans.

That should be fine as long as the remote computer can see the storage over the VPN. Obviously, if the VPN is not running or the Managed Backup Service Account cannot access the network share, you'd have an issue.

Just to confirm, you are running a Hybrid backup to cloud storage and file system storage. The file system storage is located on a remote PC, accessible via a VPN. Correct?

What account are you using for the backup service? Can that account access the remote share over the VPN?

sounds like the computer on which the agent is installed cannot see your file system storage. How do you have it set up?

The easiest way to do this is to use a Lifecycle Policy with a service like AWS to move data as it ages to less expensive storage classes like S3-Intelligent Tiering and Glacier. The other option is to back up old files to less expensive cloud storage and use a second plan for newer files.

Just to confirm, you are saying you have 4.8 Mbit Upstream connection speed, resulting in upload speeds of 600 KB / Sec. I'd estimate you're looking at a minimum of 4 hour+ upload time for that file at that speed, assuming you're able to use all available bandwidth.

Can I ask why you're using Glacier Direct as your target? Is this simply for archival reasons. Meaning, you do not have any plans to access that data unless something critical happens and you're also planning on leaving it in Glacier for at least 90 Days to avoid early deletion fees?

Upload issues can be caused anywhere in the chain. It's impossible to guess what's going on. What are your Chunk Settings? There's a section in Options called Glacier Multi-Part Upload.

You can have a look at the Log to see if anything interesting is being reported regarding the transfer to Glacier. Look at the Diagnostic and Logging section in Options. Feel free to post any log items that are of concern. Please do not attach the entire log file as they contain information that you may not want public.

I'm not sure - I'd wait it out as it might be a simple screen update issue. What is your upload bandwidth? Because you are going direct to Glacier, and Glacier is designed as archive storage, you may not get the same level of real-time reporting as other storage classes.

You can find the differences here. https://www.msp360.com/explorer/licensing/

Yes, Multi-Part Uploads are supported, but the free edition does not support multi-threading. So based on the way you formed your question, I'm going to say the free version does not support the feature you are requesting. I believe the default chunk size is 5 MB, but set accordingly to your upload bandwidth. Reducing the number of chunks may speed up the uploads as it reduces IO.

If you need multi-threading, then you'd have to consider upgrading to the paid version.

Any refund requests would need to be discussed with your account manager. If you are not sure who manages your account, then please submit your question / request via this page: https://www.msp360.com/contact.aspx?category=sales

Yes, we support that. Please refer to this article: https://www.msp360.com/resources/blog/resuming-image-based-backup-in-msp360-backup-6-0/

I have added multiple accounts. I recommend you implement and let us know if you have any issues.

Then you need to open a support case either from a working install or directly on the web site https://www.msp360.com/support.aspx?select=true I deleted your log file attachment as those files may contain information you do not want available publicly.

Some of those changes may speed up the sync process, but I'm still waiting on word as to whether there's anything specific being added for drive rotation. Can you go into more detail about your use case for needing to use drive rotation versus performing either local + cloud hybrid backups or simply copying changed files from one NAS to the other before escorting one home at night?

I do not have a firm date yet on the release. I'll have to check with the team in any new features related to disk rotation, but I'm not aware of any offhand. I'd be interested in your disk rotation needs though. Are you rotating NAS devices or external hard drives hooked up to an endpoint / server? Any information would be helpful. Thanks.

I do not believe there is any hard limit on the number of accounts you can add. You can add multiple accounts and mount drives as needed.

Make sure LAN Direct and Internet Direct connection options are enabled in the Options - Incoming Connection - Miscellaneous section. If a direct connection cannot be established then transmission would go through our servers. In what region are you located? We currently have servers in North America, Europe, and Australia - the region closest to you is automatically selected.

For direct connections, MSP360 Remote Desktop leverages the UPnP protocol.If that protocol is blocked or otherwise unavailable, the fallback would be to go through our servers, but additional latency may be visible depending on your location.

Once connected, make sure the View Options to Hide Desktop Wallpaper and Disable Aero are selected - Image Quality will likely default to High Color, but you can try 256 Colors to see if it helps and maintains sufficient image quality. Lastly check the Remote Screen Resolution - try reducing it as that will reduce the data that needs to be sent. You might also find a clean desktop helps - you can quickly hide all desktop icons on the remote system: Just right-click an empty area of the desktop and select View and then uncheck Show desktop icons from the context menu.

First, before I answer, I want to say the team changed terminology recently in what these backups are called and it's confusing to many.

Second, you do not need the block-level backup option if you do not want it. All block-level does is back up all changed / new files and may back up only the changed portion of larger files. If you do not have large files that change in a small way or you'd prefer to back up all files that change in full every time, then do not use the block-level option.

Third, if you decide to use both backups because you have large files like Outlook PST files that change little day-to-day, but are large, and you do not want to back up the entire file every time it changes, then do not schedule both job types at the same time (there's no benefit). Schedule the incremental, say every 14 days, and the block-level every day. Your actual schedule may depend a lot on your retention settings. When the block-level runs, all files that changed will be backed up - but some may just have their internal file changes backed up. When the incremental runs, all files that changed will be backed up in their entirety.

If you wanted to keep 14 days of backups, but used a 30 day Incremental Backup schedule and daily block-level backups, you'd have to store about 44 days of each file before the original backup set of 30 days of that file could be deleted from backup storage. Instead, you'd be better off using a 7 day incremental backup schedule. That way, after 21 days, the first 7 days could be removed, leaving you with 14 days of backups. Feel free to post your actual retention needs if you have questions. Or, if you don't have large files that would benefit from block-level backups, then schedule the incremental daily or more frequently as needed.

Anyone else having notification issues? Please open a Support case so the team can review. Thanks.