# FAQs for Archiving

## If I restore stubs to a volume with a different block size, what size will the restored stubs consume?

When you restore stubs to a volume with a different block size, say 512B, the disk size of the stub remains 0 for local archiving which is the same as that of the standard volume. However, the reparse stream will occupy 512B.

## Will my files get archived on an unsupported kernel version?

Archiving works on an unsupported kernel version from Feature Release 11.20 onwards only when the "archive-delete" post archiving rule is configured and the additional setting DoNotUseArchiverDriver is added to the client computer.

## Will my system files get archived if I back up my root volume?

No, backing up your root volume will not archive the system files. During backup of your entire client machine, system files are automatically excluded.

## Can I backup and archive files with path length greater than 1024 bytes?

Files with path length greater than 1024 bytes can only be backed up; archiving is not supported.

## Why am I not able to archive 0 KB files?

Files that are smaller than the file-system block size do not get archived when you select the Replace the File with a Stub option on the Disk Cleanup tab from the subclient properties. However, when you select the Delete the file option, the files that are smaller than the file-system block size, including the 0 KB files, are deleted from the disk if the files match the disk cleanup rules specified and have been backed up.

## Can I stub files pointed by symbolic links by specifying them as subclient content?

No. When a symbolic link pointing to a file is specified as subclient content, the file itself is not stubbed.

## Does changing a domain name of the CommServe Server/MediaAgent/client affect the stub recalls? Does an ACL change trigger recalls automatically?

Changing the domain name of the CommServe server, MediaAgent, or the client computer as mentioned in Changing the Domain Name for Clients and CommServe Computer does not affect the stub archive and recall operations.

If the ACLs of a top-level directory are changed, then the properties are inherited by the files and folders in that directory, but stubs are not automatically recalled. The stubs and the changed ACLs are included in the next incremental backup. The changed ACL will be available when you perform a stub recall.

## Which options are not supported with the Use native snapshot to preserve file access time option?

The following options and functions are not supported when you select the Use native snapshot to preserve file access time option:

- Subclient Properties > Content tab

  Expand symbolic links of subclient content

- Archiving for the default subclient.

- NFS archiving.

- If global wildcards are specified in subclient content, wildcards will not be applied for nested mount points.

  For example, /mnt1/**/*.doc will back up *.doc files on /mnt1, and *.doc files on a nested mount point, /mt1/mnt2, will not be backed up.

- Optimized Scan if the Optimized Scan database is located on a different mount point other than the source volume.

## How can I recall stubs if encryption via pass-phrase is enabled at the client level?

If encryption via pass-phrase is enabled at the client level, follow the steps given below prior to running a stub recall:

1. From the CommCell Console, right-click the <Client> and click Properties.

2. Click Advanced and then click the Encryption tab.

3. Click Export to export the pass-phrase to the client.

4. Enter the pass-phrase and click Export.

5. Click OK.

## Is Distributed File System Replication (DFSR) service compatible with stub recall?

Distributed File System Replication (DFSR) is not compatible with stub recalls. This is due to a Microsoft known issue.

For more information, see Microsoft article DFSR Reparse Point Support.

Contact Microsoft if you still experience issues related to archiving or stub recall.

## Will Start Over Operations Result In Full Backups?

Start over operations on storage policies do not automatically convert the next archive operation to a full backup job for archive subclients.

## Are symbolic link paths followed for archiving operations?

A symbolic link can be added as subclient content and archived. However, a symbolic link present in the subclient content path is not followed and the files under the path are not archived (stubbing or deleting).

## Extended Attributes (EA) Handling by Local Archiver

To enable EA handling by the local archiver, use the additional setting WinFsDataMigrator\bArchiveEAFiles with the value set to 1.

With the Delete option set for archiving:

- Restoring archived files with kernel-level EA will bring back the EA. However, these EA will not be applied to the restored files.

- Restoring archived files with user-level EA will bring back the EA and also apply them to the restored files.

With the Stub option set for archiving:

- Restoring archived files with kernel-level EA will bring back the EA. However, these EA will not be applied to the restored files.

- Restoring archived files with user-level EA will bring back the EA and apply them to the restored files.

- For the Stub option, recall of EA is currently not supported.

## How to archive excluded file extensions such as *.dll, *.bat, *.exe, *.cur, *.ico, *.lnk ?

To archive file extensions that are excluded by default, enable the following additional settings:

- NAS: GXHSM_ARCHIVE_EXCLUDEDEXTENSIONS_FOR_NASONEPASS

- Local File System: GXHSM_ARCHIVE_EXCLUDEDEXTENSIONS_FOR_LOCALONEPASS

## Why do recalls fail after changing the username or the password account configured on the NetApp FPolicy filer?

When the password for the user account configured on the NetApp FPolicy filer is changed, the credentials must be manually updated across all subclients within every backup set linked to the client. The recall process may randomly select a subclient and attempt to authenticate using its stored credentials. If the credentials are outdated or invalid, the recalls fail.

## What should I do if file archiving is causing degraded I/O performance?

Starting with Commvault Long-Term Support Release 11.40, Commvault file archiving uses the Linux fanotify service to provide seamless access to stubs when files are archived with stubbing. In previous versions, Commvault services used a Commvault-developed file system filter driver. If you notice degraded I/O performance, set the additional setting nUseFAN to 0 to revert back to using the Commvault file system filter driver.

## How do I disable file system monitoring when switching from stub archiving to delete archiving?

If you used archive with stub and later changed to archive with delete, and you notice that file system monitoring by Commvault services is causing I/O issues, use the DisableFileSystemMonitoring additional setting to disable the monitoring.

×

Loading...