Comments
Sort by recent activity
How about creating 2 steps in backup job at primary server.. (instead of restricting by size)
1. for taking TL backup
2. for moving TL backup file to standby server location.
if TL backup move step is taking long time, then I can execute step 1 seperatly. (like microsoft logshipping architect itself)
:idea: / comments
How about creating 2 steps in backup job at primary server.. (instead of restricting by size)
1. for taking TL backup
2. for moving TL backup file to standby server location.
if TL backup move step...
I accept, this could be a case to avoid generation of heavy log. But its production environment and all activities should be fully logged.. Can’t play with database and its core-environment!! Another, we have very complicated system architect a lot many things are dependent on it.
Thanks again :-) / comments
I accept, this could be a case to avoid generation of heavy log. But its production environment and all activities should be fully logged.. Can’t play with database and its core-environment!! Ano...
Any Reply ??
This is very comman issue, I am sure its not happening only in our scenario!! Well, does it mean.. I should:
- remove logshipping
- Keep taking transaction log backups
- use own set of process to move TL backups to remote side
- Configure a job to restore TL backup files, and move to another folder..
Ahh a lot work.. * (what if somebody has over 100's databases) / comments
Any Reply ??
This is very comman issue, I am sure its not happening only in our scenario!! Well, does it mean.. I should:
- remove logshipping
- Keep taking transaction log backups
- use own set o...
upppppps No reply :shock: :roll: / comments
upppppps No reply :shock: :roll:
BTW, How long 5.2 release would take? any time-duration. Would you be able to provide us a hotfix or patch for this issue before 5.2 release.
I am affraid to apply manual logic for settingup logshipping over 100s databases.
:shock: / comments
BTW, How long 5.2 release would take? any time-duration. Would you be able to provide us a hotfix or patch for this issue before 5.2 release.
I am affraid to apply manual logic for settingup logshi...
Test Case 2:
It's sql backup version 5.1.0.2781 installed on SQL Server 2000 Ent Edition. For another test when I am configuring logshipping between
logshipping (primary db)
logshipping_test (standby, for for configuring logshipping)
Could some please explain, why logshipping configuration steps start with
'backing up source database' and 'restoring database to destination server' even though I am already giving standby database name and details :?: / comments
Test Case 2:
It's sql backup version 5.1.0.2781 installed on SQL Server 2000 Ent Edition. For another test when I am configuring logshipping between
logshipping (primary db)
logshipping_test (stand...