log shipping &replication&mirroring&alwayson.txt - High...

This preview shows page 1 - 3 out of 9 pages.

High avalibulity: 1.logshipping-> db level->sql 2000->full/bulklog 2.db mirroring->db level->sql 2005->full 3.replication->table level->sql 7.0->full/bulk log/simple 4.clustering->instaance level->sql 2000 5.always on->group db level->sql 2012->full log shipping: automatically send transaction log backups from a primary database on a primary server instance to one or more secondary databases on separate secondary server instances. edition should be same,minimum 2 sql ,monitor 1 as well. create backup folder in primary and provide read/write permission on service account. create copy folder in secondary and provide minimum read permission express edition not supported agent not avalible. collasion setting also same maxminum we can 25 secondary servers. ================================================================================ ================== log shipping issues: jobs disable,backup folder share permission issues space issue backup folder copy folder recovery model change full to simple manuval log backup LS break network issue backup job fails: disk full,permission,invalid path,agent down,sql down db down,recovery model change to simple. restore job fails:sqldown,server down,disk down,agent down,backup file currepted LSN mismatch. ================================================================================ ================== how will change database stand by mode: manuvally restore log backup option stand by mode There are two options to make such changes for log shipping configurations: 1) by running the log shipping system stored procedure ===EXEC sp_change_log_shipping_secondary_database / @secondary_database = 'Collection',/@restore_mode = 1,/@disconnect_users = 1 2) by making changes to log shipping using SSMS. manuvally restore log backup restore stand by mode. RESTORE LOG [test] FROM DISK = N'I:\backup\test_fullbackup_3.42.pm.trn' WITH FILE = 1, STANDBY = N'I:\backup\ROLLBACK_UNDO_test.BAK', NOUNLOAD, STATS = 10 GO ================================================================================ ================== log file full 1) Open transactions
2) Missing log backups SELECT log_reuse_wait_desc from sys.databases WHERE name=<YourDBName> ================================================================================ ================== Can we shrink log shipped database log file? Yes, we can shrink the log file, but we shouldn’t use WITH TRUNCATE option. If we use this option obviously log shipping will be disturbed. ================================================================================ ================== commands: sp_help_log_shipping_monitor--status sys.sp_help_log_shipping_monitor--last backup restore. sp_help_log_shipping_monitor_primary--primary last backup sp_help_log_shipping_monitor_secondary--second copy restore ================================================================================ ================== tuf file: after restore job in secondary tuf file created it contain un commited transation ================================================================================ ================== wrk file: When the transaction log backup files are copied from the primary server to the secondary server the file is named as a work file(. wrk) till the copy operation is completed.it will trn file. ================================================================================ ================== failover log shipping: run & disable backup copy and restore check copy and restore status select secondary_database,last_copied_file,last_restored_file from msdb..log_shipping_monitor_secondary Kill the open sessions for the DB and take Tail log backup.

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture