Catalogue Reporting from Backup Exec 12.5
Hello time-travelers, No it's not 2010. No need to adjust your clocks. What's the easiest way to run a discovery report on the Backup Exec 12.5 catalogue please? Are there any native or 3rd party tools that could help the discovery? Looking for simple information about: * Names of clients with valid backup images in the catalogue. * Date ranges of valid backup images in the catalogue. * Any data restores performed in last 2 years. Background: We have a legacy Backup Exec 12.5 platform running on Server 2003 that's been sitting idle for a number of years. The last backup image was created about 2 years ago, so it definitely has valid images. We have finally decided to decommission the old platform, but our Risk team wants to know what data is still being held on backups before they'll sign off on the "early" destruction. Thanks in advance for any advice.
Discovery Accelerator exports.... .msg vs .eml
I'm working with EV 12.5.3 and Discovery Accelerator 12 doing some searches for our legal department. I'm having problems with the resulting PST files that I am exporting from DA. Some of the messages in the resulting PST cannot be opened in the Outlook preview pane. The displayed error is "This file cannot be previewed because there is no previewer installed for it". Upon closer inspection, I'm seeing that all of the messages that can't be viewed in the preview pane are actually in the generic .eml format and NOT in Outlooks native .msg format. After doing some research, I believe this is happening because we switched from Exchange journal mailbox targeted archiving to SMTP archiving last fall. All the more recent messages look to be the ones in .eml format. The problem is that, due to how our legal department is reviewing these search results (NOT in DA unfortunately), having to open every individual message in its own window instead of viewing it in the Outlook preview pane causes a huge increase in the amount of time it takes them to perform their review. Has anyone run into this problem before with .eml formatted messages, and do you have any creative solutions to this problem... something like a different export method, an add-in for outlook that can preview .eml's, maybe using a different mail client to review in? While i'm fairly certain the answer will probably be "Do your reviews in DA", there are other reasons why that is not feasible at the time that I won't get into here. Hoping to get some input from other community members on this problem and see if anyone has any ideas. Thanks everyone! Matt
Expanded Classification for Archived Data with Enterprise Vault 12.2
Enterprise Vault 12.2 will be generally available August 7th 2017. This release adds powerful, extermely accurate classification with default policies, business intelligence, new content sources and expanded records management capabilities.
Migrate from MessageOne to Veritas EV.cloud
I've read quite a few articles about migration from other solutions into EV, including exporting to PST, and importing back into EV, and the use of third-party apps to migrate to EV. Has anyone migrated from MessageOne to EV? We are looking for an idea of how long the process may take us. We have around 400 users, 1.6TB in storage, and total aggregate is 2.3TB. Any info is helpful. Thanks, Jess
Defensible Deletion: The Cornerstone of Intelligent Information Governance
The struggle to stay above the rising tide of information is a constant battle for organizations. Not only are the costs and logistics associated with data storage more troubling than ever, but so are the potential legal consequences. Indeed, the news headlines are constantly filled with horror stories of jury verdicts, court judgments and unreasonable settlements involving organizations that failed to effectively address their data stockpiles. While there are no quick or easy solutions to these problems, an ever increasing method for effectively dealing with these issues is through an organizational strategy referred to as defensible deletion. A defensible deletion strategy could refer to many items. But at its core, defensible deletion is a comprehensive approach that companies implement to reduce the storage costs and legal risks associated with the retention of electronically stored information (ESI). Organizations that have done so have been successful in avoiding court sanctions while at the same time eliminating ESI that has little or no business value. The first step to implementing a defensible deletion strategy is for organizations to ensure that they have a top-down plan for addressing data retention. This typically requires that their information governance principals – legal and IT – are cooperating with each other. These departments must also work jointly with records managers and business units to decide what data must be kept and for what length of time. All such stakeholders in information retention must be engaged and collaborate if the organization is to create a workable defensible deletion strategy. Cooperation between legal and IT naturally leads the organization to establish records retention policies, which carry out the key players’ decisions on data preservation. Such policies should address the particular needs of an organization while balancing them against litigation requirements. Not only will that enable a company to reduce its costs by decreasing data proliferation, it will minimize a company’s litigation risks by allowing it to limit the amount of potentially relevant information available for current and follow-on litigation. In like manner, legal should work with IT to develop a process for how the organization will address document preservation during litigation. This will likely involve the designation of officials who are responsible for issuing a timely and comprehensive litigation hold to custodians and data sources. This will ultimately help an organization avoid the mistakes that often plague document management during litigation. The Role of Technology in Defensible Deletion In the digital age, an essential aspect of a defensible deletion strategy is technology. Indeed, without innovations such as archiving software and automated legal hold acknowledgements, it will be difficult for an organization to achieve its defensible deletion objectives. On the information management side of defensible deletion, archiving software can help enforce organization retention policies and thereby reduce data volume and related storage costs. This can be accomplished with classification tools, which intelligently analyze and tag data content as it is ingested into the archive. By so doing, organizations may retain information that is significant or that otherwise must be kept for business, legal or regulatory purposes – and nothing else. An archiving solution can also reduce costs through efficient data storage. By expiring data in accordance with organization retention policies and by using single instance storage to eliminate ESI duplicates, archiving software frees up space on company servers for the retention of other materials and ultimately leads to decreased storage costs. Moreover, it also lessens litigation risks as it removes data available for future litigation. On the eDiscovery side of defensible deletion, an eDiscovery platform with the latest in legal hold technology is often essential for enabling a workable litigation hold process. Effective platforms enable automated legal hold acknowledgements on various custodians across multiple cases. This allows organizations to confidently place data on hold through a single user action and eliminates concerns that ESI may slip through the proverbial cracks of manual hold practices. Organizations are experiencing every day the costly mistakes of delaying implementation of a defensible deletion program. This trend can be reversed through a common sense defensible deletion strategy which, when powered by effective, enabling technologies, can help organizations decrease the costs and risks associated with the information explosion.Breaking News: Recusal Motion in Da Silva Moore Case Denied
In what might be characterized as the most anticipated ruling in the eDiscovery world over the past several months, the district court in Da Silva Moore v. Publicis Groupe today denied the plaintiffs’ motion to recuse the Honorable Andrew Peck as the assigned magistrate to that action. In rejecting the plaintiffs’ recusal request, United States District Court Judge Andrew Carter held that “Judge Peck’s decision accepting computer-assisted review, reached upon consideration of the applicable law, was not influenced by bias, nor did it create any appearance of bias.” Judge Carter’s decision is particularly significant as it leaves undisturbed Judge Peck’s orders regarding the use of predictive coding and his declaration that computer-assisted review in eDiscovery is “acceptable in appropriate cases.” Moreover, Judge Carter gave another judicial imprimatur to predictive coding with his determination that it “does not inherently favor one party over the other in this case.” With today’s ruling, Judge Carter has perhaps finally brought to a close the contentious sideshow that nearly overshadowed the first known case involving the use of predictive coding in eDiscovery. With its potential to reduce the costs and delays associated with the review of ESI, predictive coding holds incredible promise for the future of eDiscovery.Spotlighting the Top Electronic Discovery Cases from 2012
With the New Year quickly approaching, it is worth reflecting on some of the key eDiscovery developments that have occurred during 2012. While legislative, regulatory and rulemaking bodies have undoubtedly impacted eDiscovery, the judiciary has once again played the most dramatic role. There are several lessons from the top 2012 court cases that, if followed, will likely help organizations reduce the costs and risks associated with eDiscovery. These cases also spotlight the expectations that courts will likely have for organizations in 2013 and beyond. Implementing a Defensible Deletion Strategy Case: Brigham Young University v. Pfizer, 282 F.R.D. 566 (D. Utah 2012) In Brigham Young, the plaintiff university had pressed for sanctions as a result of Pfizer’s destruction of key documents pursuant to its information retention policies. The court rejected that argument because such a position failed to appreciate the basic workings of a valid corporate retention schedule. As the court reasoned, “[e]vidence may simply be discarded as a result of good faith business procedures.” When those procedures operate to inadvertently destroy evidence before the duty to preserve is triggered, the court held that sanctions should not issue: “The Federal Rules protect from sanctions those who lack control over the requested materials or who have discarded them as a result of good faith business procedures.” Summary: The Brigham Young case is significant since it emphasizes that organizations should implement a defensible deletion strategy to rid themselves of data stockpiles. Absent a preservation duty or other exceptional circumstances, organizations that pare back ESI pursuant to “good faith business procedures” (such as a neutral retention policy) will be protected from sanctions. **Another Must-Read Case: Danny Lynn Elec. v. Veolia Es Solid Waste (M.D. Ala. Mar. 9, 2012) Issuing a Timely and Comprehensive Litigation Hold Case: Apple, Inc. v. Samsung Electronics Co., Ltd, --- F. Supp. 2d. --- (N.D. Cal. 2012) Summary: The court first issued an adverse inference instruction against Samsung to address spoliation charges brought by Apple. In particular, the court faulted Samsung for failing to circulate a comprehensive litigation hold instruction when it first anticipated litigation. This eventually culminated in the loss of emails from several key Samsung custodians, inviting the court’s adverse inference sanction. Ironically, however, Apple was subsequently sanctioned for failing to issue a proper hold notice. Just like Samsung, Apple failed to distribute a hold until several months after litigation was reasonably foreseeable. The tardy hold instruction, coupled with evidence suggesting that Apple employees were “encouraged to keep the size of their email accounts below certain limits,” ultimately led the court to conclude that Apple destroyed documents after its preservation duty ripened. The Lesson for 2013: The Apple case underscores the importance of issuing a timely and comprehensive litigation hold notice. For organizations, this likely means identifying the key players and data sources that may have relevant information and then distributing an intelligible hold instruction. It may also require suspending aspects of information retention policies to preserve relevant ESI. By following these best practices, organizations can better avoid the sanctions bogeyman that haunts so many litigants in eDiscovery. **Another Must-Read Case: Chin v. Port Authority of New York, 685 F.3d 135 (2 nd Cir. 2012) Judicial Approval of Predictive Coding Case: Da Silva Moore v. Publicis Groupe, --- F.R.D. --- (S.D.N.Y. Feb. 24, 2012) Summary: The court entered an order that turned out to be the first of its kind: approving the use of predictive coding technology in the discovery phase of litigation. That order was entered pursuant to the parties’ stipulation, which provided that defendant MSL Group could use predictive coding in connection with its obligation to produce relevant documents. Pursuant to that order, the parties methodically (yet at times acrimoniously) worked over several months to fine tune the originally developed protocol to better ensure the production of relevant documents by defendant MSL. The Lesson for 2013: The court declared in its order that predictive coding “is an acceptable way to search for relevant ESI in appropriate cases.” Nevertheless, the court also made clear that this technology is not the exclusive method now for conducting document review. Instead, predictive coding should be viewed as one of many different types of tools that often can and should be used together. ** Another Must-Read Case: In Re: Actos (Pioglitazone) Prods. Liab. Litig. (W.D. La. July 10, 2012) Proportionality and Cooperation are Inextricably Intertwined Case: Pippins v. KPMG LLP, 279 F.R.D. 245 (S.D.N.Y. 2012) Summary: The court ordered the defendant accounting firm (KPMG) to preserve thousands of employee hard drives. The firm had argued that the high cost of preserving the drives was disproportionate to the value of the ESI stored on the drives. Instead of preserving all of the drives, the firm hoped to maintain a reduced sample, asserting that the ESI on the sample drives would satisfy the evidentiary demands of the plaintiffs’ class action claims. The court rejected the proportionality argument primarily because the firm refused to permit plaintiffs or the court to analyze the ESI found on the drives. Without any transparency into the contents of the drives, the court could not weigh the benefits of the discovery against the alleged burdens of preservation. The court was thus left to speculate about the nature of the ESI on the drives, reasoning that it went to the heart of plaintiffs’ class action claims. As the district court observed, the firm may very well have obtained the relief it requested had it engaged in “good faith negotiations” with the plaintiffs over the preservation of the drives. The Lesson for 2013: The Pippins decision reinforces a common refrain that parties seeking the protection of proportionality principles must engage in reasonable, cooperative discovery conduct. Staking out uncooperative positions in the name of zealous advocacy stands in sharp contrast to proportionality standards and the cost cutting mandate of Rule 1. Moreover, such a tactic may very well foreclose proportionality considerations, just as it did in Pippins. **Another Must-Read Case: Kleen Products LLC v. Packaging Corp. of America (N.D. Ill. Sept. 28, 2012) Conclusion There were any number of other significant cases from 2012 that could have made this list. We invite you to share your favorites in the comments section or contact us directly with your feedback.
