MS SQL backup

Hi,
I really have looked for this, but I cannot seem to find it. I want to do a full database backup of our SQL database, once a week, and I want it to be set up to do this automatically. I can find where to do a full backup, but cannot find where to set this up to do it by itself each week. Can someone help?
Thanks,
Jim

Hi,
are you planning to take backup on SQL server is on tape or disk drive?
if you are planning to take backup on disk then check following thread.
Re: how to change Tape to Disk for backup(via DB13) on MSSQL server
Using DB13 tcode you can schedule full online backup weekly.
backup via transaction DB13 is quite simple:
- Call the transaction DB13
- Choose the 'ADD' button of the calendar
- Now you get a popup, where you can select various kinds of jobs via listbox
- Choose the backup you want to execute (e.g. backup to device/backup to TSM)
- Set the backup parameters, e.g. set the device name, choose backup option like 'Online/Offline', 'Including Logs' etc.
- Set the start time
Then add it
you can check backup log using tcode DB12,
regards,
kaushal
Edited by: kaushal malavia on Mar 19, 2008 10:44 AM

Similar Messages

DPM failing SQL backups due to error: "the SQL Server instance refused a connection to the protection agent. (ID 30172 Details: Internal error code: 0x80990F85)

I ran across this error starting on 6/4/2011 and have been unable to find the root of the problem. In our environment, we have a DPM 2010 server dedicated to backing up all our SQL envrionment (about 45 SQL Servers total). All of the SQL
environment is backing up fine except for a SQL Cluster Application. This particular SQL Instances is part of a 6 node failover cluster with 6 SQL Instances distributed amongst them. The other 5 SQL instances in the cluster are backing
up fine; only one instance is failing. The DPM Alerts section shows this error when attempting to do a SQL backup of one of the databases on this SQL instance:
Affected area: KEN-PROD-VDB001\POSREPL1\master
Occurred since: 6/11/2011 11:00:56 PM
Description: Recovery point creation jobs for SQL Server 2008 database KEN-PROD-VDB001\POSREPL1\master on SQL Server (POSREPL1) - Store Settings.ken-prod-cl004.aarons.aaronrents.com have been failing. The number of failed recovery point creation jobs =
4.
If the datasource protected is SharePoint, then click on the Error Details to view the list of databases for which recovery point creation failed. (ID 3114)
The DPM job failed for SQL Server 2008 database KEN-PROD-VDB001\POSREPL1\master on SQL Server (POSREPL1) - Store Settings.ken-prod-cl004.aarons.aaronrents.com because the SQL Server instance refused a connection to the protection agent. (ID 30172 Details:
Internal error code: 0x80990F85)
More information
Recommended action: This can happen if the SQL Server process is overloaded, or running short of memory. Please ensure that you are able to successfully run transactions against the SQL database in question and then retry the failed job.
Create a recovery point...
Resolution: To dismiss the alert, click below
Inactivate alert
I have checked the cluster node this particular SQL instance is running on using Perfmon and the machine is nowhere near capacity on CPU, memory, network, or Disk I/O.  I have failed this SQL Application to another node in the cluster and
receive the same error (this other node has another clustered SQL application on it that is actively running as well as backing up fine). The only thing that I am aware of that has changed is that we installed SP2 for SQL 2008 about 2 weeks prior
to when the failures started to occur. However, we updated all six clustered SQL Instances at the same time and only this one is having this issue so I don't believe that caused the problem. We are running SQL 2008 SP2 (version 10.0.4000.0)
on all clustered instances along with DPM 2010 (version 3.0.7696.0) on this particular DPM server that has the issue.
One last thing, I have also noticed errors in the event log pertaining to the same SQL backups that are failing (but the time stamps are not concurrent with each backup attempt):
Log Name:      Application
Source:        MSDPM
Date:          6/13/2011 1:09:12 AM
Event ID:      4223
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      KEN-PROD-BS002.aarons.aaronrents.com
Description:
The description for Event ID 4223 from source MSDPM cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
DPM writer was unable to snapshot the replica of KEN-PROD-VDB001\POSREPL1\model. This may be due to:
1) No valid recovery points present on the replica.
2) Failure of the last express full backup job for the datasource.
3) Failure while deleting the invalid incremental recovery points on the replica.
Problem Details:
<DpmWriterEvent><__System><ID>30</ID><Seq>1833</Seq><TimeCreated>6/13/2011 5:09:12 AM</TimeCreated><Source>f:\dpmv3_rtm\private\product\tapebackup\dpswriter\vssfunctionality.cpp</Source><Line>815</Line><HasError>True</HasError></__System><DetailedCode>-2147212300</DetailedCode></DpmWriterEvent>
the message resource is present but the message is not found in the string/message table
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="MSDPM" />
    <EventID Qualifiers="0">4223</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2011-06-13T05:09:12.000000000Z" />
    <EventRecordID>68785</EventRecordID>
    <Channel>Application</Channel>
    <Computer>KEN-PROD-BS002.aarons.aaronrents.com</Computer>
    <Security />
