This document discusses system backups and disaster recovery. It covers the importance of backups, different backup strategies and scheduling, and various backup devices. For strategies, it describes the volume/calendar method, grandfather/father/son method, and Tower of Hanoi method. For devices, it outlines tape-based options like cartridge tapes and optical disks, as well as newer technologies like linear tape-open and digital linear tape that provide high storage capacities.
The document discusses disk drives and file systems. It covers disk components, geometry, partitioning, formatting, interfaces like SCSI, IDE, and Fibre Channel. It explains concepts such as cylinders, tracks, sectors, and how disk addressing works. It discusses disk formatting for SCSI and IDE drives, and how alternate sectors are used to map out bad blocks. Load balancing techniques like splitting file systems across multiple disks and spindles are also summarized.
This document provides an overview of key concepts related to web services including web clients (browsers), web servers, and security issues. It discusses how browsers make requests to servers and display pages using URLs. It also covers important client-side issues like security vulnerabilities from downloaded content, cookies, and privacy. On the server side, it recommends the Apache web server and discusses choosing, installing, and configuring a server as well as common modules to extend functionality.
The document discusses ensuring integrity and availability in networks. It covers viruses, fault tolerance techniques like redundant components and UPS systems, data backup strategies, and disaster recovery plans. Integrity ensures the soundness of network programs, data, services and connections, while availability refers to consistent access. General guidelines include limiting administrator access and regularly monitoring performance.
The document discusses the boot sequence of a computer system. It examines each step including the PROM monitor, boot block, secondary boot loader, the OS kernel, and start-up scripts. The administrator should understand this boot process as well as how to modify the boot sequence, select alternate devices, and properly shut down the system.
This chapter discusses TCP/IP network design including subnetting, CIDR, and NAT. It describes protocols for email delivery and access like SMTP, POP, and IMAP. It also explains using TCP/IP networks for voice transmission (VoIP) and provides details on TCP/IP utilities like netstat, nslookup, traceroute, and ifconfig that can be used for network discovery and troubleshooting.
The document discusses disk drives and file systems. It provides an overview of disk components like platters, heads, and sectors. It explains disk geometry including cylinders, tracks, and how addressing schemes allow unique identification of each sector. Different disk interfaces like SCSI, IDE, and Fibre Channel are covered. The document also discusses disk formatting, partitioning, and techniques for optimizing performance like load balancing and RAID.
Network file sharing allows files to be accessed over a network. It employs Remote Procedure Calls and requires setup of both server and client software. While convenient for users, it complicates administration and can introduce security issues if not configured properly. NFS and SMB are common network file sharing protocols, each with their own advantages and disadvantages.
This document discusses automating system administration tasks through shell scripting. It begins by outlining common tasks that can be automated, such as installing patches, managing accounts and configuration files. It then covers tools for automation like cron, find, and rdist. The rest of the document discusses different methods for distributing system information, such as the push and pull methods, and provides examples of rdist and package files used for automation.
The document discusses disk drives and file systems. It covers disk components, geometry, partitioning, formatting, interfaces like SCSI, IDE, and Fibre Channel. It explains concepts such as cylinders, tracks, sectors, and how disk addressing works. It discusses disk formatting for SCSI and IDE drives, and how alternate sectors are used to map out bad blocks. Load balancing techniques like splitting file systems across multiple disks and spindles are also summarized.
This document provides an overview of key concepts related to web services including web clients (browsers), web servers, and security issues. It discusses how browsers make requests to servers and display pages using URLs. It also covers important client-side issues like security vulnerabilities from downloaded content, cookies, and privacy. On the server side, it recommends the Apache web server and discusses choosing, installing, and configuring a server as well as common modules to extend functionality.
The document discusses ensuring integrity and availability in networks. It covers viruses, fault tolerance techniques like redundant components and UPS systems, data backup strategies, and disaster recovery plans. Integrity ensures the soundness of network programs, data, services and connections, while availability refers to consistent access. General guidelines include limiting administrator access and regularly monitoring performance.
The document discusses the boot sequence of a computer system. It examines each step including the PROM monitor, boot block, secondary boot loader, the OS kernel, and start-up scripts. The administrator should understand this boot process as well as how to modify the boot sequence, select alternate devices, and properly shut down the system.
This chapter discusses TCP/IP network design including subnetting, CIDR, and NAT. It describes protocols for email delivery and access like SMTP, POP, and IMAP. It also explains using TCP/IP networks for voice transmission (VoIP) and provides details on TCP/IP utilities like netstat, nslookup, traceroute, and ifconfig that can be used for network discovery and troubleshooting.
The document discusses disk drives and file systems. It provides an overview of disk components like platters, heads, and sectors. It explains disk geometry including cylinders, tracks, and how addressing schemes allow unique identification of each sector. Different disk interfaces like SCSI, IDE, and Fibre Channel are covered. The document also discusses disk formatting, partitioning, and techniques for optimizing performance like load balancing and RAID.
Network file sharing allows files to be accessed over a network. It employs Remote Procedure Calls and requires setup of both server and client software. While convenient for users, it complicates administration and can introduce security issues if not configured properly. NFS and SMB are common network file sharing protocols, each with their own advantages and disadvantages.
This document discusses automating system administration tasks through shell scripting. It begins by outlining common tasks that can be automated, such as installing patches, managing accounts and configuration files. It then covers tools for automation like cron, find, and rdist. The rest of the document discusses different methods for distributing system information, such as the push and pull methods, and provides examples of rdist and package files used for automation.
This document summarizes security risks and mitigation techniques for computer networks. It discusses risks associated with people, transmission, hardware, protocols, software, and internet access. It also outlines the goals of an effective security policy and describes physical security, firewalls, proxy servers, remote access, network operating system security, encryption, and wireless security. Key risks include social engineering, unauthorized access, transmission interception, insecure protocols, denial-of-service attacks, and improper firewall/remote access configurations. The chapter recommends conducting security audits, restricting physical access, using firewalls/proxy servers for access control, enforcing secure authentication/access, and encrypting sensitive data and wireless transmissions.
Managing system software involves maintaining operating systems, utilities, and applications through periodic installation of software packages and patches. The key challenges are the wide variety of package formats, management tools, and missing features in specific tool sets. Before installing software, administrators should understand hardware and software requirements, installation types and tools, disk layouts, and pre-installation steps.
Configuring and managing printers involves understanding printing concepts, print server and client configuration, and homogeneous and heterogeneous printing. It requires setting up print services under different operating systems like Windows, BSD and System V. Troubleshooting involves checking printers, print queues, filters and data files. Heterogeneous printing across operating systems is the most challenging.
The document discusses user account management tasks for system administrators, including creating login names, assigning home directories and user IDs, setting passwords and shells, and formatting the password file. It describes challenges around reusable passwords and methods to improve security such as password aging, lockouts for failed attempts, and one-time password tokens.
The document discusses name resolution services including NIS, DNS, and how they work together. NIS is a local name service, while DNS is global and hierarchical. It describes the components and configuration of DNS, including root, top-level, and subordinate domains as well as master, slave and caching nameservers. The document then provides an example of the name resolution process between a client, local nameserver, and external domain.
1. Project management is important for network implementation projects and involves determining feasibility, assessing needs, setting goals, planning tasks and timelines, managing communication, and contingency planning.
2. Network management includes monitoring performance and faults, tracking assets, and regularly maintaining and upgrading both hardware and software.
3. Careful planning is required for any network changes, including software updates, client and server upgrades, and adding or replacing physical equipment. Changes must be thoroughly tested and plans should allow for reverting changes if needed.
Anger is a normal human emotion, but it needs to be managed and controlled. When anger spirals out of control, it can negatively impact work, relationships, and quality of life. There are many internal and external sources that can trigger anger, such as stress, anxiety, unreasonable expectations, personal attacks, and threats to our needs. It is important to recognize the signs of anger and use techniques such as introspection, empathy, pausing before speaking harshly, organizing tasks, and sharing negative emotions respectfully to keep anger in check. Controlled and constructive anger can even be productive at times.
This document provides an overview of formatting and editing features in Microsoft Excel, including how to format values, change fonts and formatting, adjust columns and rows, apply colors and borders, use conditional formatting, name and move sheets, and check spelling. The objectives are covered in multiple sections with descriptions and screenshots illustrating each task.
This document discusses network configuration files and utilities on UNIX systems. It examines common configuration files such as /etc/hosts, /etc/hostname.if_name, /etc/nodename, /etc/services, /etc/inetd.conf, and /etc/resolv.conf that store network settings. It also describes configuration commands like ifconfig and route that can be used to modify network interfaces and routing tables. The document notes that while network configuration methods are generally similar across UNIX, there are also OS-specific differences to consider.
The document discusses the importance of drinking water for health. Some key points:
- Humans are 50-75% water and adults need 10-12 gallons daily.
- Water regulates body temperature, carries nutrients and oxygen, keeps tissues moist, and more.
- Loss of 10% water leads to weakness, 20% loss is life threatening. Most adults lose around 10 cups daily through urine, sweat, breathing, etc.
- Drinking fluids, food, and metabolism provide the necessary fluids to the body. Factors like heat, exercise, and illnesses can increase water needs.
This document provides an overview of serial ports, including their terminology, capabilities, signals, configuration, and management. It discusses the RS-232 standard for serial communication and newer standards like RS-422 and RS-423. It also covers topics like cable types, modem connections, terminal and port monitoring software, and commands for configuring serial ports and managing terminals. Common problems are addressed along with their solutions.
The document discusses various methods for installing operating systems. It covers hardware requirements, preparing for installation, different installation types including desktop, server and dual-boot installations. It also discusses Windows, Linux, Solaris and BSD installations and outlines unattended network installations using answer files.
Chapter12 Managing And Implementing Backups And Disaster RecoveryRaja Waseem Akhtar
The document discusses various methods for managing backups and disaster recovery in a Microsoft Windows Server 2003 environment. It covers planning backups, using the backup utility to perform different types of backups including system state backups, configuring shadow copies and previous versions, setting up automated system recovery backups, using advanced startup options like safe mode and last known good configuration, and installing/using the recovery console for system recovery tasks. Activities are provided to demonstrate configuring and testing many of these backup and disaster recovery features.
The document discusses NetWare, a network operating system developed by Novell. It provides an overview of NetWare's history and versions. The key advantages of NetWare include centralized management, support for multiple protocols, and integration with other network operating systems. The document also describes planning and installing a NetWare server, including hardware requirements, the installation process, establishing user accounts and groups, and providing client access and interoperability with other operating systems.
The document discusses the boot sequence of a computer system. It examines each step including the PROM monitor, boot block, secondary boot loader, and OS kernel initialization. It also covers modifying the boot process, selecting alternate boot devices, different boot loaders, and proper system shutdown procedures.
The document introduces fundamental system administration tools and practices, including navigating file trees, using the vi text editor, command line tools like grep and tar, and adopting good practices like avoiding wildcards as root. It also covers using pipes, window managers, email and web browsers to juggle multiple tasks as a system administrator.
Managing system software involves installing software packages and patches periodically. This task is conceptually straightforward but challenging due to the variety of package formats, management tools, and missing features. Before installing software, administrators should understand hardware and software requirements, installation types, tools, disk layout, and pre-installation steps.
This document discusses disk and file system concepts including:
- Creating file systems using newfs and how it connects to mkfs
- Mounting file systems manually, via fstab, and using volume manager
- Identifying mounted file systems using mount, df, and mnttab
- Repairing file systems using fsck and handling recoverable vs unrecoverable damage
- Benefits of journaling file systems like reduced reboot time and data retention
This document discusses various aspects of writing and using Visual Basic for Applications (VBA) macros in Microsoft Excel 2007, including viewing and analyzing existing VBA code, writing your own code in the Visual Basic Editor, adding conditional statements, prompting users for input, debugging macros, creating main procedures to combine multiple macros, and running macros and main procedures.
The document provides guidance on planning for Ramadan by outlining important areas to focus on such as salat, Quran recitation, zikr, dua, Umrah, Itikaf, financial obligations, family, dawah, health, and stopping bad habits. It emphasizes that failing to plan is planning to fail, and Satan tries to discourage planning or engaging in lesser good. Proper planning in these areas can help one get closer to Allah and maximize rewards during the holy month.
MySQL Enterprise Backup provides fast, consistent, online backups of MySQL databases. It allows for backing up InnoDB and MyISAM tables while the database is running, minimizing downtime. The tool takes physical backups of the data files rather than logical backups, allowing for very fast restore times compared to alternatives like mysqldump. It supports features like compressed backups, incremental backups, and point-in-time recovery.
This document summarizes security risks and mitigation techniques for computer networks. It discusses risks associated with people, transmission, hardware, protocols, software, and internet access. It also outlines the goals of an effective security policy and describes physical security, firewalls, proxy servers, remote access, network operating system security, encryption, and wireless security. Key risks include social engineering, unauthorized access, transmission interception, insecure protocols, denial-of-service attacks, and improper firewall/remote access configurations. The chapter recommends conducting security audits, restricting physical access, using firewalls/proxy servers for access control, enforcing secure authentication/access, and encrypting sensitive data and wireless transmissions.
Managing system software involves maintaining operating systems, utilities, and applications through periodic installation of software packages and patches. The key challenges are the wide variety of package formats, management tools, and missing features in specific tool sets. Before installing software, administrators should understand hardware and software requirements, installation types and tools, disk layouts, and pre-installation steps.
Configuring and managing printers involves understanding printing concepts, print server and client configuration, and homogeneous and heterogeneous printing. It requires setting up print services under different operating systems like Windows, BSD and System V. Troubleshooting involves checking printers, print queues, filters and data files. Heterogeneous printing across operating systems is the most challenging.
The document discusses user account management tasks for system administrators, including creating login names, assigning home directories and user IDs, setting passwords and shells, and formatting the password file. It describes challenges around reusable passwords and methods to improve security such as password aging, lockouts for failed attempts, and one-time password tokens.
The document discusses name resolution services including NIS, DNS, and how they work together. NIS is a local name service, while DNS is global and hierarchical. It describes the components and configuration of DNS, including root, top-level, and subordinate domains as well as master, slave and caching nameservers. The document then provides an example of the name resolution process between a client, local nameserver, and external domain.
1. Project management is important for network implementation projects and involves determining feasibility, assessing needs, setting goals, planning tasks and timelines, managing communication, and contingency planning.
2. Network management includes monitoring performance and faults, tracking assets, and regularly maintaining and upgrading both hardware and software.
3. Careful planning is required for any network changes, including software updates, client and server upgrades, and adding or replacing physical equipment. Changes must be thoroughly tested and plans should allow for reverting changes if needed.
Anger is a normal human emotion, but it needs to be managed and controlled. When anger spirals out of control, it can negatively impact work, relationships, and quality of life. There are many internal and external sources that can trigger anger, such as stress, anxiety, unreasonable expectations, personal attacks, and threats to our needs. It is important to recognize the signs of anger and use techniques such as introspection, empathy, pausing before speaking harshly, organizing tasks, and sharing negative emotions respectfully to keep anger in check. Controlled and constructive anger can even be productive at times.
This document provides an overview of formatting and editing features in Microsoft Excel, including how to format values, change fonts and formatting, adjust columns and rows, apply colors and borders, use conditional formatting, name and move sheets, and check spelling. The objectives are covered in multiple sections with descriptions and screenshots illustrating each task.
This document discusses network configuration files and utilities on UNIX systems. It examines common configuration files such as /etc/hosts, /etc/hostname.if_name, /etc/nodename, /etc/services, /etc/inetd.conf, and /etc/resolv.conf that store network settings. It also describes configuration commands like ifconfig and route that can be used to modify network interfaces and routing tables. The document notes that while network configuration methods are generally similar across UNIX, there are also OS-specific differences to consider.
The document discusses the importance of drinking water for health. Some key points:
- Humans are 50-75% water and adults need 10-12 gallons daily.
- Water regulates body temperature, carries nutrients and oxygen, keeps tissues moist, and more.
- Loss of 10% water leads to weakness, 20% loss is life threatening. Most adults lose around 10 cups daily through urine, sweat, breathing, etc.
- Drinking fluids, food, and metabolism provide the necessary fluids to the body. Factors like heat, exercise, and illnesses can increase water needs.
This document provides an overview of serial ports, including their terminology, capabilities, signals, configuration, and management. It discusses the RS-232 standard for serial communication and newer standards like RS-422 and RS-423. It also covers topics like cable types, modem connections, terminal and port monitoring software, and commands for configuring serial ports and managing terminals. Common problems are addressed along with their solutions.
The document discusses various methods for installing operating systems. It covers hardware requirements, preparing for installation, different installation types including desktop, server and dual-boot installations. It also discusses Windows, Linux, Solaris and BSD installations and outlines unattended network installations using answer files.
Chapter12 Managing And Implementing Backups And Disaster RecoveryRaja Waseem Akhtar
The document discusses various methods for managing backups and disaster recovery in a Microsoft Windows Server 2003 environment. It covers planning backups, using the backup utility to perform different types of backups including system state backups, configuring shadow copies and previous versions, setting up automated system recovery backups, using advanced startup options like safe mode and last known good configuration, and installing/using the recovery console for system recovery tasks. Activities are provided to demonstrate configuring and testing many of these backup and disaster recovery features.
The document discusses NetWare, a network operating system developed by Novell. It provides an overview of NetWare's history and versions. The key advantages of NetWare include centralized management, support for multiple protocols, and integration with other network operating systems. The document also describes planning and installing a NetWare server, including hardware requirements, the installation process, establishing user accounts and groups, and providing client access and interoperability with other operating systems.
The document discusses the boot sequence of a computer system. It examines each step including the PROM monitor, boot block, secondary boot loader, and OS kernel initialization. It also covers modifying the boot process, selecting alternate boot devices, different boot loaders, and proper system shutdown procedures.
The document introduces fundamental system administration tools and practices, including navigating file trees, using the vi text editor, command line tools like grep and tar, and adopting good practices like avoiding wildcards as root. It also covers using pipes, window managers, email and web browsers to juggle multiple tasks as a system administrator.
Managing system software involves installing software packages and patches periodically. This task is conceptually straightforward but challenging due to the variety of package formats, management tools, and missing features. Before installing software, administrators should understand hardware and software requirements, installation types, tools, disk layout, and pre-installation steps.
This document discusses disk and file system concepts including:
- Creating file systems using newfs and how it connects to mkfs
- Mounting file systems manually, via fstab, and using volume manager
- Identifying mounted file systems using mount, df, and mnttab
- Repairing file systems using fsck and handling recoverable vs unrecoverable damage
- Benefits of journaling file systems like reduced reboot time and data retention
This document discusses various aspects of writing and using Visual Basic for Applications (VBA) macros in Microsoft Excel 2007, including viewing and analyzing existing VBA code, writing your own code in the Visual Basic Editor, adding conditional statements, prompting users for input, debugging macros, creating main procedures to combine multiple macros, and running macros and main procedures.
The document provides guidance on planning for Ramadan by outlining important areas to focus on such as salat, Quran recitation, zikr, dua, Umrah, Itikaf, financial obligations, family, dawah, health, and stopping bad habits. It emphasizes that failing to plan is planning to fail, and Satan tries to discourage planning or engaging in lesser good. Proper planning in these areas can help one get closer to Allah and maximize rewards during the holy month.
MySQL Enterprise Backup provides fast, consistent, online backups of MySQL databases. It allows for backing up InnoDB and MyISAM tables while the database is running, minimizing downtime. The tool takes physical backups of the data files rather than logical backups, allowing for very fast restore times compared to alternatives like mysqldump. It supports features like compressed backups, incremental backups, and point-in-time recovery.
Backing up data involves taking copies of data so it can be recovered if the original is lost. Archiving moves less frequently used data to backup storage to free up space. An effective backup strategy includes choosing backup media, determining backup methods and frequency, storing and rotating backups, and being able to recover data from backups. Common media are tapes and external drives, while full, differential, and incremental backups are frequent methods. Rotation schemes like grandfather-father-son improve cost-efficiency and ensure all files are protected. Verification and recovery processes are also important parts of the strategy.
MySQL Enterprise Backup provides fast, consistent, online backups of MySQL databases. It allows for full and incremental backups, compressed backups to reduce storage needs, and point-in-time recovery. MySQL Enterprise Backup works by backing up InnoDB data files, copying and compressing the files, and backing up the transaction log files from the time period when the data files were copied. This allows for consistent backups and point-in-time recovery of the database.
This document discusses backup and recovery best practices. It describes the common backup topologies of direct attached, LAN based, and SAN based backups. It also discusses considerations for backup frequency and retention based on business needs. The document outlines the different types of backups including full, incremental, and cumulative. It describes backup architecture with backup clients and servers and discusses hot and cold backup methods. Finally, it discusses backup targets like tapes, disks, virtual tape libraries, and data deduplication techniques.
Power point presentation on backup and recovery.
A good presentation cover all topics.
For any other type of ppt's or pdf's to be created on demand contact -dhawalm8@gmail.com
mob. no-7023419969
Regulatory requirements for backups are stringent. An effective backup strategy minimizes the backup window while ensuring data integrity. Key considerations for backups include storing data onsite versus offsite, performing full versus partial backups, using appropriate media, and verifying backups. When decommissioning systems, the goals are to properly retain active data and securely archive or dispose of inactive data.
Presentation backup and recovery best practices for very large databases (v...xKinAnx
This document provides best practices for backup and recovery of very large databases (VLDBs). It discusses VLDB trends requiring databases to scale to terabytes and beyond. The key is protecting growing data while maintaining cost efficiency. The presentation covers assessing recovery requirements, architecting backup environments, leveraging Oracle tools, planning data layout, developing backup procedures, and recovery strategies. It also provides a Starbucks case study example.
This document discusses various methods for performing database backups, including Recovery Manager (RMAN), Oracle Secure Backup, and user-managed backups. It covers key backup concepts like full versus incremental backups, online versus offline backups, and image copies versus backup sets. The document also provides instructions on configuring backup settings and scheduling automated database backups using RMAN and Enterprise Manager.
Creating And Implementing A Data Disaster Recovery PlanRishu Mehra
This document provides guidance on creating an effective data disaster recovery plan. It discusses key considerations like recovery time objective (RTO), recovery point objective (RPO), different backup types and schedules, optimizing backup performance, and testing the restoration of data. An important part of the plan is documenting roles and procedures for restoring systems, networking, and communications in the event of an outage or disaster. Regular testing of the backup and restoration processes is also recommended to ensure the plan works smoothly.
Creating And Implementing A Data Disaster Recovery PlanRishu Mehra
This document provides guidance on creating an effective data disaster recovery plan. It discusses key considerations like recovery time objective (RTO), recovery point objective (RPO), different backup types and schedules, optimizing backup performance, and testing the restoration of data. An important part of the plan is documenting roles and procedures for restoring systems, networking, and communications in the event of an outage or disaster. Regular testing of the backup and restoration processes is also recommended to ensure the plan works smoothly.
The document discusses file storage and backup systems. It defines files and folders, describes common file storage devices like hard drives, optical disks, solid state drives and memory sticks. It emphasizes the importance of backing up files regularly using either manual backups, backup applications, automatic backup systems or cloud backup services to protect against data loss from hardware failure. Simple backup strategies and resources for learning more are provided.
Backing up data is important to protect against data loss or corruption. There are two main types of backups: incremental backups that only back up changed files, and image backups that make a complete copy of all files. Backup options include external drives, cloud storage, or network-attached storage. It is important to back up files regularly and store backups separately from the computer to ensure security.
Disaster Recovery & Data Backup StrategiesSpiceworks
This document discusses data backup strategies and planning. It emphasizes that backups are critical for businesses to protect their data and recover from data loss. The document outlines planning considerations like identifying critical systems and data, recovery objectives, and capacity needs. It then covers various backup methods and factors to consider when developing a backup plan such as repository type, media type, and testing procedures. Regularly monitoring and testing backups is key to ensuring the plan is effective.
2019 FRSecure CISSP Mentor Program: Class ElevenFRSecure
The document summarizes the notes from session 11 of a 2019 CISSP mentor program. It includes quizzes on topics like incident response backups, disaster recovery planning goals, and backup types. It also covers lectures on executive succession planning, disaster recovery plan approval, backups and availability options, software escrow, disaster recovery plan testing, and different types of disaster recovery plan tests.
Presentation on backup and recoveryyyyyyyyyyyyyyyyyyyTehmina Gulfam
The document provides an overview of backup strategies and technologies. It discusses different types of backups including full, differential, and incremental backups. It covers backup architecture including backup clients, servers, and storage nodes. Key aspects of the backup process and restore process are outlined. Different backup topologies of direct attached, LAN-based, and SAN-based backups are described. Options for backup technology include backing up to tape or disk. Features of Acronis backup software are briefly mentioned.
Presentation on backup and recoveryyyyyyyyyyyyyTehmina Gulfam
The document provides an overview of backup strategies and technologies. It discusses different types of backups including full, differential, and incremental backups. It covers backup architecture including backup clients, servers, and storage nodes. Key aspects of the backup process and restore process are outlined. Different backup topologies of direct attached, LAN-based, and SAN-based backups are described. Options for backup technology include backing up to tape or disk. Features of Acronis backup software are briefly mentioned.
This document discusses best practices for preparing for and responding to a disaster involving critical IT systems like servers and databases. It emphasizes the importance of regular backups, having recovery procedures documented, testing restores, and defining roles and responsibilities of team members. It provides guidance on backup strategies for SQL Server and SharePoint, including using different types of backups, storing backups offline, and setting backup schedules. It also stresses the value of preparation, being ready to restore from backups, and having contact information and credentials documented in advance in case of an emergency.
Session from SQLDay 2016 Conference in Wroclaw.
2 AM. We're sleeping well and our mobile is ringing and ringing. Message: DISASTER! In this session (on slides) we are NOT talking about the potential disaster (such BCM); we talk about: What happened NOW? Which tasks should have been finished BEFORE. Does virtual or physical SQL Server matter? We talk about systems, databases, people, encryption, passwords, certificates and users. In this session (on few demos) I'll show which part of our SQL Server environment are critical and how to be prepared for disaster. In some documents, I'll show You how to be BEST prepared.
The document discusses reasons why the Prophet Muhammad had multiple wives. It states that he had 12 wives total, with 10 being with him when he passed away. It argues that lust was not the reason, pointing out that he married his first wife Khadijah at age 25 and stayed with her alone for 25 years until her death when he was 52. It says the marriages were for political, social and religious reasons like spreading Islamic culture, strengthening bonds with companions, and having ties with other nations.
This document takes the reader on a trip through scales of size from micro to macro, jumping distances by factors of 10. It starts at 1 meter and increases the scale up to 10 million light years, observing different objects that come into view like planets, galaxies, and nebulae. It then returns back down to the micro scale, decreasing distances by factors of 10 until it reaches the scale of femtometers, observing subatomic particles. The document emphasizes the constancy of natural laws across all scales and encourages contemplating humanity's place in the vast universe.
1) Salat Tasbeeh is a four rakat prayer where in each posture of the rakat (standing, bowing, prostrating, sitting), the phrase "Subhan Allah-e-Wal Hamd-o-lillah-e-Wala-Ilaha -Ilallaho-Wallaho-Akbar" is uttered a specified number of times.
2) In each rakat, the phrase must be uttered 75 times total across the seven postures - with 15 times while standing after recitation, 10 times while bowing, 10 times in each prostration, and 10 times while sitting between prostrations.
3) The specified numbers of times the phrase
This document discusses the benefits of reciting Aayathul Qursi. It states that reciting it when leaving the house will result in 70,000 angels protecting from all sides. Reciting it 40 times daily at sunset earns the reward of 40 Hajj pilgrimages. Reciting it before bed will result in an angel guarding the person until morning. Reciting it after returning home and after ablution increases a person's rank with every word. Sharing it with others also provides reward from God.
Indian soldiers who were wounded fighting in World War 1 on the Western Front were sent to England for treatment. Many towns on the south coast of England, including Brighton, Bournemouth, Brockenhurst and New Milton helped care for the large numbers of wounded Indian soldiers. It is estimated that over 64,000 Indian soldiers died or went missing and more than 65,000 were wounded by the end of the war.
World War II involved major battles in the European Theater between November 1942 and May 1945. Allied forces led by generals Montgomery, Clark, Alexander, Patton, Bradley, and Devers fought against Axis forces in campaigns across Western, Central, and Eastern areas of engagement. Through coordinated operations between multiple army groups consisting of airborne, armored, and infantry divisions, the Allies were ultimately able to defeat Nazi Germany.
1) A liter of water contains enough mass to produce 9 x 1016 Joules of energy if converted entirely, which could power a 1 Watt lightbulb for around 3 billion years.
2) The sun produces its energy through nuclear fusion, where hydrogen nuclei fuse into helium. A little bit of mass is lost in this process, appearing as energy according to E=mc2.
3) Scientists are trying to create controlled nuclear fusion on Earth for a sustainable energy source, but it requires maintaining temperatures over 15 million degrees, which is technically challenging.
This document provides a high-level overview of the shuttle processing steps before flight, including:
1) The external tank arrives by barge and is moved to the Vertical Assembly Building (VAB) for preparation.
2) Solid rocket boosters and shuttle engines are attached to the external tank in the VAB.
3) The shuttle is then lifted and attached to the external tank.
4) The payload is prepared separately in the Payload Preparation Room and then transported to the launch pad for insertion into the shuttle.
This document provides guidance on securing Solaris servers through hardening and configuration best practices. It recommends removing unnecessary software and services, enabling detailed system logging, installing the latest security patches regularly, and configuring services like sendmail securely based on checklists from SANS and CIS. Key steps include a minimal OS installation, removing unneeded packages and services, setting secure permissions and logging levels, and installing tools like Tripwire and SSH.
The document discusses the benefits of meditation for reducing stress and anxiety. Regular meditation practice can help calm the mind and body by lowering heart rate and blood pressure. Studies have shown that meditating for just 10-20 minutes per day can have significant positive impacts on both mental and physical health.
The document provides a history of the internet and explains how it works and some common tools used on it. It began as a US military network called ARPANET and later expanded. The Domain Name System translates website names to IP addresses. Web browsers allow viewing web pages while email and listservs allow communication. Search engines and portals help users find information and HTML defines webpage formatting.
The document discusses a methodology for effectively troubleshooting networking problems which includes identifying symptoms, determining the scope of the problem, establishing what has changed, selecting the most probable cause, verifying physical and logical connectivity, recognizing potential solution effects, implementing and testing a solution, and documenting the problem and resolution. It also discusses various software and hardware tools that can be used to diagnose networking issues, including cable testers, network monitors, protocol analyzers, and wireless network testing tools.
This chapter discusses the history and varieties of UNIX and Linux operating systems. It describes how to install Linux, configure users and permissions, and interconnect Linux with other network operating systems using tools like Samba, WINE, VMware and Telnet. The chapter also provides examples of basic Linux commands and how to set up a Linux server with the required hardware specifications.
Chapter08 -- network operating systems and windows server 2003-based networkingRaja Waseem Akhtar
This chapter discusses network operating systems and Windows Server 2003. It covers the functions of a network OS like managing resources and users. Windows Server 2003 editions are examined along with installation requirements. Features like Active Directory, file systems, and integration with other OSs are described. The chapter concludes with instructions for a basic Windows Server 2003 installation and configuration of users and groups.
The document discusses wide area networks (WANs) and remote connectivity. It defines WANs and their essential components. It describes various WAN topologies including bus, ring, star, mesh and tiered. It also discusses several WAN transmission methods like PSTN, ISDN, T-carriers, DSL, cable, and SONET. The document concludes with an overview of remote connectivity options like dial-up networking, remote control, terminal services, web portals and virtual private networks.
This document provides an overview of network topologies and access methods. It describes physical topologies like bus, ring, and star, as well as hybrid topologies like star-wired ring and star-wired bus. It also covers backbone structures, switching methods, Ethernet, Token Ring, FDDI, ATM, and wireless networking standards like 802.11a, 802.11b, and 802.11g. Key aspects like frames, association, and quality of service are discussed for different network types.
This document provides an overview of various networking hardware components, including their functions and how they operate at different layers of the OSI model. It describes network adapters, repeaters, hubs, bridges, switches, routers, and gateways. It covers topics such as installing and configuring network adapters, choosing the right adapter, VLANs, and common routing protocols.
The document summarizes key network protocols including TCP/IP, IPX/SPX, NetBIOS, and AppleTalk. It describes the layers of the TCP/IP protocol suite and how they correspond to the OSI model. It also discusses important TCP/IP protocols like TCP, IP, UDP, ICMP, and ARP as well as addressing schemes, dynamic host configuration protocol (DHCP), and port numbers.
What is an RPA CoE? Session 1 – CoE VisionDianaGray10
In the first session, we will review the organization's vision and how this has an impact on the COE Structure.
Topics covered:
• The role of a steering committee
• How do the organization’s priorities determine CoE Structure?
Speaker:
Chris Bolin, Senior Intelligent Automation Architect Anika Systems
Lee Barnes - Path to Becoming an Effective Test Automation Engineer.pdfleebarnesutopia
So… you want to become a Test Automation Engineer (or hire and develop one)? While there’s quite a bit of information available about important technical and tool skills to master, there’s not enough discussion around the path to becoming an effective Test Automation Engineer that knows how to add VALUE. In my experience this had led to a proliferation of engineers who are proficient with tools and building frameworks but have skill and knowledge gaps, especially in software testing, that reduce the value they deliver with test automation.
In this talk, Lee will share his lessons learned from over 30 years of working with, and mentoring, hundreds of Test Automation Engineers. Whether you’re looking to get started in test automation or just want to improve your trade, this talk will give you a solid foundation and roadmap for ensuring your test automation efforts continuously add value. This talk is equally valuable for both aspiring Test Automation Engineers and those managing them! All attendees will take away a set of key foundational knowledge and a high-level learning path for leveling up test automation skills and ensuring they add value to their organizations.
The Department of Veteran Affairs (VA) invited Taylor Paschal, Knowledge & Information Management Consultant at Enterprise Knowledge, to speak at a Knowledge Management Lunch and Learn hosted on June 12, 2024. All Office of Administration staff were invited to attend and received professional development credit for participating in the voluntary event.
The objectives of the Lunch and Learn presentation were to:
- Review what KM ‘is’ and ‘isn’t’
- Understand the value of KM and the benefits of engaging
- Define and reflect on your “what’s in it for me?”
- Share actionable ways you can participate in Knowledge - - Capture & Transfer
"Scaling RAG Applications to serve millions of users", Kevin GoedeckeFwdays
How we managed to grow and scale a RAG application from zero to thousands of users in 7 months. Lessons from technical challenges around managing high load for LLMs, RAGs and Vector databases.
Must Know Postgres Extension for DBA and Developer during MigrationMydbops
Mydbops Opensource Database Meetup 16
Topic: Must-Know PostgreSQL Extensions for Developers and DBAs During Migration
Speaker: Deepak Mahto, Founder of DataCloudGaze Consulting
Date & Time: 8th June | 10 AM - 1 PM IST
Venue: Bangalore International Centre, Bangalore
Abstract: Discover how PostgreSQL extensions can be your secret weapon! This talk explores how key extensions enhance database capabilities and streamline the migration process for users moving from other relational databases like Oracle.
Key Takeaways:
* Learn about crucial extensions like oracle_fdw, pgtt, and pg_audit that ease migration complexities.
* Gain valuable strategies for implementing these extensions in PostgreSQL to achieve license freedom.
* Discover how these key extensions can empower both developers and DBAs during the migration process.
* Don't miss this chance to gain practical knowledge from an industry expert and stay updated on the latest open-source database trends.
Mydbops Managed Services specializes in taking the pain out of database management while optimizing performance. Since 2015, we have been providing top-notch support and assistance for the top three open-source databases: MySQL, MongoDB, and PostgreSQL.
Our team offers a wide range of services, including assistance, support, consulting, 24/7 operations, and expertise in all relevant technologies. We help organizations improve their database's performance, scalability, efficiency, and availability.
Contact us: info@mydbops.com
Visit: https://www.mydbops.com/
Follow us on LinkedIn: https://in.linkedin.com/company/mydbops
For more details and updates, please follow up the below links.
Meetup Page : https://www.meetup.com/mydbops-databa...
Twitter: https://twitter.com/mydbopsofficial
Blogs: https://www.mydbops.com/blog/
Facebook(Meta): https://www.facebook.com/mydbops/
Dandelion Hashtable: beyond billion requests per second on a commodity serverAntonios Katsarakis
This slide deck presents DLHT, a concurrent in-memory hashtable. Despite efforts to optimize hashtables, that go as far as sacrificing core functionality, state-of-the-art designs still incur multiple memory accesses per request and block request processing in three cases. First, most hashtables block while waiting for data to be retrieved from memory. Second, open-addressing designs, which represent the current state-of-the-art, either cannot free index slots on deletes or must block all requests to do so. Third, index resizes block every request until all objects are copied to the new index. Defying folklore wisdom, DLHT forgoes open-addressing and adopts a fully-featured and memory-aware closed-addressing design based on bounded cache-line-chaining. This design offers lock-free index operations and deletes that free slots instantly, (2) completes most requests with a single memory access, (3) utilizes software prefetching to hide memory latencies, and (4) employs a novel non-blocking and parallel resizing. In a commodity server and a memory-resident workload, DLHT surpasses 1.6B requests per second and provides 3.5x (12x) the throughput of the state-of-the-art closed-addressing (open-addressing) resizable hashtable on Gets (Deletes).
In the realm of cybersecurity, offensive security practices act as a critical shield. By simulating real-world attacks in a controlled environment, these techniques expose vulnerabilities before malicious actors can exploit them. This proactive approach allows manufacturers to identify and fix weaknesses, significantly enhancing system security.
This presentation delves into the development of a system designed to mimic Galileo's Open Service signal using software-defined radio (SDR) technology. We'll begin with a foundational overview of both Global Navigation Satellite Systems (GNSS) and the intricacies of digital signal processing.
The presentation culminates in a live demonstration. We'll showcase the manipulation of Galileo's Open Service pilot signal, simulating an attack on various software and hardware systems. This practical demonstration serves to highlight the potential consequences of unaddressed vulnerabilities, emphasizing the importance of offensive security practices in safeguarding critical infrastructure.
In our second session, we shall learn all about the main features and fundamentals of UiPath Studio that enable us to use the building blocks for any automation project.
📕 Detailed agenda:
Variables and Datatypes
Workflow Layouts
Arguments
Control Flows and Loops
Conditional Statements
💻 Extra training through UiPath Academy:
Variables, Constants, and Arguments in Studio
Control Flow in Studio
As AI technology is pushing into IT I was wondering myself, as an “infrastructure container kubernetes guy”, how get this fancy AI technology get managed from an infrastructure operational view? Is it possible to apply our lovely cloud native principals as well? What benefit’s both technologies could bring to each other?
Let me take this questions and provide you a short journey through existing deployment models and use cases for AI software. On practical examples, we discuss what cloud/on-premise strategy we may need for applying it to our own infrastructure to get it to work from an enterprise perspective. I want to give an overview about infrastructure requirements and technologies, what could be beneficial or limiting your AI use cases in an enterprise environment. An interactive Demo will give you some insides, what approaches I got already working for real.
Keywords: AI, Containeres, Kubernetes, Cloud Native
Event Link: https://meine.doag.org/events/cloudland/2024/agenda/#agendaId.4211
"Frontline Battles with DDoS: Best practices and Lessons Learned", Igor IvaniukFwdays
At this talk we will discuss DDoS protection tools and best practices, discuss network architectures and what AWS has to offer. Also, we will look into one of the largest DDoS attacks on Ukrainian infrastructure that happened in February 2022. We'll see, what techniques helped to keep the web resources available for Ukrainians and how AWS improved DDoS protection for all customers based on Ukraine experience
GlobalLogic Java Community Webinar #18 “How to Improve Web Application Perfor...GlobalLogic Ukraine
Під час доповіді відповімо на питання, навіщо потрібно підвищувати продуктивність аплікації і які є найефективніші способи для цього. А також поговоримо про те, що таке кеш, які його види бувають та, основне — як знайти performance bottleneck?
Відео та деталі заходу: https://bit.ly/45tILxj
AI in the Workplace Reskilling, Upskilling, and Future Work.pptxSunil Jagani
Discover how AI is transforming the workplace and learn strategies for reskilling and upskilling employees to stay ahead. This comprehensive guide covers the impact of AI on jobs, essential skills for the future, and successful case studies from industry leaders. Embrace AI-driven changes, foster continuous learning, and build a future-ready workforce.
Read More - https://bit.ly/3VKly70
Getting the Most Out of ScyllaDB Monitoring: ShareChat's TipsScyllaDB
ScyllaDB monitoring provides a lot of useful information. But sometimes it’s not easy to find the root of the problem if something is wrong or even estimate the remaining capacity by the load on the cluster. This talk shares our team's practical tips on: 1) How to find the root of the problem by metrics if ScyllaDB is slow 2) How to interpret the load and plan capacity for the future 3) Compaction strategies and how to choose the right one 4) Important metrics which aren’t available in the default monitoring setup.
AppSec PNW: Android and iOS Application Security with MobSFAjin Abraham
Mobile Security Framework - MobSF is a free and open source automated mobile application security testing environment designed to help security engineers, researchers, developers, and penetration testers to identify security vulnerabilities, malicious behaviours and privacy concerns in mobile applications using static and dynamic analysis. It supports all the popular mobile application binaries and source code formats built for Android and iOS devices. In addition to automated security assessment, it also offers an interactive testing environment to build and execute scenario based test/fuzz cases against the application.
This talk covers:
Using MobSF for static analysis of mobile applications.
Interactive dynamic security assessment of Android and iOS applications.
Solving Mobile app CTF challenges.
Reverse engineering and runtime analysis of Mobile malware.
How to shift left and integrate MobSF/mobsfscan SAST and DAST in your build pipeline.
2. Chapter Goals
• Understanding the importance of backups.
• Understand the issues associated with
backups.
• Understand backup strategies and
scheduling.
• Understand the basics of backup devices.
• Understand the basics of backup media.
• Understand the various types of backup
software.
3. Importance of System Backups
• Which Files Should Be Backed Up?
– OS Binaries?
– Applications?
– Configuration Files?
– User files?
– Log files?
• Generally, full backups of everything are easiest to manage, but
backup of system files is creating extra work for yourself.
– Possibly full dump when installed, then again after
patches/upgrades.
• Backup of just user files is not enough.
• Should dump the log files, and configuration information.
4. Importance of System Backups
• How Often Should Backups Be Performed?
– Need to determine what level of data loss is
acceptable:
• Web sales? - need very fine grain backups.
• Banking/Insurance? - very fine grain.
• Research and development? - fine to medium grain.
• University? - medium grain.
• Mom and Pop? - coarse grain.
5. Backup Strategy and Scheduling
• Types of Backups
– Full backup– dump every file to dump media.
– Partial (incremental) backup – dump all files that
have changed since last lower level backup to dump
media.
• Unix uses a multi-level partial scheme (level 0 is a full,
level 1 – 9 are incremental).
– All files that have been modified since the last ufsdump at a
lower dump level are copied to the dump media.
– For instance, if a "level 2" dump was done on Monday,
followed by a "level 4" dump on Tuesday, a subsequent
"level 3 dump on Wednesday would contain all files modified
or added since the "level 2" (Monday) backup.
– A "level 0" dump copies the entire file system to the
dump media.
6. Backup Strategy and Scheduling
• Backup Strategies
– There are several algorithms that might be used to schedule
full and partial backups.
– The choice of algorithm dictates the amount of media required.
– The choice of algorithm plays a large role in the size of the
restore window (how long is data available from a backup
tape).
– Some of the more popular algorithms are:
• Volume/Calendar Backup
• Grandfather/Father/Son Backup
• Tower of Hanoi Backup
7. Backup Strategy and Scheduling
• Volume/Calendar Backup
– The volume/calendar backup strategy calls for a full system
backup once a month.
– An incremental backup is performed once a week for files that
change often.
– Daily incremental backups catch files that have changed since
the last daily backup.
– A typical schedule would be to perform the full (level 0) backup
one Sunday a month, and weekly level 3 backups every Sunday
of the month.
– Daily level 5 backups would be performed Monday through
Saturday.
– This would require eight complete sets of media (one monthly
tape, one weekly tape, and six daily tapes)
8. Volume Calendar
Su M Tu W Th F Sa
Week 1 Tape A B C D E F G
Level 0 5 5 5 5 5 5
Weeks 2, 3, 4 H
Level 3 5 5 5 5 5 5
• Recovering from complete data loss with the volume/calendar scheme
requires restoring from the most recent full backup, then restoring from
the most recent weekly backup, and finally, restoring from each daily
backup tape written since the weekly backup.
• An advantage to this backup scheme is that it requires a minimum of
media, but this also points out one of the major problems with this backup
scheme: tapes are immediately reused.
– For example, every Monday overwrites last Monday’s backup
information. Consider what would happen if one of the disk drives
failed during the second Monday backup.
– It would not be possible to recover all data, because the system was in
the process of overwriting the backup tape when the drive failed.
9. Backup Strategy and Scheduling
• Grandfather/Father/Son Backup
– The grandfather/father/son backup strategy is similar to the
volume/calendar strategy.
• The major difference between the two schemes is that the
grandfather/father/son method incorporates a one-month archive
in the backup scheme. This eliminates the problem of overwriting
a tape before completing a more recent backup of the file
system.
• Implementing the grandfather/father/son strategy requires
performing a full (level 0) dump once a month to new media.
• Once a week, an incremental (level 3) backup must be
performed that captures all files changed since the last weekly
backup.
• This weekly backup should also be saved on new media.
• Each day an incremental level 5 backup must be performed to
capture files that have changed since the last daily backup.
•
10. Grandfather/Father/Son
Su M Tu W Th F Sa
Week 1 Tape A B C D E F G
Level 0 5 5 5 5 5 3
Week 2 Tape H I
Level 5 3
Week 3 Tape H J
Level 5 3
Week 4 Tape H K
Level 5 3
Week 5 L M
Level 0 3
Week 6 Tape H G
Level 5 3
Week 7 Tape H I
Level 5 3
Week 8 Tape H J
Level 5 3
Week 9 Tape A
Level 0
11. Grandfather/father/son
• To maintain a one-month archive, the monthly full backup tape should be
placed in storage.
• Each weekly full backup should be placed in storage.
• The second monthly full backup, should use new media.
• When the third monthly backup is due, the first month’s full backup media
should be reused. The weekly backups are archived in a similar manner.
• This scheme requires two sets of monthly backup media, five sets of
weekly backup media, and six sets of daily backup media.
• A total of 13 sets of media are required to implement this strategy with a
one-month archive of information.
• To recover from complete data loss, first restore the most recent level 0
backup tape.
• Next, restore from the most recent of the level 3 backups, if that backup
was written after the level 0 backup.
• When the level 3 backup has been restored, the operator would restore
from each of the level 5 backups written after the level 3 backup.
• This backup strategy requires much more media than the simple volume /
calendar strategy. Although media cost is increased with this plan, data
survivability also increases.
12. Backup Strategy and Scheduling
• Tower of Hanoi Backup
– The Tower of Hanoi backup strategy is a variation of “exponential
backup.” Both strategies rely on functions of powers of 2.
– For example, the use of five backup tapes provides for a 32-day
schedule. The use of six tapes would provide for a 64-day
schedule.
– The Tower of Hanoi backup schedule provides outstanding data
survivability and a minimum of media. Unfortunately, on a seven-
day backup system, the scheduling of full backups as opposed to
partial backups can become a problem for the operator.
– One way to avoid operator confusion is to perform a special level
0 backup on the first day of each month. This tape would not be
one of the five tapes used in the backup cycle. Total media
requirements in this scheme would be seven sets of media.
13. Su M Tu W Th F Sa
Week 1 Tape E A B A C A B
Level 0 5 4 5 3 5 4
Week 2 Tape A D A B A C A
Level 5 1 5 4 5 3 5
Week 3 Tape B A E A B A C
Level 4 5 0 5 4 5 3
Week 4 Tape A B A D A B A
Level 5 4 5 1 5 4 5
Week 5 C A B A E A B
Level 3 5 4 5 0 5 4
Week 6 Tape A C A B A D A
Level 5 3 5 4 5 1 5
Week 7 Tape B A C A B A E
Level 4 5 3 5 4 5 0
Week 8 Tape A B A C A B A
Level 5 4 5 3 5 4 5
Week 9 Tape D A B
Level 1 5 4
14. Backup Strategy and Scheduling
• Tower of Hanoi Backup
– To recover from complete data loss, first restore from the most
recent level 0 backup, and then restore from the level 1 backup if
that backup was written after the level 0 backup.
– Next, restore consecutively from the most recent level 3 and 4
backups if both were written after the level 0 backup.
– Finally, restore each of the level 5 backups that were written after
the level 0 backup.
15. Reasonable Alternative
• The following four-week schedule offers a reasonable backup schedule
for most sites.
• Performing a full dump on the first Sunday of the month provides a
monthly snapshot of the system data.
• Using two sets of dump media allows the operator to store information
for two full months.
• Note that in the example the Tuesday through Friday incremental
backups contain extra copies of files from Monday.
• This schedule ensures that any file modified during the week can be
recovered from the previous day’s incremental dump.
• To recover from complete data loss, restore the most recent full (level 0)
backup tape.
• Next, restore from the most recent of the weekly (level 3) backups. Once
the weekly backups are restored, restore from each of the daily (level 5)
backups.
16. A Reasonable Alternative?
Su M Tu W Th F Sa
Week 1 Tape A B C D E
Level 0 5 5 5 3
Week 2 Tape F B C D E
Level 5 5 5 5 3
Week 3 Tape F B C D E
Level 5 5 5 5 3
Week 4 Tape F B C D E
Level 5 5 5 5 3
17. Backup Devices
• Backup devices must exhibit the following traits:
– User ability to write data to the device.
– Media capable of storing the data for long periods.
– Support of standard system interconnects.
– Support of reasonable input/output throughput.
18. Backup Devices
• Tape Backup Devices
– Cartridge Tape Drive
– 8-mm Tape Drive
– Digital Audio Tape Drive
– Linear Tape Open
– Digital Linear Tape
– Jukebox/Stacker Systems
• Optical Backup Devices
• Magneto-optical Backup Devices
• Disk Systems As Backup Devices
– RAID Disk Arrays
– Problems with Disks As Backup Devices
• High-Density Removable Media Backups
19. Backup Devices
• Tape backup devices are probably the most common
backup media in use.
– The media is relatively inexpensive, the performance is
reasonable, the data formats are standardized, and tape drives
are easy to use.
– These factors combined make magnetic tape backups an
attractive option.
– Most current-generation tape drives offer “native” mode and
compressed mode storage capabilities.
• Generally, the manufacturers claim a 2:1 compression ratio, but
this value may vary based on the data to be stored.
• Binaries (images, compiled programs, audio files, and so on)
may not be significantly smaller when compressed, whereas text
files may compress very well.
20. Tape Backup Devices
• Cartridge Tape Drive
– Cartridge tape drives store between 10 Mb and several Gb of data on a
small tape cartridge.
– Most cartridge tape systems use SCSI interconnections to the host
system.
– These devices support data transfer rates up to 5 Mb per second. The
actual transfer rate from the tape drive memory to the tape media is
typically about 500 Kb per second.
• 8-mm Tape Drive
– These tape drives are also small and fast, and use relatively inexpensive
tape media.
– The 8-mm media can hold between 2 and 100 GB of data, depending on
the drive model and type of tape in use.
– The 8-mm drives use the SCSI bus as the system inter-connection.
– Low-density 8-mm drives can store 2.2 Gb of information on tape. and
transfer data to the tape at 250 Kb per second. High-density 8-mm drives
can store up to 80 GB of information on a tape at a 16 MB/second.
– “low” end, the 8-mm drives do not use data compression to store the data
on tape. “high” end, advanced intelligent tape drives incorporate
compression hardware and improved recording techniques to increase
the amount of information that can be stored on the tape.
21. Tape Backup Devices
• Digital Audio Tape Drive
– Digital audio tape (DAT) drives are small, fast, and use
relatively inexpensive tape media. Typical DAT media
can hold between 2 and 40 GB of data.
– Although manufacturers of DAT devices have announced
the end-of-life for these products, they will remain in use
for many years.
– The various densities available on DAT drives are due to
data compression. A standard DAT drive can write 2 Gb
of data to a tape. By using various data compression
algorithms, and various lengths of tape, manufacturers
have produced drives that can store between 2 and 40
GB of data on a tape.
– DAT drives use SCSI bus interconnections to the host
system, and typically offer 3 MB/second throughput.
22. Tape Backup Devices
• Linear Tape Open
– A consortium of Hewlett Packard, IBM, and Seagate
developed the LTO technology. LTO encompasses two
formats: the Ultrium, a high-capacity solution, and Accelis
format, a fast-access format. The two formats use
different tape drives, and tape cartridges.
– LTO Ultrium drives can store up to 100 Gb of data on a
single tape cartridge at 16 Mb/second.
23. Tape Backup Devices
• Digital Linear Tape
– Digital linear tape (DLT) backup devices are also relatively new on
the backup market.
– These tape devices offer huge data storage capabilities, high
transfer rates, and small (but somewhat costly) media.
– Digital linear tape drives can store up to 110 Gb of data on a single
tape cartridge. Transfer rates of 11 Mb/second are possible on high-
end Super-DLT drives, making them very attractive at sites with
large on-line storage systems.
– Where 8-mm and DAT tapes cost (roughly) $15 per tape, the LTO,
AIT, and DLT tapes can run as much as $150 each. However, when
the tape capacity is factored into the equation, the costs of these
high-capacity tapes become much more reasonable.
• Consider an 8-mm tape that holds (up to) 14 Gb on average versus
a LTO cartridge, which can hold 100 Gb of data!
24. Tape Backup Devices
• Jukebox/Stacker Systems
– Jukebox or stacker systems combine an automated
mechanism with one or more tape drives.
– Stackers are sequential tape systems. Tapes are stacked
in a hopper, and the tape drive starts by loading the tape
at the bottom of the stack. When the tape is full, it is
ejected, and the next tape is loaded from the stack.
– Many stackers do not have the capability to load a
specific tape in the drive. Instead, these stackers simply
cycle (sequentially) through the tapes until the last tape is
reached. At this point they can either start the cycle over
again or wait for a new group of tapes to be loaded into
the hopper.
25. Tape Backup Devices
• Jukebox/Stacker Systems
– Unlike stackers, jukebox systems employ multiple tape
drives, and special “robotic” hardware to load and unload
the tapes.
– Jukebox systems require special software to control the
robotics. The software keeps track of the content of each
tape and builds an index to allow the user to quickly load
the correct tape on demand. Each tape is “labeled” with a
bar-code decal (or something similar), and the
mechanism contains a label reader that keeps track of
what tape is in the drive. Many commercially available
backup software packages allow the use of jukebox
systems to permit backup automation.
26. Optical Backup Devices
• Optical Backup Devices
– Recently, optical storage devices have become another economical
means of backing up mass storage systems.
– Compact disk read-only-memory devices (CD-ROM) are useful for
long-term archive of information.
• Although the name implies that these are read-only devices, recent
technology has made it possible to mass market the devices that
create the encoded CD-ROM media.
• These CD-ROM writers (also called CD-recordables) make it
possible to consider CD-ROM as a backup device. More recent
versions of this technology have produced rewritable CD-ROMs
(CD-RW or CDR).
27. Optical Backup Devices
• Optical Backup Devices
– One of the major decisions in choosing a backup device is the ability
of the medium to store information for long periods.
• CD-ROM media offer excellent data survivability.
• Another advantage to the CD-ROM is the availability of reliable data
transportability between systems. This reliability is possible due to
the CD-ROM’s adherence to industry standardized data formats.
• Along with these advantages, the CD-ROM offers a few unique
disadvantages. The foremost disadvantage to the CD-ROM as a
backup device is the setup cost to create a CD. Setting up and
creating a CD is a time-intensive operation.
– Some small sites may decide to back up to CD-ROM rewritable (CDR)
media. The CDR format allows the reuse of optical media, thereby
reducing the cost of backing up to optical devices.
• Unfortunately, the CDR is still a low-density solution, providing a
mere 650 Mb of storage per disk. The setup and record time for
CDR is comparable to CD-ROM media, making CDR less attractive
for backups at large sites.
28. Magneto-Optical Backup Devices
• Magneto-optical Backup Devices
– Optical storage systems and associated media are typically expensive.
They are also relatively slow devices. Consequently, optical storage
systems are rarely used as backup devices at large sites.
• In contrast, magnetic tape (or disk) storage systems are
inexpensive and fast. Unfortunately, the media is bulky and
susceptible to damage and data loss.
• By combining the two storage systems into a single system,
manufacturers have been able to provide fast, inexpensive, and
reliable backup systems.
– Many of the magneto-optical systems are hierarchical, meaning that
they keep track of how long a file has been in storage since the last
modification.
• Files that are not accessed or modified are often eligible to be
stored on the slower optical storage section of the system.
• Frequently accessed files are maintained on the magnetic storage
section of these systems, which allows for faster access to files.
– Most magneto-optical storage systems use standard SCSI bus system
interconnections. These systems can typically provide the same (or
better) data transfer rates as SCSI tape and disk systems.
29. Disk Backup Devices
• Disk Systems As Backup Devices
– One problem involved in using tape devices for backups is the
(relatively) low data throughput rate.
– If the operator had to back up several gigabytes or terabytes of data
daily, it would not take long to realize that tape drives are not the best
backup method.
– Although optical backup devices offer high storage capacity, the
optical devices are often much slower than tape devices.
– One popular method of backing up large-scale systems is to make
backup copies of the data on several disk drives.
• Disk drives are orders of magnitude faster than tape devices, and
therefore offer a solution to one of the backup problems on large-
scale systems.
– However, disk drives are much more expensive than tapes.
– Disk backups also consume large amounts of system
resources.
– For example, you would need 100 2-Gb disks to back up 100 2-
Gb disks. Fortunately, there are software applications and
hardware systems available to transparently perform this
function.
30. Disk Backup Devices
• RAID Disk Arrays
– One operating mode of redundant arrays of inexpensive disks
(RAID) enables the system to make mirror image copies of all data
on backup disk drives.
– RAID disk arrays also allow data striping for high-speed data access.
– Yet another mode stores the original data, as well as parity
information on the RAID disks. If a drive should fail, the parity
information may be used to recreate the data from the failed drive.
• Problems with Disks As Backup Devices
– When tape devices are employed as the backup platform, it is a
simple matter to keep a copy of the backups off-site.
– When disk drives are employed as a backup media, the process of
keeping a copy of the backup media off-site becomes a bit more
complicated (not to mention much more expensive).
• In the case of a RAID disk array, the primary copy of the data is
stored on one disk, and the backup copy of the data is stored on
another disk. However, both disks are housed in a single box. This
makes the task of moving one drive off-site much more
complicated.
31. Disk Backup Devices
– RAID disk arrays have recently been equipped with fiber channel
interfaces.
– The fiber channel is a high-speed interconnect that allows devices to
be located several kilometers from the computer.
• By linking RAID disk arrays to systems via optical fibers, it is
possible to have an exact copy of the data at a great distance from
the primary computing site at all times.
• High-Density Removable Media Backups
– A relatively recent addition to the backup market is the high-density
removable media drive.
– Examples of these devices include the Iomega ZIP and JAZ drives, and
the Imation Superdisk drives.
• These devices are capable of recording 100 Mb to 2 Gb of data on a
removable medium that resembles a floppy diskette.
– Until recently, UNIX could not make use of these high-density
removable media devices.
– Many of these devices employ a parallel port interface. A few of them
offer SCSI interfaces, allowing them to be connected to the external
SCSI port on a workstation.
32. Unix Backup Commands
• Unix operating environments include a plethora of backup
utilities.
– The [ufs]dump and [ufs]restore utilities are available under most
UNIX variants.
• The dump application was developed to allow the backup of entire
systems one at a time.
• The dump program allows the operator to specify files to be
“dumped” (or backed up to tape), and options to use during the
dump.
• In addition, dump enables scheduling of different levels of dumps
on different days.
• The dump command also allows for dumps that occupy multiple
tape reels.
33. UNIX Backup Commands
• dump [options] [arguments] files_to_dump
– NOTE: The dump command requires that the user have read access
privileges on the system disks.
• 0-9: These numeric values specify the dump level. All files that have
been modified since the last dump at a lower dump level are copied
to the media.
• b: Signifies the blocking factor to be used. The default is 20 blocks
per write for tape densities of 6,250 BPI (bytes per inch) or less.
The blocking factor of 64 is used for tapes with 6,250 BPI or greater
density. The default blocking factor for cartridge tapes is 126.
NOTE: blocking factor is specified in 512-byte blocks.
• c: Signifies that the backup device is a cartridge tape drive. The
option sets the density to 1,000 BPI and the blocking factor to 126.
• d: Signifies the density of the backup media in BPIs. The default
density is 6,250 BPI except when the c option is used. When the c
option is used, the density is set to 1,000 BPI per track.
34. Unix Backup Commands
• D: Signifies that the dump device is a floppy diskette.
• f: Signifies the dump file. This option causes dump to use
dump file as the file to dump to, instead of /dev/rmt/0.
• s: Signifies the size of the backup volume. This option is not normally
required because dump can detect end-of-media. When the specified
size is reached, dump waits for the operator to change the volume. The
size parameter is interpreted as the length in feet for tapes and
cartridges, and as the number of 1,024-byte blocks for diskettes.
• u: This option causes dump to annotate which file systems were
dumped, the dump level, and the date in the /etc/dumpdates file.
• v: This letter signifies that dump should verify the content of the backup
media after each tape or diskette is written.
• # dump 0fu /dev/rmt/0 /dev/rdsk/c0t3d0s2
35.
36. UNIX Backup Commands
• Now that file systems have been copied onto a tape, how is this
information retrieved?
– UNIX provides an application to restore data from the backup media
to the system mass storage devices.
– This application is called restore.
• /usr/sbin/restore options [ arguments ] [ filename ... ]
• Some of the most useful options to the restore com-mands follow.
– i: Places restore in the interactive mode. Com-mands available in this
mode follow.
– add [filename]: Adds the named file or directory to the list of files to be
extracted.
– cd directory: Changes to directory on the dump media.
– delete [filename]: Deletes the current directory or file from the list of
files to be extracted.
– extract: Extracts all files on the extraction list from the dump media.
37. UNIX Backup Commands
– ls [directory]: Lists files in directory (dump media) or the current
directory, which is represented by a period (.).
– pwd: Prints the full path name of the current working directory.
– quit: Exits immediately.
– verbose: Toggles the verbose flag (the program prints a line for every
action it takes).
– r: Restores the entire content of the media into the current directory.
– x: Extracts the named files from the media.
– b: Sets the restore blocking factor.
– f [dump file]: Tells restore to use the dump file instead of /dev/rmt/0 as
the file to restore from.
– R: Resumes restore after volume is changed.
– t: Prints table of contents for dump file.
– n: Skips to the nth file when multiple dump files exist on the same
tape.
– v: Displays the name and inode number of each file restored.
– Note that the i, r, R, t, and x arguments are mutually exclusive. Only
one of these arguments may be used at a time.
40. Unix Backup Commands
• Remote Backup and Restore
– How can a file system dump be performed on a system without a
backup device?
– The dump and restore commands allow input and output to be sent
to the standard input and output streams. This flexibility allows the
dump/restore output to be sent through the network to a system with
a backup device.
– The -f option for dump and restore specifies the dump device.
– f dump file: This option tells dump to use dump file as the file to
dump to. If dump file is specified as a hyphen ( - ), dump will dump to
standard output. If the name of the file is of the form machine:device,
the dump is carried out from the specified machine over the network
using the rmt facility.
– NOTE: Because dump is normally run by root, the name of the local
machine must appear in the /.rhosts file of the remote machine.
41. Unix Backup Commands
– To perform a remote restore using the restore command,
the operator can make use of the -f option again.
– f dump file: This option tells restore to use dump file as
the file to restore from. If dump file is specified as a
hyphen ( - ), restore reads from the standard input.
– NOTE: Because restore is also normally run by root, the
name of the local machine must appear in the /.rhosts file
of the remote machine.
– To copy a home partition to another machine with a
remote restore, consider the following command, sub-
stituting the appropriate directory and device names.
– # dump 0f - /dev/rdsk/c0t2d0s2 | (rsh machine ; cd
/home;restore xf -)
42. Unix Backup Commands
• tar Command
• What happens if the operator does not want to dump and restore complete
file systems?
– For example, what if a user simply wants to make a tape of the data
associated with one project?
– Most UNIX derivatives provide a standardized utility called tar. The tar
command creates tape archives and provides the ability to add and
extract files from these archives.
% tar c -C /home/project include -C /data/project
% tar cvf /dev/rmt/0
– Create a tar archive on device /dev/rmt/0
% tar tvf /dev/rmt/0
– List the contents of the tar archive on /dev/rmt/0
% tar xvf /dev/rmt/0
– Extract the contents of the tar archive on /dev/rmt/0
43. Unix Backup Commands
• Another command that may be used to back up and restore
files is cpio.
• The cpio command copies file archives “in and out.”
• The syntax for the cpio command follows.
cpio -key [options] filename
• The key option to cpio determines the actions to be
performed. The following flags are mutually exclusive.
44. Unix Backup Commands
• % ls | cpio -oc >> ../newfile
– NOTE: The find, echo, and cat commands can
also be used as substitutes for the ls command to
produce a list of files to be included in ../newfile.
• To extract the files from ../newfile, issue the following
command.
• % cat newfile | cpio -icd
• % find . -depth -print | cpio -pdlmv newdir
– NOTE: When using cpio in conjunction with find,
use the L option with cpio, and the -follow option
with find.
45. Unix Backup Commands
• Yet another command available to use as a backup-and-
restore utility is the dd utility.
• The dd command copies the input file to output, applying
any desired conversions in the process.
• When complete, dd reports the number of whole and partial
input and output blocks.
dd [ option = value ] ....
46. Unix Backup Commands
• Do not use dd to copy files between file systems
with different block sizes.
• Using a blocked device to copy a file will result in
extra nulls being added to the file, in order to pad
the final block to the block boundary.
• When dd reads from a pipe, using the ibs = X and
obs = Y operands, the output will always be
blocked in chunks of size Y.
• When bs = Z is used, the output block size will be
whatever could be read from the pipe at the time.
47. Unix Backup Commands
• if = filename: Use filename as the input file. stdin is the default value.
• of = filename: Use filename as the output file. stdout is the default value.
• ibs = n: Use n as the input block size. 512 is the default value.
• obs = n: Use n as the output block size. 512 is the default value.
• bs = n: Use n as the input and output block size This supersedes the ibn
and obn arguments. If no conversion is specified, preserve input block
size.
• files = n: Copy and concatenate n input files before terminating.
• skip = n: Skip n input blocks before performing copy.
• iseek = n: Seek n blocks from the beginning of the input file before
copying.
• oseek = n: Seek n blocks from the beginning of the output file before
copying.
• count = n: Copy n input blocks.
• swab: Swap every pair of bytes.
• sync: Pad every input block to ibs.
49. Windows Backup Commands
• Like its UNIX cousins, Windows provides a utility to perform
file system backups.
• The Windows backup-and-restore utility (backup.exe)
provides for backups, and restores.
– In backup mode, the operator is given the ability to select which
disk and/or files to back up, whether the local registry should be
dumped, whether the backup should use compression, and what
users may read the backup tape(s).
– Otherwise, the “menu” of backup options available to the operator
is pretty limited.
50.
51. Windows Backup Commands
• The Options menu under the Tools menu allows the
operator to determine the type of backup to be performed,
whether data should be verified after the backup is
performed, the amount of detail supplied in the log files,
whether new media should be used, backup scheduling,
and other configuration parameters for the backup utility.
52.
53. Windows Backup Commands
• The Windows backup utility also provides the interface to the restore
function.
– In restore mode, the utility displays a catalog of the tape, allowing
the user to select which files/directories need to be restored.
– The operator is also given the choice of where the file is to be
restored.
• Although the GUI may simplify the setup of Windows backups, it also
limits the choices available to the operator. Because this utility is based
on the backup utility offered in the consumer versions of Windows, the
sysadmin at a commercial site may decide that the Windows backup
utility is not the first choice for backup software at the site. Many third-
party backup utilities are available for Windows systems, including
Amanda, Legato Networker, and the Veritas backup suite.
54.
55. Dealing with Specific Backup Issues
• Certain aspects of successful backup and restore
strategies require special attention.
– For instance, how could the operator restore the root
file system if the root disk had crashed and there
was no way to boot the system?
– Many administrators are also concerned with how to
automate backups to minimize time investment while
ensuring successful backups.
– Next, what happens if a backup requires 2 Gb of
backup media, but the backup device can write only
1 Gb to the media?
56. Dealing with Specific Backup Issues
• Restoring the Root File System
– One of the most difficult problems faced when using
restore is restoring the root file system.
• If the root file system is missing, it is not possible to boot the
damaged system, and there would not be a file system tree to
restore to.
• One way to accomplish a root file system reload is by booting the
system to the single-user state from the CD-ROM distribution
media.
• Another way to reload the root file system would be to boot the
system to the single-user state as a client of another system on
the network.
• Another method of restoring the root file system is to remove the
disk from the system, and attach it to a working system.
57. Dealing with Specific Backup Issues
• Multi-volume Dumps
– Two of the backup commands mentioned in this chapter also allow
for multi-volume backups.
• The dump command and the cpio command allow a backup to be
stored over multiple media sets.
• The other commands (tar and dd) will allow the user to split the
backups onto several sets of media, but these commands require
that the user perform much of the work manually.
• The cpio command watches for the “end of medium” event. When
cpio detects this event, it stops and prints the following message
on the terminal screen.
If you want to go on, type device/file name when ready.
• To continue the dump, the operator must replace the medium and
type the character-special device name (e.g., /dev/rdiskette) and
press Enter. At this point, the operator may choose to have cpio
continue the backup to another device by typing the device’s name
at the prompt.
58. Dealing with Specific Backup Issues
• Multi-volume Dumps
– Using dump as the backup command is somewhat
simpler.
• Like cpio, dump will detect the end-of-medium event and
stop operation.
• The dump command will then wait for the operator to
change the medium before it continues.
• Unlike cpio, dump does not need the name of the backup
device to continue.
• The operator simply needs to confirm that the medium has
been changed and that everything is ready for dump to
continue operation.
60. Cross Platform Backups
• Several utilities are available for cross-platform backups:
– Veritas
– Legato Networker
– RaxCo
– Amanda – free – http://www.amanda.org/
61. Summary
• This chapter explored the commands that can be used to
make backup copies of system data, why it is important to
make such backup copies of data, and selected methods of
avoiding data loss due to natural or other disasters.
• The authors hope that readers never have to use any of
these backup copies to restore the operation of their
systems, but such restorations are inevitable.
• Good backups require a lot of time and attention, but having
a reliable copy of data is much more acceptable than the
time and expense of rebuilding a system without such
backup copies.
Editor's Notes
TIP: One method of determining which files change frequently is to use the Tripwire program. Tripwire can produce a list of files that have changed subsequent to the creation of the tripwire database. This list should be parsed to ensure that files that change are backed up to tape.
NOTE: The examples in this chapter assume computer system operation seven days a week, and thus the need for seven backups per week. In some instances, corporate computer systems are idle on weekends, enabling the administrator to use a five-day-per-week backup schedule.
To ensure that backups capture as much of the system data as possible, the interval between backups should be kept to a minimum. With these constraints in mind, it is time to examine a few of the more popular backup strategies.
NOTE: To ensure successful dumps, many operating system manufacturers recommend that the system be shut down to the single-user init state.
TIP: Many operators elect not to enable the compression hardware on tape systems, opting instead for software compression before the data are sent to the tape drive. In the event of a hardware failure in the tape drive’s compression circuitry, it is possible that the data written to tape would be scrambled. By using the software compression techniques, the operator can bypass such potential problems at the cost of a few CPU cycles.
NOTE: It is important to note that most versions of dump are incompatible. For example, using ufsdump to back up a Solaris system makes it impossible to reload the data to a Linux system. The “on-tape” formats used by different versions of dump are simply incompatible. Such a tape would need to be reloaded using a Solaris host as the tape host.
WARNING: Several releases of Solaris have included versions of ufsdump and ufsrestore that contain a buffer that is not bounds checked. This has allowed the creation of an exploit that gives a hacker root access to your system! Many security experts recommend that the file permissions of ufsdump and ufsrestore be changed to 0755. This disables the exploit, as the program no longer operates with special permissions, but it also means that the account used to run backups must be given read permission on the system disks.
Estimated 47952 blocks (23.41MB): Estimated size of the dump.
XX.XX% done, finished in H:MM: What proportion of the dump is completed, and how long the remainder will take to complete.
47948 blocks (23.41MB) on 1 volume at 1038 KB/ sec: This message tells how many blocks were dumped, and how many tapes (volumes) were required.
i: Places restore in the interactive mode. Commands available in this mode follow.
add [filename]: Adds the named file or directory to the list of files to be extracted.
cd directory: Changes to directory on the dump media.
delete [filename]: Deletes the current directory or file from the list of files to be extracted.
extract: Extracts all files on the extraction list from the dump media.
help: Displays a summary of available commands.
ls [directory]: Lists files in directory (dump media) or the current directory, which is represented by a period (.).
pwd: Prints the full path name of the current working directory.
quit: Exits immediately.
verbose: Toggles the verbose flag (the program prints a line for every action it takes).
r: Restores the entire content of the media into the current directory.
x: Extracts the named files from the media.
b: Sets the restore blocking factor.
f [dump file]: Tells restore to use the dump file instead of /dev/rmt/0 as the file to restore from.
R: Resumes restore after volume is changed.
t: Prints table of contents for dump file.
n: Skips to the nth file when multiple dump files exist on the same tape.
v: Displays the name and inode number of each file restored.
i: Places restore in the interactive mode. Commands available in this mode follow.
add [filename]: Adds the named file or directory to the list of files to be extracted.
cd directory: Changes to directory on the dump media.
delete [filename]: Deletes the current directory or file from the list of files to be extracted.
extract: Extracts all files on the extraction list from the dump media.
help: Displays a summary of available commands.
ls [directory]: Lists files in directory (dump media) or the current directory, which is represented by a period (.).
pwd: Prints the full path name of the current working directory.
quit: Exits immediately.
verbose: Toggles the verbose flag (the program prints a line for every action it takes).
r: Restores the entire content of the media into the current directory.
x: Extracts the named files from the media.
b: Sets the restore blocking factor.
f [dump file]: Tells restore to use the dump file instead of /dev/rmt/0 as the file to restore from.
R: Resumes restore after volume is changed.
t: Prints table of contents for dump file.
n: Skips to the nth file when multiple dump files exist on the same tape.
v: Displays the name and inode number of each file restored.
TIP: A side effect of using restore is that it creates a “symbol table” file in the file system where the files are restored. This file is named restoresymtable. It is wise to remove this file because it is usually quite large. Once the restore is complete, remove the file by issuing the command rm ./restoresymtable.
WARNING: Failure to remove the restoresymtable file may come back to haunt you! If the restoresymtable is left on the disk and dumped to a full dump, it will overwrite the restoresymtable file created when you perform a restore. This will prevent proper restoration of any incremental dumps required to bring the system back into operation.
TIP: A side effect of using restore is that it creates a “symbol table” file in the file system where the files are restored. This file is named restoresymtable. It is wise to remove this file because it is usually quite large. Once the restore is complete, remove the file by issuing the command rm ./restoresymtable.
WARNING: Failure to remove the restoresymtable file may come back to haunt you! If the restoresymtable is left on the disk and dumped to a full dump, it will overwrite the restoresymtable file created when you perform a restore. This will prevent proper restoration of any incremental dumps required to bring the system back into operation.
TIP: A side effect of using restore is that it creates a “symbol table” file in the file system where the files are restored. This file is named restoresymtable. It is wise to remove this file because it is usually quite large. Once the restore is complete, remove the file by issuing the command rm ./restoresymtable.
WARNING: Failure to remove the restoresymtable file may come back to haunt you! If the restoresymtable is left on the disk and dumped to a full dump, it will overwrite the restoresymtable file created when you perform a restore. This will prevent proper restoration of any incremental dumps required to bring the system back into operation.
TIP: A side effect of using restore is that it creates a “symbol table” file in the file system where the files are restored. This file is named restoresymtable. It is wise to remove this file because it is usually quite large. Once the restore is complete, remove the file by issuing the command rm ./restoresymtable.
WARNING: Failure to remove the restoresymtable file may come back to haunt you! If the restoresymtable is left on the disk and dumped to a full dump, it will overwrite the restoresymtable file created when you perform a restore. This will prevent proper restoration of any incremental dumps required to bring the system back into operation.
cpio -i (copy in): Extracts files from the standard input, which is assumed to be the product of a previous cpio -o.
cpio -o (copy out): Reads the standard input to obtain a list of path names. The cpio command then copies those files to the standard output with path name and status information. Output is padded to a 512-byte boundary by default.
cpio -p (pass): Reads the standard input to obtain a list of path names of files that are conditionally created and copied into the destination directory tree.
TIP: Although it is possible to perform the last file system backup to the “rewind” tape device (/dev/st0), this often leads to errors when the backup script is modified. If all backups use the “no-rewind” tape device, and the rewind and off-line operations are explicit system calls, the likelihood of operator errors should be minimized.