Michael Halsey
Dev Ops Engineer - intechnologyWiFi
[email protected]
Direct 01423 510650
Mobile 07467 145626
Head Office 01423 510510





Hi All,


I’m having issues using the engine-backup command.


When running:


engine-backup --mode=backup --scope=files —file=veng.bak --log backup.log

Please try '--log=backup.log' (with '=').

That was unfortunately only a typo in the email. And not when running the 
actual command.

You have an EM DASH (U+2014) instead of two HYPHEN-MINUS (U+002D) in front of 
'file='.

I suspect that my Outlook client for Mac has done that.

Where did you copy that command from?

From my command line.
I have attached the command including the entire output in plaintext.





I get back the following error:


readlink: missing operand

Try 'readlink --help' for more information.

/usr/bin/engine-backup: line 1405: : No such file or directory

Notifying engine

/usr/bin/engine-backup: line 1472: : No such file or directory

/usr/bin/engine-backup: line 1405: : No such file or directory

FATAL: Failed notifying engine


Log file is not created.

I receive similar errors when changing the scope to ‘all' and ‘db'.


I’m running:


CentOS Linux release 7.2.1511 (Core)

oVirt Engine Version: 3.6.2.6-1.el7.centos

Engine is running on bare metal.


I have tried this with SELinux in Permissive mode. No difference.

All packages are up to date.


Can anyone advise a fix for this or if I’m doing anything wrong?


Thanks in advance,




Michael Halsey
Dev Ops Engineer - intechnologyWiFi
[email protected]<mailto:[email protected]>
Direct 01423 510650
Mobile 07467 145626
Head Office 01423 510510

[X]



This is an email from inTechnology plc, Cardale House, Cardale Court, Beckwith 
Head Road, Harrogate, UK, HG3 1RY.
Registered in England 3916586.

The contents of this message may be privileged and confidential. If you have 
received this message in error, you may not use, disclose, copy or distribute 
its content in any way. Please notify the sender immediately. All messages are 
scanned for all viruses.

_______________________________________________
Users mailing list
[email protected]<mailto:[email protected]>
http://lists.ovirt.org/mailman/listinfo/users




--
Didi


This is an email from inTechnology plc, Cardale House, Cardale Court, Beckwith 
Head Road, Harrogate, UK, HG3 1RY.
Registered in England 3916586.

The contents of this message may be privileged and confidential. If you have 
received this message in error, you may not use, disclose, copy or distribute 
its content in any way. Please notify the sender immediately. All messages are 
scanned for all viruses.



--
Didi


This is an email from inTechnology plc, Cardale House, Cardale Court, Beckwith 
Head Road, Harrogate, UK, HG3 1RY.
Registered in England 3916586.

The contents of this message may be privileged and confidential. If you have 
received this message in error, you may not use, disclose, copy or distribute 
its content in any way. Please notify the sender immediately. All messages are 
scanned for all viruses.
root ~ $ engine-backup --mode=backup --scope=files --file=veng.bak 
--log=backup.log
engine-backup: back up and restore ovirt-engine environment
USAGE:
    /usr/bin/engine-backup [--mode=MODE] [--scope=SCOPE] [--file=FILE] 
[--log=FILE]
 MODE is one of the following:
    backup                          back up system into FILE
    restore                         restore system from FILE
 SCOPE is one of the following:
    all                             If MODE=backup: backup everything below.
                                    If MODE=restore: restore everything found 
in FILE.
    files                           product files only
    db                              Engine database only
    dwhdb                           Data Warehouse database only
    reportsdb                       Reports database only
    The option --scope can be passed more than once, with different scopes.
 --file=FILE                        file to use during backup or restore
 --log=FILE                         log file to use during backup or restore
 --archive-compressor=COMPRESSOR
    Use COMPRESSOR to compress the backup file, can be one of:
    gzip
    bzip2
    xz
    None
 --files-compressor=COMPRESSOR      compress the product files, same options as 
--archive-compressor
 --keep-temporary-data              do not clean up temporary data on restore
 --db-compressor=COMPRESSOR         compress the Engine database, same options 
as --archive-compressor
 --db-dump-format=FORMAT
    Engine database dump format; see pg_dump(1) for details. Can be one of:
    plain
    custom
 --db-restore-jobs=JOBS             number of restore jobs for the Engine 
database,
                                    when using custom dump format and 
compressor None.
                                    Passed to pg_restore -j. Defaults to 2.
 --provision-db                     create a PostgreSQL database for the Engine 
on restore
 --change-db-credentials            activate the following options, to restore
                                    the Engine database using credentials other
                                    than those stored in the backup itself.
                                    If used, existing credentials are ignored.
 --db-host=host                     set Engine database host
 --db-port=port                     set Engine database port
 --db-user=user                     set Engine database user
 --db-passfile=file                 set Engine database password - read from 
file
 --db-password=pass                 set Engine database password
 --db-password                      set Engine database password - interactively
 --db-name=name                     set Engine database name
 --db-secured                       set a secured connection for the Engine 
database
 --db-secured-validation            validate host for Engine database
 --dwh-db-compressor=COMPRESSOR     compress the Data Warehouse database, same 
