Frequently Asked Questions

Is CYA SmartRecovery a system-level backup product?
No. Traditional backup and recovery solutions such as Symantec VERITAS NetBackup, EMC NetWorker, and IBM Tivoli Storage Manager protect against failures and site disasters affecting an entire system infrastructure including operating systems, applications, and data, whether the data is from a SAP, CRM or ECM application.

CYA SmartRecovery provides granular recovery from partial information loss incidents that occur within the ECM repository. These incidents, which according to AIIM International and Strategic Research Inc. account for more than 80% of all ECM information loss, are caused by common occurrences such as programmatic, operational, user, and logical errors, malfeasance, viruses or metadata corruption. When a partial information loss incident occurs, CYA SmartRecovery quickly restores only the lost or corrupt content and its related metadata back into the repository to its original state, without any ECM application downtime. The solution also works seamlessly WITH system-level backup products to help reduce the ECM data loss window in the event of a disaster or full system failure to within 15 minutes, but it’s not designed to be a standalone, system-level backup product.

What is partial information loss?
Partial information loss incidents, which result in the loss or corruption of one, several, or thousands of pieces of information within an ECM repository, are caused by common occurrences such as programmatic, operational, user, and logical errors, malfeasance, viruses or metadata corruption. According to Strategic Research Inc. & AIIM International, these incidents account for more than 80 percent of ECM data loss. These chronic incidents degrade the bottom line of all companies over time, unless a granular recovery and integrity solution like CYA SmartRecovery is put in place.

The ramifications of these incidents are far-reaching, and can include millions of dollars in lost potential revenue and productivity, significant fines and penalties due to non-compliance with regulatory mandates and legal requirements, negative brand exposure, and in extreme cases, business shutdowns and jail time for executives. Even if you’re not aware of any partial information loss incidents within your organization, it is certain that they have occurred, and will continue to occur. People aren’t always fully aware of these incidents, or their true impact, until it’s too late. Many incidents are not reported because the IT department, stretched thin meeting a variety of needs, cannot justify conducting a full system restore for a granular amount of information, forcing the user to spend time recreating it, usually unbeknownst to management.

Traditional backup and recovery solutions, while ideal for recovery from full system failures and disasters, are not designed for recovery from partial information loss incidents. Trying to use these solutions to recover a granular amount of information results in ECM system downtime, as well as the loss of all changes and additions to the ECM repository since the last backup was created. To learn more about partial information loss and its impact, read Partial Information Loss: Your Business’ Silent Scream by storage journalist Mark Ferelli.

What is granular recovery?
Granular recovery refers to the act of recovering one, several, or thousands of objects that have been lost or corrupted. This is different than the functionality provided by traditional recovery solutions, which are designed to recover an entire system infrastructure. The ability to perform hot, granular recovery operations with CYA SmartRecovery empowers companies to rapidly recover from incidents of partial information loss, which account for more than 80 percent of ECM data loss according to Strategic Research Inc. & AIIM International.

Partial information loss incidents are caused by common occurrences such as programmatic, operational, user, and logical errors, malfeasance, viruses or metadata corruption. With CYA SmartRecovery, companies can protect their ECM investment and facilitate compliance by restoring only the lost or corrupted information back to its original state in the repository within minutes, with no application downtime.

What does “object integrity” mean?
To explain object integrity, one needs to first define an object. An object is comprised of both content and metadata (e.g. annotations, audit trails, digital signatures, workflows), and usually refers to an individual document. Integrity refers to preserving the original relationships between the content and metadata contained within an object. Object integrity can be compromised by traditional backup methods and recovery solutions which capture content and metadata asynchronously. This can result in broken relationships between the two, causing information to become corrupt or inaccessible. It also results in non-compliance with regulatory mandates such as Sarbanes-Oxley that require the preservation of content and metadata.CYA SmartRecovery preserves object integrity by capturing content and metadata in a single, synchronous pass, facilitating compliance and ensuring the accuracy of information in your ECM repository.

