[[["์ดํดํ๊ธฐ ์ฌ์","easyToUnderstand","thumb-up"],["๋ฌธ์ ๊ฐ ํด๊ฒฐ๋จ","solvedMyProblem","thumb-up"],["๊ธฐํ","otherUp","thumb-up"]],[["์ดํดํ๊ธฐ ์ด๋ ค์","hardToUnderstand","thumb-down"],["์๋ชป๋ ์ ๋ณด ๋๋ ์ํ ์ฝ๋","incorrectInformationOrSampleCode","thumb-down"],["ํ์ํ ์ ๋ณด/์ํ์ด ์์","missingTheInformationSamplesINeed","thumb-down"],["๋ฒ์ญ ๋ฌธ์ ","translationIssue","thumb-down"],["๊ธฐํ","otherDown","thumb-down"]],["์ต์ข ์ ๋ฐ์ดํธ: 2025-09-04(UTC)"],[[["\u003cp\u003eBackup and DR Service facilitates the capture and management of data from SMB, NFS, and Filestore file systems, enabling the use of virtual copies for various business needs.\u003c/p\u003e\n"],["\u003cp\u003eWhen configuring a backup plan, users can employ Exclude Patterns and Include Patterns to specify which file types are backed up, ensuring only crucial data is stored, without impacting directories.\u003c/p\u003e\n"],["\u003cp\u003eStart Paths in the backup configuration determine the directory in the file share where the backup process begins, while leaving the field blank will initiate the backup at the root directory.\u003c/p\u003e\n"],["\u003cp\u003ePrune Paths are utilized to halt directory traversals at specific points in the file system during backup, allowing users to exclude certain subdirectories from being copied.\u003c/p\u003e\n"],["\u003cp\u003eThe backup process utilizes a method where only changed blocks are tracked, avoiding copy-on-writes and I/O-intensive operations, and includes a recovery process where files are restored from a mounted disk.\u003c/p\u003e\n"]]],[],null,["# Backup and DR Service for Filestore and file systems\n\nBackup and DR Service lets you capture data from production SMB, NFS, and\nFilestore file systems, manage it in the most efficient way possible,\nand use virtual copies of the data for business requirements like backup, test\nand development, analytics, and AI.\n\nWhen configuring a backup plan for a file system, you have the following\nsettings to help ensure that you get exactly what you need:\n\n- Exclude Patterns and Include Patterns: You can exclude or include certain\n file types. Using either the Exclude Patterns or Include Patterns option,\n only the most crucial data is backed-up. Only files are excluded or included,\n this does not impact directories. A pattern can include wildcard characters.\n On Windows, files named pagefile.sys and hiberfil.sys that appear in the root\n directory of a drive are automatically ignored.\n\n- Start Paths: Specifies the point in the file share where backup starts. If\n the Start Path field is left blank, backup starts at the root directory of\n the file system to be backed-up.\n\n - Linux example: `/usr/local` backs up the `/usr/local` directory.\n\n - Windows example: `\\\\SERVERNAME\\SHARENAME\\abc` backs up the abc directory on the file share.\n\n- Prune Paths: A prune path specifies a point in the file system where\n directory traversals stop. If this field is left blank, the directory\n traversal descends into every subdirectory of the start paths being backed up.\n\n - Linux example: `/usr/local/lib` ensures that nothing within `/usr/local/lib` is\n copied, but all other directories and files in `/usr/local` are copied.\n\n - Windows example: `\\\\SERVERNAME\\SHARENAME\\abc` ensures that nothing within\n `\\\\SERVERNAME\\SHARENAME\\abc` is copied, but all other directories and files\n in `\\\\SERVERNAME\\SHARENAME` are copied.\n\n- Service access point IP address: This allows the backup/recovery appliance\n to connect to the Backup and DR agent using the cluster resource IP and to\n back up the file system from the active cluster node.\n\nHow it works example: Backup and DR volume-based backup with Linux CBT\n----------------------------------------------------------------------\n\nOnly changed blocks are tracked in the bitmap, there are no copy-on-writes or\nI/O-intensive operations.\n\nThe following steps describe the process for how to perform data backup and\nrecovery with volume-based backup images and CBT:\n\n1. The Backup and DR agent has CBT to track changed blocks in the file system.\n\n2. The agent calls the OS API to freeze or pause file changes.\n\n3. Agent creates a LVM snapshot of the file system and synthesizes a bitmap.\n\n4. Agent API call to unfreeze the file system.\n\n5. Agent copies changed blocks to backup/recovery appliance, which then deletes\n the snapshot and catalogs the backup.\n\n6. The appliance issues an internal snapshot and synthesizes a point-in-time\n virtual full backup.\n\n7. For data recovery, Backup and DR instantly mounts a rewritable staging disk\n and brings the file system online.\n\nWhat's next\n-----------\n\n[Manage hosts and their connected applications](/backup-disaster-recovery/docs/configuration/manage-hosts-and-their-connected-applications)\n\nOther documentation for Backup and DR for file systems\n------------------------------------------------------\n\nThis page is one in a series of pages specific to protecting and recovering\nfilesystems with Backup and DR Service.\nYou can find additional information in the following pages:\n\n- [Backup and DR for file systems](/backup-disaster-recovery/docs/concepts/filesystem-intro)\n- [Manage hosts and their connected applications](/backup-disaster-recovery/docs/configuration/manage-hosts-and-their-connected-applications)\n- [Configure application details and settings to protect file system data](/backup-disaster-recovery/docs/backup/configure-app-settings-for-filesystems)\n- [Apply a backup plan to protect a file system](/backup-disaster-recovery/docs/create-plan/apply-backup-plan-to-filesystem)\n- [Restore a file system to the source](/backup-disaster-recovery/docs/access-data/filesystem-restore)\n- [Mount a file system or file share](/backup-disaster-recovery/docs/access-data/mount-file-system)\n- [Mount and migrate a file system for instant recovery to any target](/backup-disaster-recovery/docs/access-data/filesystem-mount-and-migrate)"]]
