Backing up an individual CMS project can be achieved by running a project export from Server Manager. There is plenty of documentation on how to do that.
Backing up ALL your CMS projects can be achieved using a combination of file system and database backup techniques. Backing up a run-time environment is considerably harder and demands an intimate knowledge of the tools and technologies being used. Some important questions: - Windows / Linux / Mac? - IIS or Apache? - Databases? - File system? - Registry? - LiveServer / Delivery Server - ASP.NET? - Supporting utilities? e.g. Windows Services, SSIS packages, scripts, etc? Rgds, Richard H. On Aug 14, 7:08 am, Flapi <[email protected]> wrote: > If you use II 7.0 (Win 2008) you can try msdeploy.exe > (http://learn.iis.net/page.aspx/427/migrate-a-web-site-from-iis-60-to-...) > IIS 6.0 works for export, but not for reimporting. > You get one "zip" file with the configration of the Website, Files > (asp,aspx,...) and all Files, that are in virtual directories (also outside > from the "web-root"). Databases (MS-SQL) needs an extra backup. -- You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/reddot-cms-users?hl=en.
