Forum Discussion

Alex_Kovalev's avatar
Alex_Kovalev
Level 2
13 years ago

Status of restore from image created Mon May 21 16:01:43 2012 = allocation failed

Hello all! We trying to resore documentum content from image Flashbackup (FULL) and recieving error:

Restore started 05/22/2012 17:58:38

22:07:21 Status of restore from image created Mon May 21 16:01:43 2012 = allocation failed

22:07:21 The following files/folders were not restored:
22:07:21 UTF - /doc/flashtst/
22:07:21 UTF - /doc/flashtst/DCTM/
22:07:21 UTF - /doc/flashtst/DCTM/documentum/
22:07:21 UTF - /doc/flashtst/DCTM/documentum/data/
22:07:21 UTF - /doc/flashtst/DCTM/documentum/data/CTC/
22:07:21 UTF - /doc/flashtst/DCTM/documentum/data/CTC/content_storage_01/
22:07:21 UTF - /doc/flashtst/DCTM/documentum/data/CTC/content_storage_01/00e6703a/
22:07:21 UTF - /doc/flashtst/DCTM/documentum/data/CTC/content_storage_01/00e6703a/80/
22:07:21 UTF - /doc/flashtst/DCTM/documentum/data/CTC/content_storage_01/00e6703a/80/c4/
22:07:21 UTF - /doc/flashtst/DCTM/documentum/data/CTC/content_storage_01/00e6703a/80/c4/9c/
22:07:21 UTF - /doc/flashtst/DCTM/documentum/data/CTC/content_storage_01/00e6703a/80/c4/9c/7c.txt
22:07:21 UTF - /doc/flashtst/DCTM/documentum/data/CTC/content_storage_01/00e6703a/80/c4/9c/7d.txt
22:07:21 UTF - /doc/flashtst/DCTM/documentum/data/CTC/content_storage_01/00e6703a/80/c4/9c/7e.txt
22:07:21 UTF - /doc/flashtst/DCTM/documentum/data/CTC/content_storage_01/00e6703a/80/c4/9c/7f.txt
22:07:21 UTF - /doc/flashtst/DCTM/documentum/data/CTC/content_storage_01/00e6703a/80/c4/9c/80.txt
22:07:21 UTF - /doc/flashtst/DCTM/documentum/data/CTC/content_storage_01/00e6703a/80/c4/9c/81.txt
22:07:21 UTF - /doc/flashtst/DCTM/documentum/data/CTC/content_storage_01/00e6703a/80/c4/9c/82.txt
22:07:21 UTF - /doc/flashtst/DCTM/documentum/data/CTC/content_storage_01/00e6703a/80/c4/9c/83.txt
22:07:21 UTF - /doc/flashtst/DCTM/documentum/data/CTC/content_storage_01/00e6703a/80/c4/9c/84.txt
22:07:21 UTF - /doc/flashtst/DCTM/documentum/data/CTC/content_storage_01/00e6703a/80/c4/9c/85.txt
22:07:21 UTF - /doc/flashtst/DCTM/documentum/data/CTC/content_storage_01/00e6703a/80/c4/9c/86.txt
22:07:21 UTF - /doc/flashtst/DCTM/documentum/data/CTC/content_storage_01/00e6703a/80/c4/9c/87.txt
22:07:21 UTF - /doc/flashtst/DCTM/documentum/data/CTC/content_storage_01/00e6703a/80/c4/9c/88.txt
22:07:21 UTF - /doc/flashtst/DCTM/documentum/data/CTC/content_storage_01/00e6703a/80/c4/9c/89.txt
22:07:21 UTF - /doc/flashtst/DCTM/documentum/data/CTC/content_storage_01/00e6703a/80/c4/9c/8a.txt

Can you explain what it means?

7.1.x and Earlier
Backup and Recovery
Error messages
NetBackup
Recovering
Restore
Troubleshooting

7 Replies

Sort By
  • revarooo's avatar
    revarooo
    Level 6
    13 years ago

    I've seen this happen before with flashbackup restores and the solution was to restore "piece meal", so restore large sections bit by bit. I think in the instances I have seen the servers were simply out of resources due to the sheer size of the restores.

  • Marianne's avatar
    Marianne
    Level 6
    13 years ago

    I have also seen this where bprd ran out of memory building the file list for restore.

    There have been various fixes over the years for this.
    Which NBU version and OS on the master?

    I agree with revaroo - workaround is to select smaller amount of folder/files.

  • Nicolai's avatar
    Nicolai
    Moderator
    13 years ago

    Check free memory during restore. Try restoring a subset of the data and see if the issues continue to exists. Documentum is a document control system can usually contain millions of small files.

    NetBackup Status Code 10: allocation failed

    Solution

    Overview: NetBackup Status 10 : allocation failed

    Explanation: The system memory allocation fails because of insufficient system memory available. A possible cause is that the system is overloaded with too many processes and not enough physical or virtual memory. 

    Recommended action: Free up memory by terminating any unneeded processes that consume memory. Add more swap space or physical memory. 

    update: To late cheeky

  • revarooo's avatar
    revarooo
    Level 6
    13 years ago

    Yes, I remember monitoring the Master server and a bprd process hits a limit of memory consumed (from my poor memory) , this is when the Allocation failed error then appeared.

    Can't for the life of me remember what that limit was. workaround restoring a smaller selection at a time worked a treat though, and that was the recommendation from "higher above" :)

  • Marianne's avatar
    Marianne
    Level 6
    13 years ago

    You will probably need verbose bprd log to troubleshoot.

    I have seen this problem across most NBU versions. Unix and Windows.

    Even documented in NBU 7.5 EEB Guide:

    The bprd process runs out of memory when it prepares restores with millions of files.

  • revarooo's avatar
    revarooo
    Level 6
    13 years ago

    Doesn't matter how much free memory you have, bprd hits a limit and then that is it, game over.

    Split the restore into smaller chunks as previously mentioned.