1 Paneles de control local y
LISTA DE REFERENCIAS DE SEÑALES A SUPERVISAR Y TELEMANDAR
3.3.1 Descripción del sistema.
Vembu OnlineBackup can be configured to backup PosgreSQL Database(s) available in the local machine. Vembu OnlineBackup uses the internal PostgreSQLDump utility (pg_dump) to backup PosgtreSQL Database(s) and it uses the PostgreSQL utility (psql) to list the database names in the Step 2 of the 'Additional Backups -‐> PosgreSQL' page.
Before a PostgreSQL backup can be configured in Vembu OnlineBackup, you should configure the PostgreSQL settings through "Settings and click on the "PostgreSQL Settings" icon in the left hand side. Without correct values for PostgreSQL settings,Vembu OnlineBackup will not be able to list the databases to be configured for backups in "Additional Backups -‐> PostgreSQL" page.
If "PosgreSQL" database(s) is not listed in the Step 2 of the 'Additional Backups -‐> PostgreSQL' page, then refer the PostgreSQL Settings help for more details.
Vembu OnlineBackup | Admin User Guide | PostgreSQL Database Backup and Restore 168
PostgreSQL Backup Configuration
Step 1: Schedule Name
The first step in configuring a backup is to give a name for the backup schedule. The backup schedule name will uniquely identify the backup. While restoring your backup data, you need to choose the data to be restored using its schedule name.
Step 2: Select Database(s)
Select the databases that need to be backed up as a part of this schedule.
Select All Databases for this schedule
If "Select All Databases for this Schedule" option is chosen, it will include all the databases present in the PostgreSQL server. If a new database is later added to the PostgreSQL Server, it will be automatically included in this backup schedule.
Let me manually choose databases
If "Let me manually choose databases" option is chosen, then any databases can be selected for backup. However, if a new database is later added to the PostgreSQL Server, it will not be automatically included in this backup schedule.
Step 3: Set Basic Configuration
Backup Type
Vembu OnlineBackup provides 2 types of Backup options.
1. Seed Backup – With this option you can seed backup to local drive which you can
migrate to the Vembu Cloud using USB/External Hard drives to avoid more network bandwidth. It can be done only with the initial Full backup and incremental backup will not be continued.
2. Vembu Cloud – With this option you can directly backup the data into the Vembu Cloud
over the Internet.
Test connectivity -‐ Before you proceed with the backup, you can check the connectivity to
Backup Server (Vembu Cloud). It will check the Connectivity and DNS Lookup with the Vembu Cloud.
Retention Policies
Vembu OnlineBackup provides the retention feature where backups of multiple versions of a file can be maintain at the Vembu Cloud. Vembu OnlineBackup cleans up the version files in the Vembu Cloud based on two major retention policies:
1. Version-‐Based Retention -‐ Retains multiple version files in the Vembu Cloud based on the version file count.
2. Time-‐Based Retention -‐ Retains multiple version files in the backup up server based on the age of the version files.
1. Version-Based Retention
Vembu OnlineBackup can retain backups of multiple versions of a file based on the version retention count specified. The number of version files to be retained can be specified as any value from 0 to 99 with a default setting of 5.This option is useful when you wish to store just the complete latest version of a file.
For example, if the version file retention count is specified as 5, then Vembu OnlineBackup retains the latest five version files. These files can be restored from the Vembu Cloud at any point of time. When the sixth version of the file is created, Vembu Cloud automatically deletes the first version.
2. Time-Based Retention
Vembu OnlineBackup can retain version files in the Vembu Cloud based on the age of version files. Default setting is for 5 years, meaning the version files will be retained in the Vembu Cloud for 5 years and then will be removed automatically. The maximum number of versions that can be created during the retention period can also be optionally further configured. There are two options:
o Any number of versions can be created within this retention period -‐ This is the
default setting. If enabled, Vembu OnlineBackup retains all the versions created during the specified retention time period.
o Restrict the maximum number of versions that can be created within this
retention period to 'n'. -‐ If this option is enabled, Vembu OnlineBackup will clean up the version files based on both; retention time period and maximum version file count. For example, if the retention time period is set to 1 month and maximum version file count is 5, Vembu OnlineBackup will retain only the last five version files created within the last one month and versions older than one month with be deleted.
Vembu OnlineBackup | Admin User Guide | PostgreSQL Database Backup and Restore 170
Step 4: Scheduling Options (Timings)
In PostgreSQL Backup we can perform 3 types of scheduling options as per the requirements.
Run Every Few Minutes
Choose the hours/minutes interval between each time Vembu OnlineBackup must run. If Vembu OnlineBackup is restarted in the interim, the backup will run once Vembu OnlineBackup starts. Thereafter, Vembu OnlineBackup automatically reschedules the next backup after the period you’ve set. For example, if you created a backup schedule at 10 am and set it to run every 1 hour, Vembu OnlineBackup will first run the schedule at 10am and the next scheduled time will be 11am. However, if at 10.15am, Vembu OnlineBackup is restarted, then the
schedule will run once at 10.15am and the next scheduled time will now be set to 11.15am.
Additionally, you can also select the days in which this schedule should run. For example, if you do not want to run this backup schedule on Saturdays and Sundays, uncheck the check box against these days. If the "Select all days" check box is checked, then the schedule will be run on all the days of the week.
Run Daily
Choose the time at which the backup should run daily. This will execute the backup everyday at the time you have provided. Unless you’ve selected the “Run this Backup each time Vembu OnlineBackup restarts” option in Advanced Options, Vembu OnlineBackup will run at the stipulated time only.
Run Weekly
Choose the time and the day of the week the backup should run. Vembu OnlineBackup will execute the backup every week on the particular day and time chosen. Note that you can select multiple days of the week if you wish to run the backup on multiple days of the week. Unless you’ve selected the “Run this Backup each time Vembu OnlineBackup restarts” option in Advanced Options, Vembu OnlineBackup will run at the stipulated time/day only.
Step 5: Additional Full Backups
Typically, you would do a full backup first time you backup your data and thereafter only do incremental backups. However, like in a typical enterprise scenario, if you want to run full backups periodically and run the incremental backups in between two full backups, then you can configure the scheduling for how to run the full backups here.
For Run Every Few Minutes and Run Daily backups, the Additional Full Backup settings will allow you to configure daily/weekly/monthly additional full backups. For weekly backups, only
Monthly additional full backups are possible.
Additionally you can specify the maximum number of full backups that need to be stored in the server. For example if you configured a weekly backup and additionally if you configure a monthly full backup, then Vembu OnlineBackup will take a full backup the first time and then weekly do an incremental backup. The next month, Vembu OnlineBackup will do a new full backup and subsequently run the weekly incremental backup over this full backup. After 6 months you will have 6 separate full backups in the Vembu Cloud along with weekly
incremental versions under each of the 6 full backups. If your policy is to retain only backup data for 6 months, then you can configure "Store maximum of 6 full backups" here. On the 7th month, Vembu OnlineBackup, after finishing the 7th full backup, will delete the first full backup along with its weekly incremental backups thus retaining always the last 6 month backups.
Advanced Options
If you want to configure some additional advanced options -‐ like, Data Integrity, etc. click on the Advanced Options button.
Vembu OnlineBackup | Admin User Guide | PostgreSQL Database Backup and Restore 172
Advanced Backup Schedule Settings
There are several options here on how the backup should be scheduled.
1. Run this backup each time Vembu OnlineBackup restarts – If you enable this option by checking the check box, then this backup schedule will be run every time Vembu
OnlineBackup is restarted or the machine is rebooted irrespective of the actual schedule time of this backup schedule. This is to ensure that any modified or new files created when Vembu OnlineBackup was down are backed up as soon as possible. In case of the Continuous backup or ‘Run every…’ scheduling options, backups will run each time Vembu OnlineBackup restarts – by default.
2. Run this backup immediately after saving this configuration (thereafter, Backups will be scheduled as per the schedule stipulated) -‐ If you enable this option, then this backup schedule will be executed once immediately after you save this backup schedule – even if it's not yet ‘time’ as per the schedule. For example if you configure a daily backup at 10.00 AM but you configured the backup at 8.00 AM, then the backup schedule will be run once immediately (8.00 AM) and then as per schedule (e.g. daily at 10.00 AM). 3. Attempt to run this backup every 5 minutes in case of non completion because of a problem
(Network error etc.) -‐ If enabled, the user can choose to reschedule this backup every 5/10/15/20/25/30 minutes, whenever an attempted backup is incomplete because of a network error, server crash etc. The number of times the backup will be rescheduled (due to an error) can be configured to be in between 1-‐5 or unlimited, with the default setting as 5. This is to ensure that an incomplete backup is completed as soon as possible without waiting for the next actual schedule time. Note that this option is enabled by default.
4. Data Integrity Check -‐ Vembu OnlineBackup supports data integrity check where the data sent from the client machine is verified for integrity at the Vembu Cloud. When a file's integrity check fails, Vembu OnlineBackup flags that file as skipped and the file is then again backed up during the next backup schedule.
Pre & Post Backup Commands (Optional)
This feature provides the ability to configure running custom actions before and after executing a backup schedule. The custom actions may include running an application or some script files.
When is this feature useful?
If an application has exclusively locked a file and you need to close the application before Vembu OnlineBackup can backup that file, then you can run a Pre-‐backup command to close the application and then a post-‐backup command to open the application again after Vembu OnlineBackup successfully backs up the file.
How does this feature work?
Whenever a backup schedule starts, Vembu OnlineBackup will start the Pre Backup commands and wait till the timeout value. After completing the Pre Backup commands, Vembu
OnlineBackup will transfer the configured files & folders to the Vembu Cloud. After transferring the configured files and folders, Vembu OnlineBackup will run the Post Backup Commands. If multiple servers are configured for the backup schedule, then both the Pre and Post Backup commands will run while backing up to each of the servers.
Pre & Post Backup command settings:
You can provide maximum of 5 Pre Backup commands and maximum of 5 Post Backup commands for each backup schedule. Both the Pre and Post Backup commands are optional.
1. Command Name: This filed is mandatory. This is the command that should be run. The command should be provided with full path. If the command name is in the system command path, then providing full path for the command is not necessary. The command can be an executable file such as application exe, batch files, script files etc. Example: C:\MyTools\myzip.exe. A simple zip tool which compresses the given files or folders.
2. Arguments: You can provide any command line arguments for the command to be executed.
Example: For the Command C:\MyTools\myzip.exe, the arguments may be 'High Zip Replace "D:\Project" myproject.zip' [without quotes]. Here, the High may denote high compression, Zip denotes zip file format, Replace denotes replacing existing files, 'D:\Project' denotes folder to compress and 'myproject.zip' denotes the target compressed file name.
Vembu OnlineBackup | Admin User Guide | PostgreSQL Database Backup and Restore 174 3. Working Path: This field specifies the directory path from which the Command has to be
run. If this field is left empty, then the command will be executed from the Vembu OnlineBackup working path [Vembu OnlineBackup Home]
Example: 'D:\Project'. The command will be executed from the directory D:\Project. 4. Timeout: This filed is used to specify a timeout value, in seconds, for the command to
finish execution. Vembu OnlineBackup will wait for so many seconds for the Pre and post command to finish running. If the command still runs beyond the timeout period, then Vembu OnlineBackup will abruptly terminate the command and will continue with the backup schedule.
Please note that if you provide -‐1 value, then the command will run till completion and Vembu OnlineBackup will wait till the command completes. If command never
completes, then Vembu OnlineBackup may just infinitely wait without proceeding with the backup schedule.
Example: 60. For the myzip.exe command, the myzip.exe command will compress the given project folder up to 60 seconds. If the myzip.exe completes before the timeout period, say 15 seconds, then Vembu OnlineBackup will immediately continue the next Pre Backup Command [if configured] or continue with the backup schedule.
So, the example command will look like below: Command Name : C:\MyTools\myzip.exe Arguments: High Zip Replace
Working Path : D:\Project Time out : 60
The whole command will be run up to 60 seconds as below: C:\MyTools\myzip.exe High Zip Replace "D:\Project"
Saving the configured backup
Once all the SharePoint components to be backed up are chosen and the configuration options are set, you simply need to click on the "Configure/Save Backup” button to activate the backup as per the schedule-‐ on to the configured on Vembu Cloud.
Troubleshooting Tips
Error: Database names are not listed in the Step 2 of the 'Additional Backups -‐>
PostgreSQL' page.
Cause1: If PostgreSQL Settings for Vembu OnlineBackup is not configured.
Solution: Configure postgreSQL settings from "Settings menu "PostgreSQL Settings" icon in
the left hand side and then check if PostgreSQL database(s) are listed in the "Additional Backups -‐> postgreSQL" page.
Cause 2: If PosgtreSQL service is not started in the machine.
Solution: Start the PostgreSQL service and then check if PostgreSQL database(s) are listed
in the "Additional Backups -‐> PostgreSQL" page.
Cause 3: postgresqldatabase.lst file present in the
"<INSTALLATION_HOME>/plugins/PostgreSQLServer/" folder does not have the database list.
Solution: Check the PostgreSQL version running in the machine (8.3 and above). Vembu
OnlineBackup only supports listing PostgreSQL 8.3 and above version database(s) for backup.
Error: Database names are listed in the Step 2 of the 'Additional Backups -‐>
PostgreSQL' page, but backup dump is not created.
Cause: Configured username and password in the PostgreSQL settings page may not
have access to the database(s) configured for the backup schedule.
Solution: Check if the user name and password entered in the PostgreSQL settings have
appropriate permissions to take a backup dump of the database(s).
Limitations
Ø Databases listed in the "Additional Backups -‐> PostgreSQL" page will be for the the last saved PostgreSQL Server instance port in the PostgreSQL Settings.
Ø Backup Report/View Backup/Edit Backup UI pages does not provide the details like PostgreSQL Server name, port etc.
Vembu OnlineBackup | Admin User Guide | PostgreSQL Database Backup and Restore 176
Restore PostgreSQL database
Restoring a database is sometimes necessary when a database becomes corrupt. You can restore your PostgreSQL Server databases using your most recent full backup. This section gives you information on how to restore PostgreSQL Server database using Vembu OnlineBackup.
Restoring PostgreSQL databases require a couple of extra steps. Please follow the instructions detailed below in sequential order.
1. Follow the steps for a regular restore operation and restore the required database backup files.
2. Once restored, the required files are now in their designated locations: <Restore
Path>\<Temp_Dump_Location>\<Backup_Name>\<Database_Name>\<Restore_File_Na me>
The restored PostgreSQL database files end with an extension ".sql". In order to use the restored database, please follow the steps given below:
i. If the restoring database is unavailable in PostgreSQL Server, create the database using the command "createdb <DB_NAME>".
ii. Reload the database with the data using psql -‐U [username] [<DB_NAME>] < [<Restore
Path>\<Dump_Location>\<Backup_Name>\<Database_Name>.sql]. This will dump the sql back to the database.