</System>
<EventData>
    <Data>DPM writer was unable to snapshot the replica of KEN-PROD-VDB001\POSREPL1\model. This may be due to:
1) No valid recovery points present on the replica.
2) Failure of the last express full backup job for the datasource.
3) Failure while deleting the invalid incremental recovery points on the replica.
Problem Details:
<DpmWriterEvent><__System><ID>30</ID><Seq>1833</Seq><TimeCreated>6/13/2011 5:09:12 AM</TimeCreated><Source>f:\dpmv3_rtm\private\product\tapebackup\dpswriter\vssfunctionality.cpp</Source><Line>815</Line><HasError>True</HasError></__System><DetailedCode>-2147212300</DetailedCode></DpmWriterEvent>
</Data>
    <Binary>3C00440070006D005700720069007400650072004500760065006E0074003E003C005F005F00530079007300740065006D003E003C00490044003E00330030003C002F00490044003E003C005300650071003E0031003800330033003C002F005300650071003E003C00540069006D00650043007200650061007400650064003E0036002F00310033002F003200300031003100200035003A00300039003A0031003200200041004D003C002F00540069006D00650043007200650061007400650064003E003C0053006F0075007200630065003E0066003A005C00640070006D00760033005F00720074006D005C0070007200690076006100740065005C00700072006F0064007500630074005C0074006100700065006200610063006B00750070005C006400700073007700720069007400650072005C00760073007300660075006E006300740069006F006E0061006C006900740079002E006300700070003C002F0053006F0075007200630065003E003C004C0069006E0065003E003800310035003C002F004C0069006E0065003E003C004800610073004500720072006F0072003E0054007200750065003C002F004800610073004500720072006F0072003E003C002F005F005F00530079007300740065006D003E003C00440065007400610069006C006500640043006F00640065003E002D0032003100340037003200310032003300300030003C002F00440065007400610069006C006500640043006F00640065003E003C002F00440070006D005700720069007400650072004500760065006E0074003E00</Binary>
</EventData>
</Event>
Any help would be greatly appreciated!

Don't know if this helps or not, but I also noticed another peculiar issue that is derived from this problem. If I go to "Modify protection group", then expand the cluster, then expand all six nodes in the cluster, five of them show "All SQL Servers"
and allow me to expand the SQL Instance and show all databases; the one that is having a problem backing up, when I expand the node, doesn't even show that SQL exists on the node, when in fact, it does.
I would also like to add that the databases on this node that will not backup are running fine. They run hundreds of transactions daily so we know SQL itself is OK. Even though it is a busy SQL Server, there is plenty of available resources as
the SQL buffer and memory counters show the node is not under durress.

Advice on SQL Backup POC tests

Hello,
We are going to be performing a POC for backup software. I don't know much about restoring SQL2008 and SQL2010 so I would like to know what tests SQL pros would want to see succeed before approving a solution. One of our DBAs will be participating later in
the process.
Thanks,
Robert

