News:

RAID is not a replacement for a backup! Here's why.

Main Menu

How do I verify Failover is working?

Started by Dalton, February 27, 2017, 06:08:36 AM

Previous topic - Next topic

Dalton

Hi all,
I have a client with 2 TS5400 installed 1 as main unit (192.168.0.216) and the second as a failover unit (192.168.0.217). Following a power failure the units developed issues which required me to dissolve the failover status and create it again.

In the past if I logged into the ip address of the second unit using file explorer \\192.168.0.217\ (not the interface) I could see all the files replicated on the second unit. Now all I can see is an info folder.  I have spoken to a very hard to understand support technician at Buffalo who advises that this is normal since the latest update. However I am not convinced he is correct as there now doesn't seem to be any way to check/confirm that failover replication is actually working. The failover was configured 4 days ago and I still dont know if failover replication is taking place.

In the software control panel of the main unit it's status is shown as standalone and I cannot log into the second unit as it states that it is configured as a failover unit.

Can anyone please advise how I can confirm that the failover service is actually running and copying the data over.

Thanks in advance for any help provided.

Texturtle

If the primary unit says it's standalone then failover is definitely not configured. I suggest you contact support again to get this corrected.

Browser ID: smf (is_webkit)
Templates: 4: index (default), Display (default), GenericControls (default), GenericControls (default).
Sub templates: 6: init, html_above, body_above, main, body_below, html_below.
Language files: 5: index+Modifications.english (default), Post.english (default), Editor.english (default), Drafts.english (default), StopForumSpam.english (default).
Style sheets: 4: index.css, attachments.css, jquery.sceditor.css, responsive.css.
Hooks called: 131 (show)
Files included: 35 - 1354KB. (show)
Memory used: 942KB.
Tokens: post-login.
Queries used: 16.

[Show Queries]