We do have backups nightly to a dedicated drive. We ARE looking for a less expensive Cloud Storage ~TB solution for offsite backups.I am assuming your team has backups of the website in the event something goes wrong. It might be a good idea to utilize differential backups so that they can restore much quicker as opposed to using incremental backups (but the tradeoff is differential backups take longer to save as opposed to incremental backups). Plus, keep encrypted backups on a Cloud Storage as a Service provider's SAN (Storage Area Network).
I know, when the site was down for so long, evil thoughts began to creep into my head, like maybe DP was shutting down for good, or something stupid like that. I was wondering what I would do for entertainment without this forum.I almost went into depression.
'/tired': I'll bet. Quite a bit of a marathon session to sort that out.Events:
Notes:
- Last week, it was confirmed that we had the green light for migration.
- Yesterday
- the server was cloned (took almost 6 hours)
- upgrade proceeded
- reboots during the upgrade failed, several were needed
- upgrade failed
- level 3 techs had to login to assist
- upgrade completed after 16 hrs
- A symlink (sorry for the technical) was missing to our database. Troubleshooting.
- This morning I verified the data is there and was not missing! We were concerned to say the least.
- Finally, I had given very specific instruction on our redis server before the upgrade, but the config file was missing.
- Add cloned drive to the server
- Verify database was a mirror
- Copy/paste config file to from clone, restart redis - badah bing!
They completely ignored both of these requests.
- I formally asked the technical team to preserve the redis.conf file
- We also informed them that a bios update was needed else there would be reboot issues
/tired
You are both awesome! Glad it's back up and running.Thanks to @Schweddy for his tireless patience and determination to get DP back up and running! It was a long 24+ hours of waiting, frustration and cursing on our end. We hope to never be in this situation again.
Events:
Notes:
- Last week, it was confirmed that we had the green light for migration.
- Yesterday
- the server was cloned (took almost 6 hours)
- upgrade proceeded
- reboots during the upgrade failed, several were needed
- upgrade failed
- level 3 techs had to login to assist
- upgrade completed after 16 hrs
- A symlink (sorry for the technical) was missing to our database. Troubleshooting.
- This morning I verified the data is there and was not missing! We were concerned to say the least.
- Finally, I had given very specific instruction on our redis server before the upgrade, but the config file was missing.
- Add cloned drive to the server
- Verify database was a mirror
- Copy/paste config file to from clone, restart redis - badah bing!
They completely ignored both of these requests.
- I formally asked the technical team to preserve the redis.conf file
- We also informed them that a bios update was needed else there would be reboot issues
/tired
Sounds good.The changes from this weekend made zero changes to the experience. No extra buttons or whistles. This was necessary so that we can continue to have an experience here with the latest security updates.
The changes last week upgraded our database to the latest software which is supposed to allow a lot more people to connect at one time.
Nor am I. Probably on the "moron mirror" since my IQ is 79.There are actually two mirrored forums. The good posters are on one, and the morons relegated to the other. Neither group knows about the other parallel universe.
Not sure which one we're on
Or to paraphrase every Osprey pilot: "please don't crash".Thanks, guys. Sorry for all the agita you went through to get up and running. To paraphrase Sally Field, you must really like us.
When listening to software salespeople, the terms "improved", "supposed to", "intended", "tested", and "better" should always be regarded as meaningless noises designed to increase sales prospects and not much else (along the lines of "low mileage" and "well maintained" and "immaculate" when uttered by used car salespeople).
Better a forum crash than a pilot and his crew.Or to paraphrase every Osprey pilot: "please don't crash".
You did your best, it all worked out in the end, relax. We love this site.Red worked double shifts at his job all weekend.
Was just me, myself and I. However, he did checkin and give guidance not to punch the ****ing wall a few times!
Sounds like someone needs a talking to.Events:
Notes:
- Last week, it was confirmed that we had the green light for migration.
- Yesterday
- the server was cloned (took almost 6 hours)
- upgrade proceeded
- reboots during the upgrade failed, several were needed
- upgrade failed
- level 3 techs had to login to assist
- upgrade completed after 16 hrs
- A symlink (sorry for the technical) was missing to our database. Troubleshooting.
- This morning I verified the data is there and was not missing! We were concerned to say the least.
- Finally, I had given very specific instruction on our redis server before the upgrade, but the config file was missing.
- Add cloned drive to the server
- Verify database was a mirror
- Copy/paste config file to from clone, restart redis - badah bing!
They completely ignored both of these requests.
- I formally asked the technical team to preserve the redis.conf file
- We also informed them that a bios update was needed else there would be reboot issues
/tired
Your hard work is appreciated! Kudos.Events:
Notes:
- Last week, it was confirmed that we had the green light for migration.
- Yesterday
- the server was cloned (took almost 6 hours)
- upgrade proceeded
- reboots during the upgrade failed, several were needed
- upgrade failed
- level 3 techs had to login to assist
- upgrade completed after 16 hrs
- A symlink (sorry for the technical) was missing to our database. Troubleshooting.
- This morning I verified the data is there and was not missing! We were concerned to say the least.
- Finally, I had given very specific instruction on our redis server before the upgrade, but the config file was missing.
- Add cloned drive to the server
- Verify database was a mirror
- Copy/paste config file to from clone, restart redis - badah bing!
They completely ignored both of these requests.
- I formally asked the technical team to preserve the redis.conf file
- We also informed them that a bios update was needed else there would be reboot issues
/tired
If you were a loyal Wal-Mart shopper you would wear your jammies to your local store to shop in.Thanks to you and Red for all the work and frustrations while I and the other mods enjoyed a "snow day" and never had to get out of our jammies!
You'd need Rasmussen for that.Lol. I suspect (and hope) the ratio would deviate down from 1:1 at least a little if the entire membership were polled.
Events:
Notes:
- Last week, it was confirmed that we had the green light for migration.
- Yesterday
- the server was cloned (took almost 6 hours)
- upgrade proceeded
- reboots during the upgrade failed, several were needed
- upgrade failed
- level 3 techs had to login to assist
- upgrade completed after 16 hrs
- A symlink (sorry for the technical) was missing to our database. Troubleshooting.
- This morning I verified the data is there and was not missing! We were concerned to say the least.
- Finally, I had given very specific instruction on our redis server before the upgrade, but the config file was missing.
- Add cloned drive to the server
- Verify database was a mirror
- Copy/paste config file to from clone, restart redis - badah bing!
They completely ignored both of these requests.
- I formally asked the technical team to preserve the redis.conf file
- We also informed them that a bios update was needed else there would be reboot issues
/tired
Ditto...I’m sure I speak for everyone in thanking you for your hard work.
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?