Copy Storage

Offsite Storage preparation

On Vinchin Backup & Recovery, an offsite storage is dedicated for offsite (remote) backup copy to keep the backup data safe from site-level disasters. Below are some prerequisites of adding an offsite storage.

• There should be 2 data centers in 2 different locations, each should have a Vinchin server deployed.
• The remote site Vinchin server should have an onsite backup copy storage added.
• Primary site and remote site should be interconnected via dedicated connection or VPN connection, if there's firewall, service port 23005 needs to be accessible on the remote site Vinchin server. If the connection goes directly through Internet, the remote site must have a dedicated public IP address, and on the remote site firewall/router, the service port 23005 needs to be opened for the remote site Vinchin server.
• Bandwidth between 2 sites must be fast enough to transfer new backup data generated during the previous copy job session to the next copy job session.

Notice:

For offsite copy feature, the remote site Vinchin server does not require a paid license (if the remote site Vinchin server is dedicated for backup copy and does not need backup functionalities). A free license designated for offsite copy will be delivered along with the paid license of the primary site Vinchin server.

Offsite Storage Adding

To add an offsite copy storage, please open the web console of the primary site Vinchin server, go to Resources > Storage > Storage List page and click on Add button.

1. In Storage Type dropdown list, select Off-site Storage.
2. In the IP Address field, type the IP address of the remote site Vinchin server. As for the default port number, if modification is required, please contact Vinchin Support for help, otherwise please do not modify it.
3. In the Username and Password fields, type the web admin credentials of the remote site Vinchin server. After filling in the username and password, click on the Scan offsite backup system button.
4. Select a storage from the offsite Vinchin server as offsite copy storage from Storage Resource.
5. In the Storage Name field, give the storage a custom name for identification.
6. An offsite storage is used for offsite backup copy only, so, the Storage Usage is set to Copy by default and cannot be changed.
7. The Auto Detect option allows you to auto import backups according to the auto import time interval. If you enable the Auto Assign option, the imported backups will be automatically assigned to the user who added this storage device.
8. Optionally setup the Storage Alert as per your requirement.
9. Click on OK to add the offsite copy storage.

PostgreSQL offsite copy

To create a database copy job, please go to Data Resilience > Copy page, select the Database module, and create a new copy job.

The New Copy Job wizard for database opens. Please complete the wizard follow the below steps.

Select Copy source

As for Copy source type, you can choose one from Backup job, Backup Data, Copy Job and Copy Data, then you can select based on the storage categories you've added. Also, the storage where backup/copy data is located can be filtered.

• Users can directly select offsite copy job or restore points as the source to create new copy job for migrating off-site copy data.
• If the backup or copy job has been deleted or it's a once-off backup job, you can filter the backup data by selecting Restore Points.

You can select the copy source either way as per your convenience. Once the copy source is selected, please click on Next button to continue.

Copy Strategy

General Strategy

Under the General Strategy tab, you can setup the Copy Type, Schedule, Throttling Policy, Retention Policy.

In the Source Type dropdown, you can select the copy source as Mirror Copy.

• Mirror Copy: entire backup/copy chain will be replicated completely without the data merging.

In the Schedule dropdown list, you can choose to setup a Once-off Copy job.

Notice:

As for the schedule of the copy job, it is recommended to run the copy job right after the associated job finishes. For example, the backup job runs at 11 PM each day, and it takes approximately 2 hours to complete the backup job, so you can set the copy job to start 3 or 4 hours later than the backup job.

For Throttling Policy, it's optional, only if the copy jobs will bring network or I/O overload to your production environment, you can configure the throttling policy accordingly. The throttling policy can be configured as Customized Policy or Select Global Policy.

Transmission Strategy

Transmission Strategy contains some transmission options for the copy job.

Encrypted Transfer: use the RSA encryption algorithm by default to transfer the copy data for the data security.

For Transfer Threads, you can enable multithreaded transmission to improve the processing speed of the copy job. The default value for multithreaded transmission is 3, even if you can set the value from 1 to 8, but usually 3 threads will be enough.

Security Policy

For WORM Protection, you can only enable this option when selected storage device with the WORM protection feature enabled. Backup points with WORM Protection enabled cannot be modified or deleted and their retention period can only be extended until they expire. The default protection period is 7 days, and the support range is 1 to 9999 days.

Advanced Strategy

Retry Policy:

Retry Attempts and Retry Interval ensure the copy job continues to proceed within the set retry attempts and retry interval when the network connection the copy storage is not well.

Retry Attempts: the number of retry attempts for reconnecting when the network connection is lost. The default number of retry attempts is 60, with a maximum of 999 and a minimum of 0, where 0 represents infinite retries.

Retry Interval: retry interval can be specified between each attempt when the network is disconnected during copy job execution to avoid copy job failure. The default reconnection interval is 30 seconds, with a maximum interval of 60 seconds and a minimum interval of 5 seconds.

Overload Protection: If resource limitation are set on the backup node, backup jobs running on the corresponding node will be restricted. Backup jobs are subject to resource limitation by default. For jobs with a higher running priority, you can enable this setting to ignore the node resource limitation.

Review & Confirm

After completing the above-mentioned settings, you are able to review and confirm the settings in one screen. A job name can be specified for identification of the copy jobs, and by clicking on the Submit button to confirm the settings and create the copy job.

Copy Retrieve

When you need to use replica data stored remotely locally, you need to use the Copy retrieve function.

Please redirect to Data Resilience -- Copy -- Database -- Retrieve to get your offsite copy data to local.