It would not cause any performance problems. It is good that you are leaving some breathing space for the OS.

7 hours to backup 99 GB seems to be abnormal. Did you check if any other process is blocking this Backup session? Also check the System Event Log for any...

You may find this script useful.

select

db_name()as DBName,

object_name(i.id) as TableName,

fg.groupname as FileGroup

from sysfilegroups fg, sysindexes i

and i.indid < 2

and i.groupid = fg.groupid

RECONFIGURE accepts only valid values whereas RECONFIGURE WITH OVERRIDE accepts any value.

Both RECONFIGURE and RECONFIGURE WITH OVERRIDE work with every configuration option. However, the basic RECONFIGURE statement rejects any...

You may find SQL Server FineBuild[/url] useful.

Even my client has some servers in which they copy the .mdf & .ldf files in their "cold" backup strategy. If the application can afford the downtime, this strategy can...

Here is why

Easiest approach would have been to delete the "Subplan" in the Maintenance Plan. The job would be automatically deleted.

If the server is getting rebooted, check the System Event Log which should have more details.

You would use RESTORE HEADERONLY, RESTORE FILELISTONLY to verify if the Backup file belongs to that particular database and to check the original location of the database file. Optionally you...

You can use Performance Monitor utility to get this information. Run --> perfmon.exe

Here are the screenshots on how to add counters in Performance Monitor.

Agree with Shawn. It is a good practice to backup the database locally and copy it to the network share later on. You can also schedule a job to copy...

Please change the Service Accounts for both SQL Server service and FT service using SQL Server Configuration Manager.

Please post the complete error message

The job is timing out. Check the resource utilization and sessions on the server referred to in Step 1.