Catalog backups fail after NBU 7.1 migration

Created: 12 Jul 2012 | Updated: 12 Jul 2012 | 5 comments

Glen Newton

This issue has been solved. See solution.

Server 2003 R2

NetBackup 7.1 (*base installation. No hotfix/EEB applied)

Heya,

following a migration of NBU 7.1 to new hardware we are experiencing failed Catalog backups. Prior to the migration, the Catalog backups worked flawlessly. On the new server, with exception to the Catalog backups, all policies backup and complete successfully. Any assistance is appreciated. The errors are as follows.

--------------------------------------------------------------------------------------------

7/12/2012 12:22:39 PM - Info nbjm(pid=1480) starting backup job (jobid=230) for client evamanager, policy CatalogHotBackup, schedule Full
7/12/2012 12:22:39 PM - Info nbjm(pid=1480) requesting CATALOG_BACKUP_RESOURCE resources from RB for backup job (jobid=230, request id:{ABE69B8D-D8AF-4CAA-842B-278C6E125C93})
7/12/2012 12:22:39 PM - requesting resource evamanager.NBU_CATALOG.MAXJOBS
7/12/2012 12:22:39 PM - granted resource evamanager.NBU_CATALOG.MAXJOBS
7/12/2012 12:22:39 PM - estimated 9349879 Kbytes needed
7/12/2012 12:22:39 PM - begin Parent Job
7/12/2012 12:22:39 PM - begin Catalog Backup, Start Notify Script
7/12/2012 12:22:40 PM - Info RUNCMD(pid=5800) started
7/12/2012 12:22:40 PM - Info RUNCMD(pid=5800) exiting with status: 0
Status 0
7/12/2012 12:22:40 PM - end Catalog Backup, Start Notify Script; elapsed time: 00:00:01
7/12/2012 12:22:40 PM - begin Catalog Backup, DBM Query
Status 2
7/12/2012 12:24:21 PM - end Catalog Backup, DBM Query; elapsed time: 00:01:41
7/12/2012 12:24:21 PM - begin Catalog Backup, Stop On Error
Status 0
7/12/2012 12:24:21 PM - end Catalog Backup, Stop On Error; elapsed time: 00:00:00
7/12/2012 12:24:21 PM - begin Catalog Backup, End Notify Script
7/12/2012 12:24:22 PM - Info RUNCMD(pid=4376) started
7/12/2012 12:24:22 PM - Info RUNCMD(pid=4376) exiting with status: 0
Status 0
7/12/2012 12:24:22 PM - end Catalog Backup, End Notify Script; elapsed time: 00:00:01
Status 2
7/12/2012 12:24:22 PM - end Parent Job; elapsed time: 00:01:43
none of the requested files were backed up(2)

--------------------------------------------------------------------------------------------------------------------

