1. Tape jobs are running so long that they are being interrupted by backup jobs starting which then causes the corresponding backup to tape job to fail. Is the job able to recover from this or does it have to start from scratch again. If it fails do I have to return the tapes it used to the free pool? How can I avoid this? Do I need to set a window? Shouldn't the Veeam backup pause if a tape job is using it?
2. It isn't clear to me how I should protect my backup jobs when those are run in Incremental forever mode. Would I run a full backup initially and hold those tapes until a restore is needed and then only make incremental to tape jobs?
Should I have a media pool that corresponds for each backup job or should have media pools related to the type of media? The media pool usage is kind of tripping me up.
Is there some location that lists the variables (and examples) one can use when auto naming media sets such as %date%?
5. Veeam One has me stumped. I cannot for the life of me figure out how to get a simple clean report of all tapes used over the last 7 days (very important for audits!).
6. Again, if a tape fails is Veeam able to recover from that job, or should the tapes be recycled to the free media pool for another try?
7. Do we need to schedule cleaning jobs?
This shouldn't be the case. If a tape job is running, the source of that job should not be able to interrupt or fail it until it is finished. That should at least be an option.
So each time we run a tape job it creates a synthesized full first and then any incrementals? I guess that makes sense, but how does that work with the "After this job" and "As new backup files appear" options under schedule? I assume it doesn't do this every time with those.
So do I need to create two tape jobs associated with two media pools (F and INCR) for each VM backup job I want to protect? This seems laborious.
Still looking for a variable list that I can use in the media set creation. I'd like each tape to be called for example "Exchange 010815 Tape 1" (In this case the variables would be VM Job Name, Date of Tape Backup, Tape Sequence Number).
Should I be ignoring incrementals and only shooting Fulls to tape each week?
2. Should I rotate the Fulls that I send to tape per job so that I'm not trying to do all the job Fulls each week? … If I do the above, will those Fulls still be valid for restore after a few weeks?
d.popov wrote:It seems the only variable we have is %date% and it applies only to the name of the media set. So I count it as a good feature request.
I only want to be shipping one copy per week of a full for each job using the latest data available. What am I doing wrong?
WHAT A DIFFERENCE. Don't underestimate your data throughput needs when moving to Veeam. Previously we were only backing up Data and not entire configurations. Now as we are backing up the entire VM, we are protecting WAY more data. Our old 50MB/s cap caused by using a Dell iSCSI to SAS bridge wasn't going to work. With the Dell HBA card, we are getting ~110MB/s which is awesome. I just shot a job to tape and was super fast. I also disabled the tape compression as suggested in the job dialog box.
For some reason it was not able to eject a tape.
1. Pick the server instances you want to report on. (backup job, individual VMs, VMWare Group Folders)
2. Pick the type of job(s) you want to report on. (Backup, Tape, Copy)
3. Pick the events associated with those jobs (success, failure, success with error, etc)
4. Pick the format you would like (PDF, Excel, Word, HTML)
5. Pick who/where it should be sent if scheduled (Email, File Share, etc)
Veeam one has some of that, but it much more limited.
Some reports have the right options but are hard coded to the wrong details, etc. I'm sorry to say also that most of the reports to my eye are not laid out in a logical fashion.
Users browsing this forum: Yahoo [Bot] and 1 guest