Jump to content

Is this and April Fools joke !?!


Recommended Posts

Hi,

 

 

 

My Proactive script was running(as usual), backing up a client(as usual), when this appeared in

 

the Ops Log:

 

 

 

+ Normal backup using Retro SERVER Mobile at 4/1/2003 1:08 PM

 

To Backup Set Retro SERVER Mobile D...

 

 

 

- 4/1/2003 1:08:40 PM: Copying Drive C (C:) on CLIENT

 

4/1/2003 1:08:40 PM: Connected to CLIENT

 

Can't add that much data to Backup Set

 

(limited to 576.0 G)

 

4/1/2003 1:09:28 PM: Execution incomplete

 

Remaining: 80 files, 41.7 MB

 

Completed: 0 files, zero KB

 

Performance: 0.0 MB/minute

 

Duration: 00:00:47 (00:00:47 idle/loading/preparing)

 

 

 

4/1/2003 1:09:28 PM: Execution incomplete

 

Total duration: 00:00:47 (00:00:47 idle/loading/preparing)

 

 

 

 

 

- 4/1/2003 1:32 PM: Proactive Client Backup stopped

 

Quit at 4/1/2003 1:41 PM

 

 

 

So I reboot the SERVER and try again...

 

 

 

+ Retrospect version 6.0.206

 

Launched at 4/1/2003 1:49 PM

 

 

 

+ 4/1/2003 1:49 PM: Proactive Client Backup started

 

 

 

+ Normal backup using Retro SERVER Mobile at 4/1/2003 1:50 PM

 

To Backup Set Retro SERVER Mobile D...

 

 

 

- 4/1/2003 1:50:52 PM: Copying Drive C (C:) on CLIENT

 

4/1/2003 1:50:52 PM: Connected to CLIENT

 

TPCString::NetImport - needed 34,153, datasize 1,316

 

TPCFolderLoc::NetImport (m_path) - elsize 34,153, sz 1,316

 

PcFsVolNodeScan::NetImport (parFolder) - elsize 1,610,612,981, sz 1,320

 

Scanning incomplete, error -3102 (unknown)

 

 

 

- 4/1/2003 1:51:01 PM: Copying Drive D (D:) on CLIENT

 

4/1/2003 2:02:50 PM: Snapshot stored, 17.5 MB

 

4/1/2003 2:03:01 PM: Execution completed successfully

 

Completed: 2 files, 1,252 KB

 

Performance: 1.3 MB/minute

 

Duration: 00:11:49 (00:01:54 idle/loading/preparing)

 

 

 

4/1/2003 2:03:01 PM: Execution incomplete

 

Total duration: 00:11:58 (00:11:13 idle/loading/preparing)

 

 

 

Any ideas/comment/suggestions ????

 

 

 

thanks,

 

alan

Link to comment
Share on other sites

As the author of some other TCP/IP server software I can just say that it would not surprise me at all if it WAS a network card problem - we get certain weird problems reported all the time and the vast majority of the time changing to a different manufacturer's card solves the problem -even though other network software might be working fine through the same NIC.

 

Some manufacturer's NICs are really dreadful in our experience, but we've never had problems reported with (non faulty) 3COM or Intel NICs.

 

Sometimes a driver update will fix the problem so it's worth trying that first, but otherwise try swapping the network card temporarily - they're not that expensive (but swap it for a different make if possible). If the temporary swap doesn't improve things you can always swap it back again.

Link to comment
Share on other sites

  • 2 weeks later...

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...