Fujitsu Logo
ENQUIRE

    Questions you may have regarding Fujitsu Enterprise Postgres Operatoricon-elephant-low-poly-3d-variation-02-emerald-container-white

    Backup

    Q Can the number of backups held also control PVCs and S3?

    A Yes.

    Q Can I perform backups on demand?

    A Yes. A shell is available so you can perform backups on demand.

    kubectl exec -c fepbackup fepcluster-sts-0 -- fepbackup.sh full

    Q What happens if you perform a later backup when a backup is already running?

    A The CronJob or pgBackRest feature prevents duplicate runs, so subsequent backups will not work.
    A running backup continues.

    Q Is the backup process a Kubernetes Job?

    A Kubernetes CronJob kicks pgBackRest in the backup container of the Master POD.

    Q Where can I get more information regarding FUJITSU Enterprise Postgres?

    A Review this website or contact our experts.

    Q For PostScript, which container is it running in? When are they running?

    A Executed in the backup container of the Master POD before pgBackRest.

    Q Is it possible to connect to PGDATA dir with pre/postscript??

    A Yes.

    Q How do I check the log of a scheduled backup?

    A Logs of scheduled backups can be viewed in either of the following ways:

    • Viewing logs for pods created by CronJob

    kubectl logs pod/{clusterName} -cronjobXXX

    Each time a scheduled backup is taken, a CronJob pod will be created with the name in the format {ClusterName} -cronjobXXX. The latest 3 pods will be stored, and older pods will be deleted. Users can view logs of each CronJob pod by running the kubectl logs command above.

    • Using the command below to go to the backup container and view the logs under /var/log/pgbackrest

    kubectl rsh -c fepbackup {MasterPodName}

    Q Can backup be switched on/off?

    A Yes, backup can be switched off by setting the schedule in the FEPCluster CR to 0, as follows:

    spec:
       fepChildCrVal:
          backup:
             schedule:
                num: 0  

    Q Can the initial backup be an incremental backup?

    A Yes, an initial backup can be taken by setting up an incremental backup. However, a full backup will be performed if an incremental backup is scheduled as the first backup, since incremental backups must be based on a full backup.

    Q Are there any limitations on the parameters of pgBackRest?

    A There are limitations, such as fixed directories. For details, refer to Fujitsu Enterprise Postgres for Kubernetes User's Guide > Chapter 2 - Overview of Operator Design > 2.3 - Design perspective of each feature > 2.3.5 - Scheduling backup from Operator.

    Restore

    Q When restore is performed to a new FEP cluster, does the connection of application switch automatically?

    A No, the connection has to be changed manually.
    You can change the connection destination of Pgpool-II from the old cluster to the new cluster by editing the FEPPgpool2 CR parameter fepclustername.

    Pgpool-II

    Q What should I do if the Pgpool-II container goes down?

    A If a Pgpool-II container goes down you don't need to do anything, it is automatically recovered.

    Note that connection from applications to the container are broken and will need to be re-established. For this reason, it is recommended to design application so that they automatically reconnect if connections are broken.

    Q What should I do if the FEP container goes down?

    A If an FEP container goes down you don't need to do anything, it is automatically recovered. In a redundant configuration, the master FEP container is switched and the FEP container that went down is repopulated as a replica.

    Note that connection from applications to the container are broken and will need to be re-established. For this reason, it is recommended to design application so that they automatically reconnect if connections are broken.

    Q Is it possible to have only one Pgpool-II container?

    A Yes, it is possible to deploy only one Pgpool-II container.

    Q When the CR of a Pgpool-II instance is changed to switch the connection to another FEP cluster, will the instance be redeployed? Will the user be disconnected from the database during redeployment?

    A Yes, Pgpool-II will be redeployed in this case.

    Connections requested to a Pgpool-II instance currently being redeployed will be denied. However, if there are multiple Pgpool-II instances configured, because the redeployment of Pgpool-II instances is conducted one by one, the user will be able to connect to the database through a Pgpool-II instance that is not going through redeployment.

    Q How do new users authenticate when connecting through Pgpool-II?

    A The server is accessed every minute to obtain information of the users registered in Fujitsu Enterprise Postgres. Therefore, a connection will be made as long as the new user is registered on the Postgres side.


    Find more about Fujitsu Enterprise Postgres Operator and Container
    img-mockup-laptops-showing-manual-fep-12-k8s-variation-02
    Learn about the solution and how to operate it in the OpenShift Container Platform.

    Benefits at a glance

    • Native - Runs solutions that support PostgreSQL as a platform
    • Secure - Transparent Data Encryption, Data Masking, Dedicated Audit Log
    • Fast - HTAP workload capabilities with Fujitsu's In-Memory Columnar Index
    • Portable - Supports hybrid platforms, built for amd64, s390x, and ppc64le

    Brochure

    Leveraged by the OpenShift Container Platform, Fujitsu Enterprise Postgres for Kubernetes is a hybrid multi-cloud database that integrates container operation for rapid deployments.

    img-flyer-1st-page-fep-for-k8s-14
    View