PepsiCo Backup Validation - smk7375/backup GitHub Wiki

PepsiCo Backup Validation

Overview

We are performing backups for the PepsiCo environments using an Azure DevOps pipeline, which is defined in the pepco-devops-pipeline.yaml file. The pipeline utilizes an agent hosted on Jump Server 35.

Backup Environments

Backups are performed for three environments:

  1. Development (dev)
  2. Production (prod)
  3. Pre-production (preprod)

Each environment has its own configuration file that stores variables specific to that environment.

Backup Types

The following backups are taken for each environment:

  1. Cognos DB2 Backup
  2. Velero Backup
  3. PAW Backup

Validation of Backups

1. Cognos DB2 Backup

To validate the Cognos DB2 Backup (which includes both the DB2 online backup and DB2 config backup) for any environment (dev, prod, or preprod), follow these steps:

  1. Login to the Jump Server 35.
  2. Login to the agent machine as the user iacsadm11.
  3. Navigate to the working directory (pepco-backup):
    • Path: /data/iacsadm11-azdevops-agent/1/s/pepco-backup
working directory
  1. Open the host file for the relevant environment (dev, prod, or preprod) to get the details of the Cognos server.
  2. Login to the Cognos server using the SSH command:
    ssh <Cognos_Server_IP>
  3. Navigate to the backup location for the DB2 Online Backup:
    • Path: /data/DB2/online-backup-db2
online_baackup_db2
  1. Navigate to the backup location for the DB2 Config Backup:
    • Path: /data/DB2/backup-conf

config backup_db2
  1. Verify that both the online and config backups have been successfully created.

2. Velero Backup

To validate the Velero Backup for any environment (dev, prod, or preprod), follow these steps:

  1. Login to the Jump Server 35.

  2. Login to the agent machine as the user iacsadm11.

  3. Login to the OpenShift cluster of the specific environment using the following command:

    oc login --server=https://<ocserver-url>:<port> -u <username> -p <password>
    • Replace <ocserver-url> with the OpenShift server URL of the environment.
    • Replace <port> with the appropriate port number (e.g., 6443).
    • Replace <username> and <password> with the correct credentials for the environment.
  4. List Velero Backups for the specific environment using the following command:

    velero get backup
velero_get_backup_dev
  1. Verify that Velero backups for the specific environment have been successfully created.

3. PAW Backup

To validate the PAW Backup for any environment (dev, prod, or preprod), follow these steps:

  1. Login to the Jump Server 35.

  2. Login to the agent machine as the user iacsadm11.

  3. Login to the OpenShift cluster of the specific environment using the following command:

    oc login --server=https://<ocserver-url>:<port> -u <username> -p <password>
  4. Navigate to the backup location for the PAW backup:

    • Path: /data/backup
paw_backup_folder
  1. Go to any folder of the environment to list the successfully created PAW backups and open the generated backup to see the details of the backup.
environment_folder_ls inside_paw_backup
  1. Verify that PAW backups for the specific environment have been successfully created.

Conclusion

Each environment (dev, prod, preprod) has specific backups that need validation. Ensure that all steps outlined above are completed for each environment to guarantee the success of the backup and restore processes.

⚠️ **GitHub.com Fallback** ⚠️