From do-not-reply at jboss.org Wed Jan 26 13:20:21 2011 Content-Type: multipart/mixed; boundary="===============3292298073278089161==" MIME-Version: 1.0 From: do-not-reply at jboss.org To: exo-jcr-commits at lists.jboss.org Subject: [exo-jcr-commits] exo-jcr SVN: r3894 - jcr/trunk/exo.jcr.docs/exo.jcr.docs.developer/en/src/main/docbook/en-US/modules/jcr/backup. Date: Wed, 26 Jan 2011 13:20:21 -0500 Message-ID: <201101261820.p0QIKLto006571@svn01.web.mwc.hst.phx2.redhat.com> --===============3292298073278089161== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Author: tolusha Date: 2011-01-26 13:20:20 -0500 (Wed, 26 Jan 2011) New Revision: 3894 Modified: jcr/trunk/exo.jcr.docs/exo.jcr.docs.developer/en/src/main/docbook/en-US/= modules/jcr/backup/exojcr-backup-service.xml Log: EXOJCR-1100: RDBMS backup documentation Modified: jcr/trunk/exo.jcr.docs/exo.jcr.docs.developer/en/src/main/docbook= /en-US/modules/jcr/backup/exojcr-backup-service.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- jcr/trunk/exo.jcr.docs/exo.jcr.docs.developer/en/src/main/docbook/en-US= /modules/jcr/backup/exojcr-backup-service.xml 2011-01-26 16:25:31 UTC (rev = 3893) +++ jcr/trunk/exo.jcr.docs/exo.jcr.docs.developer/en/src/main/docbook/en-US= /modules/jcr/backup/exojcr-backup-service.xml 2011-01-26 18:20:20 UTC (rev = 3894) @@ -392,7 +392,7 @@ = Will be configured BackupWorkspaceInitializer in all configurations workspaces of the Repository to restore the Repository - from backup over initializer. + from backup over initializer. = = @@ -898,4 +898,55 @@ interactive operations via Backup API (e.g. console) and backup set fi= les for portability (e.g. on another server). + +
+ RDBMS backup + + RDBMS backup It is another implementation of full backup job for + BackupManager service. It is useful in case when database is used to s= tore + data. + + Brings such advantages: + + + + fast: backup takes only several minutes to perform full ba= ckup + of repository with 1 million rows in tables; + + + + atomic restore: restore process into existing + workspace/repository with same configuration is atomic, it means= you + don=E2=80=99t loose the data when restore failed, the original d= ata + remains; + + + + cluster aware: it is possible to make backup/restore in + cluster environment into existing workspace/repository with same + configuration; + + + + consistence backup: all threads make waiting until backup = is + finished and then continue to work, so, there are no data + modification during backup process; + + Configuration: + + <component> + <key>org.exoplatform.services.jcr.ext.backup.BackupManager</key= > + <type>org.exoplatform.services.jcr.ext.backup.impl.BackupManagerIm= pl</type> + <init-params> + <properties-param> + <name>backup-properties</name> + <property name=3D"default-incremental-job-period" value=3D"3600" = /> <!-- set default incremental period =3D 60 minutes --> + <property name=3D"full-backup-type" value=3D"org.exoplatform.serv= ices.jcr.ext.backup.impl.fs..rdbms.FullBackupJob" /> + <property name=3D"incremental-backup-type" value=3D"org.exoplatfo= rm.services.jcr.ext.backup.impl.fs.IncrementalBackupJob" /> + <property name=3D"backup-dir" value=3D"target/backup" /> + </properties-param> + </init-params> +</component> + +
--===============3292298073278089161==--