New answers tagged

0

If you had made a backup of the old master's pg_xlog content that was not applied on the new master after the point of divergence, as they call it, you can use pg_xlogdump (included in the PG distribution since 9.3) to examine the contents of transaction logs on the old master: $ pg_xlogdump -p <pg_xlog_dir> <segment_file_name> Unfortunately, ...


1

I supposed you haven't taken any LOG backup since your last FULL backup and this FULL backup was the last backup of any type taken. You need to take a Tail LOG Backup first: BACKUP LOG [MyDB] TO DISK = N'I:\MSSQL\DATA\MyDB_LogBackup_2016-01-27_17-40-41.bak' WITH NAME = N'MyDB_LogBackup_2016-01-27_17-40-41' , NOFORMAT, NOINIT, NOSKIP, ...


0

If you are in full recovery model, then you must have some log backups located some place, I would recommend you use a cool script like "RestoreScriptGenie" from Paul Brewer to do so, it's located here: http://www.sqlservercentral.com/articles/Restore/95839/ It will generate a script to recover to a point in time, with a different db name and so on. Edit: ...


10

No, you need to have taken transaction logs that cover the time frame you want to use with STOPAT. You can't do this from a full database backup only - that is just a one-time copy, and that is why we have different types of backups (full, log, diff). If you have taken transaction log backups in between your full backups, please update the question with ...


0

We use Ola Hallengren's backup scripts to perform the backups. We have created a custom TSQL script that simply runs on a development server once a week which scans the backups and restores the latest Full / Diff and TLog (Whatever is needed really to restore to the most recent backup). Very simple approach but it works for us in making sure the backups ...


3

Provided that you have alerts set up on the jobs, Log Shipping is a feature that is available on all editions, doesn't require a whole lot of effort to set up, and I believe fulfills all of your requirements. I would avoid any wizards that you might stumble upon in Management Studio. Essentially you need three jobs for the following tasks: Initialize the ...


0

We make use of Ola Hallengren's Backup scripts to do your daily backups to our network storage and we're having 3 main regions: Americas, Asia and emea. Emea having around 1.000 databases, Americas and Asia having 200 databases each. Based on this MSSQLTips article, I created a stored procedure taking 3 parameters: Database name, server name and backup path. ...


3

You may actually be able to do a restore. Grant Fritchey talked about it here. Basically if you go to the portal and look at the screen for the database there is a restore option. Once you select it it will give you the oldest restore point available. You can't overwrite your database but you can restore it to an alternate location. It looks like you ...


5

I had a large transaction fail due to the transaction log filling up yesterday, it couldn't be rolled back and SQL Server has restarted the specific DB to perform recovery. This is not totally correct when a transaction starts in SQL Server it reserves space in transaction log in case the transaction has to rollback. From Transaction Log architecture ...


2

It sounds like a simple permissions issue. Why did this happen? The Everyone permission literally allows anyone to connect to those network shares and access those files. When you remove those permissions, now no one is allowed to access them. What may be confusing is that you may think that SQL Server has access to those files and shares, when, in fact, ...


0

I just came across a way to find out which databases the old PG_DATA directory contained. It's a bit hackish, and too late for me, but it might be useful for somebody else in the future. Information about database names (etc) is not stored in PG_DATA/base, but rather in PG_DATA/global. The files in that directory are (in my case, at least) small enough to ...


6

Is there any way at all to restore these files? No. The long answer is like this: you first will have to fix the MDFs. Attempt to attach it with ATTACH_REBUILD_LOG as you encounter errors (like incorrect pageid (expected 1:134; actual 0:0). It occurred during a read of page (1:134)) you have to edit the file and fix it. This, of course, requires you ...



Top 50 recent answers are included