"One or more directories do not support Granular Recovery Technology (GRT)" error occurs when attempting a backup of a Sharepoint Content database.

  • Modified Date:
  • Article ID:000084350


Granular Recovery Technology (GRT) backups of Sharepoint 2003, 2007 or 2010 content databases fail with an error message indicating that Granular Recovery Technology is not supported for the database or directory.

Error Message

V-79-57344-38724 - The job completed successfully. However, the following condition was encountered: one or more directories do not support Granular Recovery Technology (GRT). When attempting to do a GRT restore no selection is available under the content database.

The Backup Exec Engine log on the Media Server will report the following:

[7320] (mm/dd/yy) 08:31:53 [loops]              - PDI: Tape device mounted. Checking with FS whether PDI is supported
[7320] (mm/dd/yy) 08:31:53 [loops]              - PDI - Querying application server(SPSSERVER) for PDI support.
[7320] (mm/dd/yy) 08:31:53 [loops]              - Application server(SPSSERVER) does not support PDI
[7320] (mm/dd/yy) 08:31:53 [loops]              - Remote agent does not support PDI and returned error: 0xe0009744
[7320] (mm/dd/yy) 08:31:53 [loops]              - PDI processor not needed, performing traditional backup


Sharepoint Databases with table compression or TDE encryption are not supported with GRT.  When Backup Exec Agent for Sharepoint Servers scans a database, it determines if the database has encryption or compression enabled, and disables GRT support within the backup engine for the resource.

Certain third-party Sharepoint Service Applications in Sharepoint 2010 are known to compress the SQL tables associated with the application.


To determine if a content databases has compression or encryption enabled, perform the following steps to execute a SQL query against the SQL instance in which the Content Database resides:

1. Start SQL Management Studio.
2. Connect to the SQL instance that contains the content database returning the error previously mentioned.
3. Expand "Databases" and right click on the content database returning the error, then click "New Query".
4. Enter the one or both of the following queries within the query box, typically "SQLQuery1.SQL.username", where "WSS_Content" should be replaced by the name of the content database you wish to query for the presence of compressed tables.


SELECT DB_NAME(database_id), Encryption_State FROM sys.dm_database_encryption_keys


SELECT COUNT(*) FROM WSS_Content.sys.partitions WHERE data_compression > 0

5. Check the output of the SQL query:

  • If the Encryption Query returns a database name and Encryption State, then encryption is enabled on a database.  Confirm that this is not the content database selected for GRT.  If the content database shows encryption, GRT will not be supported until the encryption is removed.
  • If the Compression Query returns a value other then 0, then one of the tables in the database is compressed and GRT will not be supported until the compression is removed.

For assistance removing encryption or compression, please contact the Database Administrator.

Terms of use for this information are found in Legal Notices.



Did this article answer your question or resolve your issue?


Did this article save you the trouble of contacting technical support?


How can we make this article more helpful?

Email Address (Optional)