"Unable to allocate memory" error

Hi,

In order to isolate the issue, Please perform the following and verify the results.

- Install SP1 from the following technote:
http://seer.support.veritas.com/docs/267182.htm

- Install Hotfix 45 and verify the results. Please refer to the following technote:
http://seer.support.veritas.com/docs/274789.htm

After doing this reboot the server and verify the results.

We hope this will help.

Assuming the solution provided is correct. Also, there is no response from the customer within 2 days from the last reply by Veritas

I noticed that SP2 was available so I decied to install it instead of SP1 and hotfix 45 (I was already running with SP1 and acoording to the SP2 doc all previous hotfixes should be in SP2)

Installed SP2 on the BE server and upgrade all my remote agents but to no avail. I still get once in while the "Unable to allocate memory" error even do I reboot my BE server every day.

Any other suggestions ?

Regards
A van der Boom

Hello,

Please try the following steps to troubleshoot the issue.
1. Ensure that no other backups are running at the same time.
2. If you are using Advanced Open File Option during these backups try disabling it
3. Is there error occuring during particular backups? Ex. Full, Differential etc?
4. Take a backup of your registry and rest the following key:
HKLM/Software/Veritas/Backup Exec/Engine/NTFS/FSUseAsyncIO = 1. Set to 0

5. If Antivirus service is running, disable it and verify the result.

Please revert with result of each step.

NOTE : If we do not receive your intimation within two business days, this post would be "assumed answered" and archived.

Archiving the post as per our previous reply

> 1. Ensure that no other backups are running at the
> same time.
I already re-scheduled my jobs to make sure not all off them are running at the same time, but the problem is the time window option. It is not flexible enough to force jobs running after each other instead of simultaneous (like BE8.5 could)

> 2. If you are using Advanced Open File Option during
> these backups try disabling it
No, I am not using this option.

> 3. Is there error occuring during particular backups?
> Ex. Full, Differential etc?
Mostly at full backups

> 4. Take a backup of your registry and rest the
> following key:
> HKLM/Software/Veritas/Backup
> Exec/Engine/NTFS/FSUseAsyncIO = 1. Set to 0
Done

> 5. If Antivirus service is running, disable it and
> verify the result.
Antivirus software is not running on my backup machine.

>
> Please revert with result of each step.
>
> NOTE : If we do not receive your intimation within
> two business days, this post would be "assumed
> answered" and archived.
two days is not enough, as I said before this error is occuring randomly.

Regards
A van der Boom

Hello,

I woul like to know if the server you are using is Dell Power Edge Servers. This error has been observed in certain Dell Power Edge Servers with Dell OpenManage Array Manager installed. The error is prominent when System state is selected for backup.

Please refer to the following solutions, which may help in resolving this issue :

1. Try disabling the antivirus software on the machines and check the results.

2. Try backup after uninstalling the Dell OpenManager. This may allow Backup Exec to access the hard disk. Reboot the server, perform backup and verify. This step would isolate the cause of the issue.

However, to find out the exact cause of this error and provide you a precise solution, we suggest you to perform the following steps and send us the output files generated.

1. Run SGMON utility in the background and ensure that it is logging the events. (Path - Program files\VERITAS\Backup Exec\NT folder)

2. Perform only System State backup. This will narrow down our search in figuring out the exact cause.

3. Are you getting following events getting logged in sgmon ?
9d8 2/7/2003 11:36:19: Informational: Gathering LDM volume info 950
2/7/2003 11:36:19: Informational: LDM interface failed
9d8 2/7/2003 11:36:19: Error: LDM connection failed
8d4 2/7/2003 11:36:19: Informational: LDM interface failed 4

Hope this helps you.

Regards,


NOTE: If we do not receive your intimation within two business days, this post would be assumed answered and archived.

> I woul like to know if the server you are using is
> Dell Power Edge Servers. This error has been observed
> in certain Dell Power Edge Servers with Dell
> OpenManage Array Manager installed. The error is
> prominent when System state is selected for backup.
I am using a DELL Powervault 745N

> Please refer to the following solutions, which may
> help in resolving this issue :
>
> 1. Try disabling the antivirus software on the
> machines and check the results.
There is no anti-virus software running on my system.

> 2. Try backup after uninstalling the Dell
> OpenManager. This may allow Backup Exec to access the
> hard disk. Reboot the server, perform backup and
> verify. This step would isolate the cause of the
> issue.
I will first contact DELL if they might have a newer version because I need the OpenManager to manage my RAID sets.

> However, to find out the exact cause of this error
> and provide you a precise solution, we suggest you to
> perform the following steps and send us the output
> files generated.
>
> 1. Run SGMON utility in the background and ensure
> that it is logging the events. (Path - Program
> files\VERITAS\Backup Exec\NT folder)
>
> 2. Perform only System State backup. This will narrow
> down our search in figuring out the exact cause.
>
> 3. Are you getting following events getting logged in
> sgmon ?
> 9d8 2/7/2003 11:36:19: Informational: Gathering LDM
> volume info 950
> 2/7/2003 11:36:19: Informational: LDM interface
> failed
> 9d8 2/7/2003 11:36:19: Error: LDM connection failed
> 8d4 2/7/2003 11:36:19: Informational: LDM interface
> failed 4

I will perform the above mentioned steps and will let you know the results

Regards
A van der Boom

Hello,


In reference to our previous reply to your post, we would request you to update us on the progress. Have you tried the remaining steps?

NOTE : If we do not receive your intimation within two business days, this post would be marked assumed answered and would be moved to the answered threads pool.

As per our previous reply, marking the case as assumed answered and moving it to answered questions pool.