Staging Disk Granularity (GB):定義為離線應用程式建立的暫存磁碟精細程度。當應用程式使用多個暫存磁碟時,此屬性會指定每個暫存磁碟的大小。有效的項目介於 1 到 128000 之間。例如:
如果應用程式為 4.3 TB,且「Stage Disk Granularity」值為 2 TB,而「Last Staging Disk Minimum Size」值為 1 TB,備份/還原機器就會建立三個暫存磁碟,分別為 2 T、2 T 和 1 T。
如果應用程式為 4.3 TB,且 Stage Disk Granularity 值為 2 TB,而 Last Staging Disk Minimum Size 值為 0.1 TB,備份/復原工具就會使用 2 T、2 T 和 0.3 T 的三個暫存磁碟。
如果應用程式為 4.3 TB,且 Stage Disk Granularity 值為 5 TB,而 Last Staging Disk Minimum Size 值為 1 TB,備份/復原工具就會建立一個 4.3 TB 的暫存磁碟。Stage Disk Granularity 和 Last Staging Disk Minimum Size 是在應用程式層級指定,並覆寫系統層級的預設值。
Linux 範例:/usr/local/lib 可確保系統不會複製 /usr/local/lib 後面的任何項目,但會複製 /usr/local 中的所有其他目錄和檔案。
Windows 範例:\\SERVERNAME\SHARENAME\abc 可確保不會複製 \\SERVERNAME\SHARENAME\abc 後面的任何項目,但會複製 \\SERVERNAME\SHARENAME 中的所有其他目錄和檔案。
如果這個欄位留空,目錄檢索作業會逐層進入要備份的起始路徑的每個子目錄。
服務存取點 IP 位址:如果檔案系統是叢集資源,且您希望無論哪個叢集節點代管檔案系統,都能夠備份檔案系統,請將叢集資源 IP 指定為服務存取點 IP。這樣一來,備份/復原設備就能使用叢集資源 IP 連線至備份和災難復原代理程式,並從有效的叢集節點備份檔案系統。為了讓備份功能在所有叢集節點上正常運作,您必須在所有叢集節點上安裝備份和災難復原代理程式。輸入叢集應用程式的虛擬 IP 位址。對於容錯移轉叢集,這項資訊可用於尋找備份的有效節點。對於主動/主動叢集,這會是逗號分隔的清單,列出可用於備份的合格伺服器。
使用服務 IP 進行還原作業:在還原叢集應用程式時,請遵循服務存取點 IP 位址。如果您要使用服務 IP 位址還原叢集應用程式,請選取「是」。如果不想使用服務 IP 位址進行還原,請選取「否」。
備份和災難復原代理人選項:除非您正在與支援團隊合作,否則請將備份和災難復原代理人選項留空。
建議為單一暫存磁碟使用 LVM:即使單一暫存磁碟已足以備份,也請建立 LVM。如要使用 LVM 的暫存磁碟,無論 Linux 來源磁碟的大小為何,您都可以選取「是」,這樣一來,您就能在不需要新的完整備份的情況下擴充磁碟。如果您不想使用擴充的 LVM 暫存磁碟,請選取「否」。
[[["容易理解","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 (世界標準時間)。"],[[["\u003cp\u003eApplication settings for file system backups can be modified on the \u003cstrong\u003eApplication Details & Settings\u003c/strong\u003e page, accessed via the \u003cstrong\u003eDetails & Settings\u003c/strong\u003e link within each application's backup plan.\u003c/p\u003e\n"],["\u003cp\u003eStaging disk settings allow you to define the size and granularity of staging disks, where the default uses the size of the managed file system unless otherwise configured.\u003c/p\u003e\n"],["\u003cp\u003eYou can specify \u003cstrong\u003eExclude Patterns\u003c/strong\u003e or \u003cstrong\u003eInclude Patterns\u003c/strong\u003e to selectively back up or exclude certain file types from backups using wildcard characters, allowing for focused data protection.\u003c/p\u003e\n"],["\u003cp\u003e\u003cstrong\u003eStart Paths\u003c/strong\u003e and \u003cstrong\u003ePrune Paths\u003c/strong\u003e define the scope of the backup, where \u003cstrong\u003eStart Paths\u003c/strong\u003e dictate the root directory for backups and \u003cstrong\u003ePrune Paths\u003c/strong\u003e limit the depth of directory traversal, so as to not copy beyond a certain point.\u003c/p\u003e\n"],["\u003cp\u003eFor clustered file systems, a \u003cstrong\u003eService Access Point IP Address\u003c/strong\u003e can be specified to ensure backups are taken from the active cluster node, with an option to \u003cstrong\u003eUse Service IP for Restore\u003c/strong\u003e during recovery.\u003c/p\u003e\n"]]],[],null,["# Configure application details and settings to protect file system data\n\nFrom the **Application Details \\& Settings** page---accessed from the\n**Details \\& Settings** link at the top of each application's backup\nplan---you can modify application-specific settings for backing up a file\nsystem.\nApplication settings may be useful or required in certain circumstances.\nAfter you configure your application settings, click **Save Changes**.\n| **Note:** To reset one or more application settings back to its default state, click the checkbox to the left of the selection you want to reset, or click **Select options that will revert back to default** to reset all application selections back to their default state.\n\nThe following is a list of the application settings and a description of what\nthey do.\n\n- **Username/Password**: If alternate credentials were specified when the network drive was mapped to the host, in the spaces provided, enter the file share username and password.\n- **Staging Disk Size (GB)**: Enter a value in gigabytes. Valid entries are one\n to 256000. By default, the Backup and DR agent uses the size of the managed file\n system as the size of the staging disk. This setting allows the administrator\n to override this value to allow for growth of the file system.\n\n- **Use Staging Disk Granularity as Minimum Staging Disk Size** : The default\n value is zero when you select **No** . If you select **Yes** , then you must\n enter a value in GB in the **Staging disk granularity** field.\n This setting is for applications that are less than the size of the\n granularity setting and tend to grow periodically. This setting helps\n avoid frequent and costly full backups. There is no initial cost to using\n a staging disk that is larger than required for immediate use because the\n staging disk is thin-provisioned.\n\n- **Staging Disk Granularity (GB)**: Defines the granularity of the staging\n disk created for an out-of-band application. It specifies the size of each\n staging disk when multiple staging disks are used for an application.\n Valid entries are one to 128000. For example, the following:\n\n - If an application is 4.3TB, and the **Stage Disk Granularity** value is 2TB and **Last Staging Disk Minimum Size** value is 1TB, the backup/recovery appliance creates three staging disks of 2T, 2T, and 1T.\n - If an application is 4.3TB, and the **Stage Disk Granularity** value is 2TB and **Last Staging Disk Minimum Size** value is 0.1TB, the backup/recovery appliance three staging disks of 2T, 2T, and 0.3T.\n - If an application is 4.3TB, and the **Stage Disk Granularity** value is 5TB and **Last Staging Disk Minimum Size** value is 1TB, the backup/recovery appliance creates one staging disk of 4.3T. **Stage Disk Granularity** and **Last Staging Disk Minimum Size** are specified at the application level and override the system-wide default values.\n- **Staging Disk Mount Point** : Enter a **Staging Disk Mount Point** if you\n need the staging disk mounted to a particular location.\n\n- **Exclude Patterns, Include Patterns** : Enter the filename pattern to be\n excluded from or included in backup. The backup/recovery appliance offers the\n ability to exclude or include certain file types. Using either the\n **Exclude Patterns** or **Include Patterns** option, only the most crucial data\n is backed-up leaving a side the non-critical files. The guidelines include the\n following:\n\n - Only files are excluded or included, this does not impact directories.\n - A pattern can include wildcard characters, for example, an asterisk (\\*) or a question mark (?). To exclude all the files that contains `.sys` as extension, enter `*.sys` in the **Exclude Pattern** or **Include Pattern** field.\n - On Windows, files named `pagefile.sys` and `hiberfil.sys` that appear in the root directory of a drive are automatically ignored.\n- **Start Paths** : Specifies the point in the file share where backup starts.\n If the **Start Path** field is left blank, backup starts at the root directory\n of 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\n on the file share.\n- **Prune Paths** : Provide the prune paths in the **Prune Paths** field. Prune\n path specifies a point in the file system where directory traversals stop.\n\n Linux example: `/usr/local/lib` ensures that nothing following\n `/usr/local/lib` is copied, but all other directories and files in\n `/usr/local` are copied.\n\n Windows example: `\\\\SERVERNAME\\SHARENAME\\abc` ensures that nothing\n following `\\\\SERVERNAME\\SHARENAME\\abc` is copied, but all other directories and\n files in `\\\\SERVERNAME\\SHARENAME` are copied.\n\n If this field is left blank, the directory traversal descends into every\n subdirectory of the start paths being backed up.\n- **Service Access Point IP Address**: If a file system is a cluster resource\n and if you want it to be backed up irrespective of which cluster node is\n hosting the file system, then specify the cluster resource IP as a service\n access point IP. This allows the backup/recovery appliance to connect to the\n Backup and DR agent using the cluster resource IP and to back up the\n file system from the active cluster node. For backup to work correctly\n across all cluster nodes, the Backup and DR agent must be installed on all\n cluster nodes.\n Enter a virtual IP address for a clustered application. For failover clusters,\n this is used to find the active node for a backup. For active/active clusters,\n this is a comma separated list of eligible servers that can be used for the\n backup.\n\n- **Use Service IP for Restore** : Honor the service access point IP address\n during restore for a clustered application. Select **Yes** if you want to use\n the service IP address for restoring a cluster application. Select **No** if\n you do not want to use the service IP address to restore.\n\n- **Backup and DR Agent Options**: Leave Backup and DR agent options blank\n unless you are working with support.\n\n- **Prefer LVM for Single Staging Disk** : Create an LVM even when a single\n staging disk is enough for backup. Select **Yes** if you want to use an LVM-based\n staging disk that can be expanded without requiring a new full backup,\n regardless of the size of the Linux source disk. Select **No** if you do not\n want to use an expanded LVM-based staging disk.\n\nBackup and DR Service for Filestore and 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/backupdr-for-filesystems)\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)"]]