Situations can arise where you must back up Data Repository. For example, back up Data Repository before you upgrade Data Aggregator or before you set up automatic backups through a cron job. Backing up Data Repository gives you a copy of Data Repository to access in case there is an unexpected failure.
Important! The first time you back up Data Repository, a full backup is done. This full backup can take a considerable amount of time to complete, and depends on the amount of historical data that exists. Once an initial backup has been performed, subsequent scheduled backups will be incremental. In the case of a daily backup, an incremental backup will have to account for database activity that has occurred within the last 24 hours only (for example, amount of time that has passed since the last backup).
To perform an incremental backup after a full backup has been performed, provide the Vertica backup script with the same snapshotName and the same backup directory that you provided when you performed the full backup. If you change these names, a full backup is performed.
Vertica (the database) creates data files to store data. These files are never modified after they are created; new files are created and old ones are deleted. This approach allows you to use the standard rsync utility that supports fast file replication to another computer to back up Data Repository. For more information about rsync, see http://everythinglinux.org/rsync/.
To set up automatic backups of Data Repository, follow these steps:
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|