Robert,
Just as an FYI - there is no such thing as "SQL2010".
Most backup software uses an agent and runs through VSS which is great if you want to backup windows, but isn't so great when it comes to SQL Server.
Things to watch out for:
1. The need of point in time recovery: While VSS does support this for SQL Server, it will not truncate the logs which means some other process will need to be run if the database is in full or bulk logged recovery model.
2. Use of Log shipping in the environment: Since part of log shipping is to take log backups and "ship" them to other servers, your essentially making this null and void. This is because SQL Server takes the log backups (which your software will now take
over doing) and puts them somewhere (configurable). Since the software will be taking over, it'll either need to have the ability to do the file movement needed for log shipping or you'll pretty much have to abandon the use of it. Also, see point #1 as log
shipping require the full or bulk_logged recovery model.
3. The use of Availability Groups in the environment: Akin to #2, backups can be taken on databases in an availability group. VSS does not take this into account as it doesn't need to. This is a SQL Server level item, not an OS level item. You'll somehow
need to build logic into the agent to first check and see if the database is part of an availability group, then check to see where the preferred backup place is, then if both are good take the backup. It also won't truncate the log as per #1 since availability
groups need the full recover model. (See a pattern?)
4. Differential: AFAIK since this is at a SQL Server level, it's not possible with VSS or agents unless the agent issues T-SQL Backup commands... at which point why run an agent or buy backup software?
5. File, Filegroup, ReadOnly filegroups, etc: See #4 for the same reason.
So that's just a few things to think about for backups, now for restores:
1. Does the software support restoring to other servers with dissimilar drive layouts?
2. Does the software support leaving databases to a point in time recovery not at a restore point? For example, at 2:53:02.666 AM or at a marked transaction (if those are used)?
3. Does the software support truncating logs after a log backup is complete?
4. Does the software support native backups with copy_only to not break log chains when needing to send to a vendor or otherwise take an out of band backup?
5. Does the software support piecemeal or partial restores (if enterprise edition and backup strategy supports it) for larger or more important databases?
Now for some admin (non-technical) items...
1. Who will be in charge of backups?
2. Who will be in charge of restores?
3. Who and how will people get/be notified if a backup fails?
4. Will your SLAs be blown if VSS has an issue (which generally required a reboot to fix) and database can't be backed up?
5. Is it possible to get a native backup out of the system if another team, project, or company needs it?
It might seem simple at first, I mean it's just a backup right... but there is definitely more going on depending on needs. If you're the kind of company that does simple recovery model for everything and plain vanilla the rest of the way - you might not
have any issues and pretty much anything will work for you. If you're the kind of company that runs different configurations, have dev environments that need refreshed daily or weekly, use any advanced features of current t-sql based backups, etc, you'll probably
end up not using the agent for the backup software and just sweeping disk or something of the like.
Good luck.
Sean Gallardy | Blog |
Twitter

SQL Backup fails with error 87 parameter incorrect

I have a SQL Server 2008 R2 SP2 Standard instance working great, except upon attempts to use SQL backup to a UNC path hosted on Server 2012 R2, backup jobs fail with error 87 (the parameter is incorrect). When backing up to Server 2008 R2 and Server 2012
shares, everything seems to work normally.
Any experience with something like this? I've verified perms to the path and reachability in general, and it's clearly not an access denied error (which I've seen before).

Thanks Alberto - I've verified that user (it's a domain user) has full access perms on that path, and tested outside of SSMS.
Detailed error:
System
- Provider
[ Name] MSSQLSERVER
- EventID 18210
[ Qualifiers] 49152
Level 2
Task 6
Keywords 0x80000000000000
- TimeCreated
[ SystemTime] 2014-05-13T15:57:52.000000000Z
EventRecordID 2083317
Channel Application
Computer GriffinSQL.[local domain here]
- Security
[ UserID] [guid here]
- EventData
BackupIoRequest::ReportIoError
write
\\storage\backups\sql\testggg.bak
87(The parameter is incorrect.)
22470000100000000B0000004700520049004600460049004E00530051004C00000000000000
Binary data:
In Words
0000: 00004722 00000010 0000000B 00520047
0008: 00460049 00490046 0053004E 004C0051
0010: 00000000 0000
In Bytes
0000: 22 47 00 00 10 00 00 00 "G......
0008: 0B 00 00 00 47 00 52 00 ....G.R.
0010: 49 00 46 00 46 00 49 00 I.F.F.I.
0018: 4E 00 53 00 51 00 4C 00 N.S.Q.L.
0020: 00 00 00 00 00 00 ......

SCCM 2012 SP1 - Native SQL backup

