Different Lengths of Time to Backup Same Data on Same Configuration
Same Job, Same Configuration, Same Media and Same load on the server and the network bandwidth. BUT the time to finish a 44 GB backup can vary anything between 7 to 14 hours on different days. The change to data is less than 1 GB if anything. Assuming this is anything to do with the network- Does the backup speed remains constant at the speed it started at during a job ? (i.e if the network becomes quiet after an hour does it not pick up that speed) Assuming this is anything to do with hardware load on the server- Shouldn’t it pickup up speed when the system is quiet? On this particular server the job start at 1800 hrs when there is no load on this machine (its the ERP system & SQL db and everyone's gone home by then) I cannot seem to identify a reason that can justify a 100% increase in time it takes to finish an identical job. What else can cause this behaviour ? Has anyone else seen this? P/S For various reasons I need to do a full backup rather than an incremental one on this server. So that is not an option as a measure to save time.
Feature Request
First of all, I will not claim this to be my idea at all. It is a simple concept wich I would find extremely useful and others should too. I just thought that I should post it here to get some comments on it and possibly even a note from Veritas on a predicted date of inclusion. "Cross-linking selection lists" or "Referred backup selections" might be semi-good names for it. The general idea is this: - Create a selection list to take a full snapshot of your small-ish server. The job using this would also update IDR and probably also use some snapshot plugin. - Create a selection list containing only selections relevant for differential backups relative to the full snapshot. This is to allow the differentials to run without job being flagged as failed due to master databases and such not being compatible with incremental/differential backups. Now comes the piccle: Tell the software that the differentials in second job with second selection set is to be done in light of the first job and selection set. This is the part that is currently missing in Backup Exec (or atleast it is eluding me). Any other tips to set up easy to run, full system restore capable jobs with incremental/differential abilitys?
Unable to establish connection to the Media Server
Running IDR test on an XP SP2 workstation. Was backed up to the media server in preparation for Disaster Recovery without any problems. Media server is running Windows Server 2003. Restore of XP SP2 workstation stops with logon prompt for the media server. Every attempt to logon comes back with "Unable to establish connection to the Media Server" Veritas knowledgebase doc# 273066 gives the opposite details (problem restoring 2003 machine from an XP media server). Any clues?
How do you restore to an exchange Recovery Storage Group
I am trying to recover email to an exchange Recovery Storage Group. I have created the storage group in exchange, it is not mounted. When I perform the restore, it puts the file in the active storage group instead of the recovery storage group. How do I get it to restore to the Recovery Storage Group? I am using backup exec 10d with exchange 2003. The help on this function is very vague. Says something like choose the appropriate settings.
Adamm Mover Error
The following error occurs: Adamm Mover Error: Write Failure! Error = ERROR_IO_DEVICE Drive = "HP Ultrium 460 Drive" {EC968C4C-F2CB-49D2-B243-FEDC020D22DE} Media = "UTR-xx-TL1-THU1" {D081E5CD-F10C-49D2-9C50-E2CE9E9DB463} Read Mode: SingleBlock(0), ScsiPass(0) Write Mode: SingleBlock(1), ScsiPass(1) We are using Veritas 10.0, with all updates. Running on Windows 2003 with all updates. As tapeloader we use a HP StorageWorks SSL1016 tapeloader with a Ultrium 460 tape unit. A couple of days ago (10) the error was nowhere. Since the last 10 days I get this error everyday. We have an identical situation here, same loader software and server and there the error does not occur. Is it possible that the problem occurs because of the use of 2 backuptapes everyday? We use slot 1 and 2 for monday, slot 3 and 4, etc. Please help me. I can't find anything about it on the internet.
