Skip to main content

Steps for restore from s3

  • March 28, 2019
  • 2 replies
  • 7 views

sarafumes
Forum|alt.badge.img+1

Hi, I am working on testing to see if the backups from s3 are able to restore to a new similar test cluster.

I am getting a permission denied error , how should i solve this? Is anyone able to successfully restore the backup.?

OSError: [Errno 13] Permission denied: '/vertica/data/.lock'

I am running the command as dbadmin user in centos machine

/opt/vertica/bin/vbr -t restore -c /opt/vertica/s3bak.ini

My config file:

[S3]
; This section replaces the [Mapping] section and is required to back up to S3

; !!Mandatory!! S3 bucket name(no default).
s3_backup_path = s3://prod/

; !!Mandatory!! directory used to manage locking during a backup (no default). If the directory is mounted on the initiator host, you should use "[]" instead of the local host name. The file system must support POSIX fcntl flock.
; s3_backup_file_system_path = []:/vertica/data/bi/vertica_backup/
;s3_backup_file_system_path = []:/vertica/data/bi/backup_locks_dir/
;s3_backup_file_system_path = []:/home/dbadmin/backup_locks_dir/
s3_backup_file_system_path = []:/vertica/data

; Specifies SSL encrypted transfer.
; s3_encrypt_transport = True

; Specifies the number of threads for upload/download - backup
; s3_concurrency_backup = 10

; Specifies the number of threads for upload/download - restore
; s3_concurrency_restore = 10

[Misc]
; !!Recommended!! Snapshot name
; Valid values: a-z A-Z 0-9 - _
snapshotName = backup_snapshot

[Transmission]
; !!Mandatory!! Identifies the backup as a hardlink style backup.
hardLinkLocal = True

[Database]
; !!Recommended!! If you have more than one database defined on this Vertica cluster, use this parameter to specify which database to backup/restore.
dbName = bi

; If this parameter is True, vbr prompts the user for the database password every time.
; If False, specify the location of password config file in 'passwordFile' parameter in [Misc] section.
dbPromptForPassword = False

; ------------------------------------------- ;
;;; ADVANCED PARAMETERS ;;;
; ------------------------------------------- ;

[Misc]
; The temp directory location on all database hosts.
; The directory must be readable and writeable by the dbadmin, and must implement POSIX style fcntl lockf locking.
; tempDir = /tmp/vbr

; Specifies the number of historical backups to retain in addition to the most recent backup.
; 1 current + n historical backups
restorePointLimit = 3
objectRestoreMode = createOrReplace

; Full path to the password configuration file
; Store this file in directory readable only by the dbadmin.
; (no default)
passwordFile = /home/dbadmin/pw.txt

2 replies

Afe
Forum|alt.badge.img
  • Participating Frequently
  • March 29, 2019

Hi @sarafumes,

It appears the dbadmin user does not have permissions to the location specified for file locking. Can you try specifying another path (perhaps a location under the dbadmin user's home dir or /tmp/)?

Also, since this is a different cluster from the initial cluster backup was taken you'll need to run the init task with --s3-force-init flag.
Refer to https://www.vertica.com/docs/9.2.x/HTML/Content/Authoring/AdministratorsGuide/BackupRestore/CreatingBackupsonAmazonS3.htm?tocpath=Administrator's Guide|Backing Up and Restoring the Database|_____7


sarafumes
Forum|alt.badge.img+1
  • Author
  • Participating Frequently
  • March 29, 2019

Thanks i figured it out,
I was able to successfully do a restore from s3 to a new cluster.

Would you be able to give some insight in this one, i was never able to solve it .
https://forum.vertica.com/discussion/239666/vertica-backups-failing-with-assertion-error#latest