ANGAR said:

Answer SEAO:

-The history of the Wall has been lost >> We are working on this issue

-The panoramic photo of the events is not displayed. >> Resolved

-Verifications can not be read >> We are working on this issue

-Advanced member search does not work >> We are working on this issue

-Gif photos of Connected Members are not displayed or have been lost. >> We are sorry to say but,we didn't get this issue.

We have checked all your reported support issues at our end and all issues have been closed and replied you in the respective support thread, but it has been not closed yet from your end. There is one support thread #47157 that is open on which we are already working with the priority and replying you at the same.

@ Donna,

The best strategy for backups (PHP and MySQL) is, which I always used to do in big/small offices or websites;

• daily backups 1 - 7 ( keep deleting the oldest)
• weekly backups 1 - 52 (on a saturday do two backups a daily and a weekly  (same backup but called different) delete the oldest of 52
• yearly backups 1 - xxxxxx as long as the company does exists. Extra backup on the last day of the year and never delete this one.

Keep the backups, if in an office, offsite. Also upload to a free or paid Cloud Service.

Never store all backups in the same location!

I store my daily backups in 3 locations;

1. One on the server in a protected directory
2. One on my personal computer with a copy to the external hard drive
3. One on a cloud service

• Weekly backups are off site, one on personal pc and one on external hard drive and one in the safe
• Yearly backups are stored in a fireproof safe

It is easy to set up using cron jobs daily, weekly, yearly and let them zip the public_html *.* into a folder like /DailyBackups /WeeklyBackups /Yearly backups

and make a routine to download the backups daily.

Test your backups at random (PHP and MySQL) by installing it on a network server and check the site. If you do, make sure you enter the right login, password and connection string in database.php and delete the cache.php and rename the cache.sample.php to cache.php. The cashing has the be set right "To File" to get the site working. Then you can test the site.

 A little more to read below why you should make a backup and what an IT Disaster Recovery plan is:

IT Disaster Recovery Plan not only for Offices but also for Online Businesses:

What is an IT Disaster Recovery Plan?

An IT disaster recovery plan is a process put in place for responding to unforeseen events affecting your data with a documented and structured approach and a clear set of instructions. These instructions include a step-by-step plan designed to greatly minimize the impact of any disaster and to allow your business to swiftly resume operations.

The broader terms business continuity or disaster recovery, generally  describe a similar concept. They are procedures allowing you to recover from a disaster quickly so you can continue your business with minimal disruption. However, the IT disaster recovery plan refers specifically to data and other IT operations.

The other two descriptions may also apply to procedures providing for things like replacement for damaged equipment or inventory and even additional part-time or full-time help where needed.

It begins by analyzing the business process and the continuity needs of the company. It requires a business impact analysis and risk analysis to establish the recovery time objective and recovery point objective — both important when setting up the plan.

Analysis

A thorough analysis of the existing digital setup is needed, including hardware, software, data, connectivity, network and more. This, of course, will depend on your business and the industry you happen to be in. The analysis should disclose the resources needed to allow the recovery of business functions and a time objective to recover those functions, as well as recovery point objective after a disaster.

The analysis will also include establishing a disaster-recovery team of employees. These should be employees with the most experience so they can be assigned with contact details and specific tasks. These individuals should be able to prioritize critical business functions and determine the speed of recovery.

Have methods of communication in the event cell towers and internet connections are down. Create a top down list so everyone can go through it until one is found that is working and connects the recovery team.

The next step involves designating a disaster recovery location where critical backup systems can be accessed allowing employees to work. For many small businesses this might be your home, hotel or the home of another business partner.

Have multiple means — phone, email, VOIP, etc. — for contacting everyone involved in the recovery process as well as for other employees, customers, vendors, suppliers, business partners, your insurance company and other resources that might be relevant for your particular business.

Make your customers aware of your emergency plan with alternative ways of getting in touch with you, placing orders, sending payments and even a backup business location. Your website is a great place to have this information.

Back up your digital information in more than one location.

Test your plan at least once a year to integrate new procedures and technologies and to eliminate those that are inefficient or no longer necessary for your business.

Who Should Implement an IT Disaster Recovery Plan?

The answer is every business, but not every business has the resources to implement such a plan with all the bells and whistles. So just having a plan and testing to see that it works no matter how small your business already puts you ahead.

However, for industries that totally rely on digital technology for their day to day operations, it is a must. And it should be as thorough as possible within the limits of your budget. Independent insurance agents, game designers, IT service providers, telecommunications companies and others come to mind as all in need of such a recovery plan. But in reality, it applies to every business that is using computers in their operations.

As far as the reason for implementing an IT disaster recovery plan, it is the same as the reason for buying insurance for your car or home. Having it will give you the peace of mind that you will be able to recover much quicker, not if, but when a disaster eventually strikes.

If the process sounds complicated and you don’t want to implement it yourself, you can have managed business continuity service providers do it for you. The price and services vary greatly, so shop around and choose a company that is able to address the particular requirements of your business.

Conclusion

Businesses, no matter how small or large are now more vulnerable than ever when it comes to cyber attacks. But disasters can also come from human error or nature, and in any event you need systems to deal with those situations and manage them effectively to minimize the negative impact. An IT disaster recovery plan will let you prevent if possible, or at least anticipate and mitigate any business interruptions to your business when a problem occurs.

@Maurits

Great info - thanks

In addition, I keep a month of dailies and also 12 monthlies (although the weeklies sortof should cover this, I like to have one at 'month-end' as well, especially for accounting purposes; I then keep the monthlies and annual for many years).  The JetBackup WHM Plugin I use provides a retention option (per each backup job) so I set that and after X times, it begins to rotate them.

Again, great post.

@GS,

Welcome

I am using in a year 60 backups and 59 on a rotating basis. I personally find it easier to do it my way to pinpoint back to an exact date.

I get +1 yearly backup per year extra.

If I calculate it correctly you are having 68 backups in total in use at all times and growing by 12(m)+1(y) a year

==>'If I calculate it correctly you are having 68 backups in total in use at all times and growing by 12(m)+1(y) a year'

Actually, a few more because I didn't explain myself well:

52 = Weekly (possibly 53? depending on DOW and leap year?  I can't recall)

12 = Monthly

31 = Daily

1 = Annual

96 Total (83 on a rotating basis) plus a few oddballs

Although that's my gameplan for SE, I'm not doing that yet as I'm not in production.  During development, I sometimes have multiple backups per day (and may continue that in the future).  So, the Total will most likely increase (at least in my non-SE accounting and business software installations it is often more).  Of course for larger sites live redundancy of files/database is a much better way to handle this, but I'm obviously not there yet.  In my experience, backup,. contingency, and retention plans (which all play a part in IT Disaster Mitigation & Recovery) are much more (or less) extensive as they are based on a myriad of factors.  But I digress... I'm already way off topic here.

I think that is "slightly" over the top  Can you imagine the user data of 10GB * 96.

I am always up for saving money but with the best results.

I worked in big finance companies, the amount of data is rediculous! Load balancing servers, cluster servers all over. Just incase one or two servers fail. Offsite backup storage servers also in clusters, all RAID 10. And on top of that a SMALL budget, sometimes you couldn't move. IT is the biggest most expensive investment in a company, to stay safe. People don't understand that. It is more expensive recovering data. It is not only restoring a backup but also the trading is interrupted for a day or even longer.

I am not in production yet. But hoping to start advertising next week. That will be a hard job to accomplish to start with an empty site!

Hi Donna,

I am happy to start with a new threat for backing up your site and will add your comment into it as well.

I am glad Angar's issues are being resolved. There is nothing more frustrating if software is not working.

Those of TMD Hosting make an automatic copy every three days. And I'm going to start making full copies of the site every week.