What is the best way to estimate the strain a backup will place on a server currenly being used?
Is there a way to limit the amout of resources given to the backup process?
Basically, i'm trying to figure out if I can run a backup up in the middle of a high usage time, even thou I relize it would be better to backup up off hours.
The best way is to try it and see. You can always kill the backup if you
need to. Backups usually don't use much CPU but will hit the disks (Both
Logs and Data Drives) pretty hard.
Andrew J. Kelly SQL MVP
"mannie" <anonymous@.discussions.microsoft.com> wrote in message
news:99231A3C-9711-4398-A530-568906D1DEAD@.microsoft.com...
> What is the best way to estimate the strain a backup will place on a
server currenly being used?
> Is there a way to limit the amout of resources given to the backup
process?
> Basically, i'm trying to figure out if I can run a backup up in the middle
of a high usage time, even thou I relize it would be better to backup up off
hours.
|||Hi,
What is the best way to estimate the strain a backup will place on a server currenly being used?
use the performance monitor counters:-
1. SQL Server Backup Device Object: Device Throughput Bytes/sec
2. Physical Disk: % Disk Time
3. Physical Disk Object: Avg. Disk Queue Length
Normally backup process will utilize a bit of more I/O ,, since it is writing into the disk.
If you have multiple disk controllers in your server you can create multiple backup devices spanned
across. And while backing up you can give both the backup devices, this will speed up the backup
process as well as reduces the resource usage.
Sample
sp_addumpdevice 'disk','backup1','D:\backup\backup1.bak'
go
sp_addumpdevice 'disk','backup2','F:\backup\backup2.bak'
go
Backup database dbname to backup1,backup2
Have a look into the SQL LITESPEED backup tool. This tool will speedup the backup and reduces I/O.
http://www.imceda.com/
Thanks
Hari
MCDBA
-- mannie wrote: --
What is the best way to estimate the strain a backup will place on a server currenly being used?
Is there a way to limit the amout of resources given to the backup process?
Basically, i'm trying to figure out if I can run a backup up in the middle of a high usage time, even thou I relize it would be better to backup up off hours.
Showing posts with label limit. Show all posts
Showing posts with label limit. Show all posts
Monday, March 19, 2012
Backup Proformance
What is the best way to estimate the strain a backup will place on a server
currenly being used?
Is there a way to limit the amout of resources given to the backup process?
Basically, i'm trying to figure out if I can run a backup up in the middle o
f a high usage time, even thou I relize it would be better to backup up off
hours.The best way is to try it and see. You can always kill the backup if you
need to. Backups usually don't use much CPU but will hit the disks (Both
Logs and Data Drives) pretty hard.
Andrew J. Kelly SQL MVP
"mannie" <anonymous@.discussions.microsoft.com> wrote in message
news:99231A3C-9711-4398-A530-568906D1DEAD@.microsoft.com...
> What is the best way to estimate the strain a backup will place on a
server currenly being used?
> Is there a way to limit the amout of resources given to the backup
process?
> Basically, i'm trying to figure out if I can run a backup up in the middle
of a high usage time, even thou I relize it would be better to backup up off
hours.|||Hi,
What is the best way to estimate the strain a backup will place on a server
currenly being used?
use the performance monitor counters:-
1. SQL Server Backup Device Object: Device Throughput Bytes/sec
2. Physical Disk: % Disk Time
3. Physical Disk Object: Avg. Disk Queue Length
Normally backup process will utilize a bit of more I/O ,, since it is writin
g into the disk.
If you have multiple disk controllers in your server you can create multiple
backup devices spanned
across. And while backing up you can give both the backup devices, this will
speed up the backup
process as well as reduces the resource usage.
Sample
sp_addumpdevice 'disk','backup1','D:\backup\backup1.bak'
go
sp_addumpdevice 'disk','backup2','F:\backup\backup2.bak'
go
Backup database dbname to backup1,backup2
Have a look into the SQL LITESPEED backup tool. This tool will speedup the b
ackup and reduces I/O.
http://www.imceda.com/
Thanks
Hari
MCDBA
-- mannie wrote: --
What is the best way to estimate the strain a backup will place on a server
currenly being used?
Is there a way to limit the amout of resources given to the backup process?
Basically, i'm trying to figure out if I can run a backup up in the middle o
f a high usage time, even thou I relize it would be better to backup up off
hours.
currenly being used?
Is there a way to limit the amout of resources given to the backup process?
Basically, i'm trying to figure out if I can run a backup up in the middle o
f a high usage time, even thou I relize it would be better to backup up off
hours.The best way is to try it and see. You can always kill the backup if you
need to. Backups usually don't use much CPU but will hit the disks (Both
Logs and Data Drives) pretty hard.
Andrew J. Kelly SQL MVP
"mannie" <anonymous@.discussions.microsoft.com> wrote in message
news:99231A3C-9711-4398-A530-568906D1DEAD@.microsoft.com...
> What is the best way to estimate the strain a backup will place on a
server currenly being used?
> Is there a way to limit the amout of resources given to the backup
process?
> Basically, i'm trying to figure out if I can run a backup up in the middle
of a high usage time, even thou I relize it would be better to backup up off
hours.|||Hi,
What is the best way to estimate the strain a backup will place on a server
currenly being used?
use the performance monitor counters:-
1. SQL Server Backup Device Object: Device Throughput Bytes/sec
2. Physical Disk: % Disk Time
3. Physical Disk Object: Avg. Disk Queue Length
Normally backup process will utilize a bit of more I/O ,, since it is writin
g into the disk.
If you have multiple disk controllers in your server you can create multiple
backup devices spanned
across. And while backing up you can give both the backup devices, this will
speed up the backup
process as well as reduces the resource usage.
Sample
sp_addumpdevice 'disk','backup1','D:\backup\backup1.bak'
go
sp_addumpdevice 'disk','backup2','F:\backup\backup2.bak'
go
Backup database dbname to backup1,backup2
Have a look into the SQL LITESPEED backup tool. This tool will speedup the b
ackup and reduces I/O.
http://www.imceda.com/
Thanks
Hari
MCDBA
-- mannie wrote: --
What is the best way to estimate the strain a backup will place on a server
currenly being used?
Is there a way to limit the amout of resources given to the backup process?
Basically, i'm trying to figure out if I can run a backup up in the middle o
f a high usage time, even thou I relize it would be better to backup up off
hours.
Thursday, March 8, 2012
Backup Options - low disk space
Howdy,
We have very a tight limit on disk space for backups.
We have a 3 GB db that we do full a weekly full backup on, followed by hourly tran log backups for the rest of the week - this adds up to a LOT of disk space usage ( we cant do differential backups due to space limitations, as diffs are almost 3 GB in size... ).
As disk space is limited, we can only keep a weeks worth of backups on the disk, and previous weeks get backed up onto tape. No big deal there....
So, when weekly full backup occurs, the only way to recover the previous weeks data is to restore previous full backup & allpy the required number of tran logs.
Is there another way to do backups perhaps using file backups , so we dont have to go all the way back to the previous weeks backups?
Thanks in advance,
SG.Do you have a tape device on the machine? If so you could copy the backup off every night and run a full backup every night...if this is an important server, buy more disks!! I bought an external 80gb drive for $90, I would push back and have the company buy more space.
HTH|||Hi,
Thanks - I have suggested to the clients the disk space option is the best way of going, I just wanted someone else to say it too. I figure its not worth the grief for skimping on disk space for the sake of operational integrity.
Cheers
SG|||Hi,
If you haven't yet bought hard disk, you could do this. You could schedule the full backups daily and 'overwrite the existing media' instead of appending. Also you can delete the transactional log after the successful backup at the end of the day.
You could continue with the weekly tape backups too. If you need to restore, you need to the full with no recovery and the tran log for just the previous day. Ofcourse if the restoration is beyond a days time, you will need to use the tape, previous days full backup and transaction logs.
Hope this help you.
Regards,
We have very a tight limit on disk space for backups.
We have a 3 GB db that we do full a weekly full backup on, followed by hourly tran log backups for the rest of the week - this adds up to a LOT of disk space usage ( we cant do differential backups due to space limitations, as diffs are almost 3 GB in size... ).
As disk space is limited, we can only keep a weeks worth of backups on the disk, and previous weeks get backed up onto tape. No big deal there....
So, when weekly full backup occurs, the only way to recover the previous weeks data is to restore previous full backup & allpy the required number of tran logs.
Is there another way to do backups perhaps using file backups , so we dont have to go all the way back to the previous weeks backups?
Thanks in advance,
SG.Do you have a tape device on the machine? If so you could copy the backup off every night and run a full backup every night...if this is an important server, buy more disks!! I bought an external 80gb drive for $90, I would push back and have the company buy more space.
HTH|||Hi,
Thanks - I have suggested to the clients the disk space option is the best way of going, I just wanted someone else to say it too. I figure its not worth the grief for skimping on disk space for the sake of operational integrity.
Cheers
SG|||Hi,
If you haven't yet bought hard disk, you could do this. You could schedule the full backups daily and 'overwrite the existing media' instead of appending. Also you can delete the transactional log after the successful backup at the end of the day.
You could continue with the weekly tape backups too. If you need to restore, you need to the full with no recovery and the tran log for just the previous day. Ofcourse if the restoration is beyond a days time, you will need to use the tape, previous days full backup and transaction logs.
Hope this help you.
Regards,
Subscribe to:
Posts (Atom)