Corruption checking during backup

1. A method comprising:

receiving a backup command at a storage server, the backup command requesting that the storage server perform a backup operation on a storage component; and

performing corruption checking over the storage component as part of the backup operation in response to the backup command,

wherein the corruption checking comprises, in the storage server,

initial scanning of the storage component for corruption,

identifying one or more corrupted files of a file system of the storage server on the storage component by utilizing a plurality of corruption tests, each of which tests for a different type of error, and

determining whether corruption in the one or more corrupted files is fatal or non-fatal, and

the backup operation comprises

copying uncorrupted files from the storage component to a backup facility and skipping the one or more corrupted files with non-fatal corruption.

2. The method of claim 1 , wherein the storage server comprises a file server.

3. The method of claim 1 , wherein the storage component comprises a volume.

4. The method of claim 1 , wherein the storage component comprises a virtual file system (“VFS”).

5. The method of claim 1 , further comprising:

aborting the backup operation when the corruption checking detects a fatal error.

6. The method of claim 1 , further comprising:

skipping the one or more corrupted files and continuing the backup operation.

7. The method of claim 1 , wherein the backup operation is an NDMP based backup operation.

8. A storage server comprising:

a storage adapter through which to communicate with a storage subsystem that includes a plurality of storage components;

a network adapter through which to receive data access requests from a storage client; and

a processor configured to control the storage server so as to cause the storage server to perform corruption checking over a target storage component as part of a backup operation performed in response to the storage server receiving a backup command, wherein the corruption checking comprises

identifying one or more corrupted files of a file system of the storage server on the target storage component by utilizing a plurality of corruption tests, each of which tests for a different type of error,

determining whether corruption in the one or more corrupted files is fatal or non-fatal, and

aborting the backup operation when the corruption checking detects a fatal error, but when the corruption checking detects only one or more non-fatal errors, then copying uncorrupted files from the storage component to a backup facility and skipping any corrupted files with non-fatal corruption.

9. The storage server of claim 8 , wherein the processor is further configured to alert a user about the fatal error.

10. The storage server of claim 8 , wherein the storage server comprises a file server.

11. The storage server of claim 8 , wherein each of the plurality of storage components comprises a volume.

12. The storage server of claim 8 , wherein each of the plurality of storage components comprises a virtual file system (“VFS”).

13. The storage server of claim 8 , wherein the corruption checking further comprises, prior to said identifying one or more corrupted files:

initial scanning of an inode file of the target storage component.

14. A method comprising:

receiving a backup command at a storage server, the backup command requesting that the storage server perform a backup operation on a storage component;

scanning a set of inodes associated with the storage component to determine a subset of inodes corresponding to files to be backed up;

identifying one or more corrupted files of a file system of the storage server during the scanning of the set of inodes, wherein a plurality of corruption tests are utilized for identifying the one or more corrupted files, wherein each of the plurality of corruption tests is for detecting a different type of error; and

determining whether corruption in the one or more corrupted files is fatal or non-fatal.

15. The method of claim 14 , further comprising performing the backup operation by skipping the one or more corrupted files and continuing the backup operation.

16. The method of claim 15 , further comprising generating a message to a user identifying the one or more corrupted files.

17. The method of claim 14 , further comprising identifying whether one of the subset of inodes or its corresponding file is corrupted.

18. The method of claim 17 , wherein performing the backup operation further comprises copying the subset of inodes and corresponding files to digital tape.

19. The method of claim 14 , wherein the storage server comprises a file server.

20. The method of claim 14 , wherein the storage component comprises a volume.

21. The method of claim 14 , wherein the storage component comprises a virtual file system (“VFS”).

22. The method of claim 14 , wherein the backup command comprises an NDMP_START_BACKUP command.

23. The method of claim 14 , wherein the backup operation is an NDMP based backup operation.

24. A method comprising:

receiving a backup command at a storage server, the backup command requesting that the storage server perform an NDMP based backup operation on a storage component; and

in response to the backup command,

scanning a set of inodes associated with the storage component to determine a subset of inodes corresponding to files to be backed up;

identifying one or more corrupted files during the scanning of the set of inodes; and

determining whether the one or more corrupted files warrant aborting the backup operation.

25. The method of claim 24 , wherein the backup command comprises an NDMP_START_BACKUP command.

26. The method of claim 24 , wherein said identifying one or more corrupted files comprises utilizing a plurality of corruption tests, each of which tests for a different type of error.