Guest User!

You are not Sophos Staff.

This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Restore to AWS UTM seems to lock it up

I built an hourly AWS UTM instance, walked thru all of the initial config stuff, updated it to 9.305-4. And everyrhing was working. I restored a backup from my UTM220, with host info removed, and how the AWS instance isn't coming backup after it rebooted.
Has anyone else tried/gad issues with this?


This thread was automatically locked due to age.
  • Probably a license issue, I don't think what you did is supported.  The AWS hourly instance uses a special license scheme I believe.

    CTO, Convergent Information Security Solutions, LLC

    https://www.convergesecurity.com

    Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries.  Use the advice given at your own risk.

  • I used a backup that has the host specific data including the license data stripped out of it.
  • It's not worth trying to fix it, thumphr.  Your 220 has eight NICs, and the AWS instance only one.  Did the right NIC get the interface you wanted in the restore - who knows?  You can delete that instance.

    If you don't have a spare 220, I think your best bet is to fire up a VM with 8 NICs, restore to that and configure it so that you can delete the other 7 NICs.  Then do an info-removed backup from it and restore to a new instance in AWS.  If that's also a broken restore, at least you can go back to your VM and try again.

    By the way, what is the purpose of a UTM instance in the cloud - is it part of a disaster recovery plan?

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • Yes for DR, We make heavy use of the Web Application Firewall routing and the goal would be to be able to restore a backup from the physical UTM to the AWS UTM make a few ip changes, bring up the replica VMs and Bob's your Uncle everything is back online while we deal with the issue at the physical data center.
  • "Bob's your Uncle" - I owe you a beer for teaching me that! [:D]

    I still think I'd go the route of the VM as a way to get the starting configuration.  If not, then just start from scratch in AWS.  You won't ever be able to do a backup/restore from 220 to AWS.  Then again, playing with the 220 and the VM, you might be able to figure out what NIC gets assigned where.

    Another idea would be to consider moving your UTM 100% to the cloud after the AWS UTM HA beta has created a reliable solution.

    Please do update us on your progress.

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Share Feedback
×

Submitted a Tech Support Case lately from the Support Portal?