HI Experts,
I got native SCCM 2012 SP1 SQL backup content (But no site server backup). Can i still restore the SCCM 2012 SP1 primary site server. Please advice
Regards, Pratap

With Configuration Manager 2012 SP1+, it is possible to recover a site (secondary sites don’t count) using a standard, native SQL Server database backup.
"Configuration Manager can recover the site database from the Configuration Manager backup maintenance task or from a site database backup that you perform by using another process. For example, you can restore the site database from a backup that is performed
as part of a Microsoft SQL Server maintenance plan. Starting in Configuration Manager SP1, you can restore the site database from a backup that is performed by using System Center 2012 Data Protection Manager (DPM). For more information,
see
Using Data Protection Manager to Back up Your Site Database."
http://technet.microsoft.com/en-us/library/gg712697.aspx#BKMK_SiteDatabaseRecoveryOption

Backup using Backup-SPFarm alongside SQL backups

Hi all,
At present I have SharePoint 2010 running on a server with it's databases off on a SQL server that hosts not only the SharePoint databases but a load more as well. I have full and transaction log backups of the databases running via the native SQL
tools, so the databases for SharePoint are covered.
Knowing that this doesn't cover me in a disaster from the SharePoint side I'm going to use Backup-SPFarm as well, but in my testing I've noticed that Backup-SPFarm and SQL native backups get into a bit of an argument when it comes to diff backups:
"The previous full SQL backup for the database Search_Service_Application_LinksStoreDB_28ce0f29952746c2931decf12e91a0e1 was performed by another backup tool and may not be restored correctly."
So what I'm currently planning on doing is leaving SQL to handle the database level backups, and to use Backup-SPFarm with the configurationonly switch. That way in the event of an emergency I would restore the dbs and then restore the SP backup.
My question really is then, will this work? Is doing the Backup-SPFarm with configurationonly switch plus the SQL backups (plus a backup of the VM running SharePoint to get web.configs etc) enough, or does running configurationonly actually stop something
else essential from backing up as well that I haven't now accounted for?
Many thanks,
Luke

The OP's question was about Backup-SPFarm with the -configurationonly switch. In that case, Backup-SPFarm certainly does not do "full/incremental SQL database backups," and cannot "replace the standard SQL backup tools for SharePoint databases."
Backup-SPFarm -configurationonly has significant limitations and cannot be used as your only form of farm configuration backup. (Limitations are detailed
here.)
In regards to backing up VMs, backing up VMs *is* supposed to be supported in certain contexts. According to
Technet, "you can create a warm standby solution by making sure that you consistently and frequently create virtual images of the servers in your farm that you ship to a secondary location."
I discussed this very question with a Microsoft PFE who said that using VM snapshots as a disaster-recovery component is not supported. (He referenced
this article.) I asked him about the conflict between the article and TechNet, and he said that TechNet is authoritative.
The key is that your snapshots must be taken of the entire SharePoint stack with all your farm servers and SQL shut down. This limitation means that content freshness will be an issue on restore, but in my opinion, it should be possible to find a DR solution
that utilizes a combination of cold VM snapshots and content freshening from content DB backups.
It would need careful testing for your specific environment, however.

VSS snapshots for DPM 2010 Hyper-V backup conflict with SQL backup on a virtual SQL server

We currently use DPM 2010 to backup our virtual servers which reside on a 5 node Hyper-V clustered share volume. DPM uses the hardware VSS writer to backup the Hyper-V guests. Several of these Hyper-V guests are SQL servers (SQL 2008) and they
are all configured to run point in time SQL backups using SQL Management Plans.
The SQL backups are scheduled to run a full database backup on a Friday and differential backups on the other days of the week. Transaction backups are scheduled to run several times throughout the day.
However we have recently discovered that there is a conflict between these two methods as it seems as though when a restore is required using a differential SQL backup, it fails as the snapshot created by DPM forces SQL to believe it has had a full backup
carried out externally from the Management Plan and is therefore unable to perform the restore.
DPM backs up the Hyper-V guests on a daily basis from 8pm.
Can anyone provide any advice or guidance on this as we need both types of backup to run successfully. We are required to backup SQL with point in time backups and we also need to protect the Hyper-V guests in their entirety.

