Goodness, no. It will definitely be longer than usual for the servers that are being merged, but not days. We'll post an estimate and an explanation of how the merge maintenance will work before the maintenance (very likely the day before).
previously they failed with first wave of paid services. their downtime was extended up to 14+ hours. isn't that a "throw half a million dollars worth of subscriptions away cause they screwed up"? :p nobody is safe from a mistake.
they have copies of our accounts... no doubts on that..
what they would likely do is do a trial run with the current specific accounts for both servers.. and then do a trial run on how things worked out..
then apply it the day of the downtime.
Frankly i can't really SEE there being much more then a 4 hour downtime for this.
servers go down, backups are made and then the databases merged onto one new server (or one of the already excisting servers are wiped and reloaded with the merged databases)
the process should be quite simple, as any conflicting data would be set to be blanked for change later or changed on the fly.
Make sure the PTS is running, and in good working condition, turn the cats on, and the catacomb (seven seals) as they still don't work. As with the extra downtime, i would expect a number of people will be rareing to spend some time playing on the pts.
12 hours, one less hour than was downtime when transfers started. They are no experienced in clicking Start -> Shutdown -> Restart -> OK. This saves them 60 minutes :D
i bet for more than 14h. previously they do it for hundreds of transfers. now they must do it for thousands of accounts which usually contain a number of toons. :p
edit: anyway, you must share the information about the secret trick with someone from L2 team. ;)
Goodness, no. It will definitely be longer than usual for the servers that are being merged, but not days. We'll post an estimate and an explanation of how the merge maintenance will work before the maintenance (very likely the day before).
i actually wonder why you have to post it at the very last day (as usually -.-) and not now o.o cause it seems you know pretty well how it will work
well it wouldn't make sense to keep servers that are uneffected by the merge to remain down for no reason at all
they would likely spending the intial time getting the nonmerging servers delt with and running first thing.... after they are up again, then start on the merge deal
From an experienced Database apps point of view, it will roll out one of three ways:
(A) Smooth - bit longer than usual, maybe 3 hours.
(B) Data integrity problems from the scripts handling the name changing, clan conflicts, etc. - 10-12 hours.
(C) They will launch in 3 hours, but then detect data corruption due to something they did not predict. They will have to roll back the data base and if you played during that time you will lose any drops / enchants / crafts / XP /etc.
From an experienced Database apps point of view, it will roll out one of three ways:
(A) Smooth - bit longer than usual, maybe 3 hours.
(B) Data integrity problems from the scripts handling the name changing, clan conflicts, etc. - 10-12 hours.
(C) They will launch in 3 hours, but then detect data corruption due to something they did not predict. They will have to roll back the data base and if you played during that time you will lose any drops / enchants / crafts / XP /etc.
From an experienced Database apps point of view, it will roll out one of three ways:
(A) Smooth - bit longer than usual, maybe 3 hours.
(B) Data integrity problems from the scripts handling the name changing, clan conflicts, etc. - 10-12 hours.
(C) They will launch in 3 hours, but then detect data corruption due to something they did not predict. They will have to roll back the data base and if you played during that time you will lose any drops / enchants / crafts / XP /etc.
(D) (after messing up the data base and loosing all the information as well as backups) They Pull an EA Stunt and announce That Lineage 2 NA will be shutting Down for good July 9th 2008.
Probably 4-5 hours I think. A database merge of this type shouldn't be that difficult, and yes they will have done a trial run or two.
I'm curious to know whether they are using some of the existing hardware for the new servers, or have new hardware, and will just turn off/stop renting the old stuff.
E.g. Hindemith + Gustin --> Phoenix (running on the old Gustin hardware), or --> completely new hardware, and stop using the old stuff.
(Yes I'm aware that each 'server' is many physical computers running in a cluster arrangement, but the new vs. old hardware question remains)
I'm curious to know whether they are using some of the existing hardware for the new servers, or have new hardware, and will just turn off/stop renting the old stuff.
E.g. Hindemith + Gustin --> Phoenix (running on the old Gustin hardware), or --> completely new hardware, and stop using the old stuff.
(Yes I'm aware that each 'server' is many physical computers running in a cluster arrangement, but the new vs. old hardware question remains)
I think they will rely on the old but utilzing fresh new ways to make our gameplay more exciting.
Here is the proposed Phoenix (gustin + hindemith or as I like to call it "Gustamith" equipment. Notice the action packed scene of Dino Island (http://storeforknowledge.com/images/oa-505.jpg) on the monitor.
Alyra:
Will the non-affected/non-merging servers be up as usual or are you bringing all servers up at once when all the work is done?
Okay, well I'm not Alyra ;), but I can tell you this...
All non-affected servers (so 1, 7, 9, 10 and 11) will experience a normal maintenance time on the day of the merges.
We are still waiting on some data, so we don't have this information available quite yet. We will announce the new server numbers on Monday, at the latest (although I'm hoping it will be sooner than that). As soon as I know, ya'll will know.
We are still waiting on some data, so we don't have this information available quite yet. We will announce the new server numbers on Monday, at the latest (although I'm hoping it will be sooner than that). As soon as I know, ya'll will know.
Sayha = Server #12
Aria = Server #13
Phoenix = Server #14
Thanks :)
Now I can make some preperations on my site and have the site up and running with the new servers before the servers go up tomorow from the down time :)
(I hope that the javaservlet that contains the servers status that is used by the official site will be updated during the downtime)
Sayha = Server #12
Aria = Server #13
Phoenix = Server #14
So they New Servers and not 3 of the Old 6?
Maybe they merge the data from the two servers to a new server. The numbers could be how their software handles the server designations. Why starting at #12? Not sure.
I'm not a computer person but that seems like it could be a logical explanation.
actually they figured at first note, that they about to make completely new servers by recombining others. also they noted that old names will be removed and never used again. so, this is obvious that they'll remove and never use again the numbers. new servers will have new numbers and new names, new players and new environment...
why 12? it's simple. we already have numbers 1, 7, 9...11 taken. numbers 2..6, 8 now are no use. so, first available number is 12.