7/19/2005 NT12.hsphere.cc

[byron]

File and folder permissions, and some other settings are currently being migrated back into the server's running directory structure. These changes can take hours to complete as scripts continue running in the background, but we should have the server back in full swing by sometime later this afternoon, Eastern time.

[cfrankland]

Two things I noticed about your backup/restore routine.

• By restoring the control panel first, the default index.html gets written to domain folders. If the tape then restores a default.aspx, the index.html continues to be served.
• I believe that the backups are skipping all 'logs' folders. I can understand skipping the customername\logs folders, but there's a domainname\_portals\logs folder that's essential to DNN's operation. I had about six sites down even after the restore.

Just observances.

Regards!

[admin]

• By restoring the control panel first, the default index.html gets written to domain folders. If the tape then restores a default.aspx, the index.html continues to be served.
  
  A: Thats not how we restore them. CP is creating all the sites and it creats the folders, users and such. We are pulling from the backup server and untar them. Then once the CP is done we rename hshome to hshome old and rename all the backup content thats in a holder called hshome.new to hshome. This way the index.html should not be there only your stuff.
  
  
• I believe that the backups are skipping all 'logs' folders. I can understand skipping the customername\logs folders, but there's a domainname\_portals\logs folder that's essential to DNN's operation. I had about six sites down even after the restore.
  
  A: We exclude everything *.log because of the huge amount of space it takes up. I was not aware DNN had or needed some kind of logs to run. Thats a first for me. I will see if we can narrow down the exlude for logs to just iis logs maybe.
  

[cfrankland]

Originally Posted by admin

This way the index.html should not be there only your stuff.

Hmmm, not the way it happened for one customer. No biggie, I fixed it. It must have been an exception of some kind.

Originally Posted by admin

I was not aware DNN had or needed some kind of logs to run.

Yeah it's kinda hokey. The \Portals\_default\Logs\ folder holds the log files such as exception.xml.resources (The .resources extension makes IIS not allow the download of the file, same as .config files), but the \Portals\_default\Logs\LogConfig\ holds the log configuration files such as LogConfig.xml.resources. These files are necessary for DNN v3.x and higher to run.

Anyway, the entire \Portals\default\Logs\ folder is missing after a restore.

[admin]

But the files don't end in .log do they? They end in .resources we only exlude .log files.

[cfrankland]

Originally Posted by admin

But the files don't end in .log do they? They end in .resources we only exclude .log files.

All the files end in .resources. However, the entire "logs" folder is missing, including all files and sub-folders. Perhaps you exclude folders named "logs"?

[admin]

Hmm, I will check I was almost 100% sure it was *.log not */log*