Hey all, I'm using AppAssure Replay build 4.7 and one of our customer's Core servers is not able to replicate to our 'master Core', but our other customers can. I'm not getting any immediate support from AppAssure, they've been 'reviewing the logs' for about 3 days now, and they have no techs available to talk to me.
I'm seeing errors like the following:
'There was an error getting the local replication status for 'SERVERNAME'. Local replication status info will not be available.'
This is related to AppAssure's Replay product. Basically, this is telling you that you have 0 space on one of your drives. Restarting the Replay service will usually not clear this up. Hey all, I'm using AppAssure Replay build 4.7 and one of our customer's Core servers is not able to replicate to our 'master Core', but our other customers can. I'm not getting any immediate support from AppAssure, they've been 'reviewing the logs' for about 3 days now,. 8 – In elevated command prompt change to the disk assigned above in Step 1 and “cd System Volume Information” 9 – “del aalog*.*”to delete them 10 – “fltmc load aafsflt” will reload the filter driver and re-create clean new AALOGs. Our database contains 11 different files for filename aavolflt.sys.You can also check most distributed file variants with name aavolflt.sys.This files most often belongs to product AppAssure Replay.and were most often developed by company AppAssure Software, Inc.This files most often have description AppAssure Volume Filter Driver.This file contains driver. Great this about this blog is that there are free drivers to download here. Like good old times. When the internet was free and friendly.
'Error while servicing connection: Error writing 32768 bytes to network - An established connection was aborted by the software in your host machine.'
Their Core is backing up and replicating about 29 Agents. Local backups are fine, just replication isn't working.
I've rebooted both the customer Core and our off-site Master Core, and I've repaired the customer's Replay Core install. No changes have been made that I'm aware of on the network.
The strange thing is that the Core Console's showed that replicating was happening/in-progress on Monday, so I thought all was well. I ran a replication report and it showed that 0 GB had been replicated, though. Now the Console's just report that 'Replication is Idle'.
Does anyone have any experience with these kinds of errors or have any suggestions? Thanks in advance.
EDIT: Some more troubleshooting that I've done: Standard stuff like ping both ways successfully. Verified DNS servers are set correctly with nslookup. Used the MS Port Query tool to test our master core IP destination over our replication TCP port, it reports 'LISTENING'.
After I did the above, the same thing happened like on Monday, I see the Replay Core in the background start replicating... So I'm going to monitor and see if it times out or something. This customer has a fiber connection which is connected directly to our Comcast 100MB line to our core, so I think we can handle the data, but I think it may be timing out for some reason.