trittnerxx wrote: »the fact the pts and live servers are connected is silly
trittnerxx wrote: »the fact the pts and live servers are connected is silly
Disable PTR until backend issue can be resolved.
Rollback NA to before PTR issue today for dupe problem resolution.
Start NA server and let people play while you figure out said PTR issue.
Doesn't seem like a many-hours downtime situation to me. Or at least it shouldn't be. Unless someone also deleted all of the server backups after they used the wrong folder path for the PTR database...
Disable PTR until backend issue can be resolved.
Rollback NA to before PTR issue today for dupe problem resolution.
Start NA server and let people play while you figure out said PTR issue.
Doesn't seem like a many-hours downtime situation to me. Or at least it shouldn't be. Unless someone also deleted all of the server backups after they used the wrong folder path for the PTR database...
Disable PTR until backend issue can be resolved.
Rollback NA to before PTR issue today for dupe problem resolution.
Start NA server and let people play while you figure out said PTR issue.
Doesn't seem like a many-hours downtime situation to me. Or at least it shouldn't be. Unless someone also deleted all of the server backups after they used the wrong folder path for the PTR database...
Disable PTR until backend issue can be resolved.
Rollback NA to before PTR issue today for dupe problem resolution.
Start NA server and let people play while you figure out said PTR issue.
Doesn't seem like a many-hours downtime situation to me. Or at least it shouldn't be. Unless someone also deleted all of the server backups after they used the wrong folder path for the PTR database...
Disable PTR until backend issue can be resolved.
Rollback NA to before PTR issue today for dupe problem resolution.
Start NA server and let people play while you figure out said PTR issue.
Doesn't seem like a many-hours downtime situation to me. Or at least it shouldn't be. Unless someone also deleted all of the server backups after they used the wrong folder path for the PTR database...
You have no idea how long any of those steps takes, as well as how long to decide what action to take. Leave it to the people who know what's going.
Disable PTR until backend issue can be resolved.
Rollback NA to before PTR issue today for dupe problem resolution.
Start NA server and let people play while you figure out said PTR issue.
Doesn't seem like a many-hours downtime situation to me. Or at least it shouldn't be. Unless someone also deleted all of the server backups after they used the wrong folder path for the PTR database...
They have scheduled maintenance tomorrow so consider this..... Even if they have a way forward tonight, are you going to call in an emergency team this late, pay them overtime and fees to push a new update, and eat the cost, when you can just wait until 3am tomorrow and they will be there anyway. As soon as I realized they had scheduled maintenance tomorrow I booted up my library of 2023 titles I still haven't completed.
Most games with a test server allow you to copy your characters from live to PTS.
This means they're usually connected *somehow*.
Disable PTR until backend issue can be resolved.
Rollback NA to before PTR issue today for dupe problem resolution.
Start NA server and let people play while you figure out said PTR issue.
Doesn't seem like a many-hours downtime situation to me. Or at least it shouldn't be. Unless someone also deleted all of the server backups after they used the wrong folder path for the PTR database...
You have no idea how long any of those steps takes, as well as how long to decide what action to take. Leave it to the people who know what's going.
Sorry, you're right. I'll leave it to the people who know what's going on. My previous idea to do it all myself was clearly a hasty decision.