Fatal error on replication between 2 SPA's

[Fr_d_ric_RIGAL]

Hi all,

I've configured replication between 2 SPA's (6.6.1.2) and each time, jobs are stopped with the following error in job details :

Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 2048 bytes) in /opt/pdmbe/mgmtclass/ReplicationStream.php on line 79

I've followed the technote TECH152393 but each SPA's has 2 To of storage (/Storage) and 48 Go of ram.

Thank you for your help

Best regards

[S_Williamson]

• edit /opt/pdweb/etc/php.ini and change the memory_limit value from 256M to 512M
• edit /opt/pdconfigure/etc/default/pdgui and change the CATALINA_OPTS allocation from 512m to 1024m
• run this command to restart the gui: /etc/init.d/puredisk restart pdgui

[Fr_d_ric_RIGAL · Accepted solution]

hi,

thank you for your answer.

I've open a case to ythe Symantec Support before and they told me to

edit /opt/pdweb/etc/php.ini and change the memory_limit value from 256M to 1024M

edit /opt/pdag/bin/php.ini and change the memory_limit value from 256M to 1024M

I' ve done this on the SPA Destination server and it works.

But I wonder if I have to apply this on the SPA Source server too.

Thank you again

[Todd_D__Woodwar]

There are several places where memory can be tweaked in PureDisk. However, since a large amount of the functionality of PureDisk is PHP-based, adjusting PHP memory usage seems to have the most impact in situations like these:

http;//www.symantec.com/docs/TECH170731

The default is 256M, but sometimes increasing it to 512M or 1024M will resolve issues like these. We've had a few extreme cases where increasing it to 2048M was required.

If just increasing the memory allocation in the destination SPA resolves the issue, there is no need to increase it on the source SPA.

[Lee_C]

Todd,

Can you fix your hyperlink in your last post?

it's attempting to go here: http://http/;//www.symantec.com/docs/TECH170731

Should be:

http://www.symantec.com/docs/TECH170731

[Todd_D__Woodwar]

Thanks for letting me know about the link error. It's fixed now.