Joshua,
I'll include a spec of RQL Heiko posted a while back (could be years?) to setup
a regular job to export your project.
I run this nightly on most of my projects. If you can pair it with a
compression so it gets zipped every night, and then ideally moved off your
server (manually or through FTP ideally) you've got a good backup script. This
will capture everything in your project, but not your assets that are stored in
folders, or your plugins or other customizations you've put together.
We often use these nightly backups to import to a testing server and prototype
large changes or new ideas.
---------------------------+
Yes, you are on the right track.
Create a user defined job, let it run every night (keep in mind: the
project is locked during export). Use your Admin-Login-Settings (or
any other with sufficient rights) and a RQL like this:
<IODATA loginguid="[!guid_login!]">
<ADMINISTRATION>
<PROJECT action="export" projectguid="----YOUR PROJCECT-GUID
HERE---" targetpath="E:\Backup\ProjectXY" emailnotification="0" to="---
USER-GUID IF EMAIL-NOTIOFICATION--" createfolderforeachexport="0"
includearchive="1" logoutusers="0" subject="Autoexport: Project XY"
message="Export started"/>
</ADMINISTRATION>
</IODATA>
if you set createfolderforeachexport="0" then the export should
overwrite your export-folder every time.
Heiko
---------------------------+
Thanks Heiko - and good luck Joshua.
.daveb
On 2010-01-23, at 6:53 AM , Joshua wrote:
>> Need some advice on project backups... we are currently backing up our
>> reddot project via SQL server daily backup. In the event of failure
>> would this be adequate to restore the project? Anyone got any
>> experience with this?
>
> There was Windows Scripting Host / VBScript program on the RedDot
> community site that iterated the list of projects and performed a
> RedDot export on each one. We have that running as a scheduled job on
> our RedDot server, the exports then are picked up by our regular
> backup software (Tivoli); it take a couple hours to export about 250
> projects each night.
>
> Having a project export provides a bit more flexibility than a
> straight database backup... we've had a few instances where we've
> wanted to restore project XYZ to the state it was yesterday; aside
> from unpleasant upgrade experiences, we've never encounter the need to
> restore our entire RedDot server to a previous state.
>
> --
> 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.
>
--
daveb
--
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.
