I have a problem in logshipping any one help would be appreciated.
during logshipping when i am adding data (log.data,transactlog)to the
destination database when i select the destination server name(server2)it
didn't showing any drives present .instead showing local drives.if i select
3rd server then it shows perfect all the available drives .If any one knows
the error please let me know u help would be appreciated.
Thanks,
pardhi
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forum...eneral/200509/1
Hi, I am trying to do logShipping from one server to another. I created the logins and restored the DB(user) with the option - "Leave DB ReadOnly and able to restore logs" I was surprised to see that the DB got restored but there were no users in that DB. Since this is a read-only DB I cannot run commands like Sp_change_users_login etc.....and neither can I create a user. Any thoghts what might have gone wrong? TIA.
Everyday we take a Fullbackup followed by every 15 mins we take transaction log backup.
Day 1:
Full Backup at 12:00 AM Transaction log backup from 4:00 AM to 11:45 PM
Day 2:
Full Backup at 12:00 AM Transaction log backup from 4:00 AM to 11:45 PM
Day 3: . . .
On Secondary server
Everyday will restore the full backup daily and followed by the transaction log backup restore with no recovery mode.
Day 1:
Full Backup Restore at 2:00 AM Transaction log backup Restore from 5:00 AM to 12:45 AM
Day 2:
Full Backup Restore at 2:00 AM Transaction log backup Restore from 5:00 AM to 12:45 AM
Day 3: . . .
The problem we have is
A third server which is remote need the full backup for the first time only and everyday they need a log backup alone and not the daily fullbackup to logship the server. Will that be possible using the logs alone for logshipping but not considering the full backup file.
Third server
Like:
One time Full Backup Restore at 4:00 AM
Day 1:
Only Transaction log backup Restore from 9:00 AM to 4:45 AM
Day 2:
Only Transaction log backup Restore from 9:00 AM to 4:45 AM
Day 3: . . .
Don't the server throws an error saying that
Msg 4305, Sev 16: The log in this backup set begins at LSN 13000001816200001, which is too late to apply to the database. An earlier log backup that includes LSN 13000001723100001 can be restored. [SQLSTATE 42000] Msg 3013, Sev 16: RESTORE LOG is terminating abnormally. [SQLSTATE 42000]
We don't know how to fullfil the request. I don't think Logshipping wizard skips the full backup file for logshipping if it has been schedule for full backup everyday and logbackup every 15 mins.
Please help. is there anyway we can solve this problem.
i have configured logshipping how to change roles is the question. By using sp_changeprimary role the database has become suspected sp_change secondary role and sp_change monitor role is not working please guide on this issue
I have setup logshipping between 2 SQL Server 2000 servers. It looks like everything is working (The transaction log files are being created, The log files are being copied to the secondary server. The restore job on the secondary server is running every 15 minutes successfully).
I cannot tell if it is actually applying the transactions.
If it is applying the transactions, it is not updating the monitor.
Does anyone have any ideas what might be causing this problem?
Hi Guys, Our servers are all standard edition of SQL Server 2000. We are trying to build Disaster recovery site with standby sql servers.
We have 2 options for this:- one is Replication(Transactional) and the other is Logshipping.
Since we don't have standard edition, Log shipping is not and option. However, we can buy just one sql enterprise edition for this pupose if logshipping requirs only one enterprise edition.
IF I CHOOSE THE LOGSHIPPING OPTION, CAN I IMPLEMENT THE STANDBY SERVER BY ONLY HAVING ONE ENTERPRISE EDITION SQL SERVER (STANDBY SERVER) where as all the pulishers are standard edition sql servers??
IF NOT IF WE CHOOSE TO GO BY TRASACTIONAL REPLICATION, HOW HARD IS TO CREATE THE STANDBY SERVER WHEN WE HAVE MOST OF THE TABLES WITHOUT PRIMARY KEYS PERTICULALY FOR THIS SERVER??
Thanks for your input and I always appreciate all you guys help in this forum. Thanks :confused: :confused:
Hey All, Hope this is the right place for this post.
I set up logshipping between two databases recently. everything looks fine. the backup, copy and restore jobs are all suceeding(from the job log). the problem is no Tlogs are being restored in secondary database. The restore job skips all the tlogs and says it did not find any tlog back up file to restore!! The jobs finishes with this:
007-07-17 14:40:30.59 Could not find a log backup file that could be applied to secondary database 'SaaSNet_dataStore'.2007-07-17 14:40:30.59 The restore operation was successful. Secondary Database: 'SaaSNet_dataStore', Number of log backup files restored: 02007-07-17 14:40:30.59 Deleting old log backup files. Primary Database: 'SaaSNet_DataStore'2007-07-17 14:40:30.59 The restore operation was successful. Secondary ID: '5808a414-2ada-41d2-a8a0-2cf84f85174a'
have a question about logshipping and full database backup: during a full database backup the log will be backed up too and emptied. If I run a full backup on databases which is setup for logshipping - does it mean I will loose data on the standby side ?
I have logshipping configured b/w Primary and DR site, Tlogs interval is every 15 minutes. Now I would like to setup another secondary for reporting purpose but I would like to restore Tlogs with a frequency of 20hrs(its long).
will this break backup chain that affects DR?what will be the size of Tlog that will be taken every 20 hours assume 10MB for 15 minutes . I assume it should have all the changes from last restore to reporting server is this correct. we are fine to kill the sessions while applying Tlog nightly .DB size is 1TB we use Redgate backup compressed size is 200GB and Tlogs are few MB's.
I am new to Forum. So not sure if i am posting my problem under the right topic.
We have a sql server 2005 enterprise edition 4 way cluster on windows 2003 advance server.
I am logshipping these database to a different server at a different location.
My logshipping went fine until one the cluster server failed and the server instance failed over to another node.
The backup that happened around that time got copied over to the secondary by the copy job.
The log file that got copied to the secondary server tried restoring and i think it failed int he middle of restoring it.
(You would think that the sql would knoe if the backup is in complete and will move on to the next file. Not sure what happened there.)
There is no indication of the *.TUF file in the directory where i have the log files.
I tried restoring it manually and i got the following error
Msg 4319, Level 16, State 3, Line 1
A previous restore operation was interrupted and did not complete processing on file 'sessionlog1'. Either restore the backup set that was interrupted or restart the restore sequence.
Msg 3013, Level 16, State 1, Line 1
RESTORE LOG is terminating abnormally.
I looked in the msdb..log_shipping_secondary_databases and looked for the last file that it restored and tried restoring it again with the following restore command by removing and adding some of the keywords that you see after the "WITH" clause.
MSFT do not recommand to use continne_after_error unless its absolutley necessary. I stilll get the above error.
restore log sessiondata
from disk = 'I:sql13qasmlogssessiondatasessiondata_20070901124516.trn'
with restart, CONTINUE_AFTER_ERROR, norecovery
When i add the restart int he with clause,
The restart-checkpoint file 'J:Microsoft SQL ServerMSSQL.5MSSQLBackupsessiondata.CKP' was not found. The RESTORE command will continue from the beginning as if RESTART had not been specified.
Msg 4319, Level 16, State 1, Line 1
A previous restore operation was interrupted and did not complete processing on file 'sessionlog1'. Either restore the backup set that was interrupted or restart the restore sequence.
Msg 3013, Level 16, State 1, Line 1
RESTORE LOG is terminating abnormally.
I checked it the backup directory and i can't locate the .CKP file.
Does anyone ever come accross this issue?
Is there anyother way i could recover this DB in a standby or norecovery mode.
Any kind of help to resolve this issue (beside copy the full backup and redo the whole log-shipping process again) would be appreciated. sicne my primary and secondary server are totally ina different location, i need to ship a tape, if i need a full backup. This is the 3rd time its happening on that cluster. its frustrating to ship a tape everytime this happens.
In my environment Mirroring is set up and the Principal/Primary and secondary are set up as well. I am having trouble added my mirror as a logshipping primary.
BOL says to create the Mirror/Primary I need to use the Transact-SQL commands. But sp_add_log_shipping_primary_database checks to make sure the status of the database is "Online". So when I run sp_add_log_shipping_primary_database to add the mirror db as a Primary I get the following error:
Msg 32008, Level 16, State 1, Procedure sp_add_log_shipping_primary_database, Line 58 Database TestMirror is not ONLINE. Cannot proceed with log shipping primary processing.
Am I doing something wrong? I am following the BOL page http://msdn2.microsoft.com/en-us/library/ms187016.aspx .
We are planning to setup log shipping model being setup between two sqlserver 2005 enterprise edition.
Our transaction log backup sizes are not consistent through out the day.The following is the scenario.
T1 at 8.00 -- 315MB
T2 at 8.30 -- 152MB
T3 at 9.00 -- 2.5GB
T4 at 10.00 -- 500MB
The bandwidth available is 25MB/minute. We are taking the backups of Tlogs at 30mins interval.Now at 'T3' log transfer we want to zip the file on the primary server,copy the file over the WAN and unzip it standby server.
Now i wanted to know whether to perform this kind of action(Zip,copy,unzip), can i create a separate job on primary ?? which will put the unzipped file on standby and allow the log shipping job to restore the log file (T3)
Also i wish to carry my T3,T4 etc backup -- copy-- restores through my Log shipping activity.
I cannot take 15mins backup on primary server to reduce the transaction log backup size.Thts another constraint i have.
Also tell me how to zip and unzip thru command line if u hve any link.
Hi , I am working on logshipping DRS trail and have done role successfully. Now after doing the role change I want to rebuild the logshipping for database which is already existing in secondary server. I tried adding destination server with existing database. It gives me message as " The database is not in standbymode to do logshipping". Can anyone help me on this. How should I bring the existing database in warm standby mode.
I created log shipping btw two servers using maintenance plan.
maintainanace plan taking the log backups and copying those backups in the standby server but unable to restore thos log backups
i am getting the following error ( for the Log Restore job) Executed as user: NT AUTHORITYSYSTEM. sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed.
In the logshipping monitor history i found the follwing error [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 4305: [Microsoft][ODBC SQL Server Driver][SQL Server]The log in this backup set begins at LSN 4830000001442600001, which is too late to apply to the database. An earlier log backup that includes LSN 4828000001884200001 can be restored. [Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is terminating abnormally.
Hi,Currently we have logshipping setup with one production db serversending the logs to one standby database server.we would like to have setup where there will be two standby dbservers. Second server will be located in different country.Kindly let me know if we can have the setup wherethere is one primary server and two standby db servers.When I tried to configure the same I am not able to complete themaintenance plan.It gives error that logshipping monitor already exists.Please help me. tks in advance.RegardsKamal
I have a primary SQL cluster, logshipping my SQL 2005 db to a secondary server used for the logshipping/recovery server only.
Say my primary server starts on fire, melts down, etc. How do I bring the database on the secondary server online? Do I need to roll in the transaction logs, etc.? I'm looking for a step-by-step, as I am very new to SQL.
I've seen some articles in the SQL Books Online, but things don't seem to work correctly when I follow the steps.
I implement Log Shipping in 2 servers with Sql 2005, but when i drop log shipping at the first server the second server locks the DB. I can not copy, drop or select any table, object...
The second server displays the following messaje
Error 952 - Database '%.*ls' is in transition. Try the statement later.
Any help you can give to me to the resolve this cuestion?
I am set up log shipping as backup and copy every one hour and restore every ( disconnect users and stand by) one hour on servers in same domain. Set-up completes successfully.Copy job works as expected. but the restore job fails intermittently to restore the .trn file saying ' could not apply log, data invalid' .
when i delete and copy the files for which restore failed manually using CTRL+C and CTRL+V across network and re run the restore job it does restore successfully . Through out the day i get about 5-6 problematic .trn files on secondary server which are copied from primary server and when restore fails i have to manually delete the log file which had problem restoring and then copy that file again using CTRL+C and CTRL+V then run the restore and it gets restored successfully.when running restore filelistonly on the logfile in issue on secondary server it gives below error
Cmd:
RESTORE verifyonly FROM disk='G:xxxx_Copyxxx_20150604010501.trn'
Error:
Msg 3203, Level 16, State 1, Line 2 Read on "G:xxxxxxx_20150604010501.trn" failed: 13(The data is invalid.) Msg 3013, Level 16, State 1, Line 2 VERIFY DATABASE is terminating abnormally.
and when i run restore filelistonly using netwok path then is seem s good and i can restore the logs as well
CMD:
RESTORE verifyonly from disk='1.2.3.4xxx_Backupsxxx_20150604010501.trn'
Output: The backup set on file 1 is valid.I can assure there is no corruption on the log back up, no lsn mismatch, no log files missing.Same version and edition on both servers. Both servers are SQL server 2012 Enterprise edition on window server 2012
We are using Sql server 2012. One of our production database has hight no of vlfs. We are planning to shrink the logfile to reduce the no of VLFs but the database is configured for logshipping.
What is the effect of logshipping when you shrink the logfile?
Hey, my logshipping is working just fine but the name of the backup file is of a concern to me. It's using the name in the format of DbName_20061011200002.trn. I know 20061011 is the date. That's fine. 2000 is supposed to be the time but it's giving the wrong time. It's supposed to be 1500 because the time right now is 3pm. And I dont know why the last 2 digits before the .trn are for. Is this something new in SQL 2005 logshipping? SQL 2000 didn't have it. Thank you.
Logshipping was working fine till last Friday...Looks like there was a cluster node failover during the weekend on the Secondary SQL cluster....From that time, restore log is not working, I am able to see all the log backup files are being copied to the secondary server...its no the transaction log backup share missing problem......I see this message:
The RESTORE statement could not access file 'J:MSSQLBackupDBName_200712081350.tuf'. Error was '2(The system cannot find the file specified.)'
I gooled and found that .tuf file has the LSN information as which log needs to be restored next....I looked at the sql error log and tried to restore the next log manually with "norecovery" option, but still get the same message....Is there any other option other than to remove and reconfigure logshipping ?
I am doing a logshipping in sqlserver2000. I have PrimaryServer database A and Secondaryserver A which is already existing. Now if i am trying to establish logshipping with this existing db in secondaryserver it says db A in destination is not in standy mode.
Please help me how to bring the db in standy mode that can be used to do logshipping.
I am trying to set up log shipping in a clustered server environment. I am pretty confused about the location of the shared folder to be created to put backup created by log shipping job. Which drive should I use either local or clustered shared drive to store the backups in primary server and to copy the same in secondary Server?
Hi Please help me sort out this issue, Can Logshipping server be a primary server for any other server. Or any other way to transfer the data [DTS] to third server once in a day so that third server will also update.
