SQL log backup change temporary folder

[OmiFreak]

Hello,

We backup SQL transaction log from some bigger servers with Veeam.
Veeam makes a normal SQL transaction log backup to a temporary folder ("C:\Documents and Settings\All Users\Application Data\Veeam\Backup\SqlLogBackup\) first.
With a high amount of logs this could be a problem because C:\ is running out of disk space.
Is there a way to change this path to another drive?

Regards,
Bernd

[veremin]

You can set a different folder by using SqlTempLogPath (STRING) regkey on the SQL Server. Thanks.

[darren.goobey]

On a SQL Server in "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Veeam\Veeam Backup and Replication" try adding a registry key 'SqlTempLogPath' of type String. And specify a destination path. Important note: do not add "\" to the end of the path! Out of interest what are the size of your SQL transaction log backups for your bigger servers? Did you ever consider using RedGate SQL Backup?

[OmiFreak]

Thank you for the answer.
I added the key but nothing changed. Do I need to restart something to take this affect?

@darrem: Our biggest SQL server has 300GB logfiles, the log backup itself can go up to 50GB. Never consider RedGate. If possible I want to have all our backup in one software to keep things simple.

[veremin]

Just to be sure you've created it on a SQL VM, not a backup server, right?

[OmiFreak]

Yes on the SQL VM. I tried it under [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Veeam\Veeam Backup and Replication] and [HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication]. because there was no Veeam in Wow6432Node.

[veremin]

Restart backup log service is necessary inside the guest VM. However, it should happen automatically, once the current log collection interval expires. If that doesn't occur, try to restart the said service manually and see whether it helps or not.

[OmiFreak]

After restarting the log service it use the new path.

[veremin]

Thank you for the confirmation. Should other help be needed, feel free to ask.

[jwmaynar]

I saw on another thread there there is a way to change the directory that Veeam uses to hold logs on the log shipping server. It seems to default to C:\Windows\Temp but what do you need to change in the registry to change that directory?

[foggy]

Please review the thread above for details.

[jwmaynar]

Foggy,

The above thread seem to be about how to change the directory on the SQL server, not the Backup server. I'm looking to change the directory on the backup server that is used as the intermediate destination for the logs before they are more into the backup repository. In our case the SQL servers do not have direct access to our repositories.

Thanks!

[foggy]

Right, my bad. However, seems there's no similar key for the case when log shipping server is used.

[andreash]

Hi,

trying to implement this onto our SQL Server as well. Could you please detail the location of the registry key and which Service to restart?
I'm afraid there is no VEEAM structure in the Wow6432 Node.

Regards,
Andreas

[foggy]

The key depends on the OS, so you can specify the value in both locations, for reliability. The service is called either Veeam SQL Service or Veeam Log Shipper, as far as I can recall.

[DeaconZ]

Trying to do this as well since a large Tlog backup filled up my C drive on the SQL VM. I can't find any service on the SQL or Veeam server named like what is referenced.

[veremin]

So, the SQL VM is processed with AAIP enabled and the log job is enabled for it? In the meantime, there is no service inside this VM that looks like Veeam SQL Service or Veeam Log Shipper? Are there any services inside SQL VM which have Veeam as a prefix? If so, what are those services?

[foggy]

The exact name of the service is VeeamLogShipper.

[DeaconZ]

Yes. SQL VM's with AAIP enabled and log backups every 60 minutes. There are no Veeam services on the Guest at all.

EDIT: running Veeam v9

[foggy]

And do you see the logs being processed in the job stats?

[DeaconZ]

Yes. Here is one from a SQL node in our SharePoint farm.

Code: Select all

1/27/2016 10:16:14 AM :: Performing SQL Server transaction log backup for WSS_Content; User Profile Service Application_SocialDB_c709fb00cc8d46bd92ae55e8fb961990; UPSA Social DB; UPSA Sync DB; UPSA Profile DB; TranslationService_98689d98e5ec41d2b32b6a891faf487e; StateService_90e666d5d2664f82b76aaff676a7682d; User Profile Service Application_ProfileDB_fb005471265141dfb136ec9cbcab0bb3; SP15_Content_fin_corp2016; SP15_Content_MySites; SharePoint_Config; and 18 other databases

EDIT: scratch that, it failed witha message about an agent not reachable. How do I install this agent?

[veremin]

Is the SQL VM reachable from the backup server and the account used has required permissions? Thanks.

[DeaconZ]

It was Windows permissions. Thanks.

[veremin]

Glad to hear that you've resolved the issue. Should other help be needed, don't hesitate to let us know. Thanks.

[lightsout]

All,

So with Veeam v9 (and with v8 too), when I do SQL transaction log backups, it puts the files into c:\programdata\veeam\blah\blah on the local machine during the backup process.

The problem is, I've got some huge transaction log backups, so I'll need to expand C: as a one time deal to get the transaction logs shrank. Once the logs are shrunk, this won't be a problem though. There are other drives on the same server, which already have the necessary space.

Is there anyway to redirect the SQL transaction logs to a different local location somehow?

[foggy]

Please see above for details on how to do that.

[stuladhar]

I Manually Altered the registry [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\VeeaM\Veeam Backup and Replication] .. Here is the screen shot

http://i1305.photobucket.com/albums/s54 ... q2nmf1.jpg

This is done on VM SQL server ... then restart the server after registry update.... this should redirect logbackup L drive rather than C .....

[ober72]

Hi

We are getting an error when running an SQL backup of transaction logs. There is not enough space in the C:\ProgramData\Veeam\Backup\SqlLogBackup\.....bak
This is the temp location where the logs are shipped from to the veeam backup repository.
Can this location be changed somewhere as we can't get more space on the C drive?

Thanks

[foggy]

Geoff, there's a registry value for that, please review this thread for details.

[frankwijers]

Hi,
I'm running into a small issue. We are using a backup proxy to offload SQL log backups. I found that these backups have problems, due to disk space limitations. On the backup proxy, I see everything is being written to C:\Windows\Temp, but I want to redirect it to E:\Temp. Can anybody tell me how I can achieve that?

Thanks.