We are working on creating a copy of our SQL server machine for disaster
recovery purposes. ReportServerTempDB is purely a temp database, correct?
Meaning, the data in it does not need to be replicated from our production
server to our disaster recovery server, correct?
Could someone just verify this for me.
Thanks.Yes, you don't need to replicated your ReportServerTempDB
According to BOL "Backup and Restore Operations for a Reporting Services
Installation"
The only reason to backup the reportservertempdb is to avoid having to
recreate it if there is a hardware failure.
Med bouchenafa
"Jeff" <Jeff@.discussions.microsoft.com> a écrit dans le message de news:
C440E7E5-D027-4C98-9A8B-EA0C8C2B245B@.microsoft.com...
> We are working on creating a copy of our SQL server machine for disaster
> recovery purposes. ReportServerTempDB is purely a temp database, correct?
> Meaning, the data in it does not need to be replicated from our production
> server to our disaster recovery server, correct?
> Could someone just verify this for me.
> Thanks.|||Depends... are you talking disaster recovery... in which you would
re-establish services from a repository of stored data? ...or... are you
looking for fault tollerance where a more real-time fail over takes place
imediately after the falure due to disaster?
"Jeff" wrote:
> We are working on creating a copy of our SQL server machine for disaster
> recovery purposes. ReportServerTempDB is purely a temp database, correct?
> Meaning, the data in it does not need to be replicated from our production
> server to our disaster recovery server, correct?
> Could someone just verify this for me.
> Thanks.|||Ken,
We're looking a the former. We have an offsite repository of data, which we
would use to re-establish services in the event of a fire or something like
that. This isn't for real time failover.
"Ken Carter" wrote:
> Depends... are you talking disaster recovery... in which you would
> re-establish services from a repository of stored data? ...or... are you
> looking for fault tollerance where a more real-time fail over takes place
> imediately after the falure due to disaster?
> "Jeff" wrote:
> > We are working on creating a copy of our SQL server machine for disaster
> > recovery purposes. ReportServerTempDB is purely a temp database, correct?
> > Meaning, the data in it does not need to be replicated from our production
> > server to our disaster recovery server, correct?
> >
> > Could someone just verify this for me.
> >
> > Thanks.
Showing posts with label recovery. Show all posts
Showing posts with label recovery. Show all posts
Friday, March 23, 2012
Wednesday, March 7, 2012
ReportIoError 2 - Further Info
Context
--
The first of the failed log backups was run after a series
of indexes on the database were rebuilt.
Recovery mode is changed to "bulk-logged" before rebuiding
indexes. This is followed by the log backup and then
recovery mode is changed back to "full".
Additional Error Messages in SQL Server Log
---
BackupMedium::ReportIoError: write failure on backup
device 'D:\mssql7\backup\Proclaim_backup.bak'. Operating
system error 2(error not found).
Internal I/O request 0x2E45D1A8: Op: Write, pBuffer:
0x3BE50000, Size: 65536, Position: 4293497344, UMS:
Internal: 0x103, InternalHigh: 0x0, Offset: 0xFFE99200,
OffsetHigh: 0x0, m_buf: 0x3BE50000, m_len: 65536,
m_actualBytes: 0, m_errcode: 2, BackupFile: D:\mssql7
\backup\Proclaim_backup.bak
BACKUP failed to complete the command BACKUP LOG
[Proclaim] TO DISK = N'D:\mssql7
\backup\Proclaim_backup.bak' WITH NOINIT , NOUNLOAD ,
NAME = N'Proclaim backup', SKIP , STATS = 10, NOFORMATHi Kim,
When ever you perform a recovery model change, it is always suggested to do
a full database backup and
then goahead with Transaction log backup.
This I/O issue can araises due to free space in hard disk, permissions on
the disk.
Thanks
Hari
MCDBA
"Kim" <anonymous@.discussions.microsoft.com> wrote in message
news:25bce01c46248$42024970$a601280a@.phx
.gbl...
> Context
> --
> The first of the failed log backups was run after a series
> of indexes on the database were rebuilt.
> Recovery mode is changed to "bulk-logged" before rebuiding
> indexes. This is followed by the log backup and then
> recovery mode is changed back to "full".
>
> Additional Error Messages in SQL Server Log
> ---
> BackupMedium::ReportIoError: write failure on backup
> device 'D:\mssql7\backup\Proclaim_backup.bak'. Operating
> system error 2(error not found).
> Internal I/O request 0x2E45D1A8: Op: Write, pBuffer:
> 0x3BE50000, Size: 65536, Position: 4293497344, UMS:
> Internal: 0x103, InternalHigh: 0x0, Offset: 0xFFE99200,
> OffsetHigh: 0x0, m_buf: 0x3BE50000, m_len: 65536,
> m_actualBytes: 0, m_errcode: 2, BackupFile: D:\mssql7
> \backup\Proclaim_backup.bak
> BACKUP failed to complete the command BACKUP LOG
> [Proclaim] TO DISK = N'D:\mssql7
> \backup\Proclaim_backup.bak' WITH NOINIT , NOUNLOAD ,
> NAME = N'Proclaim backup', SKIP , STATS = 10, NOFORMAT|||Thanks for the suggestion.
I'll add a full backup to the scheduled job before and
after the recovery mode change and see if the issue
persists.
--
The first of the failed log backups was run after a series
of indexes on the database were rebuilt.
Recovery mode is changed to "bulk-logged" before rebuiding
indexes. This is followed by the log backup and then
recovery mode is changed back to "full".
Additional Error Messages in SQL Server Log
---
BackupMedium::ReportIoError: write failure on backup
device 'D:\mssql7\backup\Proclaim_backup.bak'. Operating
system error 2(error not found).
Internal I/O request 0x2E45D1A8: Op: Write, pBuffer:
0x3BE50000, Size: 65536, Position: 4293497344, UMS:
Internal: 0x103, InternalHigh: 0x0, Offset: 0xFFE99200,
OffsetHigh: 0x0, m_buf: 0x3BE50000, m_len: 65536,
m_actualBytes: 0, m_errcode: 2, BackupFile: D:\mssql7
\backup\Proclaim_backup.bak
BACKUP failed to complete the command BACKUP LOG
[Proclaim] TO DISK = N'D:\mssql7
\backup\Proclaim_backup.bak' WITH NOINIT , NOUNLOAD ,
NAME = N'Proclaim backup', SKIP , STATS = 10, NOFORMATHi Kim,
When ever you perform a recovery model change, it is always suggested to do
a full database backup and
then goahead with Transaction log backup.
This I/O issue can araises due to free space in hard disk, permissions on
the disk.
Thanks
Hari
MCDBA
"Kim" <anonymous@.discussions.microsoft.com> wrote in message
news:25bce01c46248$42024970$a601280a@.phx
.gbl...
> Context
> --
> The first of the failed log backups was run after a series
> of indexes on the database were rebuilt.
> Recovery mode is changed to "bulk-logged" before rebuiding
> indexes. This is followed by the log backup and then
> recovery mode is changed back to "full".
>
> Additional Error Messages in SQL Server Log
> ---
> BackupMedium::ReportIoError: write failure on backup
> device 'D:\mssql7\backup\Proclaim_backup.bak'. Operating
> system error 2(error not found).
> Internal I/O request 0x2E45D1A8: Op: Write, pBuffer:
> 0x3BE50000, Size: 65536, Position: 4293497344, UMS:
> Internal: 0x103, InternalHigh: 0x0, Offset: 0xFFE99200,
> OffsetHigh: 0x0, m_buf: 0x3BE50000, m_len: 65536,
> m_actualBytes: 0, m_errcode: 2, BackupFile: D:\mssql7
> \backup\Proclaim_backup.bak
> BACKUP failed to complete the command BACKUP LOG
> [Proclaim] TO DISK = N'D:\mssql7
> \backup\Proclaim_backup.bak' WITH NOINIT , NOUNLOAD ,
> NAME = N'Proclaim backup', SKIP , STATS = 10, NOFORMAT|||Thanks for the suggestion.
I'll add a full backup to the scheduled job before and
after the recovery mode change and see if the issue
persists.
ReportIoError 2 - Further Info
Context
The first of the failed log backups was run after a series
of indexes on the database were rebuilt.
Recovery mode is changed to "bulk-logged" before rebuiding
indexes. This is followed by the log backup and then
recovery mode is changed back to "full".
Additional Error Messages in SQL Server Log
BackupMedium::ReportIoError: write failure on backup
device 'D:\mssql7\backup\Proclaim_backup.bak'. Operating
system error 2(error not found).
Internal I/O request 0x2E45D1A8: Op: Write, pBuffer:
0x3BE50000, Size: 65536, Position: 4293497344, UMS:
Internal: 0x103, InternalHigh: 0x0, Offset: 0xFFE99200,
OffsetHigh: 0x0, m_buf: 0x3BE50000, m_len: 65536,
m_actualBytes: 0, m_errcode: 2, BackupFile: D:\mssql7
\backup\Proclaim_backup.bak
BACKUP failed to complete the command BACKUP LOG
[Proclaim] TO DISK = N'D:\mssql7
\backup\Proclaim_backup.bak' WITH NOINIT , NOUNLOAD ,
NAME = N'Proclaim backup', SKIP , STATS = 10, NOFORMAT
Hi Kim,
When ever you perform a recovery model change, it is always suggested to do
a full database backup and
then goahead with Transaction log backup.
This I/O issue can araises due to free space in hard disk, permissions on
the disk.
Thanks
Hari
MCDBA
"Kim" <anonymous@.discussions.microsoft.com> wrote in message
news:25bce01c46248$42024970$a601280a@.phx.gbl...
> Context
> --
> The first of the failed log backups was run after a series
> of indexes on the database were rebuilt.
> Recovery mode is changed to "bulk-logged" before rebuiding
> indexes. This is followed by the log backup and then
> recovery mode is changed back to "full".
>
> Additional Error Messages in SQL Server Log
> BackupMedium::ReportIoError: write failure on backup
> device 'D:\mssql7\backup\Proclaim_backup.bak'. Operating
> system error 2(error not found).
> Internal I/O request 0x2E45D1A8: Op: Write, pBuffer:
> 0x3BE50000, Size: 65536, Position: 4293497344, UMS:
> Internal: 0x103, InternalHigh: 0x0, Offset: 0xFFE99200,
> OffsetHigh: 0x0, m_buf: 0x3BE50000, m_len: 65536,
> m_actualBytes: 0, m_errcode: 2, BackupFile: D:\mssql7
> \backup\Proclaim_backup.bak
> BACKUP failed to complete the command BACKUP LOG
> [Proclaim] TO DISK = N'D:\mssql7
> \backup\Proclaim_backup.bak' WITH NOINIT , NOUNLOAD ,
> NAME = N'Proclaim backup', SKIP , STATS = 10, NOFORMAT
|||Thanks for the suggestion.
I'll add a full backup to the scheduled job before and
after the recovery mode change and see if the issue
persists.
The first of the failed log backups was run after a series
of indexes on the database were rebuilt.
Recovery mode is changed to "bulk-logged" before rebuiding
indexes. This is followed by the log backup and then
recovery mode is changed back to "full".
Additional Error Messages in SQL Server Log
BackupMedium::ReportIoError: write failure on backup
device 'D:\mssql7\backup\Proclaim_backup.bak'. Operating
system error 2(error not found).
Internal I/O request 0x2E45D1A8: Op: Write, pBuffer:
0x3BE50000, Size: 65536, Position: 4293497344, UMS:
Internal: 0x103, InternalHigh: 0x0, Offset: 0xFFE99200,
OffsetHigh: 0x0, m_buf: 0x3BE50000, m_len: 65536,
m_actualBytes: 0, m_errcode: 2, BackupFile: D:\mssql7
\backup\Proclaim_backup.bak
BACKUP failed to complete the command BACKUP LOG
[Proclaim] TO DISK = N'D:\mssql7
\backup\Proclaim_backup.bak' WITH NOINIT , NOUNLOAD ,
NAME = N'Proclaim backup', SKIP , STATS = 10, NOFORMAT
Hi Kim,
When ever you perform a recovery model change, it is always suggested to do
a full database backup and
then goahead with Transaction log backup.
This I/O issue can araises due to free space in hard disk, permissions on
the disk.
Thanks
Hari
MCDBA
"Kim" <anonymous@.discussions.microsoft.com> wrote in message
news:25bce01c46248$42024970$a601280a@.phx.gbl...
> Context
> --
> The first of the failed log backups was run after a series
> of indexes on the database were rebuilt.
> Recovery mode is changed to "bulk-logged" before rebuiding
> indexes. This is followed by the log backup and then
> recovery mode is changed back to "full".
>
> Additional Error Messages in SQL Server Log
> BackupMedium::ReportIoError: write failure on backup
> device 'D:\mssql7\backup\Proclaim_backup.bak'. Operating
> system error 2(error not found).
> Internal I/O request 0x2E45D1A8: Op: Write, pBuffer:
> 0x3BE50000, Size: 65536, Position: 4293497344, UMS:
> Internal: 0x103, InternalHigh: 0x0, Offset: 0xFFE99200,
> OffsetHigh: 0x0, m_buf: 0x3BE50000, m_len: 65536,
> m_actualBytes: 0, m_errcode: 2, BackupFile: D:\mssql7
> \backup\Proclaim_backup.bak
> BACKUP failed to complete the command BACKUP LOG
> [Proclaim] TO DISK = N'D:\mssql7
> \backup\Proclaim_backup.bak' WITH NOINIT , NOUNLOAD ,
> NAME = N'Proclaim backup', SKIP , STATS = 10, NOFORMAT
|||Thanks for the suggestion.
I'll add a full backup to the scheduled job before and
after the recovery mode change and see if the issue
persists.
Subscribe to:
Posts (Atom)