Register a SA Forums Account here!
JOINING THE SA FORUMS WILL REMOVE THIS BIG AD, THE ANNOYING UNDERLINED ADS, AND STUPID INTERSTITIAL ADS!!!

You can: log in, read the tech support FAQ, or request your lost password. This dumb message (and those ads) will appear on every screen until you register! Get rid of this crap by registering your own SA Forums Account and joining roughly 150,000 Goons, for the one-time price of $9.95! We charge money because it costs us money per month for bills, and since we don't believe in showing ads to our users, we try to make the money back through forum registrations.
The Something Awful Forums > Discussion > Serious Hardware/Software Crap > Backup Thread 2: Test the restore procedure!
 
  • Post
  • Reply
HalloKitty
Sep 30, 2005

Adjust the bass and let the Alpine blast
I guess I can help with this, I'm responsible for backups of a shitload of data.
Pretty much exclusively Veeam. I use Macrium Reflect at home, though, it's just more suitable for home use.

HalloKitty fucked around with this message at 10:27 on Oct 7, 2018

* # ¿ Oct 6, 2018 18:05
  • Quote
Adbot
ADBOT LOVES YOU

# ¿ Apr 26, 2024 13:54
  • Quote
HalloKitty
Sep 30, 2005

Adjust the bass and let the Alpine blast

Panthrax posted:

Yeah, App aware processing is already turned off, but it's still screwing around with SQL.

Here's a log from SQL side:

code:
2019-01-25 01:21:32.37 spid87      I/O is frozen on database Applications. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
2019-01-25 01:21:32.37 spid92      I/O is frozen on database ArchivedCDRRECORD. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
2019-01-25 01:21:32.37 spid111     I/O is frozen on database aspnet-BVOSS2api. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
2019-01-25 01:21:32.37 spid112     I/O is frozen on database BulkData. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
2019-01-25 01:21:32.37 spid113     I/O is frozen on database CCMI_LERG. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
2019-01-25 01:21:32.37 spid114     I/O is frozen on database Costar. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
2019-01-25 01:21:32.37 spid115     I/O is frozen on database CovadServices. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
<snipped for brevity>
2019-01-25 01:21:32.56 spid87      I/O was resumed on database Applications. No user action is required.
2019-01-25 01:21:32.56 spid111     I/O was resumed on database aspnet-BVOSS2api. No user action is required.
2019-01-25 01:21:32.56 spid92      I/O was resumed on database ArchivedCDRRECORD. No user action is required.
2019-01-25 01:21:32.56 spid112     I/O was resumed on database BulkData. No user action is required.
<snipped for brevity>
2019-01-25 01:21:36.48 Backup      Database backed up. Database: db_manager_CLR, creation date(time): 2016/03/19(21:08:08), pages dumped: 345, first LSN: 39:989:1, last LSN: 39:992:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'{EBD1773B-7716-4568-959C-E47399BC0D26}10'}). This is an informational message only. No user action is required.
2019-01-25 01:21:36.48 Backup      Database backed up. Database: db_migrate, creation date(time): 2016/03/19(09:54:21), pages dumped: 229313, first LSN: 2053088:2521:1, last LSN: 2053088:2524:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'{EBD1773B-7716-4568-959C-E47399BC0D26}11'}). This is an informational message only. No user action is required.
2019-01-25 01:21:36.48 Backup      Database backed up. Database: db01, creation date(time): 2016/03/19(23:37:54), pages dumped: 311413, first LSN: 2316773:1402:169, last LSN: 2316773:1473:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'{EBD1773B-7716-4568-959C-E47399BC0D26}12'}). This is an informational message only. No user action is required.
2019-01-25 01:21:36.49 Backup      BACKUP DATABASE successfully processed 0 pages in 12.690 seconds (0.000 MB/sec).
2019-01-25 01:21:36.49 Backup      BACKUP DATABASE successfully processed 0 pages in 12.960 seconds (0.000 MB/sec).
2019-01-25 01:21:36.49 Backup      BACKUP DATABASE successfully processed 0 pages in 12.160 seconds (0.000 MB/sec).
<snipped for brevity>

There's a registry key that's utterly undocumented that allows you to entirely exclude an SQL instance, but I'm at home, and I have it noted down at work... I have no idea if it works with the agent, though... I know it works when VBR takes a VM backup. If I actually remember about this thread on Monday or whatever, I'll post it.

* # ¿ Jan 26, 2019 22:18
  • Quote
HalloKitty
Sep 30, 2005

Adjust the bass and let the Alpine blast

Panthrax posted:

Yeah, App aware processing is already turned off, but it's still screwing around with SQL.

Here's a log from SQL side:

