This guide explains how to implement BorgBackup for efficient backups on a ServerStadium dedicated server. BorgBackup is a fast, secure, and deduplicating backup solution designed to efficiently store your data while minimizing storage space. By deploying BorgBackup on our high-performance dedicated servers, you can ensure reliable data protection and streamlined backup management.

Prerequisites

Before you begin, ensure you have the following:

• A ServerStadium dedicated server running Ubuntu (or a similar Linux distribution).
• Basic command line knowledge and sudo privileges.
• Familiarity with backup concepts and Linux system administration.

Deployment Steps

1. Update Your System

Start by updating your system packages to ensure you have the latest updates and security patches:

sudo apt-get update && sudo apt-get upgrade -y

2. Install BorgBackup

Install BorgBackup using the package manager:

sudo apt-get install borgbackup -y

3. Initialize a Backup Repository

Create a directory to serve as your backup repository and initialize it with Borg:

mkdir -p /path/to/backup_repo
borg init --encryption=repokey /path/to/backup_repo

Replace /path/to/backup_repo with your desired backup directory path.

4. Create a Backup Archive

To create a backup of your important data, run:

borg create /path/to/backup_repo::archive-{now:%Y-%m-%d} /path/to/data_to_backup

This command creates a backup archive named with the current date. Replace /path/to/data_to_backup with the directory or files you wish to back up.

5. Automate Your Backups

To automate the backup process, schedule a cron job. Edit your crontab:

sudo crontab -e

Add a line to run your backup script daily at 2 AM:

0 2 * * * /usr/bin/borg create /path/to/backup_repo::archive-{now:%Y-%m-%d} /path/to/data_to_backup

Post-Deployment Configuration

After setting up BorgBackup, consider these enhancements:

• Regularly test your restore process to ensure data integrity.
• Configure automated cleanup policies to prune old archives and free up space.
• Monitor backup logs and repository status for any errors or warnings.

Hosting your BorgBackup solution on a ServerStadium dedicated server provides the high-performance, scalable infrastructure required to ensure efficient and secure backups.

Troubleshooting

If you encounter issues during setup or while running backups:

• Review BorgBackup logs and error messages for troubleshooting hints.
• Verify that your backup repository is accessible and has sufficient storage.
• Consult the BorgBackup documentation for advanced configuration options.
• Refer to our guides in the ServerStadium Knowledge Base for further assistance.

Conclusion

Implementing BorgBackup for efficient backups on a ServerStadium dedicated server offers a secure, fast, and storage-efficient solution for safeguarding your critical data. By following this guide and utilizing automation, you can maintain a reliable backup system that supports your business continuity needs. For more help or information about ServerStadium services, visit our knowledge base or the ServerStadium website.

The post Implementing BorgBackup for Efficient Backups on ServerStadium Dedicated Servers appeared first on ServerStadium.

This tutorial explains how to deploy a dedicated backup solution using Bacula on a ServerStadium dedicated server. Bacula is an open-source network backup solution that provides enterprise-level backup, recovery, and verification of data across a network of computers. Leveraging the robust performance of ServerStadium dedicated servers, you can build a reliable and scalable backup infrastructure to safeguard your critical data.

Prerequisites

Before you begin, ensure you have the following:

• A ServerStadium dedicated server running Ubuntu (or a similar Linux distribution).
• Basic command line knowledge and sudo privileges.
• Familiarity with backup concepts and network configuration.

Deployment Steps

1. Update Your System

Begin by updating your system packages to ensure you have the latest updates and security patches:

sudo apt-get update && sudo apt-get upgrade -y

2. Install Bacula Packages

Install Bacula and its components (Director, Storage Daemon, and Console) using the package manager:

sudo apt-get install bacula bacula-common bacula-dir bacula-sd bacula-console -y

This command installs Bacula along with its common files and essential daemons for managing backups.

3. Configure Bacula

Edit the Bacula configuration files to suit your backup environment. The main configuration files are located in /etc/bacula/. For example, open the Bacula Director configuration:

sudo nano /etc/bacula/bacula-dir.conf

Review and adjust settings such as the catalog database, job definitions, schedules, and client configurations. Similarly, configure the Storage Daemon and Console by editing bacula-sd.conf and bacula-console.conf respectively.

4. Initialize the Bacula Catalog

Create and initialize the Bacula catalog (database) which is used to store backup job information. Follow the instructions provided in the Bacula documentation for setting up the catalog. Typically, this involves running commands like:

sudo bacula-dir -t -c /etc/bacula/bacula-dir.conf

If the test is successful, proceed to populate the catalog.

5. Start Bacula Services

Start the Bacula services (Director, Storage Daemon, and Console) and enable them to run at boot:

