Hi folks,
Interesting scenario I am faced with and I need your expertise/suggestions on how to best solve it.
I backup all my web applications on a daily basis using the STSADM tool. Some web apps are less than 1GB, but one in particular is 7GB.
I was able to restore the ~1GB web apps without any issues in the past. However, this time the ~7GB web app needed to be restored to recover a document library.
On my first attempt, I got the "The site collection could not be restored. Please make sure the content databases are available and have sufficient free space." error message.
So, I added an additional 20GB virtual disk to my WSS server and set the TEMP system environment variables to point to that disk.
I learned WSS creates a folder called WebTempDir under the TEMP folder where the backup file gets deflated.
Tried again and it failed since the last restore was incomplete/corrupted. So, I run the "stsadm -o databaserepair -url <web-url> -databasename <content-db> -deletecorruption" command to repair the content database.
Tried once again and this time it run for almost 60 minutes... I could see the WebTempDir folder getting huge with the deflated data from the backup file. Suddenly, the STSADM gave me the "One or more files in the restored site collection will exceed the maximum supported path length. Please select a shorter destination site address and try again." error message.
In fact, some items from the to-be-restored backup file do exceed the URL 260 character limit imposed by WSS. I run the SQL script below and it gave me the list of items exceeding the 260 limit.
SELECT
LEN(' + DirName + '/' + LeafName) AS TotalChars,
' + DirName + '/' + LeafName AS FullUrl
FROM Docs WITH (NOLOCK)
ORDER BY TotalChars DESC
It is really disappointing that after deflating all the backup file, this URL-length constraint cancels/rolls back the whole operation
It seems since the backup file has these really long URL items, I cannot use this backup file to perform any restore.
H ow do I go around it to be able to restore the web app?
Your support is highly appreciated.
Thanks,
...Alex
Interesting scenario I am faced with and I need your expertise/suggestions on how to best solve it.
I backup all my web applications on a daily basis using the STSADM tool. Some web apps are less than 1GB, but one in particular is 7GB.
I was able to restore the ~1GB web apps without any issues in the past. However, this time the ~7GB web app needed to be restored to recover a document library.
On my first attempt, I got the "The site collection could not be restored. Please make sure the content databases are available and have sufficient free space." error message.
So, I added an additional 20GB virtual disk to my WSS server and set the TEMP system environment variables to point to that disk.
I learned WSS creates a folder called WebTempDir under the TEMP folder where the backup file gets deflated.
Tried again and it failed since the last restore was incomplete/corrupted. So, I run the "stsadm -o databaserepair -url <web-url> -databasename <content-db> -deletecorruption" command to repair the content database.
Tried once again and this time it run for almost 60 minutes... I could see the WebTempDir folder getting huge with the deflated data from the backup file. Suddenly, the STSADM gave me the "One or more files in the restored site collection will exceed the maximum supported path length. Please select a shorter destination site address and try again." error message.
In fact, some items from the to-be-restored backup file do exceed the URL 260 character limit imposed by WSS. I run the SQL script below and it gave me the list of items exceeding the 260 limit.
SELECT
LEN(' + DirName + '/' + LeafName) AS TotalChars,
' + DirName + '/' + LeafName AS FullUrl
FROM Docs WITH (NOLOCK)
ORDER BY TotalChars DESC
It is really disappointing that after deflating all the backup file, this URL-length constraint cancels/rolls back the whole operation
It seems since the backup file has these really long URL items, I cannot use this backup file to perform any restore.
H ow do I go around it to be able to restore the web app?
Your support is highly appreciated.
Thanks,
...Alex