What is metadata and why is it important?
Metadata is traditionally defined as “data about data.” In the ECM world, metadata refers to the audit trails, workflows, renditions, digital signatures, and other properties associated with a document or specific sets of content. It also includes complex process and lifecycle information, which is often customized to meet the user organization’s environment and application. ECM systems dynamically create and manage the entire content lifecycle along with its associated metadata. An infrastructure of metadata is built around the content (documents and transactions) as it is added to the ECM repository. If it lost or corrupted, it can cause significant, negative impact to the business.

Take, for example, the government procurement manager coordinating responses from defense contractors replying to an RFI for a guidance system. The procurement manager must be certain that the response documents, which may include a contracts section, an engineering section, a project management section, specific responses to questions, and a number of appendices, are routed through the various steps integral to the contractor selection process. As the responses move through these steps, they “collect” metadata - workflows, digital signatures, approvals and renditions. Any loss or corruption of this metadata could significantly delay the contractor selection process.

Metadata is also important because its preservation is required by legal initiatives (i.e. The Federal Rules of Civil Procedure eDiscovery Rules Amendment), and numerous regulatory mandates (i.e. Sarbanes-Oxley) holding IT and business managers liable for the retention of unaltered information down to the individual record. Without proper safeguards, the loss of ECM system metadata carries the liability of non-compliance, the result of which can include significant fines, negative brand exposure, and even jail time. Preserving ECM content and metadata such as audit trails while ensuring granular recoverability and creating a demonstrable “chain of custody” can help organizations avoid many of the risks associated with the loss or corruption of complex ECM system information

We are not aware of any partial information loss incidents at our company, so why should we consider buying CYA SmartRecovery?
Even if you’re not aware of any partial information loss incidents within your organization, it is certain that they have occurred, and will continue to occur. People aren’t always fully aware of these incidents, or their true impact, until it’s too late. Many incidents are not reported because the IT department, stretched thin meeting a variety of needs, cannot justify conducting a full system restore for a granular amount of information, forcing the user to spend time recreating it, usually unbeknownst to management.

The loss of an individual document may not seem like a big deal, but according to a “Cost of Downtime” survey from Deloitte, it will cost you between $2,000 and $8,000 per MB. And most likely you won’t be able to recreate the critical metadata (audit trails, workflows, digital signatures) associated with the content, putting you in non-compliance with regulatory mandates requiring the preservation of information such as Sarbanes-Oxley. Even if you’re willing to suffer those consequences, think about how these chronic incidents will affect your bottom line over time – consider what else you could do with the money spent dealing with these incidents, such as invest in a better IT infrastructure and hire additional staff.

The consequences of these incidents can also be more immediate and far-reaching, resulting in halted productivity, lost potential revenue, and in extreme cases, business shutdowns. For example, consider the real world incident where an administrator administered a faulty query that halted thousands of workflows, or the one where a misplayed keystroke resulted in deletion of 8,000 subcontractor bids, delaying the construction of an entire industrial city for months and causing extreme negative brand exposure. Read more about real incidents like these and their consequences in the white paper Partial Information Loss: Your Business’ Silent Scream by storage journalist Mark Ferelli.

Can’t I recover lost or deleted information from my backup files?
While it is possible to recover lost or deleted information from backup files, locating the information you want to recover can consume significant time and resources, and in order to recover it, you must roll back to the last known good backup – you cannot recover only the lost or deleted information In addition, it is impossible to recover the critical metadata (audit trails, workflows, digital signatures, etc.) directly back into the repository in its original state, which is crucial for maintaining compliance with industry and government regulatory mandates. With CYA SmartRecovery, one administrator can locate the affected information within seconds using powerful search functionality that leverages the folder structure of your ECM system. Content and its associated metadata can be recovered back to its original state in the repository with just a few mouse clicks, and without any application downtime.

Our users are not allowed to delete within the ECM repository, so why do we need CYA SmartRecovery?
There are multiple causes of information loss besides accidental deletion which include programmatic, operational, and logical errors, malfeasance, viruses, and metadata corruption. In addition, information loss associated with human error can be caused by events other than end user deletions. It can occur during routine system administration practices where accidental entries and incorrect parameters are defined. Other causes could be miscommunication between users and administrators, or errors due to lack of experience.