code:
2019-01-25 01:21:32.37 spid87      I/O is frozen on database Applications. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
2019-01-25 01:21:32.37 spid92      I/O is frozen on database ArchivedCDRRECORD. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
2019-01-25 01:21:32.37 spid111     I/O is frozen on database aspnet-BVOSS2api. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
2019-01-25 01:21:32.37 spid112     I/O is frozen on database BulkData. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
2019-01-25 01:21:32.37 spid113     I/O is frozen on database CCMI_LERG. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
2019-01-25 01:21:32.37 spid114     I/O is frozen on database Costar. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
2019-01-25 01:21:32.37 spid115     I/O is frozen on database CovadServices. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
<snipped for brevity>
2019-01-25 01:21:32.56 spid87      I/O was resumed on database Applications. No user action is required.
2019-01-25 01:21:32.56 spid111     I/O was resumed on database aspnet-BVOSS2api. No user action is required.
2019-01-25 01:21:32.56 spid92      I/O was resumed on database ArchivedCDRRECORD. No user action is required.
2019-01-25 01:21:32.56 spid112     I/O was resumed on database BulkData. No user action is required.
<snipped for brevity>
2019-01-25 01:21:36.48 Backup      Database backed up. Database: db_manager_CLR, creation date(time): 2016/03/19(21:08:08), pages dumped: 345, first LSN: 39:989:1, last LSN: 39:992:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'{EBD1773B-7716-4568-959C-E47399BC0D26}10'}). This is an informational message only. No user action is required.
2019-01-25 01:21:36.48 Backup      Database backed up. Database: db_migrate, creation date(time): 2016/03/19(09:54:21), pages dumped: 229313, first LSN: 2053088:2521:1, last LSN: 2053088:2524:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'{EBD1773B-7716-4568-959C-E47399BC0D26}11'}). This is an informational message only. No user action is required.
2019-01-25 01:21:36.48 Backup      Database backed up. Database: db01, creation date(time): 2016/03/19(23:37:54), pages dumped: 311413, first LSN: 2316773:1402:169, last LSN: 2316773:1473:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'{EBD1773B-7716-4568-959C-E47399BC0D26}12'}). This is an informational message only. No user action is required.
2019-01-25 01:21:36.49 Backup      BACKUP DATABASE successfully processed 0 pages in 12.690 seconds (0.000 MB/sec).
2019-01-25 01:21:36.49 Backup      BACKUP DATABASE successfully processed 0 pages in 12.960 seconds (0.000 MB/sec).
2019-01-25 01:21:36.49 Backup      BACKUP DATABASE successfully processed 0 pages in 12.160 seconds (0.000 MB/sec).
<snipped for brevity>

Right, I actually did remember to reply with something useful.

Assuming we are talking about VBR backups (again, it might work with an agent, but I haven't tried), you need to create a registry key on the server to be backed up:

HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication
ExcludeSQLInstances

As a Multi-String Value

Then simply write the exact name of every SQL instance you want to exclude, each on a newline inside the multi-string value. Hope this helps.

* # ¿ Jan 28, 2019 20:31
  • Quote
HalloKitty
Sep 30, 2005

Adjust the bass and let the Alpine blast

Combat Pretzel posted:

Someone tell me about Veeam and SQL Server.

Up until recently, using SQL Server Management Studio, we could restore any scheduled backups of our databases just fine ourselves with whatever solution the IT department used. But they switched to Veeam now (more like let a third party talk them into it and offer maintenance). When I trigger backups manually (which also seems to trigger Veeam, considering where they'll be stored), I still can restore them just fine. But Veeam's scheduled backups not so much. SQL Server Management Studio lists all scheduled backups Veeam has done, but verifying backup media and/or attempting to restore just fails. IT doesn't want to give us access to Veeam itself, either.

I guess this are how things are gonna be? On the off chance there's some database drama, write some stupid ticket and hope they react timely?

The restore needs to be done through Veeam, because it backs up and truncates the logs. If you're running SQL in full recovery model, then Veeam also can be configured to back up and truncate the logs on a regular interval.

Yeah, that's how things are going to be, you need their help to get things done. I've got a customer that wants to do everything themselves, using only standard SQL backups that they have access to. They run regular backups, and we simply backup the backup files in Veeam. It's ridiculously space inefficient as the bak files are already compressed, but it means no backup admins need to be around to help the SQL admins when the excrement impacts the impeller.

That said, plenty of other customers I work with rely on us to restore their databases and yeah, just have to write a ticket or call to get things done.

There are some self-service possibilities in Veeam, licencing dependant there's even a web portal that can be used, but I imagine the IT department wants to keep people away from the backup as much as possible.

* # ¿ Nov 5, 2022 20:09
  • Quote
HalloKitty
Sep 30, 2005

Adjust the bass and let the Alpine blast

YarPirate posted:

IIRC veeam agent is still free if not managed by backup and replication server

Vbr is free up to 10 instances too, so you can install it on a server, and deploy backup agents for all your machines from it

* # ¿ Jan 24, 2024 09:43
  • Quote
  • 1
  • 2
  • 3
  • 4
  • 5
  • Post
  • Reply
The Something Awful Forums > Discussion > Serious Hardware/Software Crap > Backup Thread 2: Test the restore procedure!