Thanks Mike,
I have tried this but unfortunately it has no effect. The VM has Oracle installed (although not the Oracle VSS Writer). It is the Oracle application server, not the database server, and the customer has a script that is used to stop and start
the Oracle application when required. Through troubleshooting this with them I have noticed that after the WLS_Reports service/process is stopped the backups run successfully but when it is running the backups fail.
I have also noticed that when I stop the Hyper-V Volume Shadow Copy Requestor the backup runs successfully, which I guess is as expected.
When the backups fail I get 2 errors in the application log:
Event Id 12293, VSS - Error calling a routine on a shadow copy provider {GUID for the Hyper-V IC Software Shadow Copy Provider}. Routine details PreFinalCommitSnapshots ({GUID}, 5) [hr = 0x800705b4, This operation returned because
the timeout period expired.]
Event Id 19, vmicvss - Not all the shadow volumes arrived in the guest operating system.
This is also part of the same problem I have posted here: Backup
fails for a Hyper-V guest with VSS Writer failures using DPM 2012 R2 - Hyper-V guest has Oracle application installed
Regards
Chris

SAP ECC6.0 on SQL BACKUP ISSUE THROUGH DB13

Dear All,
My SAP Environment is : Windows Server 2003
Database : SQL2005
SAP version: ECC6.0 SR3
I am in process to configure backup system of Development server through DB13 but i am getting the below error : -
Jobname:    SAP CCMS Full DB Backup of DEV [20090618113720-4-113720]
Type:       TSQL
DB-Name:    DEV
For Run:    20090618 11:37:20
Job history information *****************************
Stepname:   CCMS-step 1
Command:    declare @exeStmt nvarchar(2000) exec dev.sap_backup_databases @dbList=
            "DEV",@r3Db="DEV",@bDev="R3DUMP0",@expDays= 27,@jobName= "SAP CCMS Ful
            l DB Backup of DEV [20090618113720-4-113720]",@bkupChecksum="N",@bkupT
            ype="F",@nativeBkup="N",@exeDate = "20090618113720",@bkupSim = "N",@fo
            rmat = 0,@init = 1,@bkupDb = "DEV",@unload = 0,@exeStmt = @exeStmt OUT
            PUT
Status:     (failure)
Message:    2528
Severity:                                                                                16
Duration:   0 hours(s) 0 min(s) 1 sec(s)
Last msg:   Executed as user: NT AUTHORITY\SYSTEM. Mount tape for BACKUP DATABASE
            of database 'DEV' on tape drive '
.\tape0'. [SQLSTATE 42000] (Error 4
            027) DBCC execution completed. If DBCC printed error messages, contac
            t your system administrator. [SQLSTATE 01000] (Error 2528). The step
            failed.
                    <----
End of Job Step History -
>
Job history information *****************************
but i am able to take backup on tape through SQL Server management studio.
Do we have to do some steps before scheduling backup through DB13 ?
Please suggest.
Regards,
Rohit

Hi Markus,
Thanks for reply.
No i have not provide any speacial permission to user SAPServiceDEV by default this user is member of : SAP_DEV_GlobalAdmin , SAP_DEV_LocalAdmin , SAP_LocalAdmin , User group.
Which permission i have to assign to this user?
kindly suggest.
Thanks in advance.
Rohit

Sql backup best practice on vms that are backed up as a complete vm

hi,
apologies as i am sure this has been asked many times before but i cant really find an answer to my question. so my situation is this. I have two types of backups; agent based and snap based backups.
For the vm's that are being backed up by snapshots the process is: vmware does the snap, then the san takes a snap of the storage and then the backup is taken from the san. we then have full vm backups.
For the agent based backups, these are only backing up file level stuff. so we use this for our sql cluster and some other servers. these are not snaps/full vm backups, but simply backups of databases and files etc.
this works well, but there are a couple of servers that need to be in the full vm snap category and therefore cant have the backup agent installed on that vm as it is already being backed up by the snap technology. so what would be the best practice on these
snapped vms that have sql installed as well? should i configure a reoccurring backup in sql management studio (if this is possible??) which is done before the vm snap backup? or is there another way i should be backing up the dbs?
any suggestions would be very welcome.
thanks
aaron