How does CYA SmartRecovery help us quickly respond to information requests related to compliance audits, inspections, and e-discovery?
CYA SmartRecovery helps organizations quickly respond to information requests by enabling fast and easy retrieval of granular ECM objects that have been lost or corrupted due to partial information loss incidents. Within minutes, just one administrator can locate the needed information using CYA SmartRecovery’s intuitive interface while the ECM system stays online. Because CYA’s application-aware, near-CDP technology captures, validates, and preserves content and metadata in its original state, your can be confident that you will be able to easily comply with requirements from the SEC, Sarbanes-Oxley, the Federal Rules of Civil Procedure eDiscovery Rules Amendment, and other initiatives related to the preservation of authentic information at the record level.

I was told that our existing backup and recovery solution has granular recovery functionality, so why do I need CYA SmartRecovery?
Some more traditional backup and recovery solutions allow administrators to recover granular content, but they don’t recover the critical, associated metadata that provide the context for the content. CYA SmartRecovery restores granular content and all its associated metadata, such as audit trails, workflows, lifecycle states, and digital signatures directly back into the repository in their original states. These metadata must be protected to ensure that the authenticity of the information being recovered isn’t compromised. A user or administrator cannot manually recreate metadata, and therefore if it is unrecoverable, the information is considered corrupted. This puts companies at risk for significant legal fees and fines should the information be requested for audits, e-discovery or other compliance-related purposes.

How can CYA SmartRecovery help my company achieve stringent recovery point objectives (RPOs)?
CYA SmartRecovery’s application-aware, near-CDP technology helps your company achieve very stringent RPOs in response to all causes of ECM information loss. Any-point-in-time recovery capabilities enable the recovery of granular objects that have been created or modified as little as 15 minutes ago in response to partial information loss incidents. A time-based recovery feature ensures you can achieve RPOs of less than 15 minutes in the event of a system failure or natural disaster by enabling you to roll forward to the most recent CYA capture after using your traditional recovery solution to roll back to the last known good backup.

How does CYA SmartRecovery complement traditional backup and recovery solutions?
Should a full system failure or disaster occur, CYA SmartRecovery works seamlessly with traditional solutions such as EMC NetWorker, Symantec VERITAS NetBackup, and IBM Tivoli Storage Manager to achieve recovery point objectives (RPOs) of just 15 minutes. The ECM system can be rolled back to its last known good state using the traditional solution, and then rolled forward to the most recent CYA SmartRecovery capture. In addition, when a partial information loss incident occurs, a single administrator can use CYA SmartRecovery to recover just the needed information within minutes while the ECM system stays online, ensuring there are no user disruptions. Traditional backup solutions are not effective in these scenarios because the entire system must be taken offline and rolled back in order to recover granular information, resulting in additional information loss and halted user productivity.

What are the information synchronicity issues associated with more traditional “hot” backup methods and how does CYA SmartRecovery help solve them?
“Hot” backup solutions have become very popular since they eliminate the need to take applications offline for the backups. However, these solutions frequently back up the file server containing the ECM content and the database containing the content’s related, complex metadata asynchronously – one after the other. This can result in broken relationships, because changes can be made to one or the other by users during the backup process. These broken relationships, or corruptions, render information inaccessible, causing lost productivity and non-compliance with regulations requiring the preservation of information down to the individual record.

Some solutions such as EMC NetWorker Module for Documentum (NMD) do perform hot, synchronous backups of EMC repository information, however, they still cannot recover granular objects (content and metadata) directly back into the repository in their original state. CYA SmartRecovery captures ECM content and metadata in a single, synchronous pass while the application remains online to ensure information integrity and authenticity while maintaining user productivity. Organizations can be confident that should they need to recover information, they will be able to restore both the content and its associated metadata back to the repository in its original state. Read more about the differences between CYA SmartRecovery and NMD.

Can CYA SmartRecovery help me proactively identify corrupt information in my repository, before it’s discovered by users?
Yes. The optional Data Integrity Module (DIM) performs integrity checks that automatically identify the broken relationships (corruption) that typically exist in repositories between content and its associated metadata. This empowers administrators to perform preventative maintenance on the repository by enabling them to resolve corruption issues before a user attempts to access the information for an audit, inspection, or general business demand. CYA also offers a Data Integrity Service that includes repository corruption identification and analysis, and the development and execution of a plan for effective corruption remediation.

