Sql server logshipping

log shipping backup jobs is failing due to the below error.
The job failed.the job was invoked by schedule(ls backup_server name).The last step to run was step 1.(log shipping backup job step)
executed as user:username.the step failed.
could any one help me on this issue.
in eventviewr I am finding this error.
The log shipping primary database servername.dbname has backup threshold of 60 minutes and has not performed a backup log operation for 952 minutes. Check agent log and log shipping monitor information.

>>executed as user:username.the step failed.
Does the user have enough rights to invoke the job and write to a mentioned file location?
--Prashanth

Similar Messages

SQL Server 2012 - Wat Is The Best Solution For Creating a Read Only Replicated/AlwaysOn Database

Hi there I was wondering if someone may have a best recommendation for the following requirement I have with regards setting up a third database server for reporting?
Current Setup
SQL Server 2012 Enterprise setup at two sites (Site A & Site B).
Configured to use AlwaysOn Availability groups for HA and DR.
Installed on Windows 2012 Servers.
This is all working and failover works fine and no issues. So…
Requirement
A third server needs to be added for the purpose of reporting, to be located on another site (Site C) possibly in another domain. This server needs to have a replicated read only copy of the live database from site A or Site B, whichever is in use. The Site
C reporting database should be as up-to-date to the Site A or Site B database as possible – preferably within a few seconds anyway….
Solution - What I believe are available to me
I believe I can use AlwaysOn and create a ReadOnly replica for the Site C. If so do I assume Site C needs to have the Enterprise version of SQL server i.e. to match Site A & Site B?
Using log shipping which if I am correct means the Site C does not need to be an Enterprise version.
Any help on the best solution for this would be greatly appreciated.
Thanks, Steve

for always on - all nodes should be part of one windows cluster..if there site C is on different domain - I do not think it works.
Logshipping works --as long as the sql on site C is is same or higher version(sql 2012 or above). you can only do read only.
IMHo, if you can make site C in the same domain then, Always is better solution else log shipping
also, if your database has enterprise level features such as - partitonin, data compression -- you cannot restore the database on lower editions- so you need to have enterprise edition.
Hope it Helps!!

SQL Server wants to open properties of wrong database and cannot restore logs of different databases at the same time

We have implemented our own way of logshipping by backing up the transaction logs of all our non-system databases every hour. Then we transfer the backups (before SQL Server 2008 R2 with additional zip and unzip steps) to the second environment where we
restore them only during the night on databases in standby-state (Like this, our developers can access the databases without disturbing the productive system and we can restore the t-logs during night, so not shutting out the developers during the day).
Now since we replaced our hardware in the productive environment, we replaced the hardware in the second environment with the servers from previous productive environment. Same SQL Server 2008 R2, same Service Pack (SP2), same installation procedure. But
since then the SQL Server in the second environment behaves different:
- When the logs of some database "A" are restored, I cannot access the properties of any database, i.e. database "B", I only get the error message "Cannot show requested dialog. (SqlMgmt) Database 'A' cannot be opened. It is in the
middle of a restore. (Microsoft SQL Server, Error: 927)"
- Our logshipping runs multiple instance at the same time, so restoring multiple databases' logs. But since the change, two of the instances fail restoring of datatbases, i.e. "B" and "C" with the error message "Database 'A' cannot
be opened. It is in the middle of a restore.". The jobs guarantee to restore only logs of the database they need to restore, they have strictly separated sets of target databases and only try to restore the databases of their sets.
Before the new installations, we did not have these strange behaviours. But as said, it is the same SQL Server version, the same service pack, and we followed the same installation document but maybe with the small changes in settings. The user the jobs
are running under is a domain admin, the login they use has dbcreator, processadmin, db_owner and db_backupoperator roles. My login on the SQL Server has sysadmin rights and as described similar problems.
Is this problem known or does somebody have an idea where to go looking for?
Thanks, Chris

Hi Christar,
According to your description, after you configuring Log shipping between two database, you remove the hardware from production environment to dev environment, in this hardware, there are saved the transaction logs of your database.
When restoring your database, there will occurs error 927, right?
SQL Server Log shipping allows you to 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. It consists of three operations:
1.Back up the transaction log at the primary server instance.
2.Copy the transaction log file to the secondary server instance.
3.Restore the log backup on the secondary server instance.
Since you want to move your hardware avoiding copy job, we need to verify if .mdf and .ldf file are not saved in your hardware, or else,
if you move your hardware, you could not open your database in your Primary Server. I recommend you can refer to the following steps.
Full back up your primary database and restore it into the secondary database. It would have been set up as WITH STANDBY ,the databases would read StandBy/ Read Only.
Perform transaction log backups via a SQL Server Agent job running on the primary server instance, save them in your hardware.
In night, you move hardware to your dev environment, you can manually restore these transaction log backups or set up a SQL Server Agent job to restoring them from your hardware.
There is detail about how to configure log shipping in SQL Server 2008R2 step by step, you can review it.
http://mostafaelmasry.wordpress.com/2013/01/02/log-shipping-in-sql-server-2008r2-step-by-step/
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

