Diferencia entre revisiones de «Respaldo de curso automatizado»

De MoodleDocs
m (tidy up)
(updated as per English 3.4)
 
(No se muestran 12 ediciones intermedias del mismo usuario)
Línea 1: Línea 1:
{{Versiones|Esta página es acerca del '''Respaldo de curso automatizado''' para Moodle 3.0 y más recientes. Para la documentación anterior, vaya a '''[[29/Respaldo de curso automatizado]]'''}}
{{Respaldo}}
{{Respaldo}}
{{Notadeltraductor|La frase inglesa [https://docs.moodle.org/26/en/Backup backup] se tradujo como '''Copia de seguridad''' en el [[Español internacional]] y como '''[[Respaldo]]''' en el [[Español de México]].}}
==Automatización de respaldos de curso==
{{Pendiente de traducir}}
{{Pendiente de traducir}}
'''Nota del traductor:''' La frase inglesa [https://docs.moodle.org/26/en/Backup backup] se tradujo como [[Copia de seguridad]] en el [[Español internacional]] y como '''respaldo''' en el [[Español de México]].
Automated course backups runs the same functions as individual [[Respaldo de curso|respaldos de curso]]. It's a good idea to schedule backups for when your server isn't usually busy. Running the backup tool over all the courses can be processor-intensive, so you shouldn't run it when there are a lot of students trying to access the server. You should always alert users with an announcement on the first page that if they log on during the backup hours they may notice a decrease in performance.


Un administrador del sitio puede configurar una agenda para respaldos (copias de seguridad) de curso automatizados en ''Configuraciones > Administración del sitio > > Cursos > Respaldos > Configuración de respaldo automatizado''.
In order to make scheduled backups, you have to set up CRON to run periodically. Please refer to the [[Cron|cron instructions]].


Los respaldos automatizados de curso corren la misma función que los [[Respaldo del curso|Respaldos del curso]] individuales. Es una buena idea el agendar los respaldos para cuando su servidor no esté demasiado ocupado. El correr la herramienta de respaldo sobre todos los cursos puede ser muy intensivo para el procesador, por lo que Usted no debería de correrla cuando haya muchos estudiantes tratando de acceder al servidor. Siempre debería de alertar a los usuarios con un anuncio en la portada del sitio que en caso de que ingresen al sitio durante las horas del respaldo, podrán notar una disminución en el desempeño.
==Configurar una agenda para respaldo de curso automatizado==


Para hacer respaldos agendados, Usted debe de configurar que [[Cron]] corra periodicamente. Por favor refiérase a las [[Cron|Instrucciones de cron]].
To set the backup schedule:
 
#Go to ''Administration > Site administration > Courses > Backups > Automated backup setup''.
==Configurar una agenda para respaldo de curso automatizado==
{{Nuevas características de Moodle 2.4}}
Para configurar la agenda de respaldo:
#Go to ''Settings > Site administration > > Courses > Backups > Automated backup setup''.
#Set backup_auto_active to enabled.
#Set backup_auto_active to enabled.
#Select the days of the week to run the backup.
#Select the days of the week to run the backup.
#Set the execution time for the backup process. For most servers, early morning will be the best time.  Keep in mind the time zone your server is using.
#Set the execution time for the backup process. For most servers, early morning will be the best time.  Keep in mind the time zone your server is using.
#Set the "Save to..." path. If you can, choose a backup path on another machine or on a different drive than the one Moodle is on. You don’t want to lose your backups at the same time you lose your Moodle site if the drive fails. If you leave the field blank, then backup zip files will be saved in the backup folder of each course files folder. On a Linux server the path might look like: /home/(your user or domain)/public_html/archive/ or if it's below the publicly accessible folders: /home/(your user or domain)/archive/ if the path is not recognized a red X is shown after saving, otherwise a green check.
#Set the "Save to..." path. If you can, choose a backup path on another machine or on a different drive than the one Moodle is on. You don’t want to lose your backups at the same time you lose your Moodle site if the drive fails. If you leave the field blank, then backup zip files will be saved in the backup folder of each course files folder. On a Linux server the path might look like: /home/(your user or domain)/public_html/archive/ or if it's below the publicly accessible folders: /home/(your user or domain)/archive/ if the path is not recognized a red X is shown after saving, otherwise a green check.
#Choose whether to skip the backup of hidden courses or courses which have not been modified within a specified number of days, or not modified since the last backup (new settings in Moodle 2.4 onwards).
#Set all other options appropriately.  
#Click the "Save changes" button.
#Click the "Save changes" button.


Once you've set up your backup schedule, Moodle will automatically create archives of all the courses on the server at the time you specified. Once the backup is complete, Moodle will send you an email describing the status of the backup.
{{Nuevas características de Moodle 3.0}}'''Sugerencia''': Para ahorrar espacio de disco, Usted puede elegir eliminar respaldos más antiguos que un número especificado de días. Si lo hace así, Usted también puede especificar un número mínimo de respaldos a conservar. (Las configuraciones ' Eliminar respaldos más antiguos que ' y 'Número mínimo de respaldos conservados' son nuevas a partir de Moodle 3.0 en adelante.)
 
===Use nombres de curso para sus respaldos===


By default, the backups will be named according to the course ID, which is not always easily recognisable. Check the box ''Use course name in backup filename'' in ''Settings > Site Administration > Courses > Backups > Automated backup setup'' to have them saved with the course shortname instead.
Una vez que Usted haya configurado su agenda de respaldar, Moodle creará automáticamente archivos de todos los cursos en el servidor al momento que Usted especificó. Una vez que el respaldo esté completo, Moodle le enviará a Usted un Email que describa el estatus del respaldo.


==Reporte de Respaldos==
==Reporte de respaldos==


A last execution log of scheduled course backups can be found in ''Settings > Site administration > Reports > Backups''. It displays a list of all course backups made, the time taken to create them, their status (see below), and the next scheduled automated backup execution time.
A last execution log of scheduled course backups can be found in ''Administration > Site administration > Reports > Backups''. It displays a list of all course backups made, the time taken to create them, their status (see below), and the next scheduled automated backup execution time.


Clicking on a particular course name will cause a detailed execution log to be displayed, including date, hour and minute when each step of the backup was performed.  
Clicking the 'View logs' icon next to the course name (1 in screenshot below) will display a detailed backup log for a particular course, including date, hour and minute when each step of the backup was performed (2). This log is useful for troubleshooting backup errors.


[[Image:Reports_Site_Backups_1.jpg]]
[[File:backuplogs.png|thumb|500px|center|]]


===Status del Respaldo===
===Backup status===


*'''OK''' - El respaldo del curso fue completado exitosamente.
*'''OK''' - The course backup was successfully completed.
*'''Skipped''' - The course was skipped (not backed up) because the course was unavailable to students and had not been changed in the last 31 days. This is not an error, but a feature designed to save process time.
*'''Skipped''' - The course was skipped (not backed up) because the course was unavailable to students and had not been changed in the last 31 days. This is not an error, but a feature designed to save process time.
*'''Unfinished''' - The backup was not finished. This might have happened because the job to execute backups ran out of time or resources (e.g., the cron running the backups ran out of time before finishing all the courses waiting). The unfinished jobs should be completed when the next scheduled backups are repeated.  
*'''Unfinished''' - The backup was not finished. This might have happened because the job to execute backups ran out of time or resources (e.g., the cron running the backups ran out of time before finishing all the courses waiting). The unfinished jobs should be completed when the next scheduled backups are repeated.  
*'''Error''' - There were errors in the backup process for the course, so a backup was not completed. For additional details about the error (1) check the backup log for the affected course (i.e., click the course name in the backups log), or (2) back up the course manually with debugging turned on to see what error message is displayed.
*'''Error''' - There were errors in the backup process for the course, so a backup was not completed. For additional details about the error (1) check the backup log for the affected course (i.e. click the 'View logs' icon next to the course name) or (2) back up the course manually with debugging turned on to see what error message is displayed.


==Respaldos de curso contra respaldos del sitio==
==Course versus site backups==


* Los respaldos de curso automatizados son más costosos en términos de tiempo y uso del CPU. El tiempo de recuperación para volver atener su sitio corriendo es más largo..  
*Automated course backups are more expensive in terms of time and CPU usage. The recovery time to have your site running again is longer.  
* Los respaldos de curso son útiles para obtener copias "frescas" de cursos que serán re-utilizados o distribuidos en forma individual; sin embargo, nunca deben de usarse como el sistema de respaldo primario (a menos que el sitio donde está alojado no le permita los [[Respaldo del sitio|respaldos del sitio]] que son preferibles).  
*Course backups are useful for obtaining "fresh" copies of courses to be re-used or distributed individually, however they should never be used as a primary backup system (unless your hosting doesn't allow the preferred [[Respaldo del sitio|respaldos del sitio]]).  


==Vea también==
==Capacidades==


* MDL-30725 Automated backups with external storage fill trashdir


Using Moodle forum discussions:
Ambas, la capacidad [[Capabilities/moodle/backup:downloadfile|download course backup files]] y la capacidad [[Capabilities/moodle/restore:userinfo|restore user data from a course backup]] son necesarias para poder descargar respaldos automatizados del curso. También hay una capacidad para  [[Capabilities/moodle/restore:viewautomatedfilearea|restore courses from the automated backup storage ]].
*[http://moodle.org/mod/forum/discuss.php?d=167471 Where is the Moodle 2.0 "Course Backup Filearea"?]
*[http://moodle.org/mod/forum/discuss.php?d=191275 the story of the mysteriously filling up hard disk]


[[Category:Reporte]]
[[Category:Reporte]]
[[Category:Administración del sitio]]
[[Category:Administración del sitio]]


[[en:Autamated course backup]]
[[en:Automated course backup]]
[[eu:Ikastaroen_segurtasun-kopia_automatikoa]]
[[eu:Ikastaroen_segurtasun-kopia_automatikoa]]
[[fr:Sauvegarde (administrateur)]]
[[fr:Sauvegarde (administrateur)]]
[[ja:自動コースバックアップ]]
[[ja:自動コースバックアップ]]
[[de:Automatische Kurssicherung]]
[[de:Automatische Kurssicherung]]

Revisión actual - 20:31 4 feb 2018

note icon.png Existe documentación diferente para varias versiones de Moodle: Esta página es acerca del Respaldo de curso automatizado para Moodle 3.0 y más recientes. Para la documentación anterior, vaya a 29/Respaldo de curso automatizado


translator note icon.png Nota del traductor: La frase inglesa backup se tradujo como Copia de seguridad en el Español internacional y como Respaldo en el Español de México.


Automatización de respaldos de curso

Nota: Pendiente de Traducir. ¡Anímese a traducir esta página!.     ( y otras páginas pendientes)

Automated course backups runs the same functions as individual respaldos de curso. It's a good idea to schedule backups for when your server isn't usually busy. Running the backup tool over all the courses can be processor-intensive, so you shouldn't run it when there are a lot of students trying to access the server. You should always alert users with an announcement on the first page that if they log on during the backup hours they may notice a decrease in performance.

In order to make scheduled backups, you have to set up CRON to run periodically. Please refer to the cron instructions.

Configurar una agenda para respaldo de curso automatizado

To set the backup schedule:

  1. Go to Administration > Site administration > Courses > Backups > Automated backup setup.
  2. Set backup_auto_active to enabled.
  3. Select the days of the week to run the backup.
  4. Set the execution time for the backup process. For most servers, early morning will be the best time. Keep in mind the time zone your server is using.
  5. Set the "Save to..." path. If you can, choose a backup path on another machine or on a different drive than the one Moodle is on. You don’t want to lose your backups at the same time you lose your Moodle site if the drive fails. If you leave the field blank, then backup zip files will be saved in the backup folder of each course files folder. On a Linux server the path might look like: /home/(your user or domain)/public_html/archive/ or if it's below the publicly accessible folders: /home/(your user or domain)/archive/ if the path is not recognized a red X is shown after saving, otherwise a green check.
  6. Set all other options appropriately.
  7. Click the "Save changes" button.

¡Nueva característica
en Moodle 3.0!
Sugerencia: Para ahorrar espacio de disco, Usted puede elegir eliminar respaldos más antiguos que un número especificado de días. Si lo hace así, Usted también puede especificar un número mínimo de respaldos a conservar. (Las configuraciones ' Eliminar respaldos más antiguos que ' y 'Número mínimo de respaldos conservados' son nuevas a partir de Moodle 3.0 en adelante.)

Una vez que Usted haya configurado su agenda de respaldar, Moodle creará automáticamente archivos de todos los cursos en el servidor al momento que Usted especificó. Una vez que el respaldo esté completo, Moodle le enviará a Usted un Email que describa el estatus del respaldo.

Reporte de respaldos

A last execution log of scheduled course backups can be found in Administration > Site administration > Reports > Backups. It displays a list of all course backups made, the time taken to create them, their status (see below), and the next scheduled automated backup execution time.

Clicking the 'View logs' icon next to the course name (1 in screenshot below) will display a detailed backup log for a particular course, including date, hour and minute when each step of the backup was performed (2). This log is useful for troubleshooting backup errors.

backuplogs.png

Backup status

  • OK - The course backup was successfully completed.
  • Skipped - The course was skipped (not backed up) because the course was unavailable to students and had not been changed in the last 31 days. This is not an error, but a feature designed to save process time.
  • Unfinished - The backup was not finished. This might have happened because the job to execute backups ran out of time or resources (e.g., the cron running the backups ran out of time before finishing all the courses waiting). The unfinished jobs should be completed when the next scheduled backups are repeated.
  • Error - There were errors in the backup process for the course, so a backup was not completed. For additional details about the error (1) check the backup log for the affected course (i.e. click the 'View logs' icon next to the course name) or (2) back up the course manually with debugging turned on to see what error message is displayed.

Course versus site backups

  • Automated course backups are more expensive in terms of time and CPU usage. The recovery time to have your site running again is longer.
  • Course backups are useful for obtaining "fresh" copies of courses to be re-used or distributed individually, however they should never be used as a primary backup system (unless your hosting doesn't allow the preferred respaldos del sitio).

Capacidades

Ambas, la capacidad download course backup files y la capacidad restore user data from a course backup son necesarias para poder descargar respaldos automatizados del curso. También hay una capacidad para restore courses from the automated backup storage .