Does CYA SmartRecovery facilitate compliance with records management policies?
Yes, CYA SmartRecovery facilitates compliance with records management policies by enabling administrators to specify a retention period which when expired triggers permanent deletion of records from CYA backups. In addition, it permanently purges records in accordance with ECM application records retention policies such as EMC Documentum Retention Policy Services.

My ECM vendor recommends cold backups but our business requirements are driving the need for hot backups. How does CYA SmartRecovery help with this?
Your vendor is recommending backups be taken cold due to the risk of data corruption that is associated with most hot backups. An ECM system is comprised, at the most basic level, of a content storage location and a database containing critical metadata that is linked to the content (audit trails, digital signatures, etc.). Most hot backup solutions are application-unaware, and capture the content and the data asynchronously (one after the other), which can break the relationships between them. These broken relationships render the information corrupt, and can cause lost productivity, lost potential revenue, and non-compliance with regulations requiring the preservation of information down to the individual record.

CYA SmartRecovery ’s application-aware architecture leverages the application programming interfaces (API’s) of the ECM system, enabling it to capture content and metadata synchronously (at the same time) while the ECM system stays online. This ensures that the links between the content and metadata remain intact, so that if the information needs to be recovered for a compliance or general business demand, it can be retrieved quickly and easily in its original state.

In the case of a disaster that forces you to rebuild your ECM system using a traditional, hot backup that contains unsynchronized and potentially corrupt information, CYA SmartRecovery is able to use the information it has captured to repair and rebuild damaged or missing information caused by the hot backup used to restore the system.

We are migrating to the latest version of our ECM software. How does CYA SmartRecovery protect our ECM information from corruption and loss during the migration?
CYA has found corruption in over 80% of its customers’ ECM repositories. If you migrate repository corruptions to your new environment, they can become unrepairable, resulting in the inability to produce information in response to business and compliance demands, and costing you significant time and money.

The optional Data Integrity Module (DIM) within CYA SmartRecovery identifies all of the corruptions that can render your valuable information useless. DIM performs over 70 checks that identify referential integrity issues caused by everyday operational and user errors, which often go unnoticed until they cause budget-busting delays in the data conversion process. DIM:

Ensures upgrade success and prevents halted migration timelines by identifying corrupt and inconsistent objects so issues can be proactively resolved prior to data conversion.
Guarantees the integrity of migrated data, ensuring that accurate information can be rapidly accessed in response to business, compliance, and legal demands.
Maintains repository integrity post-upgrade by enabling the administrator to schedule automatic integrity checks.

CYA also offers a Data Integrity Service which includes identification and in-depth analysis of repository integrity issues, along with the development of a corruption remediation plan.

How is CYA SmartRecovery licensed?
CYA SmartRecovery licenses are based on the number of servers/CPUs associated with an ECM implementation. Please contact CYA Sales at 203.513.3111 ext. 501 or send an email to sales@cya.com for additional information.

What is the difference between CYA SmartRecovery and the various recycle bin products on the market, including CYA Recycle Bin?
Recycle bin products typically only recover items that have been accidentally deleted by a user. However, accidental deletions account for only a small portion of incidents causing ECM partial information loss. Other incidents contributing to ECM information loss include programmatic, operational, and logical errors, viruses, and metadata corruption.

In order to protect your organization against all forms of ECM partial information loss, which collectively accounts for over 80% of all ECM data loss according to AIIM International and Strategic Research Inc., you need an ECM-specific granular recovery solution like CYA SmartRecovery. CYA SmartRecovery enables IT administrators or help desk personnel to rapidly recover granular objects that have been lost or corrupted due to any type of partial information loss directly back into the repository, without any application downtime. By performing hot, synchronous backups that maintain information integrity, the solution mitigates the need to take the ECM application down for backups. CYA SmartRecovery also works seamlessly with existing disaster recovery solutions to achieve recovery point objectives (RPOs) of less than 15 minutes.

