database backup-overwrites old backupfile?

Hi just wondering when you set up a scheluled database backup, does the old
backup file get written over each time the scheduled backup takes place as
this is what I would like it to do?
thanks.
Paul G
Software engineer.
The BACKUP command does not overwrite by default. Defile is NOINIT which is append. To overwrite,
specify INIT. If you schedule using some type if GUI instead of typing the command, we need to know
more about that GUI and what checkboxes etc you have checked.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:D8C9F159-8933-4EF8-85E8-2873E9815B22@.microsoft.com...
> Hi just wondering when you set up a scheluled database backup, does the old
> backup file get written over each time the scheduled backup takes place as
> this is what I would like it to do?
> thanks.
> --
> Paul G
> Software engineer.
|||Paul,
The default is NOINIT which appends the backup to the device. You can use
WITH INIT to overwrite the contents of the backup device.
See BACKUP in the SQL BOL for more details.
HTH
Jerry
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:D8C9F159-8933-4EF8-85E8-2873E9815B22@.microsoft.com...
> Hi just wondering when you set up a scheluled database backup, does the
> old
> backup file get written over each time the scheduled backup takes place as
> this is what I would like it to do?
> thanks.
> --
> Paul G
> Software engineer.
|||ok thanks did use the gui to set up the schedule.
Paul G
Software engineer.
"Jerry Spivey" wrote:

> Paul,
> The default is NOINIT which appends the backup to the device. You can use
> WITH INIT to overwrite the contents of the backup device.
> See BACKUP in the SQL BOL for more details.
> HTH
> Jerry
> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> news:D8C9F159-8933-4EF8-85E8-2873E9815B22@.microsoft.com...
>
>
|||looks like the gui has a selection do not keep longer than 4 weeks which will
work for what I needed. I tried to start the server agent service and get
the following error,
error 5-access is denied. I am able to access everything on the dbase
server so not sure why I am getting this error. Do you know where I need to
check the permissions? thanks.
Paul G
Software engineer.
"Tibor Karaszi" wrote:

> The BACKUP command does not overwrite by default. Defile is NOINIT which is append. To overwrite,
> specify INIT. If you schedule using some type if GUI instead of typing the command, we need to know
> more about that GUI and what checkboxes etc you have checked.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> news:D8C9F159-8933-4EF8-85E8-2873E9815B22@.microsoft.com...
>
|||By GUI, I assume you mean the Maintenance Plan Wizard. Yes, it has an option to delete old backup
files. It creates a new file each time you do backup, including a time stamp in the file name. As
for the access denied errors, we need more information. First, understand that the service account
for SQL Server Agent and for the SQL Server service need permissions on whatever you need to do
(like accessing the backup share). I suggest you define a report file for your maint plan, as that
will probably give more details information about exactly what it is that access is denied for etc.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:4AD647D2-C767-4B8B-B02D-F1752D96D0C6@.microsoft.com...[vbcol=seagreen]
> looks like the gui has a selection do not keep longer than 4 weeks which will
> work for what I needed. I tried to start the server agent service and get
> the following error,
> error 5-access is denied. I am able to access everything on the dbase
> server so not sure why I am getting this error. Do you know where I need to
> check the permissions? thanks.
> --
> Paul G
> Software engineer.
>
> "Tibor Karaszi" wrote:

database backup-overwrites old backupfile?

Hi just wondering when you set up a scheluled database backup, does the old
backup file get written over each time the scheduled backup takes place as
this is what I would like it to do?
thanks.
--
Paul G
Software engineer.The BACKUP command does not overwrite by default. Defile is NOINIT which is
append. To overwrite,
specify INIT. If you schedule using some type if GUI instead of typing the c
ommand, we need to know
more about that GUI and what checkboxes etc you have checked.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:D8C9F159-8933-4EF8-85E8-2873E9815B22@.microsoft.com...
> Hi just wondering when you set up a scheluled database backup, does the ol
d
> backup file get written over each time the scheduled backup takes place as
> this is what I would like it to do?
> thanks.
> --
> Paul G
> Software engineer.|||Paul,
The default is NOINIT which appends the backup to the device. You can use
WITH INIT to overwrite the contents of the backup device.
See BACKUP in the SQL BOL for more details.
HTH
Jerry
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:D8C9F159-8933-4EF8-85E8-2873E9815B22@.microsoft.com...
> Hi just wondering when you set up a scheluled database backup, does the
> old
> backup file get written over each time the scheduled backup takes place as
> this is what I would like it to do?
> thanks.
> --
> Paul G
> Software engineer.|||ok thanks did use the gui to set up the schedule.
--
Paul G
Software engineer.
"Jerry Spivey" wrote:

> Paul,
> The default is NOINIT which appends the backup to the device. You can use
> WITH INIT to overwrite the contents of the backup device.
> See BACKUP in the SQL BOL for more details.
> HTH
> Jerry
> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> news:D8C9F159-8933-4EF8-85E8-2873E9815B22@.microsoft.com...
>
>|||looks like the gui has a selection do not keep longer than 4 weeks which wil
l
work for what I needed. I tried to start the server agent service and get
the following error,
error 5-access is denied. I am able to access everything on the dbase
server so not sure why I am getting this error. Do you know where I need to
check the permissions? thanks.
--
Paul G
Software engineer.
"Tibor Karaszi" wrote:

> The BACKUP command does not overwrite by default. Defile is NOINIT which i
s append. To overwrite,
> specify INIT. If you schedule using some type if GUI instead of typing the
command, we need to know
> more about that GUI and what checkboxes etc you have checked.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> news:D8C9F159-8933-4EF8-85E8-2873E9815B22@.microsoft.com...
>|||By GUI, I assume you mean the Maintenance Plan Wizard. Yes, it has an option
to delete old backup
files. It creates a new file each time you do backup, including a time stamp
in the file name. As
for the access denied errors, we need more information. First, understand th
at the service account
for SQL Server Agent and for the SQL Server service need permissions on what
ever you need to do
(like accessing the backup share). I suggest you define a report file for yo
ur maint plan, as that
will probably give more details information about exactly what it is that ac
cess is denied for etc.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:4AD647D2-C767-4B8B-B02D-F1752D96D0C6@.microsoft.com...[vbcol=seagreen]
> looks like the gui has a selection do not keep longer than 4 weeks which w
ill
> work for what I needed. I tried to start the server agent service and get
> the following error,
> error 5-access is denied. I am able to access everything on the dbase
> server so not sure why I am getting this error. Do you know where I need
to
> check the permissions? thanks.
> --
> Paul G
> Software engineer.
>
> "Tibor Karaszi" wrote:
>

database backup-overwrites old backupfile?