sudo systemctl start bacula-dir
sudo systemctl start bacula-sd
sudo systemctl start bacula-console

sudo systemctl enable bacula-dir
sudo systemctl enable bacula-sd
sudo systemctl enable bacula-console

6. Test Your Backup Setup

Run a test backup job to ensure that Bacula is properly configured and that your data can be backed up and restored successfully. Monitor the job logs and check the Bacula console for job status.

Post-Deployment Configuration

After deploying Bacula, consider the following enhancements for a robust backup environment:

• Schedule regular backup jobs and verify the integrity of your backups.
• Configure email notifications or alerts for backup job statuses.
• Implement secure authentication and firewall rules to protect Bacula services.
• Periodically test your restore process to ensure data can be recovered efficiently.

Hosting your Bacula backup solution on a ServerStadium dedicated server guarantees the high performance, scalability, and reliability required for enterprise-level data protection.

Troubleshooting

If you encounter issues during deployment or operation:

• Ensure all prerequisites and Bacula packages are correctly installed.
• Review configuration files in /etc/bacula/ for errors.
• Check service logs for Bacula components (Director, Storage Daemon, Console) located in /var/log/bacula/ or via journalctl.
• Consult the Bacula documentation and our guides in the ServerStadium Knowledge Base for additional assistance.

Conclusion

Deploying a dedicated backup solution with Bacula on a ServerStadium dedicated server provides a robust and scalable framework for comprehensive data protection. Leverage our high-performance hosting services to ensure your backup infrastructure is reliable, secure, and capable of meeting the demands of your business. For more help or information about ServerStadium services, visit our knowledge base or the ServerStadium website.

The post Deploying a Dedicated Backup Solution with Bacula on Dedicated Servers appeared first on ServerStadium.

This guide explains how to deploy a custom backup solution using rsnapshot on a ServerStadium dedicated server. rsnapshot is a filesystem snapshot utility for making automated backups, offering a reliable and efficient way to secure your data. With our high-performance dedicated servers, you can implement a robust backup strategy tailored to your needs.

Prerequisites

Before you begin, ensure you have the following:

• A ServerStadium dedicated server running Ubuntu or a similar Linux distribution.
• Basic command line knowledge and sudo privileges.
• Understanding of backup concepts and familiarity with rsnapshot.

Deployment Steps

1. Update Your System

Keep your system up-to-date for security and performance. Open your terminal and run:

sudo apt-get update && sudo apt-get upgrade -y

2. Install rsnapshot

Install rsnapshot from the package repository:

sudo apt-get install rsnapshot -y

3. Configure rsnapshot

Edit the rsnapshot configuration file located at /etc/rsnapshot.conf to set up your backup intervals, retention periods, and directories to back up:

sudo nano /etc/rsnapshot.conf

Key configuration settings include:

• snapshot_root – the directory where backups will be stored.
• no_create_root – optional setting to prevent rsnapshot from creating the root backup directory.
• retain – specify the number of daily, weekly, or monthly snapshots to retain.
• backup – define the directories or files to back up.

Save and exit the editor after adjusting the settings to match your backup requirements.

4. Test the rsnapshot Configuration

Run a test backup to ensure the configuration is correct:

sudo rsnapshot configtest

If the configuration test passes, execute a manual backup:

sudo rsnapshot daily

5. Automate Backups with Cron

To automate backups, create a cron job. Open the root user’s crontab for editing:

sudo crontab -e

Add a line to schedule backups. For example, to run a daily backup at 2 AM:

0 2 * * * /usr/bin/rsnapshot daily

Post-Deployment Configuration

After configuring rsnapshot, consider the following for optimal backup performance:

• Regularly verify your backup integrity by testing restore procedures.
• Monitor backup logs for any errors or issues.
• Adjust retention policies based on your storage capacity and backup needs.

ServerStadium’s dedicated servers offer the reliability and performance necessary to support a robust backup solution using rsnapshot.

Troubleshooting

If you encounter issues during deployment or operation:

• Ensure all prerequisites are installed and the system is up-to-date.
• Review the rsnapshot configuration file for errors.
• Check log files for backup errors or permission issues.
• Consult our guides in the ServerStadium Knowledge Base for further assistance.

Conclusion

Deploying a custom backup solution using rsnapshot on a ServerStadium dedicated server ensures your critical data is safely backed up and easily recoverable. Leverage our high-performance hosting services to maintain data integrity and business continuity. For more help or information about ServerStadium services, visit our knowledge base or the ServerStadium website.

The post Deploying a Custom Backup Solution Using rsnapshot on Dedicated Servers appeared first on ServerStadium.

