User profile for ChrisAVWood

Thanks Brian. Sounds like SQLBackup rounds down so 00:00:00 means less than 1 second. Chris / comments

Thanks Brian. Sounds like SQLBackup rounds down so 00:00:00 means less than 1 second. Chris

0 votes

Thanks for all the information. Chris / comments

Thanks for all the information. Chris

0 votes

Thats just the information that I needed. Thanks Chris / comments

Thats just the information that I needed. Thanks Chris

0 votes

I am seeing this issue now running 5.3.0.178 with jobs with VERIFY. I have the GUI open and when the job submitted by SQL Agent starts it shows as a Job under the In Progress tab. When it is running the processed amount goes up. If I look in the file folder where the backup is being written to and then note when the filesize shows a number I can now see the job under the Activity History tab as well as the In progress tab. If I look at the Jobs View History in SQL Agent is shows completed yet it is still visible under the In Progress tab. I tried the same without the VERIFY and just after the filesize showed in the folder it disappeared from the In Progress tab and showed up in both the Activity History tab and the SQL Agent View History. Maybe this is a problem with VERIFY. Chris / comments

I am seeing this issue now running 5.3.0.178 with jobs with VERIFY. I have the GUI open and when the job submitted by SQL Agent starts it shows as a Job under the In Progress tab. When it is runnin...

0 votes

Thanks for the update. That is really interesting. I will certainly test out the MOVE DATAFILES and MOVE LOGFILES options. I now need to ask this further question. We will be using AlwaysOn Availability Groups. The thinking is this currently. We have a database on say the dev server, in a different location than the prod backup. We take the dev database out of the availability group and then restore the prod backup to both server A with recovery and to server B with norecovery. Then put the databases back into the availability group. Based on what you have said and I saw I need the MOVE statements this first time. Now this stays the same for a few days and we start taking backups, on the node that the availability group allows. Now we have to perform another restore from prod to dev. Will I still need the MOVE or will SQL2012 remember where the databases reside on dev and I can restore without the MOVE? Thanks Chris / comments

Thanks for the update. That is really interesting. I will certainly test out the MOVE DATAFILES and MOVE LOGFILES options. I now need to ask this further question. We will be using AlwaysOn Availab...

0 votes

Pete, Here is what I did. I created the new database under E:\applctn\ahah\devl\database with 3 files, SYS/DATA_001 and LOG_001. This is in SQL2012 running on W2K12. I had a backup taken using SQLBackup 7.1 in SQL2005 on W2K3R2 of the prod database where it resides under [image] \applctn\ahah\prod\database with the same 3 files, SYS/DATA_001 and LOG_001. The backup creates two files to speed the process up. I copied the 2 backups files to the W2K12 server. When I tried to run the script it failed because it tried to restore to [image] \applctn\ahah\prod\database. Once I put the moved statements in it worked fine and replaced the original databases I had created. I had this happen to another database under the same circumstances. This made me believe that maybe the restore from script had looked at the backup files for its location information rather than the master DB locations. We do lots of restored from production backups to at and dev servers where the file locations differ from the original ones and the script works fine. It gets its location information from the master DB rather than the backup file itself. Can you check this out please? Thanks Chris / comments

Pete, Here is what I did. I created the new database under E:\applctn\ahah\devl\database with 3 files, SYS/DATA_001 and LOG_001. This is in SQL2012 running on W2K12. I had a backup taken using SQLB...

0 votes

I should add the GUI works as expected. It is when you use a script. Chris / comments

I should add the GUI works as expected. It is when you use a script. Chris

0 votes

I am also interested in the permissions. Our current method involves using the windows account that runs SQL Server to be the account used to run SQLBackup. To install SQLBackup I had made this account a sysadmin. I then changed that to db_creator when I wanted to restore. We use a proxy to run the actual backup jobs. Now I believe that I would have to give the proxy account the availability groups permissions. Chris / comments

I am also interested in the permissions. Our current method involves using the windows account that runs SQL Server to be the account used to run SQLBackup. To install SQLBackup I had made this acc...

0 votes

Thanks Manfred. As I read more about AlwaysOn Availability Groups I see that most things have to be duplicated. Chris / comments

Thanks Manfred. As I read more about AlwaysOn Availability Groups I see that most things have to be duplicated. Chris

0 votes

Thanks Marianne. Sounds just like the reason I had included the VERIFYINTERVAL on advice from Pete Yeoh. Chris / comments

Thanks Marianne. Sounds just like the reason I had included the VERIFYINTERVAL on advice from Pete Yeoh. Chris

0 votes

How can we help you today?

ChrisAVWood

Comments