New answers tagged backup
I can't see that you are using backup to URL. It looks like a local drive and a file share. If you read about mirrored backups you see that there are some special requirements: "Mirroring applies both to disk and tape (disks do not support continuation tapes). All backup devices for a single backup or restore operation must be of the same type, disk or ...
INIT will simply overwrite the existing file if it already exists, rather than append. However, you can prevent this from happening if you use the RETAINDAYS option, and set it to a really long time (you will have to maintain and manage these files as they get older, of course). If all of your backup files are initially set to last 10 years, and you always ...
you can run RMAN command validate backup so you can check the backup before restoring it every database block has (or might have) a check sum in it. This is validated during both backup and restore Also every datafile has "timestamp" (SCN) of the last modification written in it's header. And the database won't start if these SCN differ. you can also check ...
You can use SQL Developer, Tools - Database Diff, this would give you an idea. There is a tutorial here http://www.oracle.com/technetwork/issue-archive/2012/12-sep/o52sqldev-1735911.html. Only use the compare/diff section.
MIRROR TO is not supported with backup to URL: https://msdn.microsoft.com/en-us/library/dn435916.aspx#limitations Specifically under the "Support for Backup Arguments" section, you'll see "Mirror To" has a "-" for not supported.
Full backup is not showing up because it has already been restored and no new latest info is there in msdb to reflect the same. Moreover, once msdb is updated with the backup info, it lets you avail with such info and in a manner of chain as followed in as LSN. However, you can do this manually by running below script on a specific database to retrieve ...
IMHO you MUST take transaction log backup before swithching to simple recovery it would help you in PIT recovery as well as its documented and recommended in BOL Article. It wont do any harm and you will have a failsafe. Please also note its advisable to change recovery model when load on database is relatively less. Although you can change it in peak hour ...
Once you switch to Simple the Trans Log will no longer maintain a log of operations since your last (database files) backup - at the point of the switch all transactions will have been committed to the main database files so will not be discarded - they are already effective in the database files. Your point 1 is not (in my opinion) worth doing - once ...
Differential backups are backups of any changes to the DB since the last full backup. So in theory, yes, you could have it do a diff backup since some date (if you did a full backup on that date). Otherwise, no. It'll always be since the last full backup.
Just take a full backup (with compression, if possible), restore it on the other server, and then you can select into or insert/select without having to worry about what happens to carriage returns, line feeds, and other characters that cause problems for files. You want to move (parts of) a database, not files. Trying to just extract some 120 million rows ...
Its not easy because SQL Server does not allow you to do partial restores (by filegroup maybe but...) You have to do a full restore to another name or instance and insert the old rows (from the restored database) to the existing table without overwriting existing records.
If somebody came to this question when looking for answer to failed attempt to restore SQL Server database to localdb (like I did) then it might be localdb limitation. I used SQL Server Express and was able to do a restore.
Simple way to query the end time: use MSDB go select * from restorehistory; Or use MSDB go SELECT MAX(restore_date) as LAST_RESTORE_DT FROM restorehistory WHERE destination_database_name = 'DB_NAME' The restorehistory table doesn't have the start time of the refresh.
Top 50 recent answers are included