Question

Locked

Backup-to-disk configuration question

By otaku_lord ·
OK, here is the setup:

Full backup to tape on weekends.
Differential backup to disk on weekdays.

I have been tasked with moving the backup-to-disk folders to a new server that has a lot more space on it than the current device.

I have created the folders on the new servers. I have gone into "Devices" and added the folders as Backup-To-Disk entries.

Each backup job is run to a device pool consisting of the native server and a remote server folder. I removed the original BTD folders from the remote server and added the newly created folders to the device pool for each job accordingly.

When I procede to the testrun, the jobs fail stating: "Warning: Unable to reasonably detect which device this job will run to. Different possible outcomes depending on which device this job runs to. Please target a specific device to avoid this conflict."

I have checked the settings on the original, remote drive folders and see nothing different in the properties of either set.

If anyone has any ideas, I would really appreciate the input.

This conversation is currently closed to new comments.

15 total posts (Page 1 of 2)   01 | 02   Next
| Thread display: Collapse - | Expand +

All Answers

Collapse -

Check the back up job properties

by netwrk_admn In reply to Backup-to-disk configurat ...

Have you gone into the specific job and changed it's device path? It's one thing to configure it on the application settings, but the back up job should have a place where it needs to know where to write (it could be tape, disk, etc).

Also which application are you using to back up? Would help for tech members to give you more specific answers.

Collapse -

To answer your question...

by otaku_lord In reply to Check the back up job pro ...

The drive path never changed. I only changed the devices in the pool. My assumption being that the job wouldn't care as long as the pool was the same.

Under DEVICE AND MEDIA:
Device: ADC1 <pool>
Media set:
Harddrive

The software I am using is Symantec Backup Exec 11.0 R. 7170...

Collapse -

I got the thumb,

by netwrk_admn In reply to To answer your question.. ...

But did I provide the right answer? I use Symantec 11D, and I've changed my BtD drive multiple times, can't recall an issue, maybe the services could use a restart?

Under the back up job properties - Destination (Device and Media subfolder) there's the value.

A good bet, is to delete the BtD altogether and create a new one with a new alias and re-point your back up jobs.

Good luck!

Collapse -

You got the thumb...

by otaku_lord In reply to I got the thumb,

because you gave me some avenues to consider which I had not yet... I consider that a good answer...

I posted the information under the Destination already. That doesn't change from job to job. The only thing that changes is the devices in the pool.

Collapse -

Symantec link

by netwrk_admn In reply to You got the thumb...

http://seer.entsupport.symantec.com/docs/263679.htm

It states:

---------------
Error Text in Job History:
"Warning: Unable to reasonably detect which device this job will run to. Different possible outcomes depending on which device this job runs to. Please target a specific device to avoid this conflict."

Reason: The backup job is configured to use a "Drive Pool," "Cascaded Drive Pool," or "All Drives."
Solution: In order for the Test Run to succeed, a specific backup device must be targeted in the backup job.
-------------------------

So for mine, I have selected not a device pool (are your back up servers linked?). I have my BtD folder set up one further section below under a stand-alone media server labelled <SERVERNAME> -> Backup-to-disk folders -> back up to disk folder 3 (i've changed mine a couple times and always created a new BtD folder). Hope that helps.

Collapse -

Test for tomorrow...

by otaku_lord In reply to Symantec link

I am leaving for the day as I am only PT currently. I will try this tomorrow and let you know how it goes...

Collapse -

And the status so far...

by otaku_lord In reply to I got the thumb,

I restarted the services after making the change I wanted. Then I ran a test run.

Here are the results...

Device : INC-ADC01Online append capacity : 0.000 MBOnline overwrite capacity: 7,275 MBTotal append capacity : 0.000 MBTotal overwrite capacity : 696,515 MBCapacity check status : SuccessDevice : ADC01Online append capacity : 0.000 MBOnline overwrite capacity: 0.000 MBTotal append capacity : 0.000 MBTotal overwrite capacity : 696,515 MBCapacity check status : FailedMiscellaneous : Warning: Unable to reasonably detect which device this job will run to. Different possible outcomes depending on which device this job runs to. Please target a specific device to avoid this conflict.

Collapse -

OK, getting discouraged...

by otaku_lord In reply to And the status so far...

I have a completely clean, remote server setup. I created a B2D folder and a job from scratch. The folder is located on this new server.

I ran the job and got the following error:

"Backup Diff - INCADC01 -- The job failed with the following error: This operation requires a backup-to-disk folder on a local NTFS volume on the media server. Check the job log for details."

Do I need to map the remote server's drive to "trick" the media server into thinking it is a local drive? Is there something I am missing?

Collapse -

Yeah try mapping the drive to the computer

by netwrk_admn In reply to OK, getting discouraged.. ...

Sorry you're still having such a hard time with this. I use all local drives for my set up, but Symantec 11D (I know you're on 11.0) documentation allows for remote storage. My set up is an iSCSI SAN that appears as a local drive.

But yeah, like the subject, try mapping it locally as whatever drive you choose and try to back up a small test file from the back up server's C:.

From Symantec:
Requirements for creating a backup-to-disk folder
■ NTFS partitions (local or remote)
■ DFS shares
■ FAT/FAT32 partitions (local or remote)
■ Veritas? Volume Manager partitions
■ RAID drives with any configuration
■ NFS volumes
■ Network Attached Storage (NAS) devices

Collapse -

Hmmmm...

by otaku_lord In reply to Yeah try mapping the driv ...

I will try that. I am also trying to get my IS Manager to allow me to just install Backup Exec on the remote server. That would eliminate the need for having to go through any of this... I will try the mapped drive approach though and see what happens.

Back to Networks Forum
15 total posts (Page 1 of 2)   01 | 02   Next

Related Discussions

Related Forums