cancel
Showing results forΒ 
Search instead forΒ 
Did you mean:Β 

BE2014 server shows up twice after migration

bandit61
Level 6

After migration from be2012 to be2014, we find the same server twice on the MMS, once with fqdn, once without (mms_shows_server.jpg). This server is backuped by the CAS, where you only find the server once without fqdn (cas_shows_server.jpg) . Trying to restore to this server on the MMS, doesn't show up any possible selection, neither from the server with fqdn (mms_selection_fqdn.jpg), nor from the server (mms_selection_1.jpg) . If you restore from the CAS, you see that every drive is selected for possible restore (cas_selection.jpg). 

With configuration like:

Storage and media database location=CAS

keep the catalogs on = CAS

we assume the server to appear only once.

Do you have to get rid of duplicates between CAS & MMS manually?

1 ACCEPTED SOLUTION

Accepted Solutions

bandit61
Level 6

for VJware: removed the 2 entries on the MMS, no impact on the CAS until now. Backup thru the night will give us further proof.

View solution in original post

8 REPLIES 8

CraigV
Moderator
Moderator
Partner    VIP    Accredited

...have you tried to remove the correct MMS from the CASO server, and then delete the incorrect entry, and then re-add it back?

Otherwise run a repair of the BEDB on the CASO server...

Thanks!

VJware
Level 6
Employee Accredited Certified

Try updating with BE 2014 with SP2 and restart the services to see if it makes any difference or not. Else, you may have to remove the duplicate entries manually.

bandit61
Level 6

for CraigV:  it's not that we have 2 entries for the mms, it's a server which is backup/restore on the CAS, which appears 2 times on the MMS. Did run a repair already.

for VJware: this already existed on be2014 before SP2 and is still here after SP2.

 

CraigV
Moderator
Moderator
Partner    VIP    Accredited

...is there anything in the hosts file on the CASO server which might point to this?

Thanks!

bandit61
Level 6

for CraigV: will check the hosts file tomorrow morning

for VJware: removing the 2 entries on the MMS will have no impact on the CAS i hope, will try this tomorrow

as well.

 

bandit61
Level 6

for CraigV: nothing special, just the standard never put something into these 2 files

 

hosts-content: 

# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
#      102.54.94.97     rhino.acme.com          # source server
#       38.25.63.10     x.acme.com              # x client host
 
# localhost name resolution is handled within DNS itself.
#       127.0.0.1       localhost
#       ::1             localhost
 
lmhosts-content: 
# Finally, non-printing characters can be embedded in mappings by
# first surrounding the NetBIOS name in quotations, then using the
# \0xnn notation to specify a hex value for a non-printing character.
#
# The following example illustrates all of these extensions:
#
# 102.54.94.97     rhino         #PRE #DOM:networking  #net group's DC
# 102.54.94.102    "appname  \0x14"                    #special app server
# 102.54.94.123    popular            #PRE             #source server
# 102.54.94.117    localsrv           #PRE             #needed for the include
#
# #BEGIN_ALTERNATE
# #END_ALTERNATE
 

bandit61
Level 6

for VJware: removed the 2 entries on the MMS, no impact on the CAS until now. Backup thru the night will give us further proof.

bandit61
Level 6

for VJware: everything worked fine, duplicate entries din't appeared

 

thanks