Quantcast
Channel: Symantec Connect - Backup and Recovery
Viewing all 8144 articles
Browse latest View live

Need to import catalog into different master server

$
0
0
ソリューションが必要です

Hi,

I have two linux master servers. Both are running 7.1. I want to merge the catalog of one master into another one so that I can browse the catalog in secondary master. What are the steps I need to follow for this. Both are different master servers in different networks with different hostnames and IPs. Without renaming or changing the IPs of my secondary master, can I merge or move the catalog from 1st server to 2nd


Backup Exec

$
0
0
ソリューションが必要です

Hi all,

I am kindly new with Symantec Backup Exec. I am interested in licensing. First does Symantec Backup Exec server software cost? Second I have 3 physical and 6 virtual servers that I need to backup. I understand that I need 3 Agent for Windows. On two physical servers I have 6 virtual server total. One physical servers is standalone. Does it mean that I need to buy 6 Agent for VMware and Hyper-V?

Does Symantec Backup Exec software must to be instaled on standalone server or not?

Thank you for all information.

Restore System State

$
0
0
ソリューションが必要です

Good morning,

I am running into an issue with an SBS 2003 box, where I cannot restore the System State. It is SBS 2003, with all of the latest patches with BE 2012 Build 1798.

Notes:

- Single server envronment

- I have been running successful backups to an ISCSI NAS connected as a local Drive. We do not have a SDR.

- Recently the domain has become corrupted on the server. I can boot the server, but it thinks it has a different computer name, we will call that name "Confused".

- The ISCSI services are failing as well, where I cannot connect to the NAS from the server. I can successfully connect and access the backup files on another workstation, and share the files.

- All other data is intact. I only need System State.

Tasks completed:

- Create new storage device, and point it to the share on the workstation \\path\veritas\b2d. Inventory is successful, Catalogs fails with errors that the media is not in the index, even after a successful inventory. The backup sets do populate and I can run a catalog on the individual sets.

- On the Backup\Restore tab "Servers" I have two servers listed, the correct server name, and the "Confused" server name, both of which are the same server.

- If I try to run a System state restore from the "correct" server name, I am prompted for storage to restore From, but I only have the Device that is offline, not the new device. (That is pointing to the new drive share with all of the backup files). If I try from the "Confused" server name, the restore options are blank and I cannot proceed.

- I have added a local admin account to backup exec and started all services with that account. That account also has full access to the share I created and I can access the data from Windows with that login account.

Questions:

- How do I get the "Correct" server in Backup and Restore tab to see the new data store so I can access the backups?

- How can I get "Confused""Backup and Restore" server to be able to restore (Blank page)?

Best Practice for Backing Up SQL 2012 Full Models

$
0
0
ソリューションが必要です

My Backup is 2008 R2 running BE 2012.

My MS SQL is 2012 R2 running SQL 2012.

I have both simple and full model DBs.

I have two main jobs: One for Full DBs and one for Simple DBs.

Backing up the simple BDs is pretty right forward.

Just one Full backup job.

Then a Duplicate to tape job.

The full model DBs is where it get vague.

I have 8 Full model DBs and three of them generate a large amount of T-Logs.

So what is the best practice to keep the T-Logs from growing to large?

Right now I have a daily Full (at 8pm) which is then dupicated to tape.

A single daily Log Incremental (at 11pm) No dupicate to tape.

Questions:

Should I add a differental and where should it go in the schedule?

I have one BDs that need to be backed up every four hours between 6am and 6pm.

Backups were failing with 84 & 87 error intermittently - Destination Storage is Pure Disk Pool

$
0
0
ソリューションが必要です

Backups were failing with 84 & 87 error intermittently - Destination Storage is Pure Disk Pool 

Again the same backup is getting suuccessful in the next successive using different job ID

Error Code: 84

