Report a problem
Judy's Book takes violations of our Terms of Use very seriously. We encourage
you to read through our
Terms of Use
before filling report with us.
After careful review, we may remove content or replace a content warning page before
viewing content deemed offensive, harmful, or dangerous.
Additionally, we are aware that there may be content on Judy's Book that is personal
in nature or feels invasive. Please note that Judy's Book is a provider of content
creation tools, not a mediator of content. We allow our users express their opinions,
but we don't make any claims about the content of these pages. We strongly believe
in freedom of expression, even if a review contains unappealing or distasteful
content or present negative viewpoints. We realize that this may be frustrating,
and we regret any inconvenience this may cause you. In cases where contact information
for the author is listed on the page, we recommend that you work directly with this
person to have the content in question removed or changed.
Here are some examples of content we will not remove unless provided with a court
order:
Personal attacks or alleged defamation
Political or social commentary
Distasteful imagery or language
If we've read the Terms of Use and believe that this review below violates our Terms
of Use, please complete the following short form.
|
Businiess name:
Secure Data Recovery Services
|
|
Review by:
citysearch c.
|
|
Review content:
At our company we had a backup system in place - or, to be more precise, we _thought_ we did. Our server was configured to archive and sync all our critical data to an offsite storage system in a facility in another state. This would have been a proper and safe way to backup our data - had the data actually been saved in a readable format!!! We never had anything bad happen until a week ago, so we never really needed to restore from any of our backups. We just kept backing up and thought everything was dandy, until our server died right under our noses one fine morning and we needed to get back up and running STAT. So we quickly switched to our failsafe server, downloaded our latest backup archive from our out-of-state repository, and tried to unpack it and -- IT DIDN'T WORK!!!! The archive COULDN'T BE READ!!\r
We phoned Secure Data Recovery Services and told them this was an EMERGENCY - we needed to recover either the unreadable archive, or the data from our failed server, whichever, b
|
Reasons for reporting (512 characters left):
|
|
Reasons are required.
|
|
or
Cancel
|