Acronis on-premises and cloud backup and recovery software products have the reputation of being user-friendly, stable, and innovative. Its software has been designed to use minimal CPU and memory and can also be written to different destinations, including storage arrays, the cloud, and tape. This gives administrators greater flexibility with regard to mixing and matching media and destination types within their data backups.

Acronis supports many Operating Systems like Microsoft Windows, Linux, macOS, etc. Thus, we can use Acronis as a robust backup facility for many servers and VM’s in various Operating Systems.

Here are the steps for backing up a Linux VM via Acronis in ServerStadium.

Prerequisites

– VM installed with Linux OS (for this case, we use CentOS 7).
– Security Profile with list opening ports below :

TCP port 43234 for remote installation and remote upgrade
TCP ports 445 and 25001 for remote installation
TCP port 6109 for Active Protection
TCP ports 7780, 7755, 7756, 7765, 9852, 9860, 9862, 9876, 9877 for communication between components
TCP ports 9850 and 9851 for command line (acrocmd, acropsh) commands
TCP ports 443 and 902 to access the vCenter Server and ESX(i) hosts
TCP ports 443 and 44445 for backup to cloud
TCP port 30800 and 30801 for Alert Feed Manager
TCP port 2600, 2700 for Archive Server Core
TCP port 6110 for Acronis Cyber Protect service
TCP port 31009 for Active Protection Manager
TCP port 9773 for Antimalware backups scanning
TCP port 9999 for Authorization and routing requests for different components
TCP port 18018, 18019, TCP and UDP incoming port 6888, UDP port 6771 for Acronis updater
TCP port 1337 for syncing protection policies between server and agent
TCP port 8081 for Acronis Scheduler2 service
TCP port 9772 for Acronis Cyber Protect Agent

Preparation

For the CentOS (RHEL) based Linux, there are some packages needed by Acronis which is :

• kernel-devel
• gcc
• make
• elfutils-libelf-devel
• perl

Most of the packages above will be downloaded and installed when the Acronis setup program runs. But, for the Perl package, you have to install it manually by using the command :

# yum install perl

In some cases, the downloaded kernel-devel version does not match with the kernel build version when installing using the Acronis setup program. However, we have to download and install the binary package manually in this case.

To check the kernel-devel and perl installation, you can check it by using the command :

# yum list installed | grep kernel-devel

# perl --version

Installation

To begin with the installation process, first, open the Acronis portal with the URL link :

https://cloud.acronis.com/login

After that, add a new device. Then choose “Linux Servers”

Then SSH into your Linux VM, and download the Acronis Cyber Protection Agent Installer with the URL link :

https://sg-cloud.acronis.com/download/u/baas/4.0/15.0.27305/Cyber_Protection_Agent_for_Linux_x86_64.bin

The latest Acronis Cyber Protection Agent Installer version when this article was written is 15.0.27305. After the Acronis Cyber Protection Agent Installer is downloaded, change the permission of the file by adding “execute” permission with this command below :

# chmod +x Cyber_Protection_Agent_for_Linux_x86_64.bin

Execute the installer by using this command below :

# ./Cyber_Protection_Agent_for_Linux_x86_64.bin

The installer will start shortly. When the “Component Selection” pop-up appears, choose the “Agent for Linux” option. Then, proceed to the installation step with the “Next” button.

Another pop-up message will appear. Click the “Continue” button to install the additional package using “YUM“.

Wait for the installation progress until finished.

When the installation process is finished, due to the Linux VM with Command-Line Interface does not have a web browser installed in the first place, we have to register the VM manually by choosing “Show Registration Info” button.

Then, the registration Link and the Registration Code will appear in the next pop-up window.

Keep in mind that the Registration Code has an expiration of 1 hour. Therefore, you have to successfully register the machine in 1 hour period.

Open the Registration Link with your other device (PC, Laptop, Smartphone, etc), then enter the Registration Code that you got before, and click the button “Confirm Registration”.

After that, you will get a pop-up notification that the machine is successfully registered and will appear in the machine list.

Backup Configuration

The last step is we have to configure the backup plan of the Linux VM, in order to back up the VM data into Acronis. After the machine is successfully registered on the Acronis, click the machine on the “All devices” page. On the right side, a new sidebar will appear. Choose the “Protect” section, and click the “Create plan” button. Then, click the “Create” button.

After the “Create” button is clicked, a new page will appear. On this new page, you have to set up some parameters like :