SQL Server 2008 R2 and storage replication

Hello All !
On a Production site, I have a SQL Server 2008 R2 for a fat application. On a DRP site, I have the same SQL Server 2008 R2 fat application.
The production and DRP sites are interconnected with a physical SAN storage (synchrone replication). SAN LUNs are synchronous replicated (Data + logs).
In this case, is it necessary to keep logshipping beetween the 2 sites or the LUNs replication is sufficient ?
Thanks for advance for your ideas / help - Regards - Have a nice day ! RHUM2

<<In this case, is it necessary to keep logshipping beetween the 2 sites or the LUNs replication is sufficient ?>>
That question is impossible for us to answer, since we don't know your requirements (SLA etc). But if you re-phrase your question, we can give feeback with which you hopefully can make that decision:
What can log ahipping protect me from which SAN replication can't? I can think of a couple of things (others are free to chime in):
Corruption at the page level. SAN replication give you a binary image of the data. If a page is corrupt at site A, it will be corrupt at site B. Log shipping work by retorting transaction log backups.
Delayed log restore. If a problem happens at site A, you can decide to have delayed log restores at site be and restore a log backup until just prior to the accident.
Both above assumes that you know what you are doing have basically have planned for these things. But technically, they are examples of things that log shipping allows for.
Tibor Karaszi, SQL Server MVP |
web | blog

SQl Server Error:927 and Restoring

i have a problem with sharepoint database in SQL 2005.
status of tow database in sql studio mamagment are restoring...
how can i stop that? (change status to normal)
AND SO :
WHEN I GET A PROPERTISE OF THOSE DATABASE THIS ERROR APEAR:
database cannot be openned. it is in middle of restore. microsoft SQL server Error:927

Hi Tibor,
I am getting same error but here database is set to standby mode(logshipped), suggestion please..
Error:
database cannot be openned. it is in middle of
restore. microsoft SQL server Error:927
TARAK
Hi Tarak,
Did the restore complete? If there are no further backups to be restored then try below command
RESTORE DATABASE <name_here> WITH RECOVERY
Balmukund Lakhani | Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
This posting is provided "AS IS" with no warranties, and confers no rights.
My Blog |
Team Blog | @Twitter
Author: SQL Server 2012 AlwaysOn -
Paperback, Kindle

I see most recent file is called sql server log shipping work file

What is "SQL server log shipping work file"?

http://social.msdn.microsoft.com/Forums/sqlserver/en-US/62a6556e-6655-4d19-9112-1788cf7bbcfc/wrk-file-in-logshipping-2005
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance
SQL Server Integration Services:
Business Intelligence

DR - SQL Server - VM's

Hi All:
We have an discussion with VM team and DB team.
Requirement: Configure DR for all the SQL Servers hosted on Virtual Machines.
VM Team: They are asking us to configure Mirroring or Logshipping with out extra license.
DB Team: We are asking them to implement DR by using "VMware vCenter Site Recovery Manager".
We informed that we are not ready to configure either log shipping (or) mirroring for all the databases on the SQL Instance.
Please share your experiences with us who worked on DR planning on VM Hosted SQL Servers., Highly appreciated that who worked on
VMware vCenter Site Recovery Manager for there DR plans. Your experiences was help full for us.
Thanks,
Satish Kumar.
Thanks, Satish Kumar. Please mark as this post as answered if my anser helps you to resolves your issue :)

>Not sure David., as per i know NO DR for other servers.
Then what kind of DR RTO and RPO do you really need for SQL Server? Can you just copy your regular database and log backups to the other site?
David
David http://blogs.msdn.com/b/dbrowne/
1) thinking about implementing DR through "VMware vCenter Site Recovery Manager" -- do you have any idea about this
2) what is the best option to implement DR on for SQL Server VM's
Thanks,
Thanks, Satish Kumar. Please mark as this post as answered if my anser helps you to resolves your issue :)

SQL Server 2012 - DB Mirroring + Log Shipping + Multi-Subnet

