cummingsprinting Posted January 16, 2012 Report Share Posted January 16, 2012 For the last month or so, most of my backups of this one particular server generates the following error messages. The error does not show up while backing up any of the other servers. My Retrospect re-seller suggested we add more RAM to the machine. That did not fix the issue. I searched this forum and found 2 threads that discuss this issue, but did not see anything in them that would help me with this issue. Thank you for any assistance I can get with this. + Normal backup using prinergy2jobs at 1/11/2012 2:58 AM (Execution unit 1) To Backup Set prinergyjobs Set B... - 1/11/2012 2:58:09 AM: Copying Jobs on prinergy2 TMemory: heap 40 1,833 K virtual 8 430.5 M commit 430.5 M purgeable 0 zero K Pool:pools, users 2 114 max allowed mem 614.0 M max block size 8,192 K total mem blocks 2 16.0 M used mem blocks 2 16.0 M file count, size 1 8,192 K requested 48 3.6 G purgeable 0 zero K avail vm size 1,534,533,632 B TMemory::mhalloc: VirtualAlloc(351.0 M, MEM_RESERVE) failed, error 8 TMemory: heap 41 1,834 K virtual 8 430.5 M commit 430.5 M purgeable 0 zero K Pool:pools, users 2 114 max allowed mem 614.0 M max block size 8,192 K total mem blocks 2 16.0 M used mem blocks 2 16.0 M file count, size 1 8,192 K requested 49 3.6 G purgeable 0 zero K avail vm size 1,534,533,632 B TMemory::mhalloc: VirtualAlloc(351.0 M, MEM_RESERVE) failed, error 8 TMemory: heap 41 1,835 K virtual 8 430.5 M commit 430.5 M purgeable 0 zero K Pool:pools, users 2 114 max allowed mem 614.0 M max block size 8,192 K total mem blocks 2 16.0 M used mem blocks 2 16.0 M file count, size 2 16.0 M requested 49 3.6 G purgeable 0 zero K avail vm size 1,534,533,632 B TMemory::mhalloc: VirtualAlloc(368.5 M, MEM_RESERVE) failed, error 8 TMemory: heap 41 1,836 K virtual 8 430.5 M commit 430.5 M purgeable 0 zero K Pool:pools, users 2 114 max allowed mem 614.0 M max block size 8,192 K total mem blocks 2 16.0 M used mem blocks 2 16.0 M file count, size 2 16.0 M requested 49 3.6 G purgeable 0 zero K avail vm size 1,534,533,632 B TMemory::mhalloc: VirtualAlloc(368.5 M, MEM_RESERVE) failed, error 8 TMemory: heap 40 1,833 K virtual 8 430.5 M commit 430.5 M purgeable 0 zero K Pool:pools, users 2 114 max allowed mem 614.0 M max block size 8,192 K total mem blocks 2 16.0 M used mem blocks 2 16.0 M file count, size 2 16.0 M requested 48 3.6 G purgeable 0 zero K avail vm size 1,534,533,632 B TMemory::mhalloc: VirtualAlloc(368.5 M, MEM_RESERVE) failed, error 8 TMemory: heap 41 1,834 K virtual 8 430.5 M commit 430.5 M purgeable 0 zero K Pool:pools, users 2 114 max allowed mem 614.0 M max block size 8,192 K total mem blocks 2 16.0 M used mem blocks 2 16.0 M file count, size 2 16.0 M requested 49 3.6 G purgeable 0 zero K avail vm size 1,534,533,632 B TMemory::mhalloc: VirtualAlloc(368.5 M, MEM_RESERVE) failed, error 8 1/11/2012 4:54:29 AM: Snapshot stored, 262.9 MB 1/11/2012 4:54:45 AM: Execution completed successfully Completed: 2608 files, 5.0 GB Performance: 459.4 MB/minute Duration: 01:56:35 (01:45:32 idle/loading/preparing) - 1/11/2012 4:54:57 AM: Verifying prinergyjobs Set B 1/11/2012 4:55:50 AM: Execution completed successfully Completed: 2608 files, 5.0 GB Performance: 7798.8 MB/minute Duration: 00:00:52 (00:00:12 idle/loading/preparing) Retrospect Version: 7.6.2.101 Server Specs: Pentium4 3.2GHz, 4GB RAM, 2003 Std SP1, C: 34GB (26GB free) Quote Link to comment Share on other sites More sharing options...
cummingsprinting Posted January 23, 2012 Author Report Share Posted January 23, 2012 spoke with a tech on the phone. we deleted the backup set and client, restarted retro, and then recreated the client & backup set, then fixed the script. i will know if it's fixed later this afternoon. Quote Link to comment Share on other sites More sharing options...
cummingsprinting Posted January 23, 2012 Author Report Share Posted January 23, 2012 no luck. looks like i'll be calling back tomorrow to redo the config file, which i'm told means i lose all scripts, volumes, clients, preferences and have to recreate them. i'll really be looking forward to getting out of bed tomorrow morning... Quote Link to comment Share on other sites More sharing options...
cummingsprinting Posted January 26, 2012 Author Report Share Posted January 26, 2012 after recreating all clients, volumes, scripts, etc i continued to get the above errors. i called into retrospect again today. after some discussion, he asked me to hold. when he came back, he said that we "can ignore that message" and "all of your files are being backed up successfully". in future versions of retrospect (like 7.7) "these messages are suppressed" and only used for debugging purposes. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.