Frequent Contributor.. network Frequent Contributor..
Frequent Contributor..
209 views

Pre_bkp script issue

We are using pre and post script for our database backup. The script will change database in hot backup mode and update the snapshots and then snapshot will be mount in back server. Before issue ,backup completed with in 1 hour. The snapshot will mount in backup server with in 30 MIn . Now backup completion taking more than 3 hour. Now the snapshot will mount in backup server take 2 Hour. Please help me to solve this issue.

0 Likes
8 Replies
Frequent Contributor.. network Frequent Contributor..
Frequent Contributor..

Re: Pre_bkp script issue

Any one help me solve the issue

[Critical] From: BSM@xxxxxx.xxx.xxx.in "AMP_DB_BKP"  Time: 06-Oct-19 11:00:03 PM
[61:2012]   Session pre-exec script prebkp_xxxx.sh failed. Exit code = -2
 The session will not start.
[Critical] From: BSM@xxx-xx-xxx-xxxi-xxx.xxx.xxx.in "AMP_DB_BKP"  Time: 06-Oct-19 11:00:03 PM
 None of the Disk Agents completed successfully.
 Session has failed.
 

 

 

 

0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: Pre_bkp script issue

Hello @network,

This will be hard to tell because your "Pre_bkp" script was most likely created by someone in your company or the application vendor.

I would recommend troubleshooting the script itself. Data Protector only executes it as it is. So running the script or parts of it manually should help to find the root cause. Also ask the question "what was changed" in the environment.

Regards,
Sebastian Koehler

---
Please use the Like button below, if you find this post useful.
Frequent Contributor.. network Frequent Contributor..
Frequent Contributor..

Re: Pre_bkp script issue

Thanks for the update.

Last week , We done Red hat os upgrade from 6.2 to 6.8.After upgrade the issue is stared.

I check the log I didn't find any error.

Regards,

Deepu jose 

 

 

 

0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Pre_bkp script issue

The problem here is that DP does not manage the script, just run the script mentioned. If the script fails or shows an error or receives an incorrect output the backup will fail. 

In this case, the output received is this: Exit code = -2.
Normally the -2 refers to an OS error. 

What is the output if you run the command directly in the OS, not using DP? 

Andres Fallas Salazar
Customer Support Engineer

If you find that this or any other post resolves your issue, please be sure to mark it as an accepted solution.
If you are satisfied with anyone’s response please remember to give them a LIKE by clicking on the bottom at the left of the post and show your appreciation.
Frequent Contributor.. network Frequent Contributor..
Frequent Contributor..

Re: Pre_bkp script issue

When i started manually running same script  in backup server .

Showing same error .

Reading all physical volumes take more time.

Please go through below script:-

[Normal] From: BSM@xxxxxxxxx "xxxxx_Bkp" Time: 11-Oct-19 4:00:03 AM
Starting to execute "prebkp_xxxx.sh"...

* Root Login is not permitted *
-------------------------------
stty: standard input: Invalid argument
* Root Login is not permitted *
-------------------------------
stty: standard input: Invalid argument
pg_start_backup
-----------------
xxxx/xxxxxxx
(1 row)

* Root Login is not permitted *
-------------------------------
stty: standard input: Invalid argument
2019-10-11 03:37:03 IST Completed copy from VV xxxxxxxxx to VV xxxxxxxx.PC.
2019-10-11 03:49:22 IST Completed copy from VV xxxxxxxxx to VV xxxxxxxx.PC.
2019-10-11 03:34:16 IST Completed copy from VV xxxxxxxxxx to VV xxxxxxxx.PC.
2019-10-11 03:34:15 IST Completed copy from VV xxxxxxxxxxx to VV xxxxxxx.PC.
2019-10-11 03:34:14 IST Completed copy from VV xxxxxxxxxxx to VV dxxxxxxxxx.PC.
2019-10-11 03:36:02 IST Completed copy from VV xxxxxxxxxxxxx to VV xxxxxxxxxx_1.PC.

