on 2021 Jul 08 4:28 PM
error:
2021-06-26T00:23:24+02:00 P0012924 17a452fd37a ERROR BACKUP SAVE DATA finished with error: [447] backup could not be completed, [110112] Extended storage backup error : [SAP][ODBC Driver]Unable to write to archive. ('Failed to open pipe /usr/sap/PH1/SYS/global/hdb/backint/DB_PH1TEN1S/2021_06_26_00_00_00_databackup_differential_1624468383499_16')
cat /usr/sap/PH1/HDB50/ph1db/trace/backup.log | grep -i "broken"
2019-09-04T14:24:35+02:00 P074960 16cfc32a005 ERROR LOGBCKUP state of service: nameserver, ph1db:35001, volume: 1,
2021-07-08T00:52:00.141007+02:00 veat2l000022 SQLAnywhere(esph150): [00000]{0000000000}[-1/-1] 2021-07-08 00:52:00.140281 i esserver UNKNOWN(0) : Error during backup/restore: Failure while trying to fetch SAP HANA log backup option
Request clarification before answering.
Hi Sanjay,
Thanks for sharing your log files with the community. Did you have a question in mind?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Please check, if this helps further:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hakan.haslaman Thanks for the reply. when you mean trace its not system process which we have to montior. we have to montior the below logs:
ex:
mean /hana/shared/PH1/*/*/trace # ls -lrt total 371512 -rw-r--r-- 1 ph1adm sapsys 791 Mar 17 2019 esserver.err
Also, as instructed in weblink we are unable to find esServerInfo.txt file on the server.
Full System Info Dump at first should be enough.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Could be an issue with the esserver or backint, so please collect the traces and open an incident at the component HAN-DYT or HAN-DB-BAC, so Product Support can start to analyzing the traces,.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
SAP hana,
Data backups have failed with TSM ,
restarting DT services is resolving is resolving the issue but as its prod server client reqested not to do it.
The error messages i have posted are related to the same. Kindly suggest us on how to proceed. as you see odbc driver error. whats ur suggestion on that
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I guess, you are using DT, so for further investigate, we have to check the /var/log/messages and full system info dump for more information. If you can't check the traces self, please open a support incident on the component HAN-DB-BAC and let the traces analyzing from Product Support.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I Explained about backup failed with the error messages Backup error: The state 'ManagerCommandRunning' of the BackupManager or Backup error: connection broken SQLSTATE: HY000 or Error: other backup.pl is running
4> ERROR :Command
[su - siddm -c "xyz/usr/sap/SID/home/backup_bkp.pl";] failed with return code [512] and message [* 2: general error: Backup error: The state 'ManagerCommandRunning' of the BackupManager.
workaround for the error -
Backup will fail with this error when another backup is running at same time. In the HANA studio check the thread tab for this. If you see Backup manager is still running from a long time and from server level backup processes are not running. Then this problem will be solved by full system restart.
5> ERROR :Command
[su- sidadm –c “xyz/usr/sap/SID/home/backup_bkp.pl”] failed with return code [512] and message [*2: general error: Backup error: connection broken SQLSTATE: HY000]
workaround for the error -
Backup will fail with error when database went down during backup was running. For this check the availability log and backup timing. You can observe that during backup window database was unavailable.
6> ERROR :Command
[su - sidadm -c "xyz/usr/sap/SID/home/backup_bkp.pl";] failed with exit code [256] and mes-sage [Error: other backup.pl is runnig]
workaround for the error -
If the backup is failing with this error then because of previous running backup.pl new backup will fail. To solve this problem kill the backup processes which are running from a long time and run backup again.
To find the backup ID of the running data backup, use the following SQL command:
select BACKUP_ID from "SYS"."M_BACKUP_CATALOG" where entry_type_name ='complete data backup' and state_name = 'running' order by sys_start_time desc;
Backup Cancel :
Backup Cancel (backup_id)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello sanju6593!
How is your storage partition use?
Type 'df -h' to show the size used in partitions.
Regards;
Bruno Affonso.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
30 | |
21 | |
16 | |
8 | |
7 | |
6 | |
5 | |
4 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.