options as --archive-compressor
 --dwh-db-dump-format=FORMAT        Data Warehouse database dump format, same 
options as --db-dump-format
 --dwh-db-restore-jobs=JOBS         for Data Warehouse database, same as 
--db-restore-jobs
 --provision-dwh-db                 create a PostgreSQL database for Data 
Warehouse on restore
 --change-dwh-db-credentials        activate the following options, to restore
                                    the Data Warehouse database using 
credentials other
                                    than those stored in the backup itself.
                                    If used, existing credentials are ignored.
 --dwh-db-host=host                 set Data Warehouse database host
 --dwh-db-port=port                 set Data Warehouse database port
 --dwh-db-user=user                 set Data Warehouse database user
 --dwh-db-passfile=file             set Data Warehouse database password - read 
from file
 --dwh-db-password=pass             set Data Warehouse database password
 --dwh-db-password                  set Data Warehouse database password - 
interactively
 --dwh-db-name=name                 set Data Warehouse database name
 --dwh-db-secured                   set a secured connection for the Data 
Warehouse database
 --dwh-db-secured-validation        validate host for Data Warehouse database
 --reports-db-compressor=COMPRESSOR compress the Reports database, same options 
as --archive-compressor
 --reports-db-dump-format=FORMAT    Reports database dump format, same options 
as --db-dump-format
 --reports-db-restore-jobs=JOBS     for Reports database, same as 
--db-restore-jobs
 --provision-reports-db             create a PostgreSQL database for Reports on 
restore
 --change-reports-db-credentials    activate the following options, to restore
                                    the Reports database using credentials other
                                    than those stored in the backup itself.
                                    If used, existing credentials are ignored.
 --reports-db-host=host             set Reports database host
 --reports-db-port=port             set Reports database port
 --reports-db-user=user             set Reports database user
 --reports-db-passfile=file         set Reports database password - read from 
file
 --reports-db-password=pass         set Reports database password
 --reports-db-password              set Reports database password - 
interactively
 --reports-db-name=name             set Reports database name
 --reports-db-secured               set a secured connection for the Reports 
database
 --reports-db-secured-validation    validate host for Reports database

 --fast-restore                     the default for backup, equivalent to:
         --archive-compressor=gzip \
         --files-compressor=xz \
         --db-dump-format=custom \
         --db-compressor=None \
         --dwh-db-dump-format=custom \
         --dwh-db-compressor=None \
         --reports-db-dump-format=custom \
         --reports-db-compressor=None

    In addition, you should pass, when restoring:
        --db-restore-jobs=N \
        --dwh-db-restore-jobs=N \
        --reports-db-restore-jobs=N
        where 'N' is around 150% of available cpu cores.

 --small-size                       for a small backup file, equivalent to:
         --archive-compressor=xz \
         --files-compressor=xz \
         --db-dump-format=plain \
         --db-compressor=xz \
         --dwh-db-dump-format=plain \
         --dwh-db-compressor=xz \
         --reports-db-dump-format=plain \
         --reports-db-compressor=xz

 --fast-backup                      for a fast backup, equivalent to:
         --archive-compressor=gzip \
         --files-compressor=xz \
         --db-dump-format=custom \
         --db-compressor=None \
         --dwh-db-dump-format=custom \
         --dwh-db-compressor=None \
         --reports-db-dump-format=custom \
         --reports-db-compressor=None

 You can use one of --fast-restore, --small-size, --fast-backup, and after that
 one of the other compressor/format options for further fine-tuning.


 ENVIRONMENT VARIABLES

 OVIRT_ENGINE_DATABASE_PASSWORD
     Database password as if provided by --db-password=pass option.
 OVIRT_DWH_DATABASE_PASSWORD
     Database password as if provided by --dwh-db-password=pass option.
 OVIRT_REPORTS_DATABASE_PASSWORD
     Database password as if provided by --reports-db-password=pass option.

 Wiki

 See http://www.ovirt.org/Ovirt-engine-backup for more info.

 To create a new user/database:

 create role <user> with login encrypted password '<password>';
 create database <database> owner <user> template template0
 encoding 'UTF8' lc_collate 'en_US.UTF-8' lc_ctype 'en_US.UTF-8';

 Open access in the firewall/iptables/etc. to the PostgreSQL port,
 5432/tcp by default.

 Locate pg_hba.conf within your distribution,
 common locations are:
  - /var/lib/pgsql/data/pg_hba.conf
  - /etc/postgresql-*/pg_hba.conf
  - /etc/postgresql/*/main/pg_hba.conf

 and open access there by adding the following lines:

 host    <database>      <user>          0.0.0.0/0               md5
 host    <database>      <user>          ::0/0                   md5

 Replace <user>, <password>, <database> with appropriate values.
 Repeat for Engine, Data Warehouse, Reports as required.

readlink: missing operand
Try 'readlink --help' for more information.
/usr/bin/engine-backup: line 1405: : No such file or directory
Notifying engine
/usr/bin/engine-backup: line 1472: : No such file or directory
/usr/bin/engine-backup: line 1405: : No such file or directory
FATAL: Failed notifying engine
_______________________________________________
Users mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/users

Reply via email to