If you get the following error message during a backup:
[JOB-BAK:1301#1] Failed to backup <database name> database with "Full" backup type: Failed to backup <database name> database. There is no destination selected to keep Full database backup type. Continue reading [JOB-BAK:1301#1] Failed to backup database. There is no destination selected to keep Full database backup type
If the following error message happens:
[DST-1:1003#53] Destination error: Failed to open "\\networkpath\backupfolder" destination connection. > The network path was not found
Continue reading [DST-1:1003#53] The network path was not found
Typically, the following error message:
Destination error: Could not find a part of the path 'y:\1'.
Destination error: #[DST-1:1001#103] Failed to connect to the Folder destination. > Failed to create folder "y:\1". > Could not find a part of the path 'y:\1'.
Continue reading [DST-1:1001#103] Destination error: Could not find a part of the path
During the backup you can face the following warning:
[Warning] [JOB-BAK:2006#11008]. The previous full backup of <database name> database was created with a different application (non-SQLBackupAndFTP). You may not able to restore the database automatically using SQLBackupAndFTP.
Continue reading Solved: [JOB-BAK:2006#11008] Previous Full backup of a database was created with a different application
If, after installing PostgreSQL, you face “psql not recognized as an internal or external command” error when you try to run psql from the command prompt, then most probably all you need to do to solve this problem is to add Postgres’s bin directory to the PATH system variable (the PATH is a system variable which allows Windows with the help of the Command prompt or the Terminal window find executables).
In this blog post, we’ll share seven simple steps that describe how to add the folder to the Windows 10 PATH variable.
Continue reading Setting Windows PATH for Postgres tools
How do you make your PostgreSQL database backups, with the help of pg_dump utility or in any other way? Do you prefer to store your backup in the cloud, like Amazon S3? How much time do you usually spend every day to make your database backup and send them to Amazon S3? It is really very easy to backup PostgreSQL to Amazon S3 with the help of SQLBackupAndFTP. You can create a backup job just in a few minutes. Continue reading How to Backup PostgreSQL to Amazon S3
In this blog post, we are going to discuss causes, reasons, and solutions related to the following error “Unable to Create a PostgreSQL Instance”. Here are the error messages you can receive:
Invalid PostgreSQL User Name and Password.
Connection to PostgreSQL server failed.
Continue reading Unable to Create a PostgreSQL Instance
We spent several hours composing PostgreSQL String Functions Cheat Sheet. It’s yours now, enjoy ))
Are you sure that your method to backup PostgreSQL databases is reliable, safe, and convenient? What if you need to backup your database somewhere to the cloud, let’s say to Azure Storage. How much time will you spend every day to complete this scenario? You can do it simply with the help of SQLBackupAndFTP. Below we are going to show you how to create a backup job that will backup PostgreSQL to Azure Storage on a regular basis. Continue reading How to backup PostgreSQL to Azure Storage
PostgreSQL doesn’t provide a built-in job scheduler like MS SQL, MySQL, and Oracle do. So if you need to run recurring tasks (like database backup), you have to use some other external tools like pgAgent, corn, or pg_cron (on Linux), and Task Scheduler (on Windows). Let’s look at these options closer.
Continue reading PostgreSQL Job Scheduler