backup - pull or push? [on hold]Use or don't use virtualization for Linux Webserver?Anybody knows a Backup software working in a “push” rather than “pull” way?GIT as a backup toolWhich is better for website backup - rsync or git pushVM NetWorker server loses hard drive every nightHow to backup 20+TB of data?Backing up multiple git repos of the same project (deduplication)NetApp Backup Strategy - Snapshots to SnapMirrors to Tape?Cronjob to push MongoDB Backup via gitHow to reduce the IO Wait Time during a rsync backup?
What Exploit Are These User Agents Trying to Use?
Send out email when Apex Queueable fails and test it
What is a Samsaran Word™?
Can compressed videos be decoded back to their uncompresed original format?
Placement of More Information/Help Icon button for Radio Buttons
Avoiding the "not like other girls" trope?
Should I tell management that I intend to leave due to bad software development practices?
Is there a hemisphere-neutral way of specifying a season?
Theorists sure want true answers to this!
In the UK, is it possible to get a referendum by a court decision?
Why were 5.25" floppy drives cheaper than 8"?
What is the fastest integer factorization to break RSA?
How to show a landlord what we have in savings?
files created then deleted at every second in tmp directory
Why was Sir Cadogan fired?
Is it "common practice in Fourier transform spectroscopy to multiply the measured interferogram by an apodizing function"? If so, why?
Was the Stack Exchange "Happy April Fools" page fitting with the '90's code?
Finding the reason behind the value of the integral.
Processor speed limited at 0.4 Ghz
What does the same-ish mean?
ssTTsSTtRrriinInnnnNNNIiinngg
Can I hook these wires up to find the connection to a dead outlet?
How do I exit BASH while loop using modulus operator?
Ambiguity in the definition of entropy
backup - pull or push? [on hold]
Use or don't use virtualization for Linux Webserver?Anybody knows a Backup software working in a “push” rather than “pull” way?GIT as a backup toolWhich is better for website backup - rsync or git pushVM NetWorker server loses hard drive every nightHow to backup 20+TB of data?Backing up multiple git repos of the same project (deduplication)NetApp Backup Strategy - Snapshots to SnapMirrors to Tape?Cronjob to push MongoDB Backup via gitHow to reduce the IO Wait Time during a rsync backup?
PULL OR PUSH, thats the Question!
We are currently planning a backup system and are faced with the question of whether we should follow the push or pull approach. In other words, all systems independently store their backups on a central server or the server collects all backups independently. The following pros and cons have been set for each approach so far.
Pull:
Pro:
- Maintainability
- central approach
- no need of backup configuration on server
- no need of backup vm as a server, no ports to be opened to the
servers, less administration
Con:
- Security risk due to centrality and access to all other systems
- need of backup user with database wide privileges
Push:
Pro:
- Easier to handle for special cases
- Encryption before transmission for particularly sensitive data in special cases
- adjustment of backup on server side (intransparency in backup - the backup server does not have to know what to backup)
Con:
- no configuration management (also not realizable in short time), consequently worse maintainability
- configuration on each database server -> responsibility of backup on server side
Can you tell us about your experiences or share your opinion so that we can make a final selection? We would also be very happy about other pros and cons we didn't think of. Many thanks in advance.
debian backup
asked yesterday
umgumg
1
New contributor
umg is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
put on hold as primarily opinion-based by Sven♦ yesterday
Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |
PULL OR PUSH, thats the Question!
We are currently planning a backup system and are faced with the question of whether we should follow the push or pull approach. In other words, all systems independently store their backups on a central server or the server collects all backups independently. The following pros and cons have been set for each approach so far.
Pull:
Pro:
- Maintainability
- central approach
- no need of backup configuration on server
- no need of backup vm as a server, no ports to be opened to the
servers, less administration
Con:
- Security risk due to centrality and access to all other systems
- need of backup user with database wide privileges
Push:
Pro:
- Easier to handle for special cases
- Encryption before transmission for particularly sensitive data in special cases
- adjustment of backup on server side (intransparency in backup - the backup server does not have to know what to backup)
Con:
- no configuration management (also not realizable in short time), consequently worse maintainability
- configuration on each database server -> responsibility of backup on server side
Can you tell us about your experiences or share your opinion so that we can make a final selection? We would also be very happy about other pros and cons we didn't think of. Many thanks in advance.
debian backup
asked yesterday
umgumg
1
New contributor
umg is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
put on hold as primarily opinion-based by Sven♦ yesterday
Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |
PULL OR PUSH, thats the Question!
We are currently planning a backup system and are faced with the question of whether we should follow the push or pull approach. In other words, all systems independently store their backups on a central server or the server collects all backups independently. The following pros and cons have been set for each approach so far.
Pull:
Pro:
- Maintainability
- central approach
- no need of backup configuration on server
- no need of backup vm as a server, no ports to be opened to the
servers, less administration
Con:
- Security risk due to centrality and access to all other systems
- need of backup user with database wide privileges
Push:
Pro:
- Easier to handle for special cases
- Encryption before transmission for particularly sensitive data in special cases
- adjustment of backup on server side (intransparency in backup - the backup server does not have to know what to backup)
Con:
- no configuration management (also not realizable in short time), consequently worse maintainability
- configuration on each database server -> responsibility of backup on server side
Can you tell us about your experiences or share your opinion so that we can make a final selection? We would also be very happy about other pros and cons we didn't think of. Many thanks in advance.
debian backup
asked yesterday
umgumg
1
New contributor
umg is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
PULL OR PUSH, thats the Question!
We are currently planning a backup system and are faced with the question of whether we should follow the push or pull approach. In other words, all systems independently store their backups on a central server or the server collects all backups independently. The following pros and cons have been set for each approach so far.
Pull:
Pro:
- Maintainability
- central approach
- no need of backup configuration on server
- no need of backup vm as a server, no ports to be opened to the
servers, less administration
Con:
- Security risk due to centrality and access to all other systems
- need of backup user with database wide privileges
Push:
Pro:
- Easier to handle for special cases
- Encryption before transmission for particularly sensitive data in special cases
- adjustment of backup on server side (intransparency in backup - the backup server does not have to know what to backup)
Con:
- no configuration management (also not realizable in short time), consequently worse maintainability
- configuration on each database server -> responsibility of backup on server side
Can you tell us about your experiences or share your opinion so that we can make a final selection? We would also be very happy about other pros and cons we didn't think of. Many thanks in advance.
debian backup
debian backup
asked yesterday
umgumg
1
New contributor
umg is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked yesterday
umgumg
1
New contributor
umg is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked yesterday
umgumg
1
New contributor
umg is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked yesterday
umgumg
1
asked yesterday
umgumg
1
1
New contributor
umg is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
umg is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
umg is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
put on hold as primarily opinion-based by Sven♦ yesterday
Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.
put on hold as primarily opinion-based by Sven♦ yesterday
Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |
add a comment |
0
active
oldest
votes
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
