#Tsm sniper string classic wow update
#Tsm sniper string classic wow full
#Tsm sniper string classic wow password

Lastly, the affected database has been running since 2016. WeвЂ™ve also built a number of additional tools to help us recover any lost data in the future, although, of course, we hope weвЂ™ll never need to use those. Next, we have addressed the gap in our database backup process which resulted in some user configuration data being lost, so any similar event in the future will just be a matter of quickly restoring the backups we have. This will have a non-negligible impact on our infrastructure costs, as it is certainly a non-trivial amount of data, especially with the change weвЂ™re making to not limit the number of backups we store for people but is the right thing to do given the importance of this data. This will prevent them from being irreversibly lost in the future, along with providing a mechanism to quickly recover them if any issues arise. We do take seriously the impact of this event and are working hard to correct things in the short-term, as we discussed above, as well as make immediate changes to prevent this from happening again in the future.ДЇirst and foremost, weвЂ™ve enabled multiple additional levels of redundancy and protection around our Premium user addon backups. WeвЂ™ve only had one outage like this in the past, but this one is significantly more serious given the loss of user data.

#Tsm sniper string classic wow password

This means Premium users no longer have to decide which backups to keep available long-term and all backups will be saved indefinitely.ДЇinally, if you created an account or reset your password on March 24th or March 25th and are having trouble logging in, it is recommended to re-create your account or reset your password again. We encourage those to reach out to and we will explore any available options to make this right.ДЄdditionally, with new resources available along with the protections and processes described in the next section of this post, we have removed the limit on the number of Premium user addon backups that can be marked as вЂsavedвЂ™ and stored by TSM in the cloud going forward. With this in mind, we have set up a dedicated contact address that is available to Premium users who may be missing an important backup that was not captured in the re-upload efforts.

#Tsm sniper string classic wow full

While we realize this does not guarantee a full recovery of all previously synced backups we have been able to get coverage of a majority of recent backups stored locally to Premium users. Working with a manifest of the missing files, we modified TSM Desktop Application (version r410) to re-upload any backup files that match the name from the recovered manifest. Naturally, the Premium user addon backups are the most critical.

After much work, we were successful at restoring some additional data which we otherwise didnвЂ™t have proper backups of, but unfortunately, this still left us at the list above of completely lost data.

On Saturday we brought the website back online in a read-only mode as we continued to try to restore some additional database data from a few raw database files which had not been corrupted. Additionally, a configuration issue with a script that manages Premium user addon backups also resulted in all backups being lost as a result of this outage. Unfortunately, we realized that our backup process had not been updated to include database tables related to Burning Crusade Classic. We take regular backups of our database and quickly worked to restore from those backups on Friday.

Some other user account-level and user configuration changes between 4am PDT on March 24th and when our website was brought back online including new accounts and any other changes made on our website during that time.

User configuration data for Group Notifications.

Desktop App realm selections for Burning Crusade realms.

However, there was some data which we, unfortunately, were not able to recover, which is listed as follows: After a ton of work, we have since been able to restore all of our services.

All users: Enable any Group Notifications previously selected on the Deal Notifications PageД®arly in the morning US time on Friday, March 25th, we were notified by our hosting provider that the hard drive containing our primary database died, and they were unable to recover any data from it.

All users: Re-select any Burning Crusade Realms previously configured on the Realm Selection Page for pricing data.

#Tsm sniper string classic wow update

Your app should update automatically, but you can download it here manually.

All users: Update the TSM Desktop Application to the latest version (r410).

LetвЂ™s start with the actions you are recommended to take as a TSM user: