Platform/OS
Cross-platform
Category
Backup & Recovery
MSP360 Managed Backup Service
MSP360 Managed Backup Service is a simple online backup tool that businesses and IT teams use to automatically protect their important files, servers, and computers. It quietly makes copies of your data every day so you can quickly recover everything if a computer crashes, gets hacked, or a file gets deleted by mistake. It connects to S3-compatible object storage to keep these backup copies safe, spreading them across many secure locations so they stay protected even if one hard drive fails. Using S3 storage helps MSP360 keep costs low while giving you fast access to your backed-up files whenever you need them without worrying about running out of space. This combination means small businesses get enterprise-level protection at a price they can afford, with the peace of mind that their data is stored reliably in the cloud.
Connection / Setup
- Create an account and log in to DiskSpace
- Click I'm ready to set up my storage
- Enter Bucket Name following the instructions
- Click Create Bucket and wait for it to be generated
- Find your Endpoint URL, Access Key, and Secret Key in the S3 Client Configuration section for use below
Connecting DiskSpace.sh to MSP360 Managed Backup Service
DiskSpace.sh is a fully S3 API compatible storage solution. Follow the steps below to configure MSP360 Managed Backup Service to use DiskSpace.sh as your storage destination.
Connection Steps
- Log in to the MSP360 Management Console and open your backup plan or create a new one.
- Navigate to the Storage or Destination section and select Amazon S3 Compatible Storage.
- Enter the following connection details:
Use this exact endpoint URL.
Can be left empty or set to us-east-1.
Important: Path-Style Requests Required
DiskSpace.sh requires path-style URLs (not virtual-hosted style). MSP360 will automatically use the correct format when the endpoint is configured as shown above.
Example URL Format
https://s3.diskspace.sh/bucket-name/key
Troubleshooting Tips
- Ensure you are using the exact endpoint: https://s3.diskspace.sh
- Verify that both Access Key and Secret Key are copied correctly without extra spaces.
- If connection fails, try setting the Region explicitly to us-east-1.
- Confirm that your bucket name follows S3 naming rules and that you have full permissions.
- MSP360 must be allowed to use path-style addressing for this endpoint.
Once configured, test the connection within MSP360 before running your first backup.