7/12/2012 10:07:04 AM - Info nbjm(pid=1480) starting backup job (jobid=229) for client evamanager, policy CatalogHotBackup, schedule Full
7/12/2012 10:07:04 AM - Info nbjm(pid=1480) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=229, request id:{125E3491-B175-4DA5-B745-2E3CDA1851CF})
7/12/2012 10:07:04 AM - requesting resource evamanager-hcart3-robot-tld-0
7/12/2012 10:07:04 AM - requesting resource evamanager.NBU_CLIENT.MAXJOBS.evamanager
7/12/2012 10:07:04 AM - requesting resource evamanager.NBU_POLICY.MAXJOBS.CatalogHotBackup
7/12/2012 10:07:04 AM - granted resource evamanager.NBU_CLIENT.MAXJOBS.evamanager
7/12/2012 10:07:04 AM - granted resource evamanager.NBU_POLICY.MAXJOBS.CatalogHotBackup
7/12/2012 10:07:04 AM - granted resource 000058
7/12/2012 10:07:04 AM - granted resource HP.ULTRIUM3-SCSI.000
7/12/2012 10:07:04 AM - granted resource evamanager-hcart3-robot-tld-0
7/12/2012 10:07:05 AM - Info bpbrm(pid=620) evamanager is the host to backup data from
7/12/2012 10:07:05 AM - Info bpbrm(pid=620) reading file list from client
7/12/2012 10:07:05 AM - Info bpbrm(pid=620) listening for client connection
7/12/2012 10:07:05 AM - Info bpbrm(pid=620) INF - Client read timeout = 300
7/12/2012 10:07:05 AM - estimated 0 Kbytes needed
7/12/2012 10:07:05 AM - Info nbjm(pid=1480) started backup job for client evamanager, policy CatalogHotBackup, schedule Full on storage unit evamanager-hcart3-robot-tld-0
7/12/2012 10:07:05 AM - started process bpbrm (620)
7/12/2012 10:07:05 AM - connecting
7/12/2012 10:07:06 AM - Info bpbrm(pid=620) accepted connection from client
7/12/2012 10:07:06 AM - Info bpbrm(pid=620) start bpbkar on client
7/12/2012 10:07:06 AM - connected; connect time: 00:00:01
7/12/2012 10:07:08 AM - Info bphdb(pid=5628) Backup started
7/12/2012 10:07:08 AM - Info bphdb(pid=5248) Backup started
7/12/2012 10:07:09 AM - Info bptm(pid=1400) start
7/12/2012 10:07:09 AM - Info bptm(pid=1400) using 65536 data buffer size
7/12/2012 10:07:09 AM - Info bptm(pid=1400) setting receive network buffer to 263168 bytes
7/12/2012 10:07:09 AM - Info bptm(pid=1400) using 256 data buffers
7/12/2012 10:07:09 AM - Info bptm(pid=1400) start backup
7/12/2012 10:07:09 AM - Info bptm(pid=1400) Waiting for mount of media id 000058 (copy 1) on server evamanager.
7/12/2012 10:07:09 AM - mounting 000058
7/12/2012 10:07:45 AM - Info bptm(pid=1400) media id 000058 mounted on drive index 0, drivepath {3,0,0,1}, drivename HP.ULTRIUM3-SCSI.000, copy 1
7/12/2012 10:07:45 AM - mounted; mount time: 00:00:36
7/12/2012 10:07:48 AM - positioning 000058 to file 19
7/12/2012 10:08:23 AM - positioned 000058; position time: 00:00:35
7/12/2012 10:08:23 AM - begin writing
7/12/2012 10:08:27 AM - Info bphdb(pid=5248) bpbkar waited 1 times for empty buffer, delayed 1 times.
7/12/2012 10:08:27 AM - Info bphdb(pid=5248) done. status: 0
7/12/2012 10:08:27 AM - Info bptm(pid=1400) waited for full buffer 0 times, delayed 0 times
7/12/2012 10:08:34 AM - Info bptm(pid=1400) EXITING with status 0 <----------
7/12/2012 10:08:34 AM - Info bpbrm(pid=620) validating image for client evamanager
7/12/2012 10:08:34 AM - end writing; write time: 00:00:11
the requested operation was successfully completed(0)
7/12/2012 10:08:39 AM - Info bphdb(pid=5248) done. status: 0: the requested operation was successfully completed

----------------------------------------------------------------------------------------------------------------

7/12/2012 12:22:40 PM - Info bpdbm(pid=944) staging relational database files for catalog backup
7/12/2012 12:22:40 PM - Info bpdbm(pid=944) staging BMRDB backup to D:\Veritas\NetBackupDB\staging
7/12/2012 12:22:42 PM - Info bpdbm(pid=944) done staging BMRDB backup to D:\Veritas\NetBackupDB\staging
7/12/2012 12:22:43 PM - Info bpdbm(pid=944) done staging NBAZDB backup to D:\Veritas\NetBackupDB\staging
7/12/2012 12:22:43 PM - Info bpdbm(pid=944) staging NBDB backup to D:\Veritas\NetBackupDB\staging
7/12/2012 12:22:48 PM - Info bpdbm(pid=944) done staging NBDB backup to D:\Veritas\NetBackupDB\staging
none of the requested files were backed up(2)

------------------------------------------------------------------------------------------------------------------

7/12/2012 12:22:51 PM - Info nbjm(pid=1480) starting backup job (jobid=232) for client evamanager, policy CatalogHotBackup, schedule Full
7/12/2012 12:22:51 PM - Info nbjm(pid=1480) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=232, request id:{47E7FCE6-A2B1-485E-8685-A7FEB2462862})
7/12/2012 12:22:51 PM - requesting resource evamanager-hcart3-robot-tld-0
7/12/2012 12:22:51 PM - requesting resource evamanager.NBU_CLIENT.MAXJOBS.evamanager
7/12/2012 12:22:51 PM - requesting resource evamanager.NBU_POLICY.MAXJOBS.CatalogHotBackup
7/12/2012 12:22:51 PM - granted resource evamanager.NBU_CLIENT.MAXJOBS.evamanager
7/12/2012 12:22:51 PM - granted resource evamanager.NBU_POLICY.MAXJOBS.CatalogHotBackup
7/12/2012 12:22:51 PM - granted resource 000058
7/12/2012 12:22:51 PM - granted resource HP.ULTRIUM3-SCSI.000
7/12/2012 12:22:51 PM - granted resource evamanager-hcart3-robot-tld-0
7/12/2012 12:22:52 PM - Info bpbrm(pid=6112) evamanager is the host to backup data from
7/12/2012 12:22:52 PM - Info bpbrm(pid=6112) reading file list from client
7/12/2012 12:22:52 PM - Info bpbrm(pid=6112) listening for client connection
7/12/2012 12:22:52 PM - Info bpbrm(pid=6112) INF - Client read timeout = 300
7/12/2012 12:22:52 PM - estimated 0 Kbytes needed
7/12/2012 12:22:52 PM - Info nbjm(pid=1480) started backup job for client evamanager, policy CatalogHotBackup, schedule Full on storage unit evamanager-hcart3-robot-tld-0
7/12/2012 12:22:52 PM - started process bpbrm (6112)
7/12/2012 12:22:52 PM - connecting
7/12/2012 12:22:53 PM - Info bpbrm(pid=6112) accepted connection from client
7/12/2012 12:22:53 PM - Info bpbrm(pid=6112) start bpbkar on client
7/12/2012 12:22:53 PM - connected; connect time: 00:00:01
7/12/2012 12:22:56 PM - Info bphdb(pid=1696) Backup started
7/12/2012 12:22:56 PM - Info bphdb(pid=944) Backup started
7/12/2012 12:22:56 PM - Info bptm(pid=1372) start
7/12/2012 12:22:57 PM - Info bptm(pid=1372) using 65536 data buffer size
7/12/2012 12:22:57 PM - Info bptm(pid=1372) setting receive network buffer to 263168 bytes
7/12/2012 12:22:57 PM - Info bptm(pid=1372) using 256 data buffers
7/12/2012 12:22:57 PM - Info bptm(pid=1372) start backup
7/12/2012 12:22:57 PM - Info bptm(pid=1372) Waiting for mount of media id 000058 (copy 1) on server evamanager.
7/12/2012 12:22:57 PM - mounting 000058
7/12/2012 12:23:31 PM - Info bptm(pid=1372) media id 000058 mounted on drive index 0, drivepath {3,0,0,1}, drivename HP.ULTRIUM3-SCSI.000, copy 1
7/12/2012 12:23:31 PM - mounted; mount time: 00:00:34
7/12/2012 12:23:34 PM - positioning 000058 to file 20
7/12/2012 12:24:09 PM - positioned 000058; position time: 00:00:35
7/12/2012 12:24:09 PM - begin writing
7/12/2012 12:24:13 PM - Info bphdb(pid=944) bpbkar waited 1 times for empty buffer, delayed 1 times.
7/12/2012 12:24:13 PM - Info bphdb(pid=944) done. status: 0
7/12/2012 12:24:13 PM - Info bptm(pid=1372) waited for full buffer 1 times, delayed 29 times
7/12/2012 12:24:19 PM - Info bptm(pid=1372) EXITING with status 0 <----------
7/12/2012 12:24:19 PM - Info bpbrm(pid=6112) validating image for client evamanager
7/12/2012 12:24:20 PM - end writing; write time: 00:00:11
7/12/2012 12:24:25 PM - Info bphdb(pid=944) done. status: 0: the requested operation was successfully completed
the requested operation was successfully completed(0)

Discussion Filed Under:

Comments RSS Feed

Comments 5 Comments • Jump to latest comment

revaroo Symantec Employee

Catalog backups fail after NBU 7.1 migration - Comment:12 Jul 2012 : Link

Glen,

Have you tried deleting and recreating the catalog backup?

If for some reason that is not an option, I suggest increasing VERBOSE (logging) to maximum and creating the following log directories

Client (which is also the Master server:-

netbackup\logs\bpbkar

Media server (which could also be the master server or another media server depending on the storage unit in the policy), also with logging to maximum:-

netbackup\logs\bptm\

netbackup\logs\bpbrm\

SOLUTION

Glen Newton

Catalog backups fail after NBU 7.1 migration - Comment:12 Jul 2012 : Link

Thanks.

I created another Catalog Backup policy and ran it manually. The job failed again but this time with additional errors. So I then increased logging to maximum, rebooted the server and re-ran the Catalog backup policy. This time it succeeded, but I do not know if the logged details are to be expected. I pasted Detailed Status logs of both the initial failure and the following success runs of the policy. The logs from bpbkar, bpbrm and bptm are attached.

7/12/2012 2:42:15 PM - Info nbjm(pid=1480) starting backup job (jobid=237) for client evamanager, policy CatalogHotBackups, schedule Full
7/12/2012 2:42:15 PM - Info nbjm(pid=1480) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=237, request id:{F60A515A-25BF-4A8A-AA7D-D0D17F3E1FDD})
7/12/2012 2:42:15 PM - requesting resource Any
7/12/2012 2:42:15 PM - requesting resource evamanager.NBU_CLIENT.MAXJOBS.evamanager
7/12/2012 2:42:15 PM - requesting resource evamanager.NBU_POLICY.MAXJOBS.CatalogHotBackups
7/12/2012 2:42:15 PM - granted resource evamanager.NBU_CLIENT.MAXJOBS.evamanager
7/12/2012 2:42:15 PM - granted resource evamanager.NBU_POLICY.MAXJOBS.CatalogHotBackups
7/12/2012 2:42:15 PM - granted resource 000058
7/12/2012 2:42:15 PM - granted resource HP.ULTRIUM3-SCSI.000
7/12/2012 2:42:15 PM - granted resource evamanager-hcart3-robot-tld-0
7/12/2012 2:42:16 PM - Info bpbrm(pid=1204) evamanager is the host to backup data from
7/12/2012 2:42:16 PM - Info bpbrm(pid=1204) reading file list from client
7/12/2012 2:42:16 PM - Info bpbrm(pid=1204) listening for client connection
7/12/2012 2:42:16 PM - Info bpbrm(pid=1204) INF - Client read timeout = 300
7/12/2012 2:42:16 PM - estimated 0 Kbytes needed
7/12/2012 2:42:16 PM - Info nbjm(pid=1480) started backup job for client evamanager, policy CatalogHotBackups, schedule Full on storage unit evamanager-hcart3-robot-tld-0
7/12/2012 2:42:16 PM - started process bpbrm (1204)
7/12/2012 2:42:16 PM - connecting
7/12/2012 2:42:17 PM - Info bpbrm(pid=1204) accepted connection from client
7/12/2012 2:42:17 PM - Info bpbrm(pid=1204) start bpbkar on client
7/12/2012 2:42:17 PM - connected; connect time: 00:00:01
7/12/2012 2:42:20 PM - Info bphdb(pid=876) Backup started
7/12/2012 2:42:20 PM - Info bphdb(pid=976) Backup started
7/12/2012 2:42:20 PM - Info bptm(pid=1008) start
7/12/2012 2:42:20 PM - Info bptm(pid=1008) using 65536 data buffer size
7/12/2012 2:42:20 PM - Info bptm(pid=1008) setting receive network buffer to 263168 bytes
7/12/2012 2:42:20 PM - Info bptm(pid=1008) using 256 data buffers
7/12/2012 2:42:21 PM - Info bptm(pid=1008) start backup
7/12/2012 2:42:21 PM - Info bptm(pid=1008) Waiting for mount of media id 000058 (copy 1) on server evamanager.
7/12/2012 2:42:21 PM - mounting 000058
7/12/2012 2:42:50 PM - Error bptm(pid=1008) NBEMM returned an extended error status: SQL query returned client unable to establish connection (2007054)
7/12/2012 2:42:50 PM - Error bptm(pid=1008) error requesting media, TpErrno = Mount canceled, device daemon is terminating
client process aborted(50)

----------------------------------------------------------------------------------------------

7/12/2012 2:49:30 PM - Info nbjm(pid=168) starting backup job (jobid=241) for client evamanager, policy CatalogHotBackups, schedule Full
7/12/2012 2:49:30 PM - Info nbjm(pid=168) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=241, request id:{2BED3F2B-E19A-42CA-9D08-30E04143F7A4})
7/12/2012 2:49:30 PM - requesting resource Any
7/12/2012 2:49:30 PM - requesting resource evamanager.NBU_CLIENT.MAXJOBS.evamanager
7/12/2012 2:49:30 PM - requesting resource evamanager.NBU_POLICY.MAXJOBS.CatalogHotBackups
7/12/2012 2:49:30 PM - awaiting resource Any - No drives are available
7/12/2012 2:50:15 PM - Info bpbrm(pid=5972) evamanager is the host to backup data from
7/12/2012 2:50:15 PM - Info bpbrm(pid=5972) reading file list from client
7/12/2012 2:50:15 PM - granted resource evamanager.NBU_CLIENT.MAXJOBS.evamanager
7/12/2012 2:50:15 PM - granted resource evamanager.NBU_POLICY.MAXJOBS.CatalogHotBackups
7/12/2012 2:50:15 PM - granted resource 000058
7/12/2012 2:50:15 PM - granted resource HP.ULTRIUM3-SCSI.000
7/12/2012 2:50:15 PM - granted resource evamanager-hcart3-robot-tld-0
7/12/2012 2:50:15 PM - estimated 0 Kbytes needed
7/12/2012 2:50:15 PM - Info nbjm(pid=168) started backup job for client evamanager, policy CatalogHotBackups, schedule Full on storage unit evamanager-hcart3-robot-tld-0
7/12/2012 2:50:15 PM - started process bpbrm (5972)
7/12/2012 2:50:15 PM - connecting
7/12/2012 2:50:16 PM - Info bpbrm(pid=5972) starting bpbkar32 on client
7/12/2012 2:50:16 PM - connected; connect time: 00:00:01
7/12/2012 2:50:18 PM - Info bpbkar32(pid=6060) Backup started
7/12/2012 2:50:18 PM - Info bptm(pid=6028) start
7/12/2012 2:50:19 PM - Info bptm(pid=6028) using 65536 data buffer size
7/12/2012 2:50:19 PM - Info bptm(pid=6028) setting receive network buffer to 263168 bytes
7/12/2012 2:50:19 PM - Info bptm(pid=6028) using 256 data buffers
7/12/2012 2:50:19 PM - Info bptm(pid=6028) start backup
7/12/2012 2:50:19 PM - Info bptm(pid=6028) Waiting for mount of media id 000058 (copy 1) on server evamanager.
7/12/2012 2:50:19 PM - Warning bpbrm(pid=5972) from client evamanager: WRN - old TIR info file 'D:\Veritas\NetBackup\tir_info\DB\NetBackup_file_info.CatalogHotBackups' is missing. Backing up everything in 'root'
7/12/2012 2:50:19 PM - mounting 000058
7/12/2012 2:50:53 PM - Info bptm(pid=6028) media id 000058 mounted on drive index 0, drivepath {3,0,0,1}, drivename HP.ULTRIUM3-SCSI.000, copy 1
7/12/2012 2:50:53 PM - mounted; mount time: 00:00:34
7/12/2012 2:50:56 PM - positioning 000058 to file 23
7/12/2012 2:51:31 PM - positioned 000058; position time: 00:00:35
7/12/2012 2:51:31 PM - begin writing
7/12/2012 2:53:55 PM - Info bptm(pid=6028) waited for full buffer 1687 times, delayed 2217 times
7/12/2012 2:53:55 PM - Info bpbkar32(pid=6060) bpbkar waited 173 times for empty buffer, delayed 173 times.
7/12/2012 2:54:12 PM - Info bptm(pid=6028) EXITING with status 0 <----------
7/12/2012 2:54:12 PM - Info bpbrm(pid=5972) validating image for client evamanager
7/12/2012 2:54:13 PM - end writing; write time: 00:02:42
the requested operation was successfully completed(0)
7/12/2012 2:54:18 PM - Info bpbkar32(pid=6060) done. status: 0: the requested operation was successfully completed

Attachment	Size
Netbackup_logs.zip	54.35 KB

mph999 Symantec Employee

Catalog backups fail after NBU 7.1 migration - Comment:12 Jul 2012 : Link

Hey Glen,

Good work so far on the logs, it is such a change to see the issue descripbed correctly, and relevant logs supplied without asking.

bptm shows a clue ...

