Prepared by Jaroslav makovski

Slides:



Advertisements
Similar presentations
© 2006 DataCore Software Corp DataCore Traveller Travel in Time : Do More with Time The Continuous Protection and Recovery (CPR) Solution Time Optimized.
Advertisements

By Rashid Khan Lesson 6-A Place for Everything: Storage Management.
Chapter 16: Recovery System
June 23rd, 2009Inflectra Proprietary InformationPage: 1 SpiraTest/Plan/Team Deployment Considerations How to deploy for high-availability and strategies.
Barracuda Backup Service Data Backup and Disaster Recovery.
The Ultimate Backup Solution.
File Management Systems
70-290: MCSE Guide to Managing a Microsoft Windows Server 2003 Environment Chapter 12: Managing and Implementing Backups and Disaster Recovery.
Chapter 12 File Management Systems
Week:#14 Windows Recovery
MCTS Guide to Microsoft Windows Server 2008 Network Infrastructure Configuration Chapter 11 Managing and Monitoring a Windows Server 2008 Network.
Genie Backup ManagerServer 7.0 Product Profile. Copyright© Genie-Soft Corporation All rights reserved. Overview GBM Server 7.0 is a fully integrated.
Operating Systems.
Barracuda Networks Confidential1 Barracuda Backup Service Integrated Local & Offsite Data Backup.
Backup Concepts. Introduction Backup and recovery procedures protect your database against data loss and reconstruct the data, should loss occur. The.
Session 3 Windows Platform Dina Alkhoudari. Learning Objectives Understanding Server Storage Technologies Direct Attached Storage DAS Network-Attached.
Maintaining Windows Server 2008 File Services
Module 8 Implementing Backup and Recovery. Module Overview Planning Backup and Recovery Backing Up Exchange Server 2010 Restoring Exchange Server 2010.
TNT Microsoft Exchange Server 2003 Disaster Recovery Michael J. Murphy TechNet Presenter
Navigating the Oracle Backup Maze Robert Spurzem Senior Product Marketing Manager
IBM TotalStorage ® IBM logo must not be moved, added to, or altered in any way. © 2007 IBM Corporation Break through with IBM TotalStorage Business Continuity.
70-290: MCSE Guide to Managing a Microsoft Windows Server 2003 Environment, Enhanced Chapter 12: Managing and Implementing Backups and Disaster Recovery.
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network, Enhanced Chapter 14: Problem Recovery.
1 Management Pain points now Existing tools: Do not map to virtual environments Provisioning Backup Health monitoring Performance monitoring / management.
STEALTH Content Store for SharePoint using Windows Azure  Boosting your SharePoint to the MAX! "Optimizing your Business behind the scenes"
SQL Server 2008 Implementation and Maintenance Chapter 7: Performing Backups and Restores.
Introduction to Computer Networks Introduction to Computer Networks.
Managing Multi-User Databases AIMS 3710 R. Nakatsu.
1 © 2006 SolidWorks Corp. Confidential. Clustering  SQL can be used in “Cluster Pack” –A pack is a group of servers that operate together and share partitioned.
1 Chapter 12 File Management Systems. 2 Systems Architecture Chapter 12.
Guide to Linux Installation and Administration, 2e 1 Chapter 9 Preparing for Emergencies.
STEALTH Content Store for SharePoint using Caringo CAStor  Boosting your SharePoint to the MAX! "Optimizing your Business behind the scenes"
INSTALLING MICROSOFT EXCHANGE SERVER 2003 CLUSTERS AND FRONT-END AND BACK ‑ END SERVERS Chapter 4.
70-290: MCSE Guide to Managing a Microsoft Windows Server 2003 Environment, Enhanced Chapter 12: Managing and Implementing Backups and Disaster Recovery.
Chapter 8 Implementing Disaster Recovery and High Availability Hands-On Virtual Computing.
Window NT File System JianJing Cao (#98284).
Maintaining File Services. Shadow Copies of Shared Folders Automatically retains copies of files on a server from specific points in time Prevents administrators.
© 2006 IBM Corporation Flash Copy Solutions im Windows Umfeld TSM for Copy Services Wolfgang Hitzler Technical Sales Tivoli Storage Management
Module 9 Planning a Disaster Recovery Solution. Module Overview Planning for Disaster Mitigation Planning Exchange Server Backup Planning Exchange Server.
Module 6 Backup of SQL Server 2008 R2 Databases. Module Overview Backing up Databases and Transaction Logs Managing Database Backups Working with Backup.
Mark A. Magumba Storage Management. What is storage An electronic place where computer may store data and instructions for retrieval The objective of.
11 DISASTER RECOVERY Chapter 13. Chapter 13: DISASTER RECOVERY2 OVERVIEW  Back up server data using the Backup utility and the Ntbackup command  Restore.
1 Week #10Business Continuity Backing Up Data Configuring Shadow Copies Providing Server and Service Availability.
Backup & Restore The purpose of backup is to protect data from loss. The purpose of restore is to recover data that is temporarily unavailable due to some.
11 BACKING UP AND RESTORING SYSTEMS AND DATA Chapter 15.
Component 8/Unit 9bHealth IT Workforce Curriculum Version 1.0 Fall Installation and Maintenance of Health IT Systems Unit 9b Creating Fault Tolerant.
Connect with life Vinod Kumar Technology Evangelist - Microsoft
Data Disaster Recovery Planning Greg Fibiger 1/7/2016.
Component 8 Installation and Maintenance of Health IT Systems Unit 9b Creating Fault-Tolerant Systems, Backups, and Decommissioning This material was developed.
Hands-On Microsoft Windows Server 2008 Chapter 7 Configuring and Managing Data Storage.
Praveen Srivatsa Director| AstrhaSoft Consulting blogs.asthrasoft.com/praveens |
BACKUP AND RESTORE. The main area to be consider when designing a backup strategy Which information should be backed up Which technology should be backed.
File-System Management
Integrating Disk into Backup for Faster Restores
Database Recovery Techniques
Database Administration
Managing Multi-User Databases
Maintaining Windows Server 2008 File Services
Introduction to Operating Systems
Unit 10 NT1330 Client-Server Networking II Date: 8/16/2016
CONFIGURING HARDWARE DEVICE & START UP PROCESS
Database Management System (DBMS)
File Managements.
SpiraTest/Plan/Team Deployment Considerations
Hybrid Storage Competitive Sales Guide INTERNAL ONLY
Chapter 2: Operating-System Structures
MAINTAINING SERVER AVAILIBILITY
Using the Cloud for Backup, Archiving & Disaster Recovery
Chapter 2: Operating-System Structures
Presentation transcript:

Prepared by Jaroslav makovski Data backup Prepared by Jaroslav makovski

Table of contents Windows Server Backup Volume Shadow Copy Service Tape/Disk Backup

Windows Server Backup The Windows Server Backup feature automatically backs up and restores application data. Windows Server Backup also provides registry keys and APIs that: Allow your application to appear in the Recovery Wizard as a separately recoverable item. Allow your cloud backup provider to report its status in the Windows Server Backup Microsoft Management Console (MMC) snap-in.

Volume Shadow Copy Service The Volume Shadow Copy Service (VSS) is a set of COM interfaces that implements a framework to allow volume backups to be performed while applications on a system continue to write to the volumes.

Volume Shadow Copy Service Backing up and restoring critical business data can be very complex due to the following issues: The data usually needs to be backed up while the applications that produce the data are still running. This means that some of the data files might be open or they might be in an inconsistent state. If the data set is large, it can be difficult to back up all of it at one time.

Volume Shadow Copy Service VSS coordinates the actions that are required to create a consistent shadow copy (also known as a snapshot or a point-in- time copy) of the data that is to be backed up. The shadow copy can be used as-is, or it can be used in scenarios such as the following: You want to back up application data and system state information, including archiving data to another hard disk drive, to tape, or to other removable media. You are performing disk-to-disk backups.

How VSS Works A complete VSS solution requires all of the following basic parts: VSS service - Part of the Windows operating system that ensures the other components can communicate with each other properly and work together. VSS requester - The software that requests the actual creation of shadow copies, Typically, this is the backup application. VSS writer - The component that guarantees we have a consistent data set to back up. This is typically provided as part of a line-of-business application, such as SQL Server® or Exchange Server. VSS provider - The component that creates and maintains the shadow copies. This can occur in the software or in the hardware.

How a Shadow Copy Is Created The requester asks the Volume Shadow Copy Service to enumerate the writers, gather the writer metadata, and prepare for shadow copy creation. Each writer creates an XML description of the components and data stores that need to be backed up and provides it to the Volume Shadow Copy Service. The writer also defines a restore method, which is used for all components. The Volume Shadow Copy Service provides the writer's description to the requester, which selects the components that will be backed up.

How a Shadow Copy Is Created The Volume Shadow Copy Service notifies all the writers to prepare their data for making a shadow copy. Each writer prepares the data as appropriate, such as completing all open transactions, rolling transaction logs, and flushing caches. When the data is ready to be shadow-copied, the writer notifies the Volume Shadow Copy Service.

How a Shadow Copy Is Created The Volume Shadow Copy Service tells the writers to temporarily freeze application write I/O requests (read I/O requests are still possible) for the few seconds that are required to create the shadow copy of the volume or volumes. The application freeze is not allowed to take longer than 60 seconds. The Volume Shadow Copy Service flushes the file system buffers and then freezes the file system, which ensures that the file system metadata is recorded correctly and the data to be shadow-copied is written in a consistent order.

How a Shadow Copy Is Created The Volume Shadow Copy Service tells the provider to create the shadow copy. The shadow copy creation period lasts no more than 10 seconds, during which all write I/O requests to the file system remain frozen. The Volume Shadow Copy Service releases file system write I/O requests. VSS tells the writers to thaw application write I/O requests. At this point applications are free to resume writing data to the disk that is being shadow-copied.

How a Shadow Copy Is Created The requester can retry the process (go back to step 1) or notify the administrator to retry at a later time. If the shadow copy is successfully created, the Volume Shadow Copy Service returns the location information for the shadow copy to the requester. In some cases, the shadow copy can be temporarily made available as a read-write volume so that VSS and one or more applications can alter the contents of the shadow copy before the shadow copy is finished. After VSS and the applications make their alterations, the shadow copy is made read-only. 

Complete copy A complete copy is usually created by making a "split mirror" as follows: The original volume and the shadow copy volume are a mirrored volume set. The shadow copy volume is separated from the original volume. This breaks the mirror connection. After the mirror connection is broken, the original volume and the shadow copy volume are independent. The original volume continues to accept all changes (write I/O requests), while the shadow copy volume remains an exact read-only copy of the original data at the time of the break.

Tape/Disk Backup A strong disaster recovery strategy provides essential protection for your business, but to keep your data safe, you need to choose appropriate storage media. 

Disk backup Disk backups provide some obvious advantages over tapes. Tape drives cannot randomly access data, so they offer extremely slow access speeds for individual files when compared to disk-based systems. Some manufacturers have attempted to correct this discrepancy by introducing specialized file systems that allow for faster access (notably IBM's Linear Tape File System), but tapes are still intrinsically slower than disk-based media in this respect.

Disk advantages Fast Access to Stored Data Lower Setup Costs Easier to Recall Specific Backups Electronically Flexible Security Features Easier to Verify Written Data Better Scalability

Tape backup While tape backups require a significant initial investment, they often provide a better long-term return on investment for larger businesses. Tape drives use less electricity than disk-based systems, and you can store tapes for decades without losing data. However, media storage and management adds to the cost of a tape-based backup system.

Tape advantages Dependable Durability for Long-Term Storage Greater Portability Lower Costs for Enterprise-Level Systems Excellent Security and Encryption Capabilities Less Susceptible to Environmental Damage and Shock Damage Effective for Full System Backups

Sources https://docs.microsoft.com/en-us/windows/desktop/backup https://www.securedatarecovery.com/services/tape-data-recovery/tape-backup- vs-disk-backup