Backups using differential and full and causing issues
i sharepoint administrator using sharepoint 2010 sp1 enteprise edition , running powershell backup nightly full farm backup.
backup-spfarm -directory \\serversqlbackup01\sql_full_backups\sharepoint\spbackup\production-farm -backupmethod full -verbose
i run backup's in sharepoint's central administration nightly perform full database crawl , incremental crawl every half hour on sharepoint farm.
my dba finding these backup's , causing him wonder going on not doing differntial , states happen simple database mode, not full.
it happened on simple model databases
this export sql management studio 2012 sp1 bi edition
databasename recovery_model user_name duration in mins backup_start_date backup_finish_date backuptype backup_size size_unit physical_device_name backup_set_id
search_service_application_server1_crawlstoredb_c9d7342c169a4b75a6254c0b6871f44e simple domain\farm-account 0.016666 2013-05-29 23:16:06.000 2013-05-29 23:16:07.000 differential 1.273437500000000 mb \\serversqlbackup01\sql_full_backups\sharepoint\spbackup\production-farm\spbr00b5\00000134.bak 29638
search_service_application_server1_crawlstoredb_c9d7342c169a4b75a6254c0b6871f44e simple domain\farm-account 0.283333 2013-05-29 23:14:12.000 2013-05-29 23:14:29.000 full 451.274414062000000 mb \\serversqlbackup01\sql_full_backups\sharepoint\spbackup\production-farm\spbr00b5\00000134.bak 29635
here concern,
backup history sql server database indicates backups getting appended existing backup devices. increases risk of losing backups when backup device gets damaged. performance of backup , restore operations might degraded when several backups appended 1 on same backup device resides on remote server , accessed on network
thank you!
upon looking @ this, location, starting "serversqlbackup01" is using backup's sharepoint creating , referencing setting in powershell script. why sql management studio reading / referencing / getting errors this?
here concern,
backup history sql server database indicates backups getting appended existing backup devices. increases risk of losing backups when backup device gets damaged. performance of backup , restore operations might degraded when several backups appended 1 on same backup device resides on remote server , accessed on network
hi ,
i hope taking backups on tape drive ..its highly unlikely tape set corrupt...and apending backups set default during backup
appending lets u manage ur backup set through 1 tape..its easier transfer it..
if taking on local disk think not practice
for pros , con on appending backup u can read tbelow
http://www.sqlservercentral.com/forums/topic796873-146-1.aspx
http://msdn.microsoft.com/en-us/library/ms191505(v=sql.105).aspx
please mark reply answer or vote helpful, appropriate, make useful other readers
SQL Server > SQL Server Database Engine
Comments
Post a Comment