Deploying both CYA SmartRecovery along with a recycle bin product such as CYA Recycle Bin empowers you to cost-effectively achieve maximum protection against all forms of ECM information loss.

Backup & Recovery Process

How often and for how long do we have to bring our ECM system down to use CYA SmartRecovery?
Your ECM system never has to be taken offline to use CYA SmartRecovery. Both the information capture and recovery processes are performed while the ECM system stays online.

Our ECM system must adhere to stringent government regulations requiring extensive auditing of all repository-related events. When a recovery is performed, what type of logging and/or audit trail does CYA SmartRecovery create?
CYA SmartRecovery provides multiple levels of logging that can be configured on a per recovery basis. The detail of the log file can be modified to output an entry for every instance required for the recovery of content and metadata. In addition, CYA SmartRecovery can create an audit trail object during the recovery process that indicates a recovery was performed, ensuring compliance for the organization.

How is a recovery with CYA SmartRecovery different than restoring a content file based on the results from running a file report job?
The CYA SmartRecovery recovery process restores not only content, but also all of its associated metadata, such as its audit trails, workflows, lifecycle states, and digital signatures. These metadata must be protected and recoverable to their original states to ensure that the authenticity of the information being recovered isn’t compromised. A user or administrator cannot manually recreate metadata, and therefore if it is unrecoverable, the information is considered corrupted. This puts companies at risk for significant legal fees and fines should the information be requested for e-discovery or other compliance-related purposes.

How frequently can I back up my repository information, and how does this impact my users?
With CYA SmartRecovery, you can perform hot, synchronous backups of your repository as frequently as every 15 minutes. The impact on your users is minimal – it’s the equivalent of one additional user accessing the ECM application.

What kind of overhead does CYA SmartRecovery put on the system during the capture process?
Minimal. CYA SmartRecovery uses proprietary application-aware, near-CDP technology to identify the incremental content and properties that are being added to and changed in the repository. By leveraging this intelligent functionality, it significantly reduces system overhead and the related storage costs that would typically be associated with the processing and maintenance of large amounts of redundant information. The impact to the system is equivalent to a single user accessing the repository.

What happens if the metadata associated with the content becomes corrupted – do the corruptions become part of the CYA SmartRecovery backups?
Maintaining the integrity of the content and its associated metadata is required to ensure compliance with government and industry regulatory mandates. CYA’s proprietary application-aware, near-CDP technology fully understands the repository framework, enabling CYA SmartRecovery to intelligently identify metadata corruption during the capture process. In order to maintain the integrity of information, CYA SmartRecovery does not capture corrupted information. Instead, its Data Integrity Module (DIM) creates a comprehensive log that identifies the corruptions and notifies the administrator so that they may be proactively resolved.

Does CYA SmartRecovery notify users or administrators of corrupt metadata?
CYA SmartRecovery’s Data Integrity Module (DIM) proactively identifies broken relationships (corruption) that typically exist in repositories between content and its associated metadata, and flags them for an administrator so they can be proactively resolved. Users are not notified.

In addition, CYA SmartRecovery will alert administrators to any corruptions found during a capture operation via the LOG file created for that operation.

Does CYA SmartRecovery enable me to proactively identify information that has been removed/ deleted from the repository?
Yes. CYA SmartRecovery facilitates rapid, granular recovery by enabling the administrator to see at a glance what specific information within the repository has been “hard” deleted based on a particular date range, folder, or other criteria. Just the needed information can be recovered with a single keystroke.

Are new dates and point-of-access information added to information once it is restored?
No. During the capture process, CYA SmartRecovery preserves the dates, point-of-access information, and other metadata associated with the information in the repository, so that when you perform a recovery operation, it is restored with all of its original properties, including its authentic and complete audit history.

What is the typical recovery time for a singular object?
Objects that require recovery, whether it is a single object or a complete folder structure, can be quickly and easily identified using the user-friendly CYA SmartRecovery interface. Actual processing time for the recovery varies based on the amount of information that needs to be recovered to its original state, and the environment into which it is being recovered, but using CYA’s proprietary architecture, the recovery operation is very efficient and does not impact ECM system performance while it is running. Most recovery operations are completed in seconds or minutes, and the ECM system is never brought offline so your user remain productive during the entire recovery process.