Hi again,
So AG would be nice to have, but considering the costs of getting it, well, it is a no go for me at the moment (This is like a 1:20 ratio considering Std comes with server licencing and enterprise is only per 2 cores).
So, having 2 sites, with different subnet. Is it possible to configure automatic failover for DBM ? We are running Windows 2012 R2 which supports multi subnet failover. But what about DBM in this case ?
Can the witness be configured on a third site ? (I was thinking of having the following weights: Site 1:2, Site 2:1, Quorum:2 just to have no reconfig to do in case of Datacenter failure)
Also, in order to offload some of the backup load as the DB are somewhat big (1TB), I was thinking of having one additional node per site to which the logs are shipped and that are used to run the backups. The question being, is it possible to log ship from
each "primary" on each site rather than have the primary on site 1 do it for all the servers across the subnets ?
It would be a setup like this:
Site 1 Primary <---DBM---> Site 2 Primary (Hot failover)
Site 1 Primary <---LogShips---> Site 1 Secondary
Site 2 Primary <---LogShips---> Site 2 Secondary
And thus reduces the load on the link between the 2 sites.
I do hope to see AG in the future for Std as they are removing DBM in the next version.
Thanks,

The idea behind the cluster is to have a single IP on which the applications can reach the DB in case of a failover to the secondary site.
This requires a failover cluster instance - mirroring does not work this way.
Because as far as I understand it, either the application has to be aware and able to switch to the new DB primary, or we can use a multisubnet cluster or we can manually reconfigure the applications (so painful)
Mirroring has the failover partner attribute in the connection string that can be utilized. A multi-subnet cluster would require, again, a FCI.
AFAIK, DBM is not recommended for more than 10 DB on an instance due to the worker threads.
"It depends". There can be worker thread issues, but this will entirely depend on your hardware and architecture of processor/SQL Server. In 32-bit world it'll eat up all of your worker threads. In 64-bit world on a decent server it shouldn't be
a problem to have 10-20 out of the box.
I don't mind having to failover multiple database residing on the same instance and having to setup them per DB.
If any of your databases have a dependency on one another, this isn't going to work well as one database could be failed over and another might not be. Just food for thought.
What it sound like you really want is a failover cluster instance and use log shipping to have a "readable copy" somewhere even if it is behind on time. The problem comes in is that a cluster all has to be in the same domain and part of the same
cluster. Your thoughts involve a separate cluster - so I'm not sure why two different ones unless you have multiple environments you're trying to add some HA to.
-Sean
The views, opinions, and posts do not reflect those of my company and are solely my own. No warranty, service, or results are expressed or implied.

Always on Availability on 2 different SQL Server clusters

SQL Server 2012 EE on WIndows 2008 R2.
Is it possible to have Always on Availability on 2 different SQL Server clusters ?. Could 2 SQL Server clusters be on 1 Windows server failover cluster (WSFC) ?. We have a Prod domain and DR01 domain with 3 nodes SQL Server clusters each. How can we setup
Always On Availability groups on these clusters to make replica of Production databases on the Prod to DR01 domain cluster ?. What do we need to do to get this working ?...................Thanks.

DCarlos unfortunately the requirement for AlwaysOn Availability Groups are a Single Domain, A single WSFC. The WSFC in multiple sites is supported with either a stretched VLan or multiple Subnets.
If your environment does require you to have different Domains for Prod and DR then you would have to look at potentially other ways of achieving your data replicated across from prod to DR.
You could look at using Database Mirroring (Yes I know this has been marked for deprecation) to achieve your data transfer. Or depending on your RPO and RTO requirements Logshipping may be an option.
Thanks
Warwick Rudd (MCM - SQL 2008 | MCT)
(SQL Masters Consulting |
My SQL Server Blog | Twitter)

Unable to capture SQL Server Schema

I am trying to capture SQL Server 2005 demo schema (AdventureWorks). It does shows the numbers of Tables/Indexes captured..but finishes with this error..
Error ocurred during capture: Exhausted Resultset
Column not found. Skipping index detail on index 'IX_StoreContact_ContactTypeID'
Column not found. Skipping index detail on index 'IX_StoreContact_ContactID'
Column not found. Skipping index detail on index 'AK_StoreContact_rowguid'
Column not found. Skipping index detail on index 'IX_ProductVendor_VendorID'
Column not found. Skipping index detail on index 'IX_ProductVendor_UnitMeasureCode'
Column not found. Skipping index detail on index 'IX_Address_StateProvinceID'
Column not found. Skipping index detail on index 'IX_Address_AddressLine1_AddressLine2_City_StateProvinceID_PostalCode'
Column not found. Skipping index detail on index 'IX_Address_AddressLine1_AddressLine2_City_StateProvinceID_PostalCode'
Column not found. Skipping index detail on index 'IX_Address_AddressLine1_AddressLine2_City_StateProvinceID_PostalCode'
Column not found. Skipping index detail on index 'IX_Address_AddressLine1_AddressLine2_City_StateProvinceID_PostalCode'
Column not found. Skipping index detail on index 'IX_Address_AddressLine1_AddressLine2_City_StateProvinceID_PostalCode'
Column not found. Skipping index detail on index 'AK_Address_rowguid'
Column not found. Skipping index detail on index 'AK_Department_Name'
Any help is appreciated..
Ajay