Hi just wondering when you set up a scheluled database backup, does the old
backup file get written over each time the scheduled backup takes place as
this is what I would like it to do?
thanks.
--
Paul G
Software engineer.The BACKUP command does not overwrite by default. Defile is NOINIT which is append. To overwrite,
specify INIT. If you schedule using some type if GUI instead of typing the command, we need to know
more about that GUI and what checkboxes etc you have checked.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:D8C9F159-8933-4EF8-85E8-2873E9815B22@.microsoft.com...
> Hi just wondering when you set up a scheluled database backup, does the old
> backup file get written over each time the scheduled backup takes place as
> this is what I would like it to do?
> thanks.
> --
> Paul G
> Software engineer.|||Paul,
The default is NOINIT which appends the backup to the device. You can use
WITH INIT to overwrite the contents of the backup device.
See BACKUP in the SQL BOL for more details.
HTH
Jerry
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:D8C9F159-8933-4EF8-85E8-2873E9815B22@.microsoft.com...
> Hi just wondering when you set up a scheluled database backup, does the
> old
> backup file get written over each time the scheduled backup takes place as
> this is what I would like it to do?
> thanks.
> --
> Paul G
> Software engineer.|||ok thanks did use the gui to set up the schedule.
--
Paul G
Software engineer.
"Jerry Spivey" wrote:
> Paul,
> The default is NOINIT which appends the backup to the device. You can use
> WITH INIT to overwrite the contents of the backup device.
> See BACKUP in the SQL BOL for more details.
> HTH
> Jerry
> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> news:D8C9F159-8933-4EF8-85E8-2873E9815B22@.microsoft.com...
> > Hi just wondering when you set up a scheluled database backup, does the
> > old
> > backup file get written over each time the scheduled backup takes place as
> > this is what I would like it to do?
> > thanks.
> > --
> > Paul G
> > Software engineer.
>
>|||looks like the gui has a selection do not keep longer than 4 weeks which will
work for what I needed. I tried to start the server agent service and get
the following error,
error 5-access is denied. I am able to access everything on the dbase
server so not sure why I am getting this error. Do you know where I need to
check the permissions? thanks.
--
Paul G
Software engineer.
"Tibor Karaszi" wrote:
> The BACKUP command does not overwrite by default. Defile is NOINIT which is append. To overwrite,
> specify INIT. If you schedule using some type if GUI instead of typing the command, we need to know
> more about that GUI and what checkboxes etc you have checked.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> news:D8C9F159-8933-4EF8-85E8-2873E9815B22@.microsoft.com...
> > Hi just wondering when you set up a scheluled database backup, does the old
> > backup file get written over each time the scheduled backup takes place as
> > this is what I would like it to do?
> > thanks.
> > --
> > Paul G
> > Software engineer.
>|||By GUI, I assume you mean the Maintenance Plan Wizard. Yes, it has an option to delete old backup
files. It creates a new file each time you do backup, including a time stamp in the file name. As
for the access denied errors, we need more information. First, understand that the service account
for SQL Server Agent and for the SQL Server service need permissions on whatever you need to do
(like accessing the backup share). I suggest you define a report file for your maint plan, as that
will probably give more details information about exactly what it is that access is denied for etc.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:4AD647D2-C767-4B8B-B02D-F1752D96D0C6@.microsoft.com...
> looks like the gui has a selection do not keep longer than 4 weeks which will
> work for what I needed. I tried to start the server agent service and get
> the following error,
> error 5-access is denied. I am able to access everything on the dbase
> server so not sure why I am getting this error. Do you know where I need to
> check the permissions? thanks.
> --
> Paul G
> Software engineer.
>
> "Tibor Karaszi" wrote:
>> The BACKUP command does not overwrite by default. Defile is NOINIT which is append. To overwrite,
>> specify INIT. If you schedule using some type if GUI instead of typing the command, we need to
>> know
>> more about that GUI and what checkboxes etc you have checked.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> Blog: http://solidqualitylearning.com/blogs/tibor/
>>
>> "Paul" <Paul@.discussions.microsoft.com> wrote in message
>> news:D8C9F159-8933-4EF8-85E8-2873E9815B22@.microsoft.com...
>> > Hi just wondering when you set up a scheluled database backup, does the old
>> > backup file get written over each time the scheduled backup takes place as
>> > this is what I would like it to do?
>> > thanks.
>> > --
>> > Paul G
>> > Software engineer.
>>

Database Backup

Hi All,
We have SQL Server 2000. There were daily backup jobs scheduled and the file
size has grown very big 159 GB. How can we move this. Is there any way to
break this file and move. if we take fresh backup and delete this file will
there be any effect on the database. Backup and data are in the same drive.
Thank you in Advance.Kris
WINRAR,WINZIP to compress them?
"Kris" <Kris@.discussions.microsoft.com> wrote in message
news:561A8D62-B50E-4808-AA10-A63300829165@.microsoft.com...
> Hi All,
> We have SQL Server 2000. There were daily backup jobs scheduled and the
> file
> size has grown very big 159 GB. How can we move this. Is there any way to
> break this file and move. if we take fresh backup and delete this file
> will
> there be any effect on the database. Backup and data are in the same
> drive.
> Thank you in Advance.|||Hi Kris,
You can do a fresh backup without appending to that "big" file and if the
backup is OK (test by restoring) you can delete the 159 GB File. No,
removing an old backup has no effect on the database itself [unless you
lose the database and you desperately need that backup ]
Nathan H. Omukwenyi
"Kris" <Kris@.discussions.microsoft.com> wrote in message
news:561A8D62-B50E-4808-AA10-A63300829165@.microsoft.com...
> Hi All,
> We have SQL Server 2000. There were daily backup jobs scheduled and the
> file
> size has grown very big 159 GB. How can we move this. Is there any way to
> break this file and move. if we take fresh backup and delete this file
> will
> there be any effect on the database. Backup and data are in the same
> drive.
> Thank you in Advance.|||Hi Nathan,
At present i do not have any disk space in this drive where SQL is also
there can i do the backup in other drive will there be any problem. The
previous administrator should't have taken daily backup in the same drive.
Now i am just sorting out this issue. Should i take the backup of all the
databses and master then delete this will there be any critical issues. Any
precautions during this process or did i miss any thing else to do backup.
Thank you once again
"Nathan H. Omukwenyi" wrote:

> Hi Kris,
> You can do a fresh backup without appending to that "big" file and if the
> backup is OK (test by restoring) you can delete the 159 GB File. No,
> removing an old backup has no effect on the database itself [unless y
ou
> lose the database and you desperately need that backup ]
> Nathan H. Omukwenyi
> "Kris" <Kris@.discussions.microsoft.com> wrote in message
> news:561A8D62-B50E-4808-AA10-A63300829165@.microsoft.com...
>
>|||Best way is to backup all your databases except tempdb to another drive.
There will be no problem for SQL-Server. make sure you make a full back-up
But before you delete the old backup files why don't you put them on a tape
"Kris" wrote:
[vbcol=seagreen]
> Hi Nathan,
> At present i do not have any disk space in this drive where SQL is also
> there can i do the backup in other drive will there be any problem. The
> previous administrator should't have taken daily backup in the same drive.
> Now i am just sorting out this issue. Should i take the backup of all the
> databses and master then delete this will there be any critical issues. An
y
> precautions during this process or did i miss any thing else to do backup.
> Thank you once again
>
> "Nathan H. Omukwenyi" wrote:
>|||Right now take a backup on shared drive.
Then delete the 159gb backup file on your drive.
In future do not put backup data on the same drive, or copy backup
daily to tape from drive.
This is required because if disk will fail you will lose both data and
backup.
One more thing do not append backup on same file. In stead keep backup
policy to have different file for each backup and maintain 2-3 days
backup on drive and delete old backup.
In tape we keep backup of last 7 days, every sunday backup of last four
week and a bakcup of last month. This is the policy which we follows.
Regards
Amish Shah|||Zekske
Actually there is no tape device with this server the previous admin person
just created a folder in the SQL Server and scheduled backup jobs in the
same place where data is stored daily.
Now i have paused all backup scheduled jobs. The left out space now is 350
MB will it crash and we are working on a solution. How we can move this to
other server which has more space but it is SUN.
Just working on.. any advise , Thank you once again guys.
"Zekske" wrote:
[vbcol=seagreen]
> Best way is to backup all your databases except tempdb to another drive.
> There will be no problem for SQL-Server. make sure you make a full back-up
> But before you delete the old backup files why don't you put them on a tap
e
> "Kris" wrote:
>|||Amish
At present we do not have such a big disk space. And we do not have tape
drive attached. Prior to this it was backedup in the same drive. We have Sun
unix systems which has good disk space and also backup tape drives we are
aksing our unix guys. Do you know any way we can move or copy this files.
Thank you..
"amish" wrote:

> Right now take a backup on shared drive.
> Then delete the 159gb backup file on your drive.
> In future do not put backup data on the same drive, or copy backup
> daily to tape from drive.
> This is required because if disk will fail you will lose both data and
> backup.
> One more thing do not append backup on same file. In stead keep backup
> policy to have different file for each backup and maintain 2-3 days
> backup on drive and delete old backup.
> In tape we keep backup of last 7 days, every sunday backup of last four
> week and a bakcup of last month. This is the policy which we follows.
> Regards
> Amish Shah
>|||"Kris" <Kris@.discussions.microsoft.com> wrote in message
news:2A7AC679-2081-44D1-966A-A70395C2124C@.microsoft.com...
> Amish
> At present we do not have such a big disk space. And we do not have tape
> drive attached. Prior to this it was backedup in the same drive. We have
Sun
> unix systems which has good disk space and also backup tape drives we are
> aksing our unix guys. Do you know any way we can move or copy this files.
>
If you can run a version of Samba on the SUN system, you can create a shared
drive and backup to that.
I would do what others suggested. Make a full backup to the shared drive
and then delete the 159gb drive.
I would also suggest taht you setup the backups to go to a DIFFERENT file
each time (and then deleting the oldest files).
For example, 7 scripts, one for each day of the week that backups to
\\remoteSunshare\Monday, Tuesday, etc.
Or use the maintenance wizard and setup on a daily (or however often) one to
back up and keep N copies around.
[vbcol=seagreen]
> Thank you..
> "amish" wrote:
>|||Dear Greg & All
Thank you once again, I shall do as suggested.
Keep up the good work
Regards
"Greg D. Moore (Strider)" wrote:

