Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
mx-one backups
- Thread starter sajeshS
- Start date
data_backup - stores the program units
config_mirror - stores the last data_backup, license file, and some config files that are stored normally on SLES(Ex: /etc)
eri_sn_safety_backup - didn't used it, but I guess saves the eri_sn state/program unit + data_backup
config_mirror - stores the last data_backup, license file, and some config files that are stored normally on SLES(Ex: /etc)
eri_sn_safety_backup - didn't used it, but I guess saves the eri_sn state/program unit + data_backup
- Thread starter
- #3
- Thread starter
- #4
No!
It is not that simple.
Each LIM/Server holds its own Plex type backup data from a 'data_backup' in directory /var/opt/eri_sn. LDAP data is also saved locally, but the master LDAP is normally in server 1.
Data from a 'config_mrror' is stored in /eri_sn/mirror on server 1 but can be automatically copied to other servers using the '-export' switch.
The 'eri_sn_safety_backup' command is designed to produce an off-site backup which can be used to restore the whole system in case of catastophic failure.
The output of this can be saved to any mounted filesystem e.g. flash drive, NFS, SAMBA share. There is a configuration file for this; /etc/opt/eri_sn/safety_backup.conf
Do you guys have access to the CPI document collection?
It is not that simple.
Each LIM/Server holds its own Plex type backup data from a 'data_backup' in directory /var/opt/eri_sn. LDAP data is also saved locally, but the master LDAP is normally in server 1.
Data from a 'config_mrror' is stored in /eri_sn/mirror on server 1 but can be automatically copied to other servers using the '-export' switch.
The 'eri_sn_safety_backup' command is designed to produce an off-site backup which can be used to restore the whole system in case of catastophic failure.
The output of this can be saved to any mounted filesystem e.g. flash drive, NFS, SAMBA share. There is a configuration file for this; /etc/opt/eri_sn/safety_backup.conf
Do you guys have access to the CPI document collection?
- Thread starter
- #7
With 'config_mirror', the default is to create the /eri_sn/mirror directory containng a data_backup for every server in the system and then copy that to every server in the system using rsync. This could result in a lot of data traversing the customer network. To conrol this, the '-export' switch was introduced.
With no parameter, '-export' will prevent the copying of the mirror data to other servers. This is not advisable as the repair server process uses the mirror data. If it only exists on server 1 and server 1 fails, you are in trouble.
If you have access to a TSE system use the command 'config_mirror -?' fr more info.
If you have access to the CPI documentation collection, look at 'Administrator User's Guide 154 31-ANF 901 43' which details the differences and strategies for various backups.
It is best to perform 'config_mirror' and 'eri_sn_safety_backup' in low traffic using a 'cron' job.
With no parameter, '-export' will prevent the copying of the mirror data to other servers. This is not advisable as the repair server process uses the mirror data. If it only exists on server 1 and server 1 fails, you are in trouble.
If you have access to a TSE system use the command 'config_mirror -?' fr more info.
If you have access to the CPI documentation collection, look at 'Administrator User's Guide 154 31-ANF 901 43' which details the differences and strategies for various backups.
It is best to perform 'config_mirror' and 'eri_sn_safety_backup' in low traffic using a 'cron' job.
- Thread starter
- #9
- Thread starter
- #10
- Status
Similar threads
- Locked
- Question
- Locked
- Question