Hi Nandu,
As your description, you come across an error(vsjitdebugger.exe cannot be found). Please confirm if the error occurs during the installation of SQL Server 2012. If so, please help post SQL Server setup logs. By default, SQL Server setup log file locates
in C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log.
Base on my research, this error could be caused by that the previous uninstallation is improper and vsjitdebugger.exe file could be mistakenly deleted.
To troubleshoot the issue, you could start your computer into Safe Mode and fix your problem with one of the following methods. For more information, please refer to the article:
http://www.fixerrorkit.com/fix-error/fix-vsjitdebugger.exe-error.html.
1. You could execute the sfc /scannow command following steps below.
a. Press "Windows+R", type in cmd and then right click "Run as administrator"
b. Type in sfc /scannow (There's a space between sfc and /scannow) into the dialog and hit Enter key and click ok.
c. Wait until the System File Checker finishes the check.
2. You could use a Windows repair installation, also known as a Startup Repair to repair your Windows system files.
3. You could install the latest Windows updates to fix vsjitdebugger.exe error. Microsoft often releases new service packs and system patches to replace or update some DLL files of Windows system.
4. You could use third-party tool such as Automatic Error Fix Tool to fix your vsjitdebugger.exe error. However, Microsoft cannot make any representations regarding the quality, safety, or suitability of any third-party software or information found there.
In addition, if you are unable to install Visual Studio, I suggest you post your question in Visual Studio Setup and Installation forum at
https://social.msdn.microsoft.com/Forums/vstudio/en-US/home?forum=vssetup . It is appropriate and more experts will assist you.
Regards,
Michelle Li

How do I connect to SQL Server with Muse?

I want to query items from database and load it back to front end. Is there a way Muse can connect to sql server database?

You cannot connect to databases via Muse at the moment. Please refer: http://forums.adobe.com/message/5090145#5090145
Cheers,
Vikas

I am trying to have access tables of the Sql Server through the Oracle

I am trying to have access tables of the Sql Server through the Oracle and this being occurred the error:
ORA-28500: connection from ORACLE to a non-Oracle system returned this message: [Generic Connectivity using ODBC][H006] The init parameter <HS_FDS_CONNECT_INFO> is not set.
Please set it in init <orasid>.ora file.
ORA-02063: preceding 2 lines from HSMSQL
I created the ODBC with name HSMSQL.
I made all the configurations in the archives
tnsnames.ora:
HSMSQL=
(DESCRIPTION=
(ADDRESS= (PROTOCOL = tcp)(HOST = wsus)(PORT = 1521))
(CONNECT_DATA =
(SID = HSMSQL)
(HS = OK)
listener.ora:
(SID_DESC = (SID_NAME=HSMSQL)
(ORACLE_HOME= C:\oracle\ora92)
(PROGRAM =hsodbc)
initHS_SID.ora:
HS_FDS_CONNECT_INFO = HSMSQL
HS_FDS_TRACE_LEVEL = OFF
-- Create database link
create database link HSMSQL.US.ORACLE.COM
connect to TESTE identified by TESTE2
using 'HSMSQL';
But when I execute query the error occurs:
Select * from TabTeste@HSMSQL
ORA-28500: connection from ORACLE to a non-Oracle system returned this message: [Generic Connectivity using ODBC][H006] The init parameter <HS_FDS_CONNECT_INFO> is not set.
Please set it in init <orasid>.ora file.
ORA-02063: preceding 2 lines from HSMSQL
Please they help me, thanks, Paulo.

Hi,
It seems that your configuration is Ok. By the way, the workaround for this error is:
ORA-28500: connection from ORACLE to a non-Oracle system returned this message:
[Transparent gateway for ODBC][H001] The environment variable <HS_FDS_CONNECT_INFO> is not set.
* Set HS_FDS_CONNECT_INFO in the hs{sid}init.ora file to the data source name.
Example: HS_FDS_CONNECT_INFO = <ODBC DataSource Name>
* Make sure the hs{sid}init.ora file exists in the ORACLE_HOME/hs/admin directory and has the same name as the SID in the LISTENER.ORA.
Example: If SID=hsodbc in the listener.ora file, then the hs{sid}init.ora file would be named ORACLE_HOME/hs/admin/inithsodbc.ora
For more information see if this [url http://forums.oracle.com/forums/thread.jspa?forumID=61&threadID=576975]thread can help you.
Cheers

Interface with SQL server

Hi,
I want to get data from SQL server on demand from SAP server and run a report in SAP.
Can anyone help me how to get data from SQL server?
Thanks,
Ashok.

Ashok,
I am not sure how it is done for SQL server, but here is a thread that discussed about a similar requirement with a Access database. Take a look.
SQ02 SAP Query
Regards,
Ravi
Note : Please mark the helpful answers

How can I load a .xlsx File into a SQL Server Table using a Foreach Loop Container in SSIS?

I know I've REALLY struggled with this before. I just don't understand why this has to be soooooo difficult.
I can very easily do a straight Data Pump of a .xlsX File into a SQL Server Table using a normal Excel Connection and a normal Excel Source...simply converting Unicode to DT_STR and then using an OLE DB Destination of the SQL Server Table.
If I want to make the SSIS Package a little more flexible by allowing multiple .xlsX spreadsheets to be pumped in by using a Foreach Loop Container, the whole SSIS Package seems to go to hell in a hand basket. I simply do the following...
Put the Data Flow Task within the Foreach Loop Container
Add the Variable Mapping Variable User::FilePath that I defined as a Variable and a string within the FOreach Loop Container
I change the Excel Connection and its Expression to be ExcelFilePath ==> @[User::FilePath]
I then try and change the Excel Source and its Data Access Mode to Table Name or view name variable and provide the Variable Name User::FilePath
And that's when I run into trouble...
Exception from HRESULT: 0xC02020E8
Error at Data Flow Task [Excel Source [56]]:SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occured. Error code: 0x80004005.
Error at Data Flow Task [Excel Source [56]]: Opening a rowset for "...(the EXACT Path and .xlsx File Name)...". Check that the object exists in the database. (And I know it's there!!!)
I don't understand by adding a Foreach Loop Container to try and make this as efficient as possible has caused such an error unless I'm overlooking something. I have even tried delaying my validations and that doesn't seem to help.
I have looked hard in Google and even YouTube to try and find a solution for this but for the life of me I cannot seem to find anything on pumping a .xlsX file into SQL Server using a Foreach Loop Container.
Can ANYONE please help me out here? I'm at the end of my rope trying to get this to work. I think the last time I was in this quandry, trying to pump a .xlsX File into a SQL Server Table using a Foreach Loop Container in SSIS, I actually wrote a C# Script
to write the contents of the .xlsX File into a .csv File and then Actually used the .csv File to pump the data into a SQL Server Table.
Thanks for your review and am hoping and praying for a reply and solution.

Hi ITBobbyP,
If I understand correctly, you want to load data from multiple sheets in an .xlsx file into a SQL Server table.
If in this scenario, please refer to the following tips:
The Foreach Loop container should be configured as shown below:
Enumerator: Foreach ADO.NET Schema Rowset Enumerator
Connection String: The OLE DB Connection String for the excel file.
Schema: Tables.
In the Variable Mapping, map the variable to Sheet_Name, and change the Index from 0 to 2.
The connection string for Excel Connection Manager is the original one, we needn’t make any change.
Change Table Name or View name to the variable Sheet_Name.
If you want to load data from multiple sheets in multiple .xlsx files into a SQL Server table, please refer to following thread:
http://stackoverflow.com/questions/7411741/how-to-loop-through-excel-files-and-load-them-into-a-database-using-ssis-package
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Error while installing SQL Server 2012 X64 SP2,

Error while installing SQL Server 2012 X64 SP2,
When I installed the SQL Server 2012 X64 SP1, I got the attached error.
What might be the issue here?
Thank you
Best
Jamal

Hello,
Are you trying to install SQL Server on a compressed or encrypted drive? SQL Server won’t install on a drive/folder with these attributes.
Are you trying to install SQL Server on a ReFS file system? It is not supported on SQL Server 2012.
Disable any security/antivirus software and download the media again. Mount the media (.ISO file) and try to install again.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Sql server logshipping

Similar Messages

Maybe you are looking for