Unsolved
This post is more than 5 years old
1 Message
0
2140
October 8th, 2015 04:00
Error Code:0x650000c Creating a replication session VNXe-VNX
Creating a Filesystem replication session from a VNXe to a VNX, I received "The system failed to create the replication session Error Code:0x650000c"
I checked all networking related settings and everything was OK.
Looking for logs entries into VNX, I found "Source FS Type is not compatible with Destination FS/DM Type"
Both source and destination FS were created from the GUI with standard default options.
After some investigation without success, I tried to create a test replication in the opposite direccion from the CLI, cause the VNX GUI complains with "Cannot access any Data Mover on the remote system,".
Then I got the clue: "Error 13160417332: The source file system supports SplitLog and the destination file system does not support SplitLog."
VNXe Software Version was 2.4.2.21519 and VNX File Software Version 8.1.6-101
VNX FS were using SplitLog, while VNXe FS were using common log type.
The workarround was to delete VNX FS and create a new one from the CLI with the option log_type=common. After that, I managed to create replication from VNXe GUI.
I hope this can help if someone get the same issue in the future.
doublea1
2 Posts
0
October 15th, 2015 08:00
Registered just to thank you. I had been battling this for a few weeks now and didn't want to call support as I find the VNXe support to be more painful due to babysitting a webex instead of letting them come in over ESRS on our bigger systems. I had upgraded code, recreated interconnects, tried different filesystem sizes, just about everything you can think short of doing the reverse replication like you did, but that was coming next. Glad you posted this and glad I searched again as this is only a week old now and previous searches for 0x650000c did not find anything relevant or recent in the past 6 months.
Worked as expected as soon as I created the destination filesystem via CLI with the log option.
Cheers!
kelleg
6 Operator
•
4.5K Posts
0
October 21st, 2015 09:00
Please mark your question Answered as this will help others searching for a similar issue.
glen
doublea1
2 Posts
0
October 21st, 2015 12:00
How do I do I mark it answered? I couldn't find any option for that, plus I did not post the original topic.
kelleg
6 Operator
•
4.5K Posts
0
October 22nd, 2015 08:00
Sorry - I just clicked on rely and should have sent the reply to the originator - only the owner of the thread can mark a discussion answered.
glen
Davy_Paul
10 Posts
0
January 25th, 2016 06:00
I have to say thank you too!
this has been bugging me for months. The VNXe/VNX mismatch seemed to start happening after the VNXe upgrades and I could not create any fresh replications. this log 'fix' was exactly right.