Strict Standards: Accessing static property DB::$_app as non static in /storage/content/94/1008994/ on line 131 Strict Standards: Accessing static property DB::$_app as non static in /storage/content/94/1008994/ on line 976 Frequently Asked Questions
header left header right
Frequently Asked Questions

Q. Are the backups available for download from an FTP site?

A: No. The server doing the backups is not left on 24/7. Once the backups for the day have been made, the server is shutdown. There are many advantages to this approach. It is more environmentally friendly requiring less electricity, produces less heat and noise, hardware costs less, it takes up less room. Since the hdd is not on all the time, it is less likely to die an untimely abrupt death.

Q. Can we get access to all the backups?

A: Yes. Backups are not stored on a hdd that is always on nor are the backups web accessible. So backups are copied onto a new hdd and sent by snail mail. To restrict the frequency of these requests, a modest service fee is also charged. Cost Breakdown for sending all backups:

Hdd cost   ~9,000 yen (depends on the amount of data. But a good educated guess.)
Service Fee 20,000 yen
Shipping Costs ~2,000 yen (this is just a guess, will be adjusted)
Sales Tax 5%

Q. How long will these backups be kept?

A: The general rule of thumb is backups are kept for six months. Deleting backups is not a priority, so do not be surprised if the backups are kept for a longer period.

Q. Will any files be added to our web site?

A: Yes. There are four files which will be added to each web site:

/backup/.htaccess   Apache web server file which prevents web access to the backup folder. The backup folder contains the database sql dump files.
/inc/db.class.php MySQL database access class.
/site.php Contains the database connection information for each database.
/backup_db2sql.php Creates the .sql dump files which are stored in the backup folder. Which is only accessible by ftp.

Q. What information needs to be provided?

A: The order form contains the information which is needed for each web site to be backed up. The order form can be found by clicking the Getting Started menu item on any page.

Q. What happens when a hdd becomes full?

A: Hdd are filled to ~80% capacity. Once the hdd reaches this limit the administrator is notified automatically by email. The old hdd is stored and a new hdd is prepared. When all the data contained on a hdd is older than at least six months then the hdd might be used again. We would like to use newer hdds instead of continually using the same hdds. When hdd technology improves and the new hdd technology has made improvements in terms of reliability, and not necessarily just faster than we will move over to the more reliable technology as long as it is not price prohibitive.

Q. Which databases do you currently support?

A: Currently MySQL is supported. If there is demand then at that time we will start supporting additional databases like Oracle, PostgreSQL, and/or MS SQL.

Q. What payment options are available?

A: This has not been finalized. Hope to decided on a payment processing provider that supports payments in multiple currencies and does not do the forex processing. This is a very high priority for us.

Q. Why call this service Backup Report? Why not call it site backup?

A: A site backup is merely a task. Whenever a task is delegated, management needs to get regular updates on that tasks status. When it comes to back ups, Backup Report fulfills that reporting role. Backup Report service is to report on the status of site backups. Another issue is that a site backup is non-tangable whereas a Backup Report is tangable. So the service is centered around the tangable Backup Report and not the intangable site backup.