How much administrative support is required to perform recovery operations?
One administrator can perform a recovery operation in just minutes with just a few keystrokes – all while the ECM system stays online. CYA SmartRecovery uses an intuitive, graphical interface that leverages the infrastructure of the ECM repository so that it’s extremely easy for administrators to locate the information they wish to recover.

Integration & Installation

Is any extra hardware required for CYA SmartRecovery?
No. CYA SmartRecovery runs on the same server on which your ECM system resides, so extra hardware is not required (however, we do require a separate location for storing captured information).

How much disc space does CYA SmartRecovery require?
Space requirements for CYA SmartRecovery vary by environment – they are based on the size, rate of change, and population growth of the ECM repository. Because CYA SmartRecovery is creating a complete carbon-copy of your ECM system and protecting all your information in an authentic state, space requirements are similar to those for the content and metadata in your repository, though CYA SmartRecovery offers compression to help reduce them.

Does CYA SmartRecovery support add-on applications from our ECM vendor or their ISV partners?
Yes. CYA SmartRecovery supports the applications and software solutions that follow the ECM system content server framework. In the case of EMC Documentum, this includes modules such as Web Publisher, Documentum Compliance Manager (DCM) and add-on solutions from Documentum ISV’s such as McLaren Software’s Enterprise Engineer and Qumas’ QdocCompliance.

Is CYA SmartRecovery compatible with my company’s existing storage infrastructure?
Yes. The information captured with CYA SmartRecovery can be written to any type of network-addressable storage device, whether it be a NAS or SAN device, or simply an array of discs added to an existing server. Additionally, it can be seamlessly transferred to IBM Tivoli Storage Manager, Symantec VERITAS NetBackup, or EMC NetWorker, or to low cost storage devices such as CAS (content addressable storage).

Our ECM deployment has been integrated with other enterprise systems such as SAP and Peoplesoft. Does your application support integration with those applications?
Yes, CYA SmartRecovery captures and recovers the necessary relationships managed within the repository directly through the ECM system's application programming interface (APIs). This makes it compatible with any front end or third party integration that leverages the ECM system's repository for storage.

Does CYA SmartRecovery have a Web-based client option?
CYA SmartRecovery for IBM FileNet P8 version 4.0 has a Web-based client with a central management console that enables all operations to be managed from any location.

CYA SmartRecovery for EMC Documentum does not have a Web-based client; it includes a multi-platform recovery client application that can be installed on the ECM system server or on an administrator’s local machine.

Does CYA SmartRecovery require a dedicated server?
No. CYA SmartRecovery is implemented on the ECM system server and doesn’t require dedicated server hardware. The software accesses the repository utilizing a single client connection.

How long does it take to be up and running with CYA SmartRecovery?
CYA SmartRecovery is an out-of-the-box solution that can be up and running in as little as three days. A comprehensive Rapid Deployment Service (RDS) program is available that ensures a fast start-up process minimizing impact on day-to-day operations. This program includes the services of a CYA-authorized technical resource that assists you with analysis, installation, configuration, testing and the knowledge transfer necessary to deploy the software in the fastest way possible. Because the product leverages your ECM system interface, training is simple.

How frequently are software upgrades released? When can I expect support for the latest version of my ECM software?
CYA typically releases its product upgrades to coincide with the upgrades released by the ECM vendors it supports. Occasionally, hot fixes are released between releases from the ECM vendors. CYA leverages its partnerships with the ECM vendors to obtain advanced releases of ECM applications, allowing it to offer updated versions of its products that support these upgrades within a few weeks of their release to the public.

How long does it take to deploy a new version of CYA SmartRecovery?
Deploying a new version of CYA SmartRecovery into an environment where an older version of already exists is as simple as re-running the installation wizard, which usually takes less than 10 minutes, and checking the release notes for any configuration changes from the prior version. Typically, this includes adding an additional parameter or two to the existing configuration files. In the case that the updated version of CYA SmartRecovery coincides with a major ECM Object Model change, a re-capture of historical information is necessary to protect the newly migrated objects in their latest state. This can be performed as background processing, while new data is being protected as it is created or modified.