***************************************************************************************************************************************
12/25/2014 00:10:07 - Info bpbrm (pid=13539) INF - Client read timeout = 1800
12/25/2014 00:10:07 - connecting
12/25/2014 00:10:08 - Info bpbrm (pid=13539) accepted connection from client
12/25/2014 00:10:08 - Info dbclient (pid=4951) Backup started
12/25/2014 00:10:08 - Info bpbrm (pid=13539) bptm pid: 13540
12/25/2014 00:10:08 - Info bptm (pid=13540) start
12/25/2014 00:10:08 - Info bptm (pid=13540) using 524288 data buffer size
12/25/2014 00:10:08 - Info bptm (pid=13540) setting receive network buffer to 524288 bytes
12/25/2014 00:10:08 - Info bptm (pid=13540) using 256 data buffers
12/25/2014 00:10:08 - connected; connect time: 0:00:00
12/25/2014 00:10:10 - Info bptm (pid=13540) start backup
12/25/2014 00:12:17 - Info bptm (pid=13540) backup child process is pid 16293
12/25/2014 00:12:17 - begin writing
12/25/2014 00:12:18 - Info dbclient (pid=4951) dbclient(pid=4951) wrote first buffer(size=262144)
12/25/2014 00:13:02 - Critical bptm (pid=13540) Storage Server Error: (Storage server: PureDisk:) mtstrm_write_segment: Fatal error occured in Multi-Threaded Agent: Cr_ErrnoException in void mtstrm::server::Cr_Send::ThreadSend(Pd_Thread<mtstrm::server::Cr_Send>*): CRSegmentBatchStreamPutComp V-454-95
12/25/2014 00:13:02 - Critical bptm (pid=13540) image write failed: error 2060001: one or more invalid arguments
12/25/2014 00:13:04 - Critical bptm (pid=13540) Storage Server Error: (Storage server: PureDisk:) mtstrm_close_write_channel: Fatal error occured in Multi-Threaded Agent: Cr_ErrnoException in void mtstrm::server::Cr_Send::ThreadSend(Pd_Thread<mtstrm::server::Cr_Send>*): CRSegmentBatchStreamPutComp V-454-96
12/25/2014 00:13:04 - Critical bptm (pid=13540) sts_close_handle failed: 2060001 one or more invalid arguments
12/25/2014 00:13:16 - Error bptm (pid=13540) cannot write image to disk, Invalid argument
12/25/2014 00:13:16 - Info bptm (pid=13540) EXITING with status 84 <----------
12/25/2014 00:13:16 - Info dbclient (pid=4951) done. status: 6
12/25/2014 00:13:16 - Info (pid=13540) StorageServer=PureDisk:; Report=PDDO Stats (multi-threaded stream used) for (): scanned: 49667 KB, CR sent: 0 KB, CR sent over FC: 0 KB, dedup: 100.0%, cache disabled
12/25/2014 00:13:17 - Info dbclient (pid=4951) done. status: 84: media write error
12/25/2014 00:13:17 - end writing; write time: 0:01:00
media write error  (84)

***************************************************************************************************************************************

Error Code: 87

***************************************************************************************************************************************

12/25/2014 00:12:23 - Info bpbrm (pid=7499) INF - Client read timeout = 1800
12/25/2014 00:12:23 - Info bpbrm (pid=7499) accepted connection from client
12/25/2014 00:12:24 - Info dbclient (pid=736) Backup started
12/25/2014 00:12:24 - connected; connect time: 0:00:00
12/25/2014 00:12:24 - Info bpbrm (pid=7499) bptm pid: 7500
12/25/2014 00:12:24 - Info bptm (pid=7500) start
12/25/2014 00:12:24 - Info bptm (pid=7500) using 524288 data buffer size
12/25/2014 00:12:24 - Info bptm (pid=7500) using 256 data buffers
12/25/2014 00:12:26 - Info bptm (pid=7500) start backup
12/25/2014 00:17:02 - Info bptm (pid=7500) backup child process is pid 17130
12/25/2014 00:17:02 - begin writing
12/25/2014 00:17:03 - Info dbclient (pid=736) dbclient(pid=736) wrote first buffer(size=65536)
12/25/2014 00:17:04 - Info dbclient (pid=736) done. status: 0
12/25/2014 00:18:56 - Info bptm (pid=7500) waited for full buffer 1 times, delayed 71 times
12/25/2014 00:18:59 - Critical bptm (pid=7500) Storage Server Error: (Storage server: PureDisk:) mtstrm_close_write_channel: Fatal error occured in Multi-Threaded Agent: Close Write Channel command failed: Cr_ErrnoException:  dref model has not been initialized yet V-454-96
12/25/2014 00:19:00 - Critical bptm (pid=7500) sts_close_handle failed: 2060017 system call failed
12/25/2014 00:19:00 - Error bptm (pid=7500) cannot write image to disk, media close failed with status 2060017 
12/25/2014 00:19:05 - Info bptm (pid=7500) EXITING with status 87 <----------
12/25/2014 00:19:05 - Info (pid=7500) StorageServer=PureDisk:; Report=PDDO Stats (multi-threaded stream used) for (): scanned: 4835 KB, CR sent: 0 KB, CR sent over FC: 0 KB, dedup: 100.0%, cache disabled
12/25/2014 00:20:13 - Info dbclient (pid=736) done. status: 87: media close error
12/25/2014 00:20:13 - end writing; write time: 0:03:11
media close error  (87)

***************************************************************************************************************************************
Also attached the error part in the bptm log from media server

Client Read & Connect timeout for the respective Media servers - 1800 sec

IS it due to any DPS/Timeout polling time out issue or any other issue ?

OPS center Report

$
0
0

Hi Team,

          Today  I got a chance to configure a report in OPS center, and i came to see that there is no option for creating a report which can run multiple times a day with a single schedule.

  We have Recurrence Tab in Schedule , but it just starts from Daily , weekly , Monthly, Yearly.    .   

Why cant we create it on Hourly basis also.  Customer who wishes to see their report for every 2 Hours (like archive backups) can use that.

Now i have created 12 schedules for every 2 hours each and mapped to a single report .  if that option is there we would have used it.

Exchange backup and LastFullBackup parameter

$
0
0
ソリューションが必要です

Hellow.

BackupExec 14.1 (1786)

Exchange 2013 CU6 (2 servers in DAG)

I have a problem, after backup job of 4 database (FullBackup), backupexec say me that all OK, but one database in Exchange remain LastFullBackup parameter very old, and log not truncate.

In WIndows event log i have 4 Event 2046, they log says that all DB is backedup and log mast be truncated:

The Microsoft Exchange Replication service VSS Writer instance 3751151a-8db4-469a-9203-c07117197567 has successfully completed the backup of database 'MbxDB03'. 

 Database log truncation has been requested for this database. Log truncation will occur on the active copy after the next log generation is created. Log truncation will occur automatically on the passive copies after that log file is copied.

Why one database MbxDB03 not be in backuped state ? Please help me resolve problem.

Need a report which can tell if backups actually finished after all retries.

$
0
0
ソリューションが必要です

Hi,

Trying to figure out if I can get details of all the jobs which actually became successful after multiple reties and the one which failed after all retries. There is a report for status rate but I need information about job details too.

Regards,


Backup Exec 2014 not expiring backup sets?

$
0
0
ソリューションが必要です

Hi peeps,

I wonder if anyone can help me out?  I'm using Backup Exec 2014 and ive set my backups to expire after 14 days, but I'm constantly having to manually clean up my drive.  The sets are blue and show as "Expired" but I have to manually "Expire" them to delete them, its not cleaning them up itself.  Then I have around 50 that just will not "Expire" at all so I cant get rid of those.

Can anyone tell me how I get the "Expired" sets to auto "Expire" without user input?  Also any ideas how I can delete the 50 odd that will not "Expire" at all?

Thanks

JK

Backup Exec 2010 R3 SP4 (Physical) / Exchange 2010 (Virtual)

$
0
0
ソリューションが必要です

This problem started after upgrading backup exec 2010 r3 sp3 to sp4. Every other day the backup of exchange mailbox failing with following error.

V-79-57344-759 - Unable to complete the operation for the selected resource using the specified options for the following reason: VFF Open Failure. This can be caused by low memory or disk resources.

No changes on exchange server. Was working fine for several years. Also, the memory and cpu usage on exchange server is normal

Need SRD ISO for SRR2013

$
0
0
ソリューションが必要です

I don't seem to be able to create an SRD from within SRR2013.  Another thread supposedly had a link to the SRD ISO, but it turns out to be a link for the SRR Server Trial.  Would appreciate a valid link or clarification on the file location to use if trying to create from within the application.

Regards, Dan

Migration backups from disk to tapes

$
0
0
ソリューションが必要です

Hello,

can someone explain me how can I move (migrate) already created backups from disk to tapes? 

I apologize beucase I am asking "simple" question but I am admin for one other B&R solution and I just received BE in scope because BE admin has vacation. And already have urgent problem...

That other solution which I am using, has disk storege pool for backups, from which data (backups) are automatically migrated to tapes, when disk stg utlization is more than 90%. There is also possibility to schedle migration D2T to execute when all backups are done.

Is there any similar solution? How can I implement it in BackupExec 2010?

Thank you very much on your time and help!
 

Error 130 in netbackup

$
0
0
ソリューションが必要です

Few netbackup client 6.5.6 , having 130 error's

Can any one please give me the resolution for this error's

Wrong tape used for Monthly Backup

$
0
0
ソリューションが必要です

Hi Guys,

Merry Christmas to everyone.

Need a little help with some mess from yesterday 25/12/2014

So we have 4 tapes labelled week 1 to week 4 and a Monthly tape. I was suppose to backup to Monthly tape yesterday 25/12/2014 and instead used tape labelled Week 2. 

I have looked up about relabelling which apparently does a quick erase before allowing to re-label which obviously isn't an option here. 

Here is the schedule and I want to know my options? 

Thursday to Tuesday Differential tape and Wednesday's any of the labelled tapes. 

I would be grateful if anyone could help.

P.S The tapes go out to third party backup specialists on weekly basis i.e. next week they will be expecting the tape labelled Monthlydd-yy and not Week-x.. 

Tool used for backup is BackupExec 2010

Thanks

DLM doesn't delete expired data

$
0
0
ソリューションが必要です

we use  Backup Exec 2014 for backup in our company. our dedup storage size 15 tb and in cas view show 9.78 tb used and rest of them free. but in windows explorer side there is only 770 gb free and still reduce this size. on the other hand backup sets shows lots of expired backup sets exist and no deleting for 3 months maybe later.

Also ı found some documents for manual reclaimin and test it 100-200 gb size deleted. 

please help us any idea is useful. 

thanks

Capture3.PNG

Capture2.PNG

Capture44.PNG


Backup exec management services could not be started

$
0
0
ソリューションが必要です

I am facing issue in Backup exec 2014. When i started backup exec console then it first ask for credentials and then gave an error "Backup exec management services could not be started. Backup exec database is offline, turn it online then restart backup exec services"

i re install the backup exec 2014 but still have the same issue.

Platform consist of Windows server 2008 R2 standard and also it consist of SQL 2008 which is running by client but Backup exec database use its built in database.

Media Freeze

$
0
0
ソリューションが必要です

Hello Experts,

Two media are frozen and i could see logs as it contains tar-format data and cannot be used for backups in netbackup.

I could see its size as 0 kilobites.

Pls let me know what can be done to reuse the tapes.

Thanks,

Windows backups take a lot longer when specifying ALL_LOCAL_DRIVES directive.

$
0
0
ソリューションが必要です

Hello,

I am running NBU 7.5.0.6, RH Linux Master and media servers.

we are migrating to Exchange 2010, and while we do plan on using the Exchange agent, currently I am simply trying to do an OS backup of the servers (we will be migrating to DAG env). So I added the new exchange servers to a regular Windows policy, with the ALL_LOCAL_DRIVES directive, and setup the appropriate excludes for Exchange (though exchange has yet to be installed), and it is taking over 2.5 hours to backup 14GB of data. If I explicitly list the local drives (5 in total), the backup takes less than 15 minutes.

From the bpbkar log, it appears the snapshots are taking almost exactly 30 minutes for each drive (sample output below)...

ALL_LOCAL_DRIVES:

9:48:38.118 AM: [41832.34124] <4> V_DetermineMountInfo: INF -   Adding NTFS Volume C:\ ==> \\?\Volume{b94e3504-45a4-11e4-9530-806e6f6e6963}\
9:48:38.118 AM: [41832.34124] <4> V_Snapshot::V_Snapshot_CreateSnapshot: INF - ======================================================================
9:48:38.118 AM: [41832.34124] <4> V_Snapshot::V_Snapshot_CreateSnapshot: INF - Attempting to create snapshots for 'C:'
9:48:38.118 AM: [41832.34124] <4> V_Snapshot::V_Snapshot_CreateSnapshot: INF - CREATE request: D:\VERITAS\NetBackup\bin\bpfis create -owner NBU -fso -WOFB -fim VSS -id mmxpcy701_1419432482 C:\
10:18:59.321 AM: [41832.34124] <4> V_Snapshot::V_Snapshot_ParseBpfisOutput: INF - Snapshot creation, FIS_ID: mmxpcy701_1419432482
10:18:59.321 AM: [41832.34124] <4> V_Snapshot::V_Snapshot_CreateSnapshot: INF - Snapshot creation was not successful
10:18:59.321 AM: [41832.34124] <4> V_Snapshot::V_Snapshot_CreateSnapshot: INF - ======================================================================
10:18:59.321 AM: [41832.34124] <2> tar_base::V_vTarMsgW: INF - Volume snapshots not enabled
10:18:59.321 AM: [41832.34124] <2> tar_base::V_vTarMsgW: JBD - change journal NOT enabled for <C:\>
10:18:59.368 AM: [41832.34124] <4> folder_access::V_OpenForRead: INF - obtained disk quota data: C:
10:18:59.383 AM: [41832.34124] <4> dos_backup::tfs_scannext: parent of <C:\$Recycle.Bin\S-1-5-21-1312041997-2487223646-369738992-1014\desktop.ini> has been forced, forcing backup

Specifying each drive....

10:45:19.735 AM: [11304.26688] <4> V_Snapshot::V_Snapshot_CreateSnapshot: INF - ======================================================================
10:45:19.735 AM: [11304.26688] <4> V_Snapshot::V_Snapshot_CreateSnapshot: INF - Attempting to create snapshots for 'C:'
10:45:19.735 AM: [11304.26688] <4> V_Snapshot::V_Snapshot_CreateSnapshot: INF - CREATE request: D:\VERITAS\NetBackup\bin\bpfis create -owner NBU -fso -WOFB -fim VSS -id mmxpcy701_1419608384 C:\
10:45:50.156 AM: [11304.26688] <4> V_Snapshot::V_Snapshot_AddMappings: INF - input parameters:
    source path:<C:\>
      snap path:<\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy37\>
     mount path:<(null)>
10:45:50.156 AM: [11304.26688] <4> V_Snapshot::V_GetSourceVolume: INF - input parameters:
      source:<C:\>
    snapshot:<\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy37\>
10:45:50.156 AM: [11304.26688] <4> V_Snapshot::V_Snapshot_AddMappings: INF - Volume Snapshot Mapping: \\?\Volume{b94e3504-45a4-11e4-9530-806e6f6e6963}\ --> GLOBALROOT\Device\HarddiskVolumeShadowCopy37
10:45:50.156 AM: [11304.26688] <4> V_Snapshot::V_Snapshot_ParseBpfisOutput: INF - Snapshot creation, FIS_ID: mmxpcy701_1419608384
10:45:50.156 AM: [11304.26688] <4> V_Snapshot::V_Snapshot_CreateSnapshot: INF - Snapshot creation was successful
10:45:50.156 AM: [11304.26688] <4> V_Snapshot::V_Snapshot_CreateSnapshot: INF - Snapshot provider: VSS
10:45:50.156 AM: [11304.26688] <4> V_Snapshot::V_Snapshot_CreateSnapshot: INF - ======================================================================
10:45:50.156 AM: [11304.26688] <2> tar_base::V_vTarMsgW: INF - Volume snapshots enabled
10:45:50.156 AM: [11304.26688] <2> tar_base::V_vTarMsgW: JBD - change journal NOT enabled for <C:\>

0xe000842 A memory allocation request failed.

$
0
0
ソリューションが必要です

Hello,

i recently did a fresh install of our Backup Exec Server, upgrading form 2012 SP4 to 2014.

I set up the jobs from scratch, installed the new agent on all servers, made a new Dedupe Storage, like i would start from the beginning.

Now i get this error message when i do a Backup to Dedupe:

0xe000842 A memory allocation request failed. The computer may be running low on virtual memory.

Insufficient memory available

I changed the location of the catalogs folder as described in this article: http://www.symantec.com/business/support/index?pag...

but it didn`t work out.

Backup to Disk works fine.

I tried it without the "Advanced Disk Based Backup" Option and this works so far.

How to release SSR 2013 License for reinstall

$
0
0
ソリューションが必要です

Hello,

I think I have just a quick question here. I have license for SSR 2013 which is installed and activated.

How can I release this license to reinstall on another PC? Basically I just want to move the installation to a different PC, still just one PC it will be installed on.

Does uninstalling via Control Panel communicate with the Symantec server to release the license or do I need to do something else?

Thanks much

Allen

Viewing all 8144 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>