Hello Aaron,
If I understand correctly, you perform a snapshot backup of the complete VM.
In that case you also need to create a SQL Server backup schedule to perform Full and Transaction Log backups.
(if you do a filelevel backup of the .mdf and .ldf files with an agent you also need to do this)
I would run a database backup before the VM snapshot (to a SAN location if possible), then perform the Snapshot backup.
You should set up the transaction log backups depending on business recovery needs.
For instance: if your company accepts a maximum of 30 minutes data loss make sure to perform a transaction log backup every 30 minutes.
In case of emergency you could revert to the VM Snapshot, restore the full database backup and restore transaction log backups till the point in time you need.

List sql backups in a folder then restore the selected backup to the selected database

Hi
I'm created a script that lists the backups in a folder then allows user input to select a backup.
It then needs to list the sql database on a specific server and accepts user input.
I can list the backups as follows
$Dir = get-childitem $CurDir -recurse
$List = $Dir | where {$_.extension -eq ".bak"}
$List | format-table name
but what I want to know is how to format the list to have a number for the selection next to it?
How can I get a list of the sql databases on the server.
Thanks
Wayne

Hi Wayne,
I’m writing to just check in to see
if the suggestions were helpful. If you need further help, please feel free to reply this post directly so we will be notified to follow it up.
If you have
any feedback on our support, please click here.
Best Regards,
Anna Wang
TechNet Community Support

Sql backup detected corruption in database log

Unfortunately I am not a SQL Admin. I have moderate SQL experience at best.
I have four or five database in SQL 2005 that were the primary members of a mirror. The physical server (the one I am currently working on) was virtualized (P2V) then started as a virtual machine. Downtime was minimal. Maybe an hour or so
I believe.
Although I didn't check immediately after boot up, I have since noticed the mirror status is suspended. Attempts to resume fail. It appears my best bet is to backup the database, restore on the target, then recreate the mirror. The problem
is, attempts to run a Full backup of the database returns the following error on all the database I've tried to backup. After about 20% is says: SystemData.SqlClient.SqlError: BACKUP detected corruption in the database log. Check the errorlog for
more information. (Microsoft.SqlServer.Smo)
I've tried setting the recovery type to Simple, but that fails telling me the database is part of a mirror and to be honest I'm not sure setting to Simple is the best option.
As it stands, the mirror is broken and I can not perform a full backup.
Any suggestions on how to proceed are greatly appreciated.
Thank you.