Rescanning /sys/class/scsi_host/host5
Rescanning /sys/class/scsi_host/host7
Rescanning /sys/class/scsi_host/host6
/opt/omni/lbin/prebkp_xxxx.sh: line 58: /sys/class/scsi_host/host8/scan: No such file or directory
Reading all physical volumes. This may take a while...
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 0: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 187904753664: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 187904811008: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 4096: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 0: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 107374116864: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 107374174208: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 4096: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 0: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 187904753664: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 187904811008: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 4096: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 0: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 10737352704: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 10737410048: Input/output error
/dev/mapper/3xxxxxxxxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 4096: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 0: Input/output error
/dev/mapper/3xxxxxxxxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 42949607424: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 42949664768: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 4096: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 0: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 5368643584: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 5368700928: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 4096: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 0: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 32212189184: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 32212246528: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 4096: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 0: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 42949607424: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 42949664768: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 4096: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 0: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 53687025664: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 53687083008: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 4096: Input/output error
/dev/mapper/3xxxxxxxxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 0: Input/output error
/dev/mapperxxxxxxxxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 107374116864: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 107374174208: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 4096: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxxxxxxxx1: read failed after 0 of 4096 at 0: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxxxxxxxx1: read failed after 0 of 4096 at 107374116864: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 107374174208: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 4096: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 0: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 161061208064: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 161061265408: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 4096: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 0: Input/output error
/dev/mapper/3xxxxxxxxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 107374116864: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 107374174208: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 4096: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 0: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 161061208064: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 161061265408: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 4096: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 0: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 53687025664: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 53687083008: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 4096: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 0: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 107374116864: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 107374174208: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 4096: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 0: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 10737352704: Input/output error

/dev/mapper/3xxxxxxxxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 4096: Input/output error
/dev/mapper/3xxxxxxxxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 0: Input/output error
/dev/mapper/3xxxxxxxxxxxxxxxxxxxxxxxxxxxxx1: read failed after 0 of 4096 at 10737352704: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 10737410048: Input/output error
/dev/mapper/3xxxxxxxxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 4096: Input/output error
/dev/mapper/xxxxxxxxxxxxxxxxxxxxxxxxxxxxx: read failed after 0 of 4096 at 0: Input/output error

Found volume group "xxxxx_vg" using metadata type lvm2
Found volume group "xxxxx_vg" using metadata type lvm2
Found volume group "xxxxx_vg" using metadata type lvm2
Found volume group "xxxxx_vg" using metadata type lvm2
Found volume group "xxxxx_vg" using metadata type lvm2
Found volume group "xxxxx_vg" using metadata type lvm2
Found volume group "vxxxxx" using metadata type lvm2
Found volume group "xxxxx" using metadata type lvm2
Found volume group "xxxxx_vg" using metadata type lvm2
Found volume group "xxxxx_vg" using metadata type lvm2
Found volume group "xxxxx_vg" using metadata type lvm2
[Critical] From: BSM@xxxxxxxxxxxxxxxxxxxxx "xxxx_Bkp" Time: 11-Oct-19 6:20:03 AM
[61:2012] Session pre-exec script prebkp_xxxx.sh failed. Exit code = -2
The session will not start.

[Critical] From: BSM@xxxxxxxxxxxxxxxxxxxx "xxxxxx_Bkp" Time: 11-Oct-19 6:20:03 AM
None of the Disk Agents completed successfully.
Session has failed.

[Normal] From: BSM@xxxxxxxxxxxxxxxxxxxxxxxxx "xxxxxx_Bkp" Time: 11-Oct-19 6:20:03 AM

Backup Statistics:

Session Queuing Time (hours) 0.00
-------------------------------------------
Completed Disk Agents ........ 0
Failed Disk Agents ........... 4
Aborted Disk Agents .......... 0
-------------------------------------------
Disk Agents Total ........... 4
===========================================
Completed Media Agents ....... 0
Failed Media Agents .......... 0
Aborted Media Agents ......... 0
-------------------------------------------
Media Agents Total .......... 0
===========================================
Mbytes Total ................. 0 MB
Used Media Total ............. 0
Disk Agent Errors Total ...... 0

[Warning] From: BSM@xxxxxxxxxxxxxxxxxxxxxxxx "xxxxxxxxxxx_Bkp" Time: 11-Oct-19 6:20:03 AM
Pre-exec script failed. Skipping Post-exec !

 

 

 

 

0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Pre_bkp script issue

Hello @network

If you run the script in OS level and shows the same issue, you will need to contact the person/team/vendor who give you the script. 

DP does not manage the script, just run it, if fails, DP fails too. 

Regards, 

Andres Fallas Salazar
Customer Support Engineer

If you find that this or any other post resolves your issue, please be sure to mark it as an accepted solution.
If you are satisfied with anyone’s response please remember to give them a LIKE by clicking on the bottom at the left of the post and show your appreciation.
0 Likes
Frequent Contributor.. network Frequent Contributor..
Frequent Contributor..

Re: Pre_bkp script issue

When the pre backup script fails, if we restart the session, the script runs fine and the backup is completed successfully. Could you provide and suggestions regarding this.

 

0 Likes
Knowledge Partner
Knowledge Partner

Re: Pre_bkp script issue

Hello @network,

Do you get the same results if you run the script manually (at OS level) several times?

You can share the script here so we can have a look and maybe give you at least a suggestion. But again, the script is still out of scope of Data Protector so the author of the script is the best one to reach out for.

Regards,
Sebastian Koehler

---
Please use the Like button below, if you find this post useful.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.