I've configured 2 backup tasks in Microsoft SQL Server, to have a full and incremental backup of our database. The version of Microsoft SQL Server is 2008 R2.
The problem is, I've configured a location and until a couple of weeks ago everything went fine. The problem is that it currently creates those backups in a location that is not possible to find. If I check the logs, everything went ok. But in the target directory, there's no trace of that backup file.
When I execute the following query, I get a bizarre value in physical_device_name:
SELECT
physical_device_name,
backup_start_date,
backup_finish_date,
backup_size/1024.0 AS BackupSizeKB
FROM msdb.dbo.backupset b
JOIN msdb.dbo.backupmediafamily m ON b.media_set_id = m.media_set_id
WHERE database_name = 'DB_NAME'
ORDER BY backup_finish_date DESC
These are the values that I get for physical_device_name:
{4CAE7525-44D7-4DEF-86A7-F9C7C99C013C}3
{EC6FB844-832G-4A8F-BDDE-12D073383139}3
And so on ...
Any idea why this is and how to resolve it? My initial thought was that those directories are readonly. I changed that, but I saw that one of the backups last night failed again because of the same reason.
Good day,
SQL Server supports virtualization-aware backup solutions that use volume shadow copy (VSS) also named volume snapshots. For example, SQL Server supports Hyper-V and VMware backup. For more information check this document.
When the host backups your system the SQL Server VSS Writer service is used (It should be running when SQL Server is installed on virtual machine).
You should notice that these backups have value 7 in the column "device_type" (7 means Virtual device). These rows are actually very useful, for example it help to know that the Virtual Machine backups are running full database backups on a SQL Server instance. there's no trace of these backup files since they are above the scope of the virtual machine (above the level of your machine) - these are triggered by the host (Hyper-V or VMware for example).
More information here.
Yup - If you look at device_type (in the backupmediafamily table), you will see that it is probably a virtual device (7) and is being backed up by your virtual machine software.
Related
I have three Microsoft Windows Server 2012 R2 Standard servers running on Dell PowerEdge machines that serve as Hyper-v hosts for my various virtual machines. Each server has a scheduled backup similar to the following:
Notes:
Each scheduled backup is configured to be a "VSS Full Backup".
Some backups show the VMs as online and some show as offline.
The issue is that the backups will run for several days successfully and then will stop running. After the backups begin to fail, I see the following when I open Windows Server Backup tool.
I also see Event 19 in the event log when the scheduled backup runs:
The backup operation attempted at
'?2018?-?06?-?04T02:00:01.583169900Z' has failed to start, error code
'0x8007000E' ('Ran out of memory'). Please review the event details
for a solution, and then rerun the backup operation once the issue is
resolved.
If I attempt to run the backup using the wbadmin command line, I see the following error:
Not enough storage is available to complete this operation.
If I sign out and then sign on, the issue is immediately resolved and I can see the backup history in the Windows Server Backup tool. The backup will run again for several days until the issue occurs again.
The cycle of the issue on the three machines is very similar. In other words, the backup will run successfully on all three machines for 2 days and then fail on all three machines and continue to fail until I sign in, sign out and then sign in on each machine.
Note: After verifying that the server backup is running with a sign in, sign out & sign in. I typically sign out again.
Notes
Each Hyper-v Server has 16 GB of free memory after the memory dedicated to the VMs is subtracted from the total memory.
Each Hyper-v Server has 25 GB of free hard drive space on the C drive and 500 GB or more of free space on the D drive where the VMs are stored.
Each backup drive has 1 TB of free space.
Any ideas?
I originally posted this question on Microsoft Technet.
Technet Question
The root cause of this issue was the Bomgar Jump Client version 17.1.4. After disabling the Jump Client, we have not experienced the issue. See the linked Technet Question for more detail.
Our windows 2016 server failed to restart after a windows update yesterday.
In order to avoid the update that crashed it issue (whatever it was), I'm in the process of rebuilding it clean.
So I've reinstalled Windows Server 2016, and SQL Server 2016 (same version we were using before).
I have a full system backup from a couple of days ago viz Windows SErver Backup.
What I am having a hard time finding is information on
"How do I restore a SQL Server instance directly from Win Backup files?"
I have recreated the same named instance we had before (so that the file paths match, etc.) - but I have no idea how to make that work? Can it possibly be as simple as shutting down SQL Server temporarily - using Windows Backup to restore the necessary C:\Program Files\Microsoft SQL Server\MSSQL13.SOURCEGEARVAULT\?
Or is there more to it than that? If so, where can I find instructions for this?
If I had a true backup of the database - and not simply the filesystem - I would have access to lots of how-to's - I've done that before. But I don't have that - I just have the raw filesystem a day before it died.
Any pointers would be appreciated!
UPDATE: per feedback - moved this to: https://serverfault.com/questions/914463/can-i-restore-a-sql-server-instance-from-file-backups-only
I am looking for a free DNN community edition website Backup and restore procedure working with DNN 7 and SQL server express 2008 r2.
I usually design and develop website in local PC as my connection speed to the actual server is low. And then I want to publish (deploy) the result in the server. I may need to repeat this procedure a few times as our website is always under development and I need to add new pages or update the existing ones.
I use DNN 7 community edition. I have already googled and have found plenty of commercial tools for this backup and restore. But the free methods seems to be 1.
old or
not working properly or
not a straight forward procedure or
very buggy.
I have gone e.g. through the 4 links given in
http://www.dnnsoftware.com/community-blog/cid/134680/HOW-TO-Move-a-DotNetNuke-installation
without any success.
Could you please help me 1.
how I could develop my website in local PC and then upload the
result in the server?
And later after adding a few new pages in the local PC how I could sync the result with the server?
Thank you very much in advance for your help and consideration.
.
.
.
"when using SQL express, if I simply copy the entire local folder to production (including the APP_DATA folder, which contains the database)." ... How I could just save the newly registered users data in the website's database before copying entire local folder to production and restore this data after copying. In other way, I want to update the page contents and added designs but I don't want to loose newly registered users data between two consecutive website updates. I hope could find a working procedure for this because working online with server is very slow due to my connection speed and I have to keep a replica of the website in the local PC and add new pages or programs in the local PC and then update the result to the server when required. The specs of two systems are as follows:
local PC: Windows 8 Pro (with admin access)
Server (VPS): Windows web server 2008 (with admin access)
1) The easiest way to do this, when using SQL express, is to simply copy the entire local folder to production (including the APP_DATA folder, which contains the database)
2) Repeat step 1, but you'll lose any changes you made in production since the last time you pushed things up.
DNN doesn't really support this type of synchronization as a platform. They tried to offer it in their Enterprise product, but it worked so poorly they scrapped the feature.
I have a powercenter 9.1 installation on windows server 2008 R2.
The repository is on the same box, hosted on sql server 2012. I have configured a new user (with sql server authentication) and have the repo db owned by that user. (it has the owner role)
The core problem : I am not able to run a simple test workflow on this setup.
Here's what I have been trying
The windows firewall has been taken down now for about an hour or so.
The repository service and integration service are running in trace/debug mode respectively.
The integration service log complains that it cant find a certain session for a certain workflow in certain folder (with ids for all of them).
When I log into sql server mgmt console, and try to query the repository tables for those exact items (since i have the ids from logs), all the data is present...
I fail to understand what is that I am messing up...
Disclaimer - my knowledge of sql server is really low.. may be 1 or 2 on scale of 10, since I have been living on the other side of fence (with oracle) for all of my career...
Did you try keeping the sql server login/user name and the associated default schema name as same?
I have very limited access to the SQL Server at my ISP.
I have a very simple tool to create databases and execute SQL (which is enough most of the time) but now I also want to backup (and in the case of an accident, restore) a database from my own PC (or via a web application, if that's possible, both are ok)
Is there a tool which can do that auotmatically?
It's a SQL Server 2008 database.
I guess I can do it from my SQL Server Management Studio, but I'd prefer a tool that can do it scheduled.
Kind regards,
Michel
You can only backup (and restore) your database from local drives on the SQL Server machine - e.g. the machine at your ISP's location.
You cannot backup SQL Server and store the *.bak file on your local system, over the internet.
So what you need to do is create some kind of a process that stores the BAK file on the server machine at your ISP's location, and then copies or moves it to your home machine. For that, you need to have write access to some physical drive at your ISP on their SQL Server.