Thank you Uri. Following are the results. Again, I'm not a SQL Admin but it appears this does not indicate errors?
DBCC results for 'TAIQRY'.
Service Broker Msg 9675, State 1: Message Types analyzed: 14.
Service Broker Msg 9676, State 1: Service Contracts analyzed: 6.
Service Broker Msg 9667, State 1: Services analyzed: 3.
Service Broker Msg 9668, State 1: Service Queues analyzed: 3.
Service Broker Msg 9669, State 1: Conversation Endpoints analyzed: 0.
Service Broker Msg 9674, State 1: Conversation Groups analyzed: 0.
Service Broker Msg 9670, State 1: Remote Service Bindings analyzed: 0.
DBCC results for 'sys.sysrowsetcolumns'.
There are 546 rows in 5 pages for object "sys.sysrowsetcolumns".
DBCC results for 'sys.sysrowsets'.
There are 80 rows in 1 pages for object "sys.sysrowsets".
DBCC results for 'sysallocunits'.
There are 93 rows in 1 pages for object "sysallocunits".
DBCC results for 'sys.sysfiles1'.
There are 2 rows in 1 pages for object "sys.sysfiles1".
DBCC results for 'sys.syshobtcolumns'.
There are 546 rows in 5 pages for object "sys.syshobtcolumns".
DBCC results for 'sys.syshobts'.
There are 80 rows in 1 pages for object "sys.syshobts".
DBCC results for 'sys.sysftinds'.
There are 0 rows in 0 pages for object "sys.sysftinds".
DBCC results for 'sys.sysserefs'.
There are 93 rows in 1 pages for object "sys.sysserefs".
DBCC results for 'sys.sysowners'.
There are 15 rows in 1 pages for object "sys.sysowners".
DBCC results for 'sys.sysprivs'.
There are 135 rows in 1 pages for object "sys.sysprivs".
DBCC results for 'sys.sysschobjs'.
There are 86 rows in 1 pages for object "sys.sysschobjs".
DBCC results for 'sys.syscolpars'.
There are 579 rows in 10 pages for object "sys.syscolpars".
DBCC results for 'sys.sysnsobjs'.
There are 1 rows in 1 pages for object "sys.sysnsobjs".
DBCC results for 'sys.syscerts'.
There are 0 rows in 0 pages for object "sys.syscerts".
DBCC results for 'sys.sysxprops'.
There are 9 rows in 1 pages for object "sys.sysxprops".
DBCC results for 'sys.sysscalartypes'.
There are 27 rows in 1 pages for object "sys.sysscalartypes".
DBCC results for 'sys.systypedsubobjs'.
There are 0 rows in 0 pages for object "sys.systypedsubobjs".
DBCC results for 'sys.sysidxstats'.
There are 151 rows in 2 pages for object "sys.sysidxstats".
DBCC results for 'sys.sysiscols'.
There are 266 rows in 2 pages for object "sys.sysiscols".
DBCC results for 'sys.sysbinobjs'.
There are 23 rows in 1 pages for object "sys.sysbinobjs".
DBCC results for 'sys.sysobjvalues'.
There are 187 rows in 27 pages for object "sys.sysobjvalues".
DBCC results for 'sys.sysclsobjs'.
There are 14 rows in 1 pages for object "sys.sysclsobjs".
DBCC results for 'sys.sysrowsetrefs'.
There are 0 rows in 0 pages for object "sys.sysrowsetrefs".
DBCC results for 'sys.sysremsvcbinds'.
There are 0 rows in 0 pages for object "sys.sysremsvcbinds".
DBCC results for 'sys.sysxmitqueue'.
There are 0 rows in 0 pages for object "sys.sysxmitqueue".
DBCC results for 'sys.sysrts'.
There are 1 rows in 1 pages for object "sys.sysrts".
DBCC results for 'sys.sysconvgroup'.
There are 0 rows in 0 pages for object "sys.sysconvgroup".
DBCC results for 'sys.sysdesend'.
There are 0 rows in 0 pages for object "sys.sysdesend".
DBCC results for 'sys.sysdercv'.
There are 0 rows in 0 pages for object "sys.sysdercv".
DBCC results for 'sys.syssingleobjrefs'.
There are 140 rows in 1 pages for object "sys.syssingleobjrefs".
DBCC results for 'sys.sysmultiobjrefs'.
There are 131 rows in 1 pages for object "sys.sysmultiobjrefs".
DBCC results for 'sys.sysdbfiles'.
There are 2 rows in 1 pages for object "sys.sysdbfiles".
DBCC results for 'sys.sysguidrefs'.
There are 0 rows in 0 pages for object "sys.sysguidrefs".
DBCC results for 'sys.sysqnames'.
There are 91 rows in 1 pages for object "sys.sysqnames".
DBCC results for 'sys.sysxmlcomponent'.
There are 93 rows in 1 pages for object "sys.sysxmlcomponent".
DBCC results for 'sys.sysxmlfacet'.
There are 97 rows in 1 pages for object "sys.sysxmlfacet".
DBCC results for 'sys.sysxmlplacement'.
There are 17 rows in 1 pages for object "sys.sysxmlplacement".
DBCC results for 'sys.sysobjkeycrypts'.
There are 0 rows in 0 pages for object "sys.sysobjkeycrypts".
DBCC results for 'sys.sysasymkeys'.
There are 0 rows in 0 pages for object "sys.sysasymkeys".
DBCC results for 'sys.syssqlguides'.
There are 0 rows in 0 pages for object "sys.syssqlguides".
DBCC results for 'sys.sysbinsubobjs'.
There are 0 rows in 0 pages for object "sys.sysbinsubobjs".
DBCC results for 'sysdiagrams'.
There are 0 rows in 0 pages for object "sysdiagrams".
DBCC results for 'sys.queue_messages_1977058079'.
There are 0 rows in 0 pages for object "sys.queue_messages_1977058079".
DBCC results for 'sys.queue_messages_2009058193'.
There are 0 rows in 0 pages for object "sys.queue_messages_2009058193".
DBCC results for 'sys.queue_messages_2041058307'.
There are 0 rows in 0 pages for object "sys.queue_messages_2041058307".
CHECKDB found 0 allocation errors and 0 consistency errors in database 'TAIQRY'.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.