CYA SmartRecovery for EMC Documentum

How is CYA SmartRecovery different from EMC Networker and EMC Networker Module for Documentum (NMD)? Why would I need both products?
EMC Networker and NMD protect against system and site disasters affecting an entire system infrastructure including operating systems, applications, and data, whether the data is from a SAP, CRM or ECM system. CYA provides granular recovery in response to partial data loss incidents, which account for over 80% of all ECM data loss and may be caused by operational, logical, and programmatic errors, malfeasance, viruses or corruption.

When a partial data loss incident occurs, CYA SmartRecovery quickly recovers the lost content and metadata back into the Documentum repository in its original state, without any Documentum downtime. In addition, NMD can recover the database, content and indices for the entire Documentum repository, but it does not recover granular content and metadata (objects) directly back into the repository or maintain their authenticity. CYA SmartRecovery recovers objects directly back into the repository while validating and preserving the original relationships between the content and metadata, facilitating compliance with initiatives requiring information preservation down to the individual record, such as Sarbanes-Oxley and the Federal Rules of Civil Procedure eDiscovery Rules Amendment.

In order to ensure complete protection from all causes of ECM information loss, it is imperative to deploy both a system-level recovery solution such as NetWorker/NMD alongside a granular recovery and integrity solution like CYA SmartRecovery. Read more on this topic.

In what ways does CYA SmartRecovery work with eRoom?
CYA SmartRecovery will protect eRoom information only if eRoom is integrated with the Documentum repository, and the information resides within the repository in addition to residing in eRoom.

Is CYA SmartRecovery still able to recover in the event the EMC Documentum Server Dm_Clean and Dm_ Filescan jobs run?
CYA SmartRecovery is able to recover information as long as it’s been captured at some point in time, regardless of whether these two jobs have been run, and how long it has been since they were run.

CYA SmartRecovery for IBM FileNet P8

How does CYA SmartRecovery enable me to perform hot, synchronous backups of the FileNet P8 repository with our traditional backup and recovery solution?
CYA SmartRecovery performs synchronous, incremental captures of content and metadata within the repository as frequently as every 15 minutes while FileNet P8 remains online, maintaining information integrity and authenticity, and enabling the resolution of synchronicity issues introduced from traditional hot system backup methods and recovery solutions such as continuous data processing (CDP). In the event of a system crash, the P8 object store can be rolled back to the last good backup using a traditional recovery solution, then rolled forward to the most recent CYA capture, resolving synchronization issues introduced from the system backup as well as minimizing the data loss window to minutes.

CYA SmartReplicator

General Questions

I mirror to an alternate site. Why would I consider CYA SmartReplicator for a disaster recovery solution?
It is critical to maintain synchronization between the content and its associated metadata (audit trails, workflows, digital signatures, etc.) in order to ensure the integrity of the standby repository. Solutions like mirroring replicate content or replicate metadata on a scheduled basis, but do not maintain synchronization.

How quickly can I be up and running at an alternate site with CYA SmartReplicator?
The alternate site is kept synchronized to the primary site in near-real-time, so the failover can be performed almost immediately at the primary environment’s time of failure. Scripts need to be run to prepare the secondary ECM environment for direct use, but these can be completed while you are performing your network corrections to redirect traffic, making the transition seamless.

If I use CYA SmartReplicator to failover when my primary site/application is not available, but then after a period of time my primary is available again, how long does it take to switch back to the primary environment?
The time needed to failback is directly related to how much time the primary site was offline, and how much information has been added to and changed within the secondary environment. The failback can be performed immediately after the additions and modifications from the secondary environment are propagated back to the primary environment.

Do I need an exact duplicate environment to run CYA SmartReplicator?
CYA SmartReplicator is designed to duplicate your ECM environment to machines that may potentially be unmatched in hardware to your primary environment. This can even include replication to a virtual environment. The software environment, including the versions of the OS, database, and ECM software must be identical, however, for the secondary environment, you may install your database to the same machine as the Content Server and/or use OS mappings to locate your content in a less expensive physical location if desired.