• State Verified Answer
  • +1 person also asked this people also asked this
  • Replies 10 replies
  • Subscribers 13 subscribers
  • Views 1337 views
  • Users 0 members are here
Options
Related

Issues when restoring a backed up Galaxy (CAB file) in SP2023R2

Jakob Agustsson

Hi everyone,

I am currently upgrading system platform from 2020 to 2023R2. I have taken a backup of my current galaxy through the SMC on the old and current installation. I then have a completely fresh installation of 2023R2 on a separate machine and network.  

when trying to restore the galaxy and migrating I always get the same error.

Please use a different name. The current Galaxy name conflicts with an existing object in the Galaxy.

I have tried all kind of names, and no matter which name it always gives this error.

Anyone experienced this?

Parents
  • +1

    This is likely a bit of corruption in the galaxy database.  There are some steps that can be taken to resolve, but it is a bit more complicated than what we can do here in this forum.  Please contact your support provider, and get a support ticket open.  If there ends up being an issue for them getting to the answer, let me know and I can work to get them the complicated steps on this.

  • 0 in reply to David Gardner

    Hi David,

    we are SI and have a standard customer first contract, which means I can not start a case until my distributor reviews my support request.   Unfortunately the support i get through that channel is very poor. I contacted him through email three days ago with all necessary info, and still haven't gotten any reply. Our main customer is a large utilities company running 2020 and we I am doing a parallell upgrade to 2023R2 of their system, so I am starting to be a little worried....

    Out of curiosity, are we talking about editing the SQL database for the galaxy, before importing? Just trying to get a high level understanding of what the steps are you refer to.

    I am actually wondering weather a better approach would be exporting the objects and rebuild the GR that way. But that leaves me with worrying about not getting everything exported/importing

    Thank you so much for your help :)

Reply
  • 0 in reply to David Gardner

    Hi David,

    we are SI and have a standard customer first contract, which means I can not start a case until my distributor reviews my support request.   Unfortunately the support i get through that channel is very poor. I contacted him through email three days ago with all necessary info, and still haven't gotten any reply. Our main customer is a large utilities company running 2020 and we I am doing a parallell upgrade to 2023R2 of their system, so I am starting to be a little worried....

    Out of curiosity, are we talking about editing the SQL database for the galaxy, before importing? Just trying to get a high level understanding of what the steps are you refer to.

    I am actually wondering weather a better approach would be exporting the objects and rebuild the GR that way. But that leaves me with worrying about not getting everything exported/importing

    Thank you so much for your help :)

Children
No Data
© 2024 AVEVA Group Limited or its subsidiaries. All Rights Reserved.