Whitepaper : Initializing Replication from Backup
- Overcome barriers to initialization
- Learn how to get creative with backups
Whitepaper
Initialization of a transactional replication subscriber is a highly valuable tool. For very large databases (VLDBs), snapshot generation and application can have a considerable performance impact and take a long time. Consequently, initializing a subscription from a snapshot can be prohibitive.
The next logical step in the evolution of replication was to make better use of the backups that were already being applied to the subscribers. Initialization from backup was designed to alleviate some of the problems faced by administrators of VLDBs. However, there are perceived limitations and restrictions regarding initialization from backup for transactional replication, but those are not insurmountable barriers to using this process. You can still use initialization from backup with a little creativity and by utilizing log or filegroup backups.
The reasons often given for not using initialization from backup include a need to use a third-party compression for full backups, especially as a tool for encryption or to gain maximum compression ratios; a belief that the subscriber must be initialized from a full backup; and a requirement to limit subscribers to a subset of tables. All of these limitations are easy to handle with initialization from backup.
This whitepaper provides clear guidance on the perceived limitations and restrictions on initializing transactional replication subscribers from a backup. The whitepaper describes the trouble with snapshot initialization, which backups are suitable for initialization, moving beyond simple initialization from backup, and initializing from a filegroup backup
Register to read the full whitepaper.
See Also:
- Whitepaper: Database Backup Compression Versus File Deduplication
- Whitepaper: How Compliance Impacts Backup Strategy
- Whitepaper: How To Develop And Test A Disaster Recovery Plan
- Whitepaper: Top SQL Server Backup Mistakes (and How to Avoid Them)
- Whitepaper: Understanding Database Backup Strategies
- Whitepaper: Virtual Machine Snapshots versus Database Backups
- Whitepaper: What’s on the Mind of IT When It Comes to Backup
- Webcast: How to Create Your Disaster Recovery Plan
- Webcast: Best Practices for SQL Server Backup and Disaster Recovery
- Webcast: Defend Your Database Against Disasters
- Webcast: Designing a SQL Server Backup Strategy
- Webcast: SQL Server Backup Automation and Best Practices
- Webcast: SQL Server Backup: Challenges, Best Practices and Instant Data Recovery
- Webcast: SQL Server Backup Strategies – Architect a Solid Backup Foundation
- Webcast: SQL Server Backup Strategies: One Size Does Not Fit All
- Infographic: Top 5 Backup Mistakes
Topics :
Database Backup,
Products :
SQL Safe Backup,
- Overcome barriers to initialization
- Learn how to get creative with backups
Initialization of a transactional replication subscriber is a highly valuable tool. For very large databases (VLDBs), snapshot generation and application can have a considerable performance impact and take a long time. Consequently, initializing a subscription from a snapshot can be prohibitive.
The next logical step in the evolution of replication was to make better use of the backups that were already being applied to the subscribers. Initialization from backup was designed to alleviate some of the problems faced by administrators of VLDBs. However, there are perceived limitations and restrictions regarding initialization from backup for transactional replication, but those are not insurmountable barriers to using this process. You can still use initialization from backup with a little creativity and by utilizing log or filegroup backups.
The reasons often given for not using initialization from backup include a need to use a third-party compression for full backups, especially as a tool for encryption or to gain maximum compression ratios; a belief that the subscriber must be initialized from a full backup; and a requirement to limit subscribers to a subset of tables. All of these limitations are easy to handle with initialization from backup.
This whitepaper provides clear guidance on the perceived limitations and restrictions on initializing transactional replication subscribers from a backup. The whitepaper describes the trouble with snapshot initialization, which backups are suitable for initialization, moving beyond simple initialization from backup, and initializing from a filegroup backup
Register to read the full whitepaper.
See Also:
- Whitepaper: Database Backup Compression Versus File Deduplication
- Whitepaper: How Compliance Impacts Backup Strategy
- Whitepaper: How To Develop And Test A Disaster Recovery Plan
- Whitepaper: Top SQL Server Backup Mistakes (and How to Avoid Them)
- Whitepaper: Understanding Database Backup Strategies
- Whitepaper: Virtual Machine Snapshots versus Database Backups
- Whitepaper: What’s on the Mind of IT When It Comes to Backup
- Webcast: How to Create Your Disaster Recovery Plan
- Webcast: Best Practices for SQL Server Backup and Disaster Recovery
- Webcast: Defend Your Database Against Disasters
- Webcast: Designing a SQL Server Backup Strategy
- Webcast: SQL Server Backup Automation and Best Practices
- Webcast: SQL Server Backup: Challenges, Best Practices and Instant Data Recovery
- Webcast: SQL Server Backup Strategies – Architect a Solid Backup Foundation
- Webcast: SQL Server Backup Strategies: One Size Does Not Fit All
- Infographic: Top 5 Backup Mistakes
Topics : Database Backup,
Products : SQL Safe Backup,