Basic questation about sql backup

HI all, sorry for my englisch . I have quetstaion about DPM and SQL 2012 database recovery model .
If I select recovery model simple , that DPM always backup full backup ... This create with vss providera ?
If I select full backup what work synchranization ? Every log files is copy to replica , and after copy truncate log ?
thanx
Falcon

For application data that support incremental backups (exchange, SQL Db's in full recovery mode) there are two job types.
A) Synchronization - This is equivalent of an incremental backup and only brings over log changes. Each incremental synchronization is equivalent to a recovery point. Each incremental synchronization results in application log truncation which
is performed by the application (SQL / Exchange)
B) Express full - This is equivalent to FULL backup, however only brings over Database changed blocks and applies them to the replica volume then makes a snapshot Each express full backup is recoverable. Express full backups do not result
in log truncation by the application. There is a 512 snapshot limit for express full backups.
For applications that do not support incremental backups (SharePoint, SQL Db's in simple recovery mode, Hyper-V VMs) always use express full backups.
http://social.technet.microsoft.com/Forums/en-US/b767a3fb-ce59-4599-a92e-2e5e7e1c8b98/help-to-understand-the-difference?forum=dpmfilebackup
Backing up SQL with DPM
SCDPM: Backup SQL and Truncate SQL Logs
Does DPM Clear transaction Log when Backup?
Have a nice day !!!

Restore from SQL backup

One of our sap server has gone due to hardware failures where SQL server is used as the backend.
I have the full database backup and I want to restore the server from that backup.
Can someone pls point me to good references/guides for doing the same?
Any help would be greatly appreciated.
Thanks

Hi Vasudeva,
are you talking about SAP or BO ?
If its BO there is a Backup and Restore guide available. Its for Rel.2 but also applicapable for XI 3.x
You should find it in the SAP SMP.
Regards
-Seb.

Restoring a SQL backup file

when attempting to restore a backup file to a SQL database file the restore failed and the error message referenced that the backup was from a "different" database. Trying to restore a damaged database file created in the same version of
SQL 2005. Any suggestions that would "allow" the restore to work are appreciated.

the error message referenced that the backup was from a "different" database.
When you try to restore to a different database, then you have to use the option "Overwrite existing database (WITH REPLACE)", otherwise you get this error message; it's a kind of protection, see also
http://social.msdn.microsoft.com/Forums/en-US/6eb5b1aa-511e-44d2-b677-b2ba3303c84c/datavabse-restore-error?forum=sqlsearch
Olaf Helper
[ Blog] [ Xing] [ MVP]

DPM2012 SP1 SQL backup schedule inconsistency

I have a large number of databases on multiple SQL servers (mostly 2008 R2) that are all in the same protection group with a 2 hour sync. If I look in Today's Jobs, roughly half the databases only sync once a day, rather than every 2 hours like the rest.
Please see the image linked for a good understanding: http://i.imgur.com/cxmQf7r.jpg
So every database should be doing a recovery point every 2 hours. Some are doing that, some are not and I need to find out how to fix it and/or why.
I have tried: (checking the schedule after each change)
manually creating recovery points for those items
removing individual items from protection then re-adding
removing entire servers (which included working and non-working schedule items) and re-adding
Note: This has only affected SQL protection, all other protection groups are running normally.

Hi,
You can run this SQL query to see what recovery_model each database is in and the last time it was backed up. DPM Express Full backups use snapshots, Incremental sync jobs do not, so you can see that kind of backup was performed.
USE msdb
GO
SELECT server_name, database_name, backup_start_date, backup_Finish_date, recovery_model, is_snapshot, database_backup_lsn
FROM backupset
--where database_name = 'DB_NAME'
order by backup_start_date desc
As noted previously, if the recovery model is simple, or it was changed to FULL but was never removed from protection and re-added, then only express full backups will be performed.
Changing the Recovery Model of a Database
http://technet.microsoft.com/en-us/library/bb808756.aspx
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

MS SQL backup

Similar Messages

Maybe you are looking for