• What is to backup –> Is it “Entire Machine”, “Certain Files / Folder”, “SQL data”, etc.
• Where to backup –> On the ServerStadium, currently, we have only one destination to backup. Which is the “Cloud Storage”.
• Backup schedule –> Monthly / Weekly / Daily / Hourly period.
• How long to keep the backup.
• Enable Encryption or Not.
• Enable Application backup or Not (Application Backup example is for Exchange Server, cPanel, SQL Server, etc).
• Enable Antivirus & Antimalware protection or Not.
• Enable Vulnerability assessment or Not.

Finally, the backup plan is created with the configuration setup above. Since our created backup plan above is scheduled, in order to trigger the backup process, we have to click the “Run now” button.

Wait for a while until the backup process is complete.

Then, after the backup process is successful, we have a few options to threaten this saved backup. Do we want only to keep this backup, recover this backup into the VM, or we can run this saved backup as a new VM if we choose the backup plan option “Entire Machine”. You can adjust this saved backup to meet your needs.

Conclusion

To sum up, in this guideline, we have installed and configured Acronis as a backup facility for backing up a Linux VM in ServerStadium. Also, we know that Acronis can be used as a robust backup facility that has the flexibility to meet user requirements in the Linux environment.

The post How to backup Linux VM via Acronis in ServerStadium appeared first on ServerStadium.

Acronis Cyber Protect is a backup solution provided by Acronis that integrates backup and recovery, disaster recovery, malware prevention, security controls, remote assistance, monitoring, and reporting. With Acronis Cyber Protect and your hosted VM on ServerStadium, you will achieve a 3-2-1 Backup Strategy which will let you have ease of mind with your data on the cloud.

Here are the thing you need to prepare before you start to backup your ServerStadium Windows VM using Acronis Cyber Protect.

Preparing the Infrastructure

First of all, you need a Windows virtual machine in ServerStadium Cloud Panel. You can read the detailed guides on how to create a new VM in this Knowledgebase article: Deploying a Virtual Machine in ServerStadium – Knowledge Base

After successfully deploying a Windows virtual machine in ServerStadium, you’ll need an Acronis Cyber Protect Backup solution subscription. You may use your own subscription or get one from us with a special price just by Contacting us.

Setting Up the Backup

After you have access to the Acronis Management Console, Login to it using your account. If you ordered the Cyber Protect Backup from us, you may access Management Console from this link : https://sg-cloud.acronis.com

After Acronis Management Console (MC) has opened, the next step is to add the VM to the Protection Plan. Click on the button on the top right location of the console. Then a sidebar will come up.

Since the type of your Windows VM is a Windows Server, click on Windows Button under the Servers group. After that, you will be asked to download the Acronis agent. Download and copy the agent to the VM we need to protect.

After the installer window is opened, click Install. After the installation is completed and the agent is registered, it will show up in the Console.

After the agent is recognized, we need to create a backup plan to protect the VM. We can set it up by clicking on the Gear Icon -> Protect -> Add Plan. In this article, we set the Protection Plan 1 day per week backup plan with 4 weeks of retention.

Since Acronis Cyber Protect also provides a score to evaluate a security issue within a protected VM, in the VM that we have protected, we can see the #CyberFit Score section to get the Initial Score.
Based on the initial score, the VM score is low due to poor setup. Perform all recommended fixes until the score shows green.

And that’s it!
We have successfully protected the VM with Acronis Cyber Protect. Your data will be kept safe from many risks or incidents.

In Case of an Emergency, Restore the VM

In any case of an emergency that needs you to restore the VM, you can easily perform it by following these steps:

Create a new VM on the ServerStadium Cloud Panel that will act as a restore container of the protected VM. Using the previously provided guide, create a new Windows VM in ServerStadium. After a new VM has been created. Login to the VM using the console

After that, setup the Agent in the new VM with a procedure that we’ve covered before. After the agent has been correctly configured, it will also appear in the Cyber Protect Console.
We don’t need to create a backup plan for this VM since this VM is only used as a recovery place for protected VM.

After that, log in to Acronis MC, select the protected VM, and click on Gear Icon -> Recovery. Then click on the preferred backup date and click on Recover, then Entire Machine.

Select the target machine to Target VM (in this case, errylab-dr). Then click on Start Recovery.

Now, we are waiting for the Recovery process to be completed.

After the recovery has been completed, we can check on the VM and log in.

In ServerStadium, the default Internal IP is a DHCP IP which is assigned by the system. Thus, we need to change the IP of the new VM to be the same as the old one.

And voila!
Your broken VM is now successfully restored. All with a few simple steps.

That’s it; we’ve covered backup and restoring VM on ServerStadium using Acronis Cyber Protect.
The conclusion is: A great backup strategy and solution doesn’t always need a super-sophisticated process; you only need a great backup solution and simple steps to follow.

The post Backing-Up ServerStadium Windows VM Using Acronis Cyber Protect appeared first on ServerStadium.