Hi, all
I am trying to do the data differential databackup daily and full backup
during the weekend.
Log shipping remain the same as usual.
There is anything that I should be aware of before I chnage the backup
method.
It takes too long to have full data backup every night.
Thanks,
Diff backup of the source database does not affect log shipping in any way. So, just make sure you
have thought about disaster recovery, number of backup generations and that you understand the
concept of database, diff and transaction log backups (which are pretty simple).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"mecn" <mecn2002@.yahoo.com> wrote in message news:e0FEv70JGHA.2012@.TK2MSFTNGP14.phx.gbl...
> Hi, all
> I am trying to do the data differential databackup daily and full backup during the weekend.
> Log shipping remain the same as usual.
> There is anything that I should be aware of before I chnage the backup method.
> It takes too long to have full data backup every night.
> Thanks,
>
Showing posts with label remain. Show all posts
Showing posts with label remain. Show all posts
Monday, March 19, 2012
Differential data backup sql2k
Hi, all
I am trying to do the data differential databackup daily and full backup
during the weekend.
Log shipping remain the same as usual.
There is anything that I should be aware of before I chnage the backup
method.
It takes too long to have full data backup every night.
Thanks,Diff backup of the source database does not affect log shipping in any way.
So, just make sure you
have thought about disaster recovery, number of backup generations and that
you understand the
concept of database, diff and transaction log backups (which are pretty simp
le).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"mecn" <mecn2002@.yahoo.com> wrote in message news:e0FEv70JGHA.2012@.TK2MSFTNGP14.phx.gbl...[v
bcol=seagreen]
> Hi, all
> I am trying to do the data differential databackup daily and full backup d
uring the weekend.
> Log shipping remain the same as usual.
> There is anything that I should be aware of before I chnage the backup met
hod.
> It takes too long to have full data backup every night.
> Thanks,
>[/vbcol]
I am trying to do the data differential databackup daily and full backup
during the weekend.
Log shipping remain the same as usual.
There is anything that I should be aware of before I chnage the backup
method.
It takes too long to have full data backup every night.
Thanks,Diff backup of the source database does not affect log shipping in any way.
So, just make sure you
have thought about disaster recovery, number of backup generations and that
you understand the
concept of database, diff and transaction log backups (which are pretty simp
le).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"mecn" <mecn2002@.yahoo.com> wrote in message news:e0FEv70JGHA.2012@.TK2MSFTNGP14.phx.gbl...[v
bcol=seagreen]
> Hi, all
> I am trying to do the data differential databackup daily and full backup d
uring the weekend.
> Log shipping remain the same as usual.
> There is anything that I should be aware of before I chnage the backup met
hod.
> It takes too long to have full data backup every night.
> Thanks,
>[/vbcol]
Differential data backup sql2k
Hi, all
I am trying to do the data differential databackup daily and full backup
during the weekend.
Log shipping remain the same as usual.
There is anything that I should be aware of before I chnage the backup
method.
It takes too long to have full data backup every night.
Thanks,Diff backup of the source database does not affect log shipping in any way. So, just make sure you
have thought about disaster recovery, number of backup generations and that you understand the
concept of database, diff and transaction log backups (which are pretty simple).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"mecn" <mecn2002@.yahoo.com> wrote in message news:e0FEv70JGHA.2012@.TK2MSFTNGP14.phx.gbl...
> Hi, all
> I am trying to do the data differential databackup daily and full backup during the weekend.
> Log shipping remain the same as usual.
> There is anything that I should be aware of before I chnage the backup method.
> It takes too long to have full data backup every night.
> Thanks,
>
I am trying to do the data differential databackup daily and full backup
during the weekend.
Log shipping remain the same as usual.
There is anything that I should be aware of before I chnage the backup
method.
It takes too long to have full data backup every night.
Thanks,Diff backup of the source database does not affect log shipping in any way. So, just make sure you
have thought about disaster recovery, number of backup generations and that you understand the
concept of database, diff and transaction log backups (which are pretty simple).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"mecn" <mecn2002@.yahoo.com> wrote in message news:e0FEv70JGHA.2012@.TK2MSFTNGP14.phx.gbl...
> Hi, all
> I am trying to do the data differential databackup daily and full backup during the weekend.
> Log shipping remain the same as usual.
> There is anything that I should be aware of before I chnage the backup method.
> It takes too long to have full data backup every night.
> Thanks,
>
Sunday, March 11, 2012
Differential Backup File Size
With my maintenance plans for backup jobs, I can control how long the backup
files will remain, hours, days, weeks... before deletion.
With my differential backup jobs, I don't seem to have the ability to
control the residency of a differential backup file to disk, at least I am
not aware of that capability yet, and I am new to SQL Server, and curious as
all get out about its nice features. The differential backup file just
keeps growing and growing and growing. Right now, I manually take the large
file, relocate it to another folder, then when the next differential backup
file is written to the disk location, I then delete the removed large
differential file and continue to let the new backup set grow, repeating the
process as necessary.
Is there a better way to control this process or at least automate it
somehow with T-SQL statements so the large diff file will be transferred to
a new folder until a new file is successfully generated, then deleted. I do
understand the need to maintain the differential file in correspondence with
a current full backup file and corresponding transaction logs with a
corressponding differential file got recovery purpose.
Thanks for your assistance.
Hi,
This is what
You can create two backup jobs for the differential Backups.
Let one run on Mon - Wed - Fri and the other run on Tue - Thu - Sat
On Sunday you can schedule a complete backup.
In Each of these Jobs add one more step that would get executed only if the
preceeding backup step was successful.
Let this new step be of "Operating System Command"
In the Process add the OS command to delete the file from the previous
day's differential backup or even copy the file to a different location.
You can have two separate folders, one each for the Backup Job.
Folder A for Job A and Folder B for job B
When you execute Job A on Monday, let the next step delete/move the backup
file located in the Folder B, after the diff backup is over.
Similarly when you execute Job B on Tuesday, let the next step delete/move
the backup file located in the Folder A, after the diff backup is over.
HTH
Ashish
This posting is provided "AS IS" with no warranties, and confers no rights.
|||That gives a direction to pursue, thank you.
"Ashish Ruparel [MSFT]" <v-ashrup@.online.microsoft.com> wrote in message
news:i81O3gMMEHA.3364@.cpmsftngxa10.phx.gbl...
> Hi,
> This is what
> You can create two backup jobs for the differential Backups.
> Let one run on Mon - Wed - Fri and the other run on Tue - Thu - Sat
> On Sunday you can schedule a complete backup.
> In Each of these Jobs add one more step that would get executed only if
the
> preceeding backup step was successful.
> Let this new step be of "Operating System Command"
> In the Process add the OS command to delete the file from the previous
> day's differential backup or even copy the file to a different location.
> You can have two separate folders, one each for the Backup Job.
> Folder A for Job A and Folder B for job B
> When you execute Job A on Monday, let the next step delete/move the backup
> file located in the Folder B, after the diff backup is over.
> Similarly when you execute Job B on Tuesday, let the next step delete/move
> the backup file located in the Folder A, after the diff backup is over.
> HTH
> Ashish
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
files will remain, hours, days, weeks... before deletion.
With my differential backup jobs, I don't seem to have the ability to
control the residency of a differential backup file to disk, at least I am
not aware of that capability yet, and I am new to SQL Server, and curious as
all get out about its nice features. The differential backup file just
keeps growing and growing and growing. Right now, I manually take the large
file, relocate it to another folder, then when the next differential backup
file is written to the disk location, I then delete the removed large
differential file and continue to let the new backup set grow, repeating the
process as necessary.
Is there a better way to control this process or at least automate it
somehow with T-SQL statements so the large diff file will be transferred to
a new folder until a new file is successfully generated, then deleted. I do
understand the need to maintain the differential file in correspondence with
a current full backup file and corresponding transaction logs with a
corressponding differential file got recovery purpose.
Thanks for your assistance.
Hi,
This is what
You can create two backup jobs for the differential Backups.
Let one run on Mon - Wed - Fri and the other run on Tue - Thu - Sat
On Sunday you can schedule a complete backup.
In Each of these Jobs add one more step that would get executed only if the
preceeding backup step was successful.
Let this new step be of "Operating System Command"
In the Process add the OS command to delete the file from the previous
day's differential backup or even copy the file to a different location.
You can have two separate folders, one each for the Backup Job.
Folder A for Job A and Folder B for job B
When you execute Job A on Monday, let the next step delete/move the backup
file located in the Folder B, after the diff backup is over.
Similarly when you execute Job B on Tuesday, let the next step delete/move
the backup file located in the Folder A, after the diff backup is over.
HTH
Ashish
This posting is provided "AS IS" with no warranties, and confers no rights.
|||That gives a direction to pursue, thank you.
"Ashish Ruparel [MSFT]" <v-ashrup@.online.microsoft.com> wrote in message
news:i81O3gMMEHA.3364@.cpmsftngxa10.phx.gbl...
> Hi,
> This is what
> You can create two backup jobs for the differential Backups.
> Let one run on Mon - Wed - Fri and the other run on Tue - Thu - Sat
> On Sunday you can schedule a complete backup.
> In Each of these Jobs add one more step that would get executed only if
the
> preceeding backup step was successful.
> Let this new step be of "Operating System Command"
> In the Process add the OS command to delete the file from the previous
> day's differential backup or even copy the file to a different location.
> You can have two separate folders, one each for the Backup Job.
> Folder A for Job A and Folder B for job B
> When you execute Job A on Monday, let the next step delete/move the backup
> file located in the Folder B, after the diff backup is over.
> Similarly when you execute Job B on Tuesday, let the next step delete/move
> the backup file located in the Folder A, after the diff backup is over.
> HTH
> Ashish
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
Subscribe to:
Posts (Atom)