> "Kris" <Kris@.discussions.microsoft.com> wrote in message
> news:2A7AC679-2081-44D1-966A-A70395C2124C@.microsoft.com...
> Sun
> If you can run a version of Samba on the SUN system, you can create a shar
ed
> drive and backup to that.
> I would do what others suggested. Make a full backup to the shared drive
> and then delete the 159gb drive.
> I would also suggest taht you setup the backups to go to a DIFFERENT file
> each time (and then deleting the oldest files).
> For example, 7 scripts, one for each day of the week that backups to
> \\remoteSunshare\Monday, Tuesday, etc.
> Or use the maintenance wizard and setup on a daily (or however often) one
to
> back up and keep N copies around.
>
>
>

Database Backup

Hi All,
We have SQL Server 2000. There were daily backup jobs scheduled and the file
size has grown very big 159 GB. How can we move this. Is there any way to
break this file and move. if we take fresh backup and delete this file will
there be any effect on the database. Backup and data are in the same drive.
Thank you in Advance.Kris
WINRAR,WINZIP to compress them?
"Kris" <Kris@.discussions.microsoft.com> wrote in message
news:561A8D62-B50E-4808-AA10-A63300829165@.microsoft.com...
> Hi All,
> We have SQL Server 2000. There were daily backup jobs scheduled and the
> file
> size has grown very big 159 GB. How can we move this. Is there any way to
> break this file and move. if we take fresh backup and delete this file
> will
> there be any effect on the database. Backup and data are in the same
> drive.
> Thank you in Advance.|||Hi Kris,
You can do a fresh backup without appending to that "big" file and if the
backup is OK (test by restoring) you can delete the 159 GB File. No,
removing an old backup has no effect on the database itself [unless you
lose the database and you desperately need that backup :)]
Nathan H. Omukwenyi
"Kris" <Kris@.discussions.microsoft.com> wrote in message
news:561A8D62-B50E-4808-AA10-A63300829165@.microsoft.com...
> Hi All,
> We have SQL Server 2000. There were daily backup jobs scheduled and the
> file
> size has grown very big 159 GB. How can we move this. Is there any way to
> break this file and move. if we take fresh backup and delete this file
> will
> there be any effect on the database. Backup and data are in the same
> drive.
> Thank you in Advance.|||Hi Nathan,
At present i do not have any disk space in this drive where SQL is also
there can i do the backup in other drive will there be any problem. The
previous administrator should't have taken daily backup in the same drive.
Now i am just sorting out this issue. Should i take the backup of all the
databses and master then delete this will there be any critical issues. Any
precautions during this process or did i miss any thing else to do backup.
Thank you once again
"Nathan H. Omukwenyi" wrote:
> Hi Kris,
> You can do a fresh backup without appending to that "big" file and if the
> backup is OK (test by restoring) you can delete the 159 GB File. No,
> removing an old backup has no effect on the database itself [unless you
> lose the database and you desperately need that backup :)]
> Nathan H. Omukwenyi
> "Kris" <Kris@.discussions.microsoft.com> wrote in message
> news:561A8D62-B50E-4808-AA10-A63300829165@.microsoft.com...
> > Hi All,
> > We have SQL Server 2000. There were daily backup jobs scheduled and the
> > file
> > size has grown very big 159 GB. How can we move this. Is there any way to
> > break this file and move. if we take fresh backup and delete this file
> > will
> > there be any effect on the database. Backup and data are in the same
> > drive.
> >
> > Thank you in Advance.
>
>|||Best way is to backup all your databases except tempdb to another drive.
There will be no problem for SQL-Server. make sure you make a full back-up
But before you delete the old backup files why don't you put them on a tape
"Kris" wrote:
> Hi Nathan,
> At present i do not have any disk space in this drive where SQL is also
> there can i do the backup in other drive will there be any problem. The
> previous administrator should't have taken daily backup in the same drive.
> Now i am just sorting out this issue. Should i take the backup of all the
> databses and master then delete this will there be any critical issues. Any
> precautions during this process or did i miss any thing else to do backup.
> Thank you once again
>
> "Nathan H. Omukwenyi" wrote:
> > Hi Kris,
> >
> > You can do a fresh backup without appending to that "big" file and if the
> > backup is OK (test by restoring) you can delete the 159 GB File. No,
> > removing an old backup has no effect on the database itself [unless you
> > lose the database and you desperately need that backup :)]
> >
> > Nathan H. Omukwenyi
> >
> > "Kris" <Kris@.discussions.microsoft.com> wrote in message
> > news:561A8D62-B50E-4808-AA10-A63300829165@.microsoft.com...
> > > Hi All,
> > > We have SQL Server 2000. There were daily backup jobs scheduled and the
> > > file
> > > size has grown very big 159 GB. How can we move this. Is there any way to
> > > break this file and move. if we take fresh backup and delete this file
> > > will
> > > there be any effect on the database. Backup and data are in the same
> > > drive.
> > >
> > > Thank you in Advance.
> >
> >
> >|||Right now take a backup on shared drive.
Then delete the 159gb backup file on your drive.
In future do not put backup data on the same drive, or copy backup
daily to tape from drive.
This is required because if disk will fail you will lose both data and
backup.
One more thing do not append backup on same file. In stead keep backup
policy to have different file for each backup and maintain 2-3 days
backup on drive and delete old backup.
In tape we keep backup of last 7 days, every sunday backup of last four
week and a bakcup of last month. This is the policy which we follows.
Regards
Amish Shah|||Zekske
Actually there is no tape device with this server the previous admin person
just created a folder in the SQL Server and scheduled backup jobs in the
same place where data is stored daily.
Now i have paused all backup scheduled jobs. The left out space now is 350
MB will it crash and we are working on a solution. How we can move this to
other server which has more space but it is SUN.
Just working on.. any advise , Thank you once again guys.
"Zekske" wrote:
> Best way is to backup all your databases except tempdb to another drive.
> There will be no problem for SQL-Server. make sure you make a full back-up
> But before you delete the old backup files why don't you put them on a tape
> "Kris" wrote:
> > Hi Nathan,
> > At present i do not have any disk space in this drive where SQL is also
> > there can i do the backup in other drive will there be any problem. The
> > previous administrator should't have taken daily backup in the same drive.
> > Now i am just sorting out this issue. Should i take the backup of all the
> > databses and master then delete this will there be any critical issues. Any
> > precautions during this process or did i miss any thing else to do backup.
> >
> > Thank you once again
> >
> >
> > "Nathan H. Omukwenyi" wrote:
> >
> > > Hi Kris,
> > >
> > > You can do a fresh backup without appending to that "big" file and if the
> > > backup is OK (test by restoring) you can delete the 159 GB File. No,
> > > removing an old backup has no effect on the database itself [unless you
> > > lose the database and you desperately need that backup :)]
> > >
> > > Nathan H. Omukwenyi
> > >
> > > "Kris" <Kris@.discussions.microsoft.com> wrote in message
> > > news:561A8D62-B50E-4808-AA10-A63300829165@.microsoft.com...
> > > > Hi All,
> > > > We have SQL Server 2000. There were daily backup jobs scheduled and the
> > > > file
> > > > size has grown very big 159 GB. How can we move this. Is there any way to
> > > > break this file and move. if we take fresh backup and delete this file
> > > > will
> > > > there be any effect on the database. Backup and data are in the same
> > > > drive.
> > > >
> > > > Thank you in Advance.
> > >
> > >
> > >|||Amish
At present we do not have such a big disk space. And we do not have tape
drive attached. Prior to this it was backedup in the same drive. We have Sun
unix systems which has good disk space and also backup tape drives we are
aksing our unix guys. Do you know any way we can move or copy this files.
Thank you..
"amish" wrote:
> Right now take a backup on shared drive.
> Then delete the 159gb backup file on your drive.
> In future do not put backup data on the same drive, or copy backup
> daily to tape from drive.
> This is required because if disk will fail you will lose both data and
> backup.
> One more thing do not append backup on same file. In stead keep backup
> policy to have different file for each backup and maintain 2-3 days
> backup on drive and delete old backup.
> In tape we keep backup of last 7 days, every sunday backup of last four
> week and a bakcup of last month. This is the policy which we follows.
> Regards
> Amish Shah
>|||"Kris" <Kris@.discussions.microsoft.com> wrote in message
news:2A7AC679-2081-44D1-966A-A70395C2124C@.microsoft.com...
> Amish
> At present we do not have such a big disk space. And we do not have tape
> drive attached. Prior to this it was backedup in the same drive. We have
Sun
> unix systems which has good disk space and also backup tape drives we are
> aksing our unix guys. Do you know any way we can move or copy this files.
>
If you can run a version of Samba on the SUN system, you can create a shared
drive and backup to that.
I would do what others suggested. Make a full backup to the shared drive
and then delete the 159gb drive.
I would also suggest taht you setup the backups to go to a DIFFERENT file
each time (and then deleting the oldest files).
For example, 7 scripts, one for each day of the week that backups to
\\remoteSunshare\Monday, Tuesday, etc.
Or use the maintenance wizard and setup on a daily (or however often) one to
back up and keep N copies around.
> Thank you..
> "amish" wrote:
> > Right now take a backup on shared drive.
> > Then delete the 159gb backup file on your drive.
> >
> > In future do not put backup data on the same drive, or copy backup
> > daily to tape from drive.
> > This is required because if disk will fail you will lose both data and
> > backup.
> >
> > One more thing do not append backup on same file. In stead keep backup
> > policy to have different file for each backup and maintain 2-3 days
> > backup on drive and delete old backup.
> >
> > In tape we keep backup of last 7 days, every sunday backup of last four
> > week and a bakcup of last month. This is the policy which we follows.
> >
> > Regards
> > Amish Shah
> >
> >|||Dear Greg & All
Thank you once again, I shall do as suggested.
Keep up the good work
Regards
"Greg D. Moore (Strider)" wrote:
> "Kris" <Kris@.discussions.microsoft.com> wrote in message
> news:2A7AC679-2081-44D1-966A-A70395C2124C@.microsoft.com...
> > Amish
> > At present we do not have such a big disk space. And we do not have tape
> > drive attached. Prior to this it was backedup in the same drive. We have
> Sun
> > unix systems which has good disk space and also backup tape drives we are
> > aksing our unix guys. Do you know any way we can move or copy this files.
> >
> If you can run a version of Samba on the SUN system, you can create a shared
> drive and backup to that.
> I would do what others suggested. Make a full backup to the shared drive
> and then delete the 159gb drive.
> I would also suggest taht you setup the backups to go to a DIFFERENT file
> each time (and then deleting the oldest files).
> For example, 7 scripts, one for each day of the week that backups to
> \\remoteSunshare\Monday, Tuesday, etc.
> Or use the maintenance wizard and setup on a daily (or however often) one to
> back up and keep N copies around.
>
> > Thank you..
> >
> > "amish" wrote:
> >
> > > Right now take a backup on shared drive.
> > > Then delete the 159gb backup file on your drive.
> > >
> > > In future do not put backup data on the same drive, or copy backup
> > > daily to tape from drive.
> > > This is required because if disk will fail you will lose both data and
> > > backup.
> > >
> > > One more thing do not append backup on same file. In stead keep backup
> > > policy to have different file for each backup and maintain 2-3 days
> > > backup on drive and delete old backup.
> > >
> > > In tape we keep backup of last 7 days, every sunday backup of last four
> > > week and a bakcup of last month. This is the policy which we follows.
> > >
> > > Regards
> > > Amish Shah
> > >
> > >
>
>