| Traditionally organizations followed conventional | | | | process that was used previously by enterprises. In |
| backup procedures where all data changes since the | | | | this method, new data is captured continuously, as |
| last backup is retraced and shoved through the | | | | and when it is created, and effectively backup-ed up |
| enterpriseâs network at one time. This | | | | throughout the day. |
| traditional method causes high negative impacts to | | | | By using this method, the enterprise is able to use |
| currently running business operations. When such | | | | only negligible bandwidth and this imposes no impacts |
| backups are performed, application performance is | | | | on production applications as well. Also, the enterprise |
| badly affected and it consumes considerable network | | | | is assured of recoveries from the most recent data. |
| bandwidth as well. | | | | This methodology, in no way shortens the backup |
| New advanced technologies in backup solutions have | | | | procedure, but it completely eliminates them as a |
| completely changed the conventional backup/restore | | | | discrete operation. |