14:42:50.843 [1008.1252] <16> send_MDS_msg: Error from emmlib_handleMessage, Master evamanager, type 12, returned error 2007054

14:42:50.843 [1008.1252] <2> set_job_details: Tfile (237): LOG 1342129370 16 bptm 1008 NBEMM returned an extended error status: SQL query returned client unable to establish connection (2007054)

14:42:50.843 [1008.1252] <16> send_MDS_msg: NBEMM returned an extended error status: SQL query returned client unable to establish connection (2007054)

It is late here in the UK, so I have to go to bed ZZzzzz.... However, to help you some more, looks like we need another log or two sorry.

Now the difficult bit - I have no idea exactly what EMM is talking to at this point, but it talks to nbrb, which talks to nbjm, so we get these also, using PBX, so we'll add that in for fun. I would have to run a backup and trace through the logs to see what shoud happen - sorry, NBU is way to complex to remember all this - so we play a game of seek and find ...

vxlogcfg -a -p 51216 -o 111 -s DebugLevel=6 -s DiagnosticLevel=6

vxlogcfg -a -p 51216 -o 117 -s DebugLevel=6 -s DiagnosticLevel=6

vxlogcfg -a -p 51216 -o 118 -s DebugLevel=6 -s DiagnosticLevel=6

vxlogcfg -a -p 51216 -o 143 -s DebugLevel=6 -s DiagnosticLevel=6

vxlogcfg -a -p 51216 -o 156 -s DebugLevel=6 -s DiagnosticLevel=6

vxlogcfg -a -p 51216 -o 137 -s DebugLevel=6 -s DiagnosticLevel=6

This sets up EMM (111) and (MDS). The other 2 (156 /137) give network details.

It looks to be some type of comms issue - no idea why at this stage.

Rerun the job, allow it to fail.

We then would need the EMM/ JM/ RB log, but run it like this :

vxlogview -p 51216 -i 111 -d all -t 00:40:00 >emm.txt

vxlogview -p 51216 -i 117 -d all -t 00:40:00 >nbjm.txt

vxlogview -p 51216 -i 118 -d all -t 00:40:00 >nbrb.txt

vxlogview -p 50936 -i 103 -d all -t 00:40:00 >pbx.txt

The -i <oid> gives the details from the other logs, in these logs - if you follow ...

Don't think I've every run -i on pbx, so if it doesn't work, just use -o

Supply again the bptm / bpbrm log so that all the times match.

This could be real easy - if it's a known issue or something, but I can't get to the internal DB at the moment to check. It's odd, because apart from the staging bit, a catalog backup is only a normal backup really, which you say other backups work. That said, do your other backups work on differnet media servers perhaps ? - which is still odd, as it all uses EMM ...

It could also be real hard, just don't know - for that reason you may wish to log a call, but if you supply the above info + nbsu -c -t output you'll be miles ahead in terms or progress.

If you do log a call, please do report back here with progress.

Kindest regards,

Martin

Regards, Martin

Setting Logs in NetBackup:

http://www.symantec.com/docs/TECH75805

mph999 Symantec Employee

Catalog backups fail after NBU 7.1 migration - Comment:12 Jul 2012 : Link

Oh, turn logs down after -s DebugLevel=1 / diag =6 is default.

... just noticed it worked after the reboot, that could have been the fix, it just needed a restart. Sometimes it rains .... sometimes NBU needs a restart :o)

martin

Regards, Martin

Setting Logs in NetBackup:

http://www.symantec.com/docs/TECH75805

Glen Newton

Catalog backups fail after NBU 7.1 migration - Comment:12 Jul 2012 : Link

Heya,

I agree, the reboot more than likely fixed the issue. The SQL query comm failure was probably due to incorrect credentials and once the new Catalog backup policy was created with correct credentials it required the reboot. This is still odd though, unless a Catalog restore following the migration does not pass on the credentials of the original Catalog backup policy as the credentials had not changed from the original.

To answer your question of wether or not other policies were working on other Media servers, we are actually just running a single Master/Media server.

I was at odds for a bit there. Here I was ready to provide logs requested and I could not get the policy to fail...hehe. I guess all is good.

Thanks very much for your help and the reminder to turn logging down.

-Glen

Solution:

Recreated Catalog backup policy with a reboot.

Catalog backups fail after NBU 7.1 migration

Comments 5 Comments • Jump to latest comment

Would you like to reply?

Links