on 06-11-2014 10:33 AM
Dear experts
We are facing a critical error when importing a HANA data backup.
We had a HANA box with 256GB RAM from which we made a full data backup.
Now we are trying to import that data backup into a new HANA box using the HANA Studio and following the steps. New server has similar configuration but less RAM (64GB). According the HANA experts it would be possible to import that backup into that server.
The think is that almost all services are correctly imported but the indexserver which is giving an error
RECOVERY RECOVER DATA finished with error: [448] recovery could not be completed, volume 2, reached log position 0,
[1000002] Allocation failed ; $size$=16777216; $name$=Page; $type$=pool; $inuse_count$=2693; $allocated_size$=45181042688
We have been digging into entire SDN and SAP Noted but have not been able to find anything.
We have also been trying with different values of parameter data_backup_buffer_size in global.ini but also with no success.
Does somebody know how to deal with that allocation error in order to complete the full recover?
Thanks a lot.
Below detailed logs (it get's hang usually at 45% of completion of indexserver.ini)
2014-06-10T19:31:19+00:00 P017337 1468742af9a INFO RECOVERY state of service: indexserver, hdbqatar:30003, volume: 2, RecoveryExecuteDataRecoveryInProgress
2014-06-10T19:31:19+00:00 P017337 1468742af9a INFO RECOVERY using file: /exports/Old_backup/20140501_HANA001/COMPLETE_DATA_BACKUP_databackup_2_1
2014-06-10T19:31:19+00:00 P017337 1468742af9a INFO RECOVERY progress of service: indexserver, hdbqatar:30003, volume: 2, 0% 0/260888956928
2014-06-10T19:31:26+00:00 P017337 1468742af9a INFO RECOVERY progress of service: statisticsserver, hdbqatar:30005, volume: 3, 100% 2404741120/2404741120
2014-06-10T19:31:26+00:00 P017337 1468742af9a INFO RECOVERY state of service: statisticsserver, hdbqatar:30005, volume: 3, RecoveryExecuteDataRecoveryFinished
2014-06-10T19:31:26+00:00 P017337 1468742af9a INFO RECOVERY state of service: statisticsserver, hdbqatar:30005, volume: 3, RecoveryLogInitializationStarted
2014-06-10T19:31:27+00:00 P017337 1468742af9a INFO RECOVERY state of service: statisticsserver, hdbqatar:30005, volume: 3, RecoveryLogInitializationFinished
2014-06-10T19:33:22+00:00 P017337 1468742af9a INFO RECOVERY progress of service: indexserver, hdbqatar:30003, volume: 2, 5% 13421772800/260888956928
2014-06-10T19:35:09+00:00 P017337 1468742af9a INFO RECOVERY progress of service: indexserver, hdbqatar:30003, volume: 2, 10% 26306674688/260888956928
2014-06-10T19:36:41+00:00 P017337 1468742af9a INFO RECOVERY progress of service: indexserver, hdbqatar:30003, volume: 2, 15% 39191576576/260888956928
2014-06-10T19:38:18+00:00 P017337 1468742af9a INFO RECOVERY progress of service: indexserver, hdbqatar:30003, volume: 2, 20% 52613349376/260888956928
2014-06-10T19:39:43+00:00 P017337 1468742af9a INFO RECOVERY progress of service: indexserver, hdbqatar:30003, volume: 2, 25% 65498251264/260888956928
2014-06-10T19:41:11+00:00 P017337 1468742af9a INFO RECOVERY progress of service: indexserver, hdbqatar:30003, volume: 2, 30% 78383153152/260888956928
2014-06-10T19:42:44+00:00 P017337 1468742af9a INFO RECOVERY progress of service: indexserver, hdbqatar:30003, volume: 2, 35% 91804925952/260888956928
2014-06-10T19:44:11+00:00 P017337 1468742af9a INFO RECOVERY progress of service: indexserver, hdbqatar:30003, volume: 2, 40% 104689827840/260888956928
2014-06-10T19:45:57+00:00 P017337 1468742af9a INFO RECOVERY progress of service: indexserver, hdbqatar:30003, volume: 2, 45% 117574729728/260888956928
2014-06-10T19:50:58+00:00 P017337 1468742af9a ERROR RECOVERY RECOVER DATA finished with error: [448] recovery could not be completed, volume 2, reached log position 0, [1000002] Allocation failed ; $size$=16777216; $name$=Page; $type$=pool; $inuse_count$=2693; $allocated_size$=45181042688
Sergi,
Your backup will not be restored.
During the restore it is requesting more 40gb to allocate memory.
It will only be possible if you have at appliance of at least 128gb.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi All
I am getting the same thing on my side,and i am running REV74 PL12 and the backups worked for a week but it failed over the weekend, and i also did the mem alocation in studio but it is doing the same thing, even on a manual backup it gives me an error.
has any 1 resolved the issue yet?
please
Morne
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Any solution for this problem? My backups worked for a while but now i get this error every time. I can't backup database. Im runnin hana 1.00 rev 74
Error message: backup could not be completed, Allocation failed ; $size$=536870912; $name$=ChannelUtils::copy; $type$=pool; $inuse_count$=1; $allocated_size$=536870912
Hi
please tell me what you default buffer size is, and how much ram does the server have. i have had this problem with 1 client and i read up on the error, and what i did was change the default buffer size in studio en restarted the system or better yet restarted the hole server and i haven`t got the issue again. be low is a pic. hope it helps.
Sergi, I cannot help you directly, but I can mention that I'm getting the same error when performing a data backup, it never happened before and there is enough space on disk. Perhaps it means allocating main memory? But 'free' shows 20G so this might not be it. Moreover, the backup data seems to have been created correctly, the file sizes are roughly equal to the old ones. My error is
2014-06-12T11:39:23+02:00 P004431 1468f72102b ERROR BACKUP SAVE DATA finished with error: [447] backup could not be completed, [1000002] Allocation failed ; $size$=536870912; $name$=ChannelUtils::copy; $type$=pool; $inuse_count$=1; $allocated_size$=536870912
-- Micha
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Micha,
Are you trying to backup or to restore the backup?
If you are trying to backup and get that error, try to assign a smaller to parameter data_backup_buffer_size in global.ini.
In our case, we have enough hard disk space for the restore... We observe the memory and disk utilization (using df and top commands) while the backup restore is being performed. Disk is maximum 60% used, however I see how RAM gets consumed up to 98% at the time the backup recovery crashes...
User | Count |
---|---|
86 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.