Feb 21, 2023 · Feb 15, 2023 · Feb 21, 2023
diff --git a/_docs/administration/codefresh-on-prem-upgrade.md b/_docs/administration/codefresh-on-prem-upgrade.md

 > If you run [**external** Postgresql service]({{site.baseurl}}/docs/administration/codefresh-on-prem/#configuring-an-external-postgres-database) (i.e. `postgresql.enabled=false` is specified in `config.yaml`), you can skip the following instruction.

 > **Important!** Run the upgrade with `global.seedJobs=true` flag:
 ```yaml
 global:
  seedJobs: true
 ```

 ##### Manual backup and restore

 **Before the upgrade:**
 Restore the contents of the backup into the new release using the *pg_restore* tool. If this tool is not available on your system, mount the directory containing the backup files as a volume in Bitnami's PostgreSQL Docker container and use the *pg_restore* client tool in the container image to import the backup into the new cluster, as shown below:
 ```shell
 cd psqlbackup
 docker run --rm --name postgresql-backup -e PGPASSWORD=$PGPASSWORD -v $(pwd):/app --net="host" bitnami/postgresql:13 pg_restore --Fc --create --dbname postgres -h host.docker.internal -p 5432 /app/audit.dump
 docker run --rm --name postgresql-backup -e PGPASSWORD=$PGPASSWORD -v $(pwd):/app --net="host" bitnami/postgresql:13 pg_restore -Fc --create --dbname postgres -h host.docker.internal -p 5432 /app/audit.dump
 ```

 ##### Backup and restore via Helm hooks

 > If you run [**external** MongoDB service]({{site.baseurl}}/docs/administration/codefresh-on-prem/#configuring-an-external-mongodb) (i.e. `mongo.enabled=false` is specified in `config.yaml`), you can skip the following instruction.

 > **Important!** Run the upgrade with `global.seedJobs=true` flag:
 ```yaml
 global:
  seedJobs: true
 ```

 ##### Manual backup and restore

 **Before the upgrade:**
Original file line number	Diff line number	Diff line change
Expand Up		@@ -471,6 +471,12 @@ From version 1.4.0 and higher, we have deprecated support for the `Codefresh

		> If you run [external Postgresql service]({{site.baseurl}}/docs/administration/codefresh-on-prem/#configuring-an-external-postgres-database) (i.e. `postgresql.enabled=false` is specified in `config.yaml`), you can skip the following instruction.

		> Important! Run the upgrade with `global.seedJobs=true` flag:
		```yaml
		global:
		seedJobs: true
		```

		##### Manual backup and restore

		Before the upgrade:
Expand DownExpand Up		@@ -514,7 +520,7 @@ kubectl port-forward --namespace codefresh svc/cf-postgresql 5432:5432
		Restore the contents of the backup into the new release using the pg_restore tool. If this tool is not available on your system, mount the directory containing the backup files as a volume in Bitnami's PostgreSQL Docker container and use the pg_restore client tool in the container image to import the backup into the new cluster, as shown below:
		```shell
		cd psqlbackup
		docker run --rm --name postgresql-backup -e PGPASSWORD=$PGPASSWORD -v $(pwd):/app --net="host" bitnami/postgresql:13 pg_restore --Fc --create --dbname postgres -h host.docker.internal -p 5432 /app/audit.dump
		docker run --rm --name postgresql-backup -e PGPASSWORD=$PGPASSWORD -v $(pwd):/app --net="host" bitnami/postgresql:13 pg_restore -Fc --create --dbname postgres -h host.docker.internal -p 5432 /app/audit.dump
		```

		##### Backup and restore via Helm hooks
Expand DownExpand Up		@@ -547,6 +553,12 @@ From version 1.4.0 and higher, we have deprecated support for the `Codefresh

		> If you run [external MongoDB service]({{site.baseurl}}/docs/administration/codefresh-on-prem/#configuring-an-external-mongodb) (i.e. `mongo.enabled=false` is specified in `config.yaml`), you can skip the following instruction.

		> Important! Run the upgrade with `global.seedJobs=true` flag:
		```yaml
		global:
		seedJobs: true
		```

		##### Manual backup and restore

		Before the upgrade:
Expand Down