This article describes how to change the Oracle database mode.
Before starting the Oracle database backup task, make sure that the database mode is set to ARCHIVELOG. To verify that the mode is configured correctly or to change it, open the command line as the user configured in the backup plan and run the sqlplus tool using the following command:
sqlplus / as sysdbaYou can then close this tool using the QUIT; command.
To verify that the database mode is correctly set to ARCHIVELOG, run the following command:
SELECT LOG_MODE FROM v$database;If the database mode is set to NOARCHIVELOG, change it to ARCHIVELOG.
You can switch the database mode from NOARCHIVELOG to ARCHIVELOG using the following commands:
Now, verify that the database mode has been changed successfully by running the following command:
This article describes how to change the temporary folder used for database backup dumps.
When creating a backup plan, in the Data to protect section, select the folder where database dumps will be stored. You can choose either Select from device or Select path or variable — switch between these options by clicking on the text in the list.
Create a new temporary folder.
Go to the Plans tab and edit the plan you want to change or create a new one.
In the Data to protect section, uncheck the old folder and select the new one (if you're creating a new plan, simply select the newly created temporary folder from the list).
Next, go to Advanced settings, then Backup scripts, and update the script arguments to the new database dump location.
Save the changes.
SHUTDOWN IMMEDIATE;
STARTUP MOUNT;
ALTER DATABASE ARCHIVELOG;
ALTER DATABASE OPEN;
QUIT;SELECT LOG_MODE FROM v$database;
This article describes how to configure the Oracle database environment in Xopero ONE.
The Oracle database backup process in Xopero ONE consists of two stages:
Creating a database dump using backup scripts.
Backing up the created dump file.
The first stage is executed through Xopero ONE using the backup scripts feature, while the second stage is performed as a standard file-level backup.
Xopero ONE creates a full database copy using the RMAN tool. It does not interfere with other copies performed by RMAN, but the backup created by Xopero ONE will be visible in RMAN.
The Oracle database environment must operate in ARCHIVELOG mode. For instructions on how to change the database mode, refer to .
Log in to XMS, go to the Backup tab (Plans > Backup) and click the + Add plan button in the top toolbar.
Select Devices from the platforms list.
Add a new user (for example, dbuser) to the Linux operating system by executing the following command:
Add the user to the dba group, which has permission to perform backups:
Finally, configure the system environment variables by following the instructions in .
In the next aside, select Files & folders option and choose one or more devices for the plan to apply to (you can also select the plan to include all activated devices).
Define the name of the backup plan.
Configure your backup plan according to your needs (more information about the backup plan setup can be found in this article).
Go to the Advanced settings section and click Edit to customize additional options.
Scroll down to the Backup scripts section and click the Pre-task script toggle to turn it on.
Select the script dedicated to backing up the Oracle database environment.
Set up the script arguments — it should be entered in the Script arguments field as follows:
ORACLE_SID;dbuser;temp_directoryORACLE_SID — the database identifier.
dbuser — the name of the user with backup privileges (for example, database_user). This must be a local Linux OS user with permissions to back up the Oracle environment. Instructions for creating this user are provided in the section of this article.
temp_directory — the directory where the Oracle tool will temporarily write backup files. After the backup tasks are complete, these files will be deleted. This directory must also be included in the Data to protect section when creating a .
You can enable the two additional options using the checkboxes:
Wait for the script to continue the task — the application will wait until the dump is ready.
Fail the task if the script fails — if the script fails, the system will notify you of the backup error.
Double-check your settings and click Save to close the Advanced settings aside.
After completing the configuration, click the Save button. The protection plan will then automatically begin protecting your devices and databases according to the schedule you defined.
sudo useradd dbusersudo usermod -a -G dba dbuser
This article explains how to use backup scripts to create a MySQL database dump and include it in a backup plan.
The MySQL database backup process in Xopero ONE consists of two steps:
Creating a database dump using backup scripts.
Backing up the database dump.
The first step is performed through Xopero ONE using the backup scripts feature. The second step is a standard file-level or image-level backup executed directly by Xopero ONE.
By using the mysqldump tool, Xopero ONE supports all MySQL versions that are officially supported by Oracle.
Log in to XMS, go to the Backup tab (Plans > Backup) and click the + Add plan button in the top toolbar.
Select Devices from the platforms list.
This article describes how to prepare a Linux operating system for backing up an Oracle database environment.
Using the Linux command line, log in to the account used for backing up your Oracle database and execute the following commands:
echo 'connect target /; quit' | rmanecho 'SELECT INSTANCE_NAME FROM V$INSTANCE;' | sqlplus / as sysdbaIf these tools are unavailable (example below) you need to configure the environment variables.
Edit the /home//.bash_profile file and add the following records:
Now, after logging in again, executing the following commands should complete successfully.
Once done, your Linux system should now be ready to backup an Oracle environment.
export ORACLE_SID=<database_ID>export ORACLE_HOME=database_directoryexport PATH=$ORACLE_HOME/bin:$PATHecho 'connect target /; quit' | rmanecho 'SELECT INSTANCE_NAME FROM V$INSTANCE;' | sqlplus / as sysdbaIn the next aside, select one of the available options and choose one or more devices for the plan to apply to (you can also select the plan to include all activated devices).
Define the name of the backup plan.
Configure your backup plan according to your needs (more information about the backup plan setup can be found in File-level backup and Image-level backup articles).
Go to the Advanced settings section and click Edit to customize additional options.
Scroll down to the Backup scripts section and click the Pre-task script toggle to turn it on.
Select one of the scripts dedicated to backing up the MySQL database environment (Windows or Linux).
Type your database username into the Database user field.
Choose the user password by opening the Password Manager, where you can either add a new password or select an existing one.
Set up the script arguments — it should be entered in the Script arguments field as follows:
database output_dir mysqldump_dir portdatabase output_dir portdatabase — the name of the database. To include multiple databases in one backup plan, enter their names in the following format: [database1 database2 database3]. To back up all databases, use the --all parameter instead of specifying a database name.
output_dir — the directory where the database dump will be saved. This directory must also be selected in the Data to protect section when creating a backup plan.
mysqldump_dir — the path to the mysqldump utility.
port — an optional parameter. Enter the port number only if a non-standard port is used. The default port is 3306.
For example, to back up all databases from the MySQL environment, use the following arguments:
If you want to back up only selected databases from the MySQL environment (for example, two out of seven), use the following arguments:
Enable the two additional options using the checkboxes:
Wait for the script to continue the task — the application will wait until the dump is ready.
Fail the task if the script fails — if the script fails, the system will notify you of the backup error.
Double-check your settings and click Save to close the Advanced settings aside.
After completing the configuration, click the Save button. The protection plan will then automatically begin protecting your devices and databases according to the schedule you defined.
That’s all you need to do to create the database dump — this file should now be included in the Data to protect section if you are performing a file-level backup (to back up only the database). Alternatively, you can run an image-level backup to protect the entire drive.
This article explains how to configure the Microsoft SQL database environment using Xopero ONE.
The Microsoft SQL database backup process in Xopero ONE consists of two steps:
Creating a database dump using backup scripts.
Backing up the database dump.
The first step is performed through Xopero ONE using the backup scripts feature. The second step is a standard file-level or image-level backup executed directly by Xopero ONE.
Log in to XMS, go to the Backup tab (Plans > Backup) and click the + Add plan button in the top toolbar.
Select Devices from the platforms list.
In the next aside, select one of the available options and choose one or more devices for the plan to apply to (you can also select the plan to include all activated devices).
Define the name of the backup plan.
Configure your backup plan according to your needs (more information about the backup plan setup can be found in File-level backup and Image-level backup articles).
Go to the Advanced settings section and click Edit to customize additional options.
Scroll down to the Backup scripts section and click the Pre-task script toggle to turn it on.
Select the script dedicated to backing up the Microsoft SQL database environment (Windows).
Type your database username into the Database user field.
Choose the user password by opening the Password Manager, where you can either add a new password or select an existing one.
Set up the script arguments — it should be entered in the Script arguments field as follows:
copy_type server_name "output_dir" database1 database2 ... databaseNcopy_type — defines the type of copy to be performed. You can choose one of three options: full_only, full_diff, or copy_only:
full_only — always performs a full copy.
full_diff — performs differential copies with periodic full copies.
copy_only — creates a full database copy without affecting the regular backup cycle.
server_name — the name of the Microsoft SQL server along with its instance.
output_dir — the directory where database dumps will be saved. This directory must also be selected as the location to back up.
database1 database2 (...) — names of databases to be backed up, separated by spaces. You can leave this parameter empty — if no database is specified,
You can enable the two additional options using the checkboxes:
Wait for the script to continue the task — the application will wait until the dump is ready.
Fail the task if the script fails — if the script fails, the system will notify you of the backup error.
Double-check your settings and click Save to close the Advanced settings aside.
After completing the configuration, click the Save button. The protection plan will then automatically begin protecting your devices and databases according to the schedule you defined.
That’s all you need to do to create the database dump — this file should now be included in the Data to protect section if you are performing a file-level backup (to back up only the database). Alternatively, you can run an image-level backup to protect the entire drive.
--all C:\MySQLBackup\ "C:\Program Files\MySQL\MySQL Server 8.0\bin"database1 database2 C:\MySQLBackup\ "C:\Program Files\MySQL\MySQL Server 8.0\bin"
This article explains how to configure the PostgreSQL database environment in Xopero ONE.
To maintain data consistency, Xopero recommends using a dedicated backup type: a file-based backup with a pre-backup script for the PostgreSQL database.
Database backup begins with a script that requests the database server to create a dump in a temporary directory. Once the dump is complete, Xopero ONE backs up the generated dump file.
Xopero ONE uses the pg_dump utility to back up PostgreSQL databases.
full_diff WINSRV-2019\SQLEXPRESS "C:\MsSQLDumps" database1 database2Select Devices from the platforms list.
In the next aside, select one of the available options and choose one or more devices for the plan to apply to (you can also select the plan to include all activated devices).
Define the name of the backup plan.
Configure your backup plan according to your needs (more information about the backup plan setup can be found in File-level backup and Image-level backup articles).
Go to the Advanced settings section and click Edit to customize additional options.
Scroll down to the Backup scripts section and click the Pre-task script toggle to turn it on.
Select the script dedicated to backing up the PostgreSQL database environment.
Type your database username into the Database user field.
Choose the user password by opening the Password Manager, where you can either add a new password or select an existing one.
Set up the script arguments — it should be entered in the Script arguments field as follows:
database output_dir "pg_dump_dir" port_numberdatabase — the name of the database to back up. A backup plan can target a single database or all databases. To back up all databases, use the --all parameter instead of specifying a database name.
output_dir — the directory where the database dump will be created; this is also the folder that Xopero ONE will back up.
pg_dump_dir — the path to the pg_dump utility. This is required only for PostgreSQL databases hosted on Windows.
port_number — required only if your PostgreSQL server uses a non-standard port (other than 5432).
You can enable the two additional options using the checkboxes:
Wait for the script to continue the task — the application will wait until the dump is ready.
Fail the task if the script fails — if the script fails, the system will notify you of the backup error.
Double-check your settings and click Save to close the Advanced settings aside.
After completing the configuration, click the Save button. The protection plan will then automatically begin protecting